DNS Propagation Checker
Query several public DNS resolvers at once and compare their answers to see how a record change is propagating through resolver caches.
Your input is used for this one lookup only. It is not logged or stored.
Results
How to read the results
Each card is one resolver. Match means its (order-independent, normalized) answer equals the consensus among resolvers. Differs means it returned a different set — often an older cached value. Multiple A/AAAA/MX/NS values are normalized before comparison, so a different order is not treated as a mismatch.
What this is (and isn’t)
This compares recursive resolver caches, not authoritative servers or geographic locations. "Propagation" depends on each resolver’s cache and the record’s TTL.
Data source: Multiple public DNS-over-HTTPS resolvers. Answers reflect each resolver’s current cache. Learn about our data sources →
Read more
- Why DNS changes take time: propagation and TTL explained — Propagation is not a broadcast — it is caches expiring. Here is how TTL controls the wait, and how to plan a migration around it.
Frequently asked questions
Does this check DNS from different countries?
No. It queries several public recursive resolvers and compares their cached answers. It does not measure DNS from specific cities, and we do not show a map of fake locations.
Why do resolvers disagree?
Each resolver caches records for the record’s TTL. After a change, some resolvers still serve the old value until their cache expires. That is normal propagation behavior.
What does "expected value" do?
If you enter the value you expect (e.g. a new IP), we show how many resolvers already return it — handy while waiting for a change to propagate.