DNS Propagation Checker
Check DNS record propagation across multiple global DNS resolvers. See which servers have propagated your changes.
| Resolver | Location | Status | Response Time | Result |
|---|
What is DNS Propagation?
DNS propagation is the time it takes for DNS record changes to be updated across all DNS servers worldwide. When you update a DNS record (like changing your web server IP), the change doesn't happen instantly everywhere β it spreads gradually as each DNS resolver refreshes its cache.
This tool queries multiple public DNS resolvers from different geographic locations to help you determine whether your DNS changes have propagated globally. Each resolver is queried directly via DNS-over-HTTPS (DoH), giving you accurate, real-time propagation status.
Because every resolver keeps its own cache, the answer you get depends on which resolver on the internet is asked. By querying several independent resolvers at once, this tool reveals whether your new record is already visible everywhere or only on some providers, which is the practical definition of propagation being "complete".
Key properties
- 10 resolvers — worldwide DoH resolvers across the US, Switzerland, Germany, Czechia, and Cyprus.
- Seven record types — A, AAAA, CNAME, MX, NS, TXT, and SOA.
- Response times — each resolver reports how long its lookup took in milliseconds.
- Propagation verdict — fully propagated, partial, or not checking based on whether answers match.
- Browser-only — queries go straight from your browser to the resolvers, with nothing logged.
Supported DNS record types
Choose the record type that matches the change you made. Propagation is per record type: an A record can be fully propagated while a TXT record on the same name is still stale.
| Type | Purpose | Typical value |
|---|---|---|
| A | Maps a name to an IPv4 address | 203.0.113.10 |
| AAAA | Maps a name to an IPv6 address | 2001:db8::1 |
| CNAME | Aliases one name to another | example.com |
| MX | Mail server with priority | 10 mail.example.com |
| NS | Authoritative name servers | ns1.example.com |
| TXT | Arbitrary text, SPF/DKIM/verification | "v=spf1 ..." |
| SOA | Zone authority and serial | ns1.example.com ... |
Resolvers queried
Each lookup is sent to ten independent public resolvers in different regions, so the results reflect how the wider internet sees your record rather than a single cache.
| Resolver | Location | IPs |
|---|---|---|
| Cloudflare | πΊπΈ US (Global) | 1.1.1.1, 1.0.0.1 |
| πΊπΈ US (Global) | 8.8.8.8, 8.8.4.4 | |
| Quad9 | π¨π Switzerland | 9.9.9.9, 149.112.112.112 |
| OpenDNS | πΊπΈ US (Cisco) | 208.67.222.222 |
| CleanBrowsing | πΊπΈ US | 185.228.168.9 |
| Comodo | πΊπΈ US | 8.26.56.26 |
| Neustar | πΊπΈ US | 156.154.70.1 |
| DNS.SB | π©πͺ Germany | 185.222.222.222 |
| CZ.NIC | π¨πΏ Czechia | 193.17.47.1 |
| AdGuard | π¨πΎ Cyprus | 94.140.14.14 |
Reading the propagation verdict
After the queries finish, the tool compares the answers from all ten resolvers and summarises the state:
- Fully Propagated — every resolver returned the same answer, so your change is visible globally.
- Partial Propagation — resolvers returned two or more different answers, meaning caches are still catching up.
- Not Checking — the tool could not collect comparable answers, usually due to network errors.
Individual rows can also read OK (a normal answer), NXDOMAIN (the name does not exist), or Error when a resolver is unreachable. Errors are shown per resolver and do not necessarily indicate a problem with your DNS configuration.
How to Use
- Enter Domain — Type the domain name you want to check (e.g., example.com). Do not include http:// or www.
- Select Record Type — Choose the DNS record type to check: A (IPv4), AAAA (IPv6), CNAME, MX, NS, TXT, or SOA.
- Click Check Propagation — The tool queries 8+ global DNS resolvers via DNS-over-HTTPS and displays results in real time.
- Review Results — Each resolver shows its response time, location, and the DNS records it returned. If all resolvers return the same result, your DNS has fully propagated.
Frequently Asked Questions
How long does DNS propagation take?
DNS propagation can take anywhere from a few minutes to 48 hours, depending on the TTL (Time To Live) value of your DNS records. Lower TTL values (300-600 seconds) result in faster propagation. This tool checks whether propagation has completed by comparing results from multiple global resolvers.
Which DNS resolvers are used?
This tool queries ten global DNS resolvers: Cloudflare (1.1.1.1), Google (8.8.8.8), Quad9 (9.9.9.9), OpenDNS (208.67.222.222), CleanBrowsing, Comodo SecureDNS, Neustar, DNS.SB (Germany), CZ.NIC (Czechia), and AdGuard (Cyprus). All queries use DNS-over-HTTPS (DoH) for accuracy and reliability.
What does "propagated" mean?
A DNS record is considered fully propagated when all queried resolvers return identical results. Partial propagation means some resolvers show the new record while others still show the old one. Inconsistent results may indicate you are in the middle of a propagation window.
Why do different resolvers show different results?
Each resolver has its own cache and honours the TTL on your record. Until a cached entry expires, the resolver keeps serving the old answer. Different providers also update at different times, so during the propagation window some resolvers return the new value while others still return the previous one.
What is DNS-over-HTTPS and why use it?
DNS-over-HTTPS (DoH) sends DNS queries over an encrypted HTTPS connection instead of plain UDP port 53. It works in the browser without extra software and avoids tampering or interception of the lookup, so the answers you see reflect the resolver's real cache.
What does NXDOMAIN mean?
NXDOMAIN is a DNS status code meaning the domain name does not exist at that resolver. You may see it if the domain is misspelled, if the name was just registered and is not yet in the zone, or if a resolver has cached a negative answer.
How can I speed up propagation?
Lower the TTL on the record well before you plan to change it, then raise it again after the change settles. A low TTL (for example 300 seconds) forces resolvers to re-check sooner. You cannot force third-party resolvers to flush their caches, so planning the TTL ahead of time is the effective approach.
Do DNS lookups go through a server?
No. Queries are sent directly from your browser to public DNS resolvers using DNS-over-HTTPS. Your domain is not logged or stored by this site.