DNS Propagation Checker
This free DNS propagation checker asks six public DNS resolvers for the same record and shows, side by side, whether they all see your change yet.
What is DNS propagation?
DNS propagation is the time it takes for everyone to see a DNS change. Changes aren't pushed out. Resolvers keep cached answers until the record's TTL expires, then fetch the new one.
That's why a change can show up for you straight away while a colleague, or a customer's mail server, still sees the old value for a while.
Why we compare resolvers, not countries
Big public resolvers like Cloudflare and Google answer from hundreds of locations, and a check always reaches the nearest one. A map of countries would suggest a precision that isn't really there.
Instead we ask six independent resolvers (Cloudflare, Google, AdGuard, NextDNS, DNS.SB and AliDNS) and show where they agree and where they don't. That's an honest picture of whether your change has landed.
Frequently asked questions
How long does DNS propagation take?
As long as the old record's TTL: often 5 minutes to a few hours. Nameserver changes at the registry can take up to 48 hours.
How can I make future changes propagate faster?
Lower the record's TTL to 300 seconds a day before the change. Once the new value is everywhere, raise it again.
Why do resolvers show different answers?
Each one cached the record at a different time, so they expire at different times. It sorts itself out once the old TTL has passed.
Can I clear other resolvers' caches?
For two of the biggest, yes: Cloudflare (1.1.1.1/purge-cache) and Google Public DNS both offer a public cache-flush page.