Free · live registry data · no login

DNS Propagation Checker

Query resolvers around the world to see if a change has spread.

How it works

Has your DNS change reached the big public resolvers yet?

After you edit a record, each resolver keeps serving its cached copy until the old TTL expires, so some people see the new value while others still see the old one. This checker asks Cloudflare, Google and Quad9, three global anycast resolvers that together handle a large share of the world's lookups, directly over DNS-over-HTTPS and compares their answers. Optionally paste the value you expect and we tell you exactly which resolvers have it and how long the rest will take.

Results appear here after you click Check propagation.

How this works

1
Query three resolvers
Cloudflare, Google and Quad9 are asked in parallel over DNS-over-HTTPS straight from your browser.
2
Normalise and compare
Answers are sorted and lower-cased so only real differences, not ordering or trailing dots, count as disagreement.
3
Match your expected value
If you supply the new value we report which resolvers already serve it and the longest cache left on the rest.

Frequently asked questions

What is DNS propagation?: It is the period after a DNS change when resolvers around the world still hold the old answer in cache. There is no central 'push'; each resolver simply re-asks your nameservers once its cached copy's TTL runs out. Propagation is finished when every cache has expired.
How long does DNS propagation take?: Usually from a few minutes to a few hours, governed by the TTL of the record you changed. Nameserver changes can take up to 48 hours because parent zones use long TTLs. Some ISP resolvers cache beyond the TTL, which is why a few users lag.
Why do Cloudflare and Google show different answers?: They cached the record at different moments. One re-fetched after your change and the other has not yet. If the disagreement persists past the TTL, your nameservers themselves may hold different zone copies, which the Nameserver Lookup tool can reveal.
Can I speed up propagation?: Not retroactively, but you can prepare: lower the TTL to 300 seconds at least a day before the change so caches expire quickly, make the change, confirm it here, then raise the TTL again. You can also purge Cloudflare's and Google's caches via their public purge pages.
Is three resolvers enough to judge propagation?: Cloudflare, Google and Quad9 are the largest independent public resolvers and are anycast, so each answer represents a global network rather than one city. If all three agree, the change is effectively live; remaining differences are at individual ISPs and will clear within the TTL.

Every MailShrine domain includes WHOIS privacy, transfer lock, Anycast DNS with DNSSEC and two business mailboxes.