DNS Propagation
Check the same record across multiple global resolvers to verify propagation.
Enter a target
e.g. example.com — press ⏎ / ⌘⏎
What is DNS Propagation?
DNS Propagation queries the same record across multiple public resolvers at once and shows whether the answers agree.
After a change, some resolvers return the new value while others still serve the old one until its TTL expires — that's the normal transition, not a fault. Once every resolver agrees, the state becomes consistent.
Differences that persist are not propagation but configuration: mismatched zone data between authoritative servers, or a misconfigured anycast node.
Frequently Asked Questions
8 questionsHow long does DNS propagation take?
Roughly the old record's TTL — usually minutes to a few hours. The "48 hours" myth applies to very high TTLs; modern setups propagate much faster.
Is the "Propagating" state an error?
No. Some resolvers serving the new value while others still serve the old one is a natural part of the transition. Once all agree, the state becomes "Consistent".
Can I speed propagation up?
Lower the TTL (e.g. to 300s) before the change, make the change, then restore the TTL. You can't purge remote caches, though some resolvers (Google, Cloudflare) offer cache-flush tools.
Which resolvers are checked?
Google (8.8.8.8), Cloudflare (1.1.1.1) and Quad9 (9.9.9.9) DoH endpoints are queried simultaneously and compared.
How many resolvers are checked, and why those?
The DoH endpoints of Google, Cloudflare and Quad9, queried simultaneously. They are the three most widely used public resolvers, anycast worldwide — once a change appears in all three, it has propagated for the overwhelming majority of users.
If results differ, which one is right?
Not the majority answer — the one your authoritative nameserver gives. Use DNS Health Check to see it; that tool queries your nameservers directly.
How long after a change should I check?
Wait out the old record's TTL. At 300s most resolvers refresh within five minutes; at 86400 it can take a day. If you didn't lower the TTL beforehand, there's no way to shorten it.
What if one resolver still serves the old value?
Google and Cloudflare offer public cache-flush tools (Google Public DNS Flush Cache, Cloudflare Purge Cache). You can't reach into other resolvers' caches — you have to wait for the TTL.