DNS Propagation Checker
Enter a domain and a record type to compare what several major public DNS resolvers and real geographic locations currently return.
Overview
After a DNS change, different resolvers around the internet pick it up at different times depending on caching and TTLs. This tool checks a record two ways at once: by resolver, querying several major public resolvers (Google, Cloudflare, Quad9, and OpenDNS) in parallel, and by location, querying from real vantage points in 6 regions around the world (USA, UK, Singapore, India, Brazil, Australia). Results from both are shown side by side, with locations that disagree with the majority answer highlighted, so you can see at a glance whether a change has propagated everywhere or is still catching up somewhere.
The resolver comparison still runs from Adikya's own server, so it reflects differences between resolver providers rather than geography. The location grid is different: each of the 6 regions runs its own lookup from that region, so it's a genuine (if representative, not exhaustive) sample of geographic propagation.
Examples
Checking A record propagation
example.com
Google: 93.184.216.34 Cloudflare: 93.184.216.34
How It Works
- Enter a domain name, e.g. example.com.
- Choose a DNS record type.
- Click Check to query each public resolver in parallel.
- Compare the results returned by each resolver.
Use Cases
Confirming a DNS change has propagated
Check whether all major resolvers already see an updated A or CNAME record after a change.
Diagnosing inconsistent DNS behavior
Spot whether some resolvers are still serving a stale, cached answer.
Tips
- If one resolver shows an old value while others show the new one, it's likely still serving a cached answer until that record's TTL expires — this is expected, not an error.
- Lowering a record's TTL before making a planned change helps it propagate faster next time.
FAQ
No — it checks several major public resolvers (Google, Cloudflare, Quad9, OpenDNS) and 6 representative geographic locations (USA, UK, Singapore, India, Brazil, Australia) as a representative sample, not an exhaustive global check.
Each resolver and each location caches DNS answers independently based on the record's TTL, so a very recent change may show up in some places before others until older cached answers expire. In the location grid, a highlighted (outlier) result usually just means that location hasn't picked up the change yet.
The resolver list compares different DNS providers (Google, Cloudflare, Quad9, OpenDNS), but every one of those queries still runs from Adikya's own server. The location grid compares real geographic origin: each of the 6 regions runs its own lookup from that region, so it reflects what someone querying from that part of the world would actually see.