DNS Propagation Checker
Check whether a DNS record has propagated by querying it against multiple public resolvers at once.
The domain is sent to our server, which queries several public resolvers. Nothing is stored.
About the DNS Propagation Checker
The DNS propagation checker queries a single record against several independent public resolvers at the same time and shows you what each one currently returns. When you change a record, every resolver keeps serving its cached copy until that record’s TTL expires, and because caches expire at different moments the new value appears in some places before others. Comparing resolvers side by side is the quickest way to see whether a change has finished rolling out or is still in flight.
Enter a domain, pick a record type (A, AAAA, CNAME, MX, TXT, or NS), and the tool fans the query out to Cloudflare, Google, OpenDNS, AdGuard, DNS.SB, and AliDNS, then reports each resolver’s answer and response time. When every resolver agrees you get a clear “propagated” verdict; when they disagree you can see exactly which ones are still holding the old value. Use it after updating an A record during a migration, switching nameservers, adding an SPF or DKIM TXT record, or pointing MX records at a new mail provider.
These resolvers run on anycast networks, so this compares independent resolver operators and their separate caches rather than physical locations in different countries. That is the thing that actually causes propagation delay: different caches letting go of the old answer at different times. The domain you enter is sent to our server only to run the lookups and is never stored or logged.
Reach developers and designers who use these tools every day. Privacy-first, no trackers.
Frequently asked questions
What does “propagated” mean here?
Every resolver we queried returned the same record set, so the change you made is now being served consistently across all of them. If even one resolver still shows the old value, the verdict is that the answers are not yet consistent.
Why do some resolvers still show the old value?
DNS answers are cached for the length of the record’s TTL. A resolver that fetched the record before your change will keep serving the cached copy until that TTL expires, which can take anywhere from a few minutes to a couple of days depending on how the TTL was set.
How can I make a change propagate faster next time?
Lower the record’s TTL well before you plan to change it. If the TTL is 300 seconds when the change goes out, caches let go of the old value within five minutes; if it is 86400 seconds, they can hold it for a full day. Drop the TTL a day ahead, make the change, then raise it again.
Does this check resolvers in different countries?
The resolvers we query are run by different operators and several front their service from anycast networks, so we compare independent caches rather than guaranteed physical locations per country. For propagation that is what matters, because the delay comes from separate caches expiring the old answer at different times, not from geography.
Does this run in my browser?
No. Browsers cannot make raw DNS queries, so the check runs on our server, which queries the public resolvers and returns their answers. The domain you enter is sent to our server only for the lookup and is not stored.