Compare DNS resolver answers
Check the same name and record type through Google Public DNS and Cloudflare. This is a focused DNS propagation check, not a survey of every resolver worldwide.
Queries go directly from your browser to Google Public DNS and Cloudflare. Use public DNS names only. Read how queries are handled.
A public-looking split-DNS name may still be confidential. Do not paste internal-only names.
Results
Enter a query and press Compare resolvers.
This link includes the queried name, not saved results. Review exported DNS answers before sharing; they may contain public tokens or other sensitive-looking data.
What matching answers establish
When both replies contain the same records, both sampled responses agree at the displayed times. It does not mean every internet provider, office network or device has the same cached answer. These are anycast services; two provider names are not two guaranteed geographic measurement points.
Why answers can differ
A recent change and cached data are possible causes. Content-delivery networks and location-dependent policies can also return different valid addresses. This tool does not automatically label a difference as a configuration fault. It compares record data separately from TTLs, so a normal cache countdown is not shown as an address change.
A missing response is not a missing record
If one provider times out or cannot be reached, the comparison is incomplete. The other provider's data remains useful, but it cannot establish agreement. A DNS SERVFAIL response is shown separately from an HTTPS connection failure.
Still reaching the old service?
Compare the exact hostname used by the application, including www and other subdomains. Then inspect the resolver and cache actually used by the affected client. A record can be correct while an HTTP redirect, virtual host, proxy or application cache still serves the old content. Changing DNS does not itself configure a web redirect.