Compare the record returned by the world’s two largest public resolvers — Google (8.8.8.8) and Cloudflare (1.1.1.1) — to see whether a recent DNS change has taken hold.HostnameRecord type A AAAA CNAME MX TXT NS Check
Runs entirely in your browser using DNS over HTTPS. No data is stored.
What This Tool Checks
When you change a DNS record, the new value does not appear everywhere at once. Each resolver on the internet keeps its own cache, and that cache only refreshes when the record’s time-to-live expires. Until then, some resolvers serve the new value while others still hand out the old one. That gap is what people mean by propagation.
This checker queries the same record on Google Public DNS and Cloudflare DNS at the same moment, then compares the answers. When both agree, the change has reached the two resolvers most of your visitors rely on. When they disagree, the change is still working its way through.
How To Read The Results
- All resolvers agree means both Google and Cloudflare return the same value. For most real-world purposes, your change is live.
- Resolvers disagree means the two return different values. One cache has updated and the other has not — wait for the TTL to expire and check again.
- No record found means neither resolver has a record of this type. Confirm the record exists and that you picked the right type.
Each row also shows the TTL the resolver currently reports. A TTL near the record’s configured value means the resolver fetched it fresh; a small, shrinking TTL means it is serving a cached copy that will refresh soon.
How Long Propagation Takes
The TTL on the record sets the ceiling. A record with a one-hour TTL can take up to an hour to refresh on a resolver that cached the old value just before you made the change. Lowering the TTL a day before a planned change shortens that window. Name server changes at the registrar are the slow exception — those can take far longer because they depend on the parent zone and registrar timing.
What This Tool Can And Cannot Show
This is a resolver-level check, not a global map. Google and Cloudflare both run anycast networks, so your query reaches the node nearest you rather than a fixed city. That makes this tool excellent for answering “have the major public resolvers picked up my change,” but it will not show propagation across dozens of specific countries. For a worldwide geographic view, a dedicated probe-network service is the right tool.
Related Tools & Resources
To inspect every record on a domain at once, use the DNS Record Checker. To go the other way and find a hostname from an IP, try the reverse DNS lookup. If you want the bigger picture, read how DNS works and the rundown of every DNS record type. Changing mail records? Verify them with the SPF, DKIM, and DMARC checker. Everything lives in the networking tools hub.
DNS Propagation Checker
Compare the record returned by the world’s two largest public resolvers — Google (8.8.8.8) and Cloudflare (1.1.1.1) — to see whether a recent DNS change has taken hold.
Runs entirely in your browser using DNS over HTTPS. No data is stored.
What This Tool Checks
When you change a DNS record, the new value does not appear everywhere at once. Each resolver on the internet keeps its own cache, and that cache only refreshes when the record’s time-to-live expires. Until then, some resolvers serve the new value while others still hand out the old one. That gap is what people mean by propagation.
This checker queries the same record on Google Public DNS and Cloudflare DNS at the same moment, then compares the answers. When both agree, the change has reached the two resolvers most of your visitors rely on. When they disagree, the change is still working its way through.
How To Read The Results
- All resolvers agree means both Google and Cloudflare return the same value. For most real-world purposes, your change is live.
- Resolvers disagree means the two return different values. One cache has updated and the other has not — wait for the TTL to expire and check again.
- No record found means neither resolver has a record of this type. Confirm the record exists and that you picked the right type.
Each row also shows the TTL the resolver currently reports. A TTL near the record’s configured value means the resolver fetched it fresh; a small, shrinking TTL means it is serving a cached copy that will refresh soon.
How Long Propagation Takes
The TTL on the record sets the ceiling. A record with a one-hour TTL can take up to an hour to refresh on a resolver that cached the old value just before you made the change. Lowering the TTL a day before a planned change shortens that window. Name server changes at the registrar are the slow exception — those can take far longer because they depend on the parent zone and registrar timing.
What This Tool Can And Cannot Show
This is a resolver-level check, not a global map. Google and Cloudflare both run anycast networks, so your query reaches the node nearest you rather than a fixed city. That makes this tool excellent for answering “have the major public resolvers picked up my change,” but it will not show propagation across dozens of specific countries. For a worldwide geographic view, a dedicated probe-network service is the right tool.
Related Tools & Resources
To inspect every record on a domain at once, use the DNS Record Checker. To go the other way and find a hostname from an IP, try the reverse DNS lookup. If you want the bigger picture, read how DNS works and the rundown of every DNS record type. Changing mail records? Verify them with the SPF, DKIM, and DMARC checker. Everything lives in the networking tools hub.