Useful for
- Format, validate, encode, decode, inspect, or generate developer-friendly values.
- Troubleshoot copied snippets before adding them to a project.
- Prepare quick examples for documentation, testing, support, or debugging.
DNS Propagation Checker
Check DNS records across trusted public resolvers and compare whether they return the same answer.
Result summary
Domain
-
Record
-
Resolver agreement
-
Resolver results
Good to know
This tool checks public recursive resolvers such as Cloudflare, Google, Quad9, OpenDNS, and AdGuard. It helps spot DNS caching and propagation differences, but it is not a true country-by-country or ISP-by-ISP probe.
Tool guide
How to use DNS Propagation Checker
DNS Propagation Checker gives you a focused way to handle one small task quickly. Check DNS records across multiple public resolvers. It is free to use, requires no login, and is built for quick checks when you need a practical result.
Example
For example, use DNS Propagation Checker while checking an API response, preparing a test value, inspecting a URL, or cleaning up code-adjacent text.
Good to know
Most developer utilities run in your browser. Avoid pasting secrets, API keys, passwords, or private production data into any online tool.
How it works
The DNS propagation checker sends the same DNS query to several public recursive resolvers and compares the answers. Different answers can suggest caching, TTL timing, resolver policy, or a recent DNS change that has not reached every resolver yet.
Supported records: A, AAAA, CNAME, MX, TXT, and NS.
Practical examples
- Check whether a new A record is visible on Cloudflare and Google DNS.
- Compare MX records after moving email providers.
- Verify whether TXT records for SPF, DKIM, or site verification are being returned consistently.
Common mistakes
- Do not treat this as a physical country-by-country test; it checks public resolvers, not every ISP.
- Remember that TTL and resolver caches can make old records appear for a while after a change.
- Check the correct hostname, such as www.example.com versus example.com.
Questions
Is this a true global propagation checker?
It checks multiple public recursive resolvers. That is useful, but it is not the same as probing every country, network, or ISP.
Why do resolvers show different answers?
DNS caches, TTL values, recent record changes, DNSSEC issues, and resolver policy can all cause differences.
Which record type should I check?
Use A for IPv4 website addresses, AAAA for IPv6, CNAME for aliases, MX for email routing, TXT for verification/SPF/DKIM, and NS for authoritative nameservers.