DNS Propagation Checker
Compare what public resolvers around the world currently return with the authoritative answer, and see how long cached data will last.
What this tool checks
- The current answer from the authoritative nameservers
- Answers from 8 public resolvers run by different operators
- Which resolvers still hold old or "no record" answers, and for how long
- SERVFAIL splits that point to DNSSEC problems
- The TTLs that control how long changes take
How to read the results
- Pass
- The check succeeded based on the observed responses.
- Warning
- Works now, but is risky, unusual or worth reviewing.
- Fail
- A problem was observed directly in the responses.
- Inconclusive
- Not enough evidence — for example a server did not respond.
Frequently asked questions
- How do I check DNS propagation?
- Enter the domain and pick a record type. The checker asks the authoritative nameservers for the current answer, compares it with public resolvers from different operators, and shows which still hold the old value and for how long.
- How long does DNS propagation take?
- For a record change, up to the old record's TTL, often 5 minutes to an hour. Nameserver changes can take up to 48 hours for .com and .net, because the parent zone's NS records are cached that long.
- Why do different resolvers show different answers?
- Each resolver cached the old answer at a different moment and keeps it until its TTL runs out. Some domains also use GeoDNS, which deliberately returns different answers in different places.
- Can I speed up DNS propagation?
- Only in advance: lower the record's TTL before a planned change. Nothing can make other resolvers drop a cached answer early. If only your own computer shows the old value, flush its DNS cache.