How to use the DNS Propagation Checker
- Enter the domain or host name, for example
www.example.com. - Pick the record type: A, AAAA, CNAME, MX, NS, TXT, SOA or CAA.
- Press Check propagation. The tool asks three public resolvers and compares their answers and TTLs.
- If the answers differ, wait and check again. Use Copy or Download to keep a record.
What the report shows
| Check | What you learn |
|---|---|
| Resolver answers | The records each resolver returns, with status code, TTL and response time. |
| Agreement | Whether all resolvers return the same data. |
| Missing records | NXDOMAIN or empty answers and what usually causes them. |
| TTL | How long resolvers may keep the answer cached. |
| Name servers | The name servers of the domain, so you can confirm you edited the right zone. |
Tips for better results
- Lower the TTL to 300 seconds a day before a planned change, then raise it again afterwards.
- A changed record is visible everywhere after the old TTL has expired. A record with TTL 86400 can take up to a day.
- When you change name servers at the registrar, allow up to 48 hours. Some registries update faster.
- Your own device and router keep a DNS cache too. Restart the router or flush the local cache if you still see old data.
Limits to know about
- The tool queries three large public resolvers, not servers in every country. It does not draw a world map and does not claim to.
- A resolver that shows old data may simply have the answer cached. That is normal and temporary.
- CDNs and load balancers legitimately give different A and AAAA answers in different places.
Frequently asked questions
What is DNS propagation?
It is the time it takes for a DNS change to reach resolvers around the internet. Resolvers keep old answers until the TTL runs out, so the change reaches different users at different times.
How long does DNS propagation take?
Usually minutes to a few hours. It can take up to 48 hours when you change name servers or when the old TTL was very high.
Why do the resolvers show different answers?
Either the change is still spreading, or the name uses a CDN or load balancer that returns different addresses by location. Check the TTL column.
Can I speed up propagation?
Not after the fact. You can only lower the TTL before the next change. Clearing your own device cache helps with what you see yourself.
Does this check the authoritative name servers?
No. A browser cannot send raw DNS queries to them. The report lists the name servers so you can compare with your DNS panel.
Related tools
About this tool: free, no sign-up, works on phone and desktop. Last reviewed: November 2026.