DNS propagation checker
Compare what several public resolvers return to see whether your latest DNS change is visible.
✓ Free, no sign-up
How it works
When you change a record, each resolver keeps serving the old answer until its TTL runs out. We query Google, Cloudflare and Quad9 at the same time, plus our own server's resolver, and compare the answers. If they match, most users already see the change.
How to use it, step by step
- Enter the domain and pick the record type you changed.
- We ask public DNS servers in different countries directly.
- The map shows in green the servers that see the majority answer, in red those that see something else.
- Run it again every few minutes until they all match.
What it's useful for
- Know when you can tell customers your new site is live.
- Confirm a server or mail move.
- Figure out why some users see the old site and others the new one.
FAQ
How long does a DNS change take to propagate?
Usually as long as the previous value's TTL, from minutes to a few hours. Name server (NS) changes can take up to 48 hours because of the parent zone's TTL.
Can I speed up propagation?
Lower the record's TTL to 300 seconds a day before the change. After the change, resolvers can't be forced to drop their cache.
How long does DNS propagation take?
Usually minutes to a few hours, and up to 48 hours in extreme cases. It mostly depends on the old record's TTL.
How can I speed it up?
Lower the record's TTL to 300 seconds a day before the change. You can't force other servers to forget the old value sooner.
Why does a server show no answer?
Some servers rate-limit queries or are temporarily unreachable from our network. It doesn't mean your domain has a problem.
What does NXDOMAIN mean?
For that server, the domain doesn't exist. It's normal right after registering a new domain.
Why do I still see the old site on my computer?
Your device and browser cache answers too. Try a private window or your phone's mobile data.