What is DNS propagation?
When you change a DNS record (pointing a domain at a new server, updating an MX record, or rotating a TXT value), that change doesn't take effect everywhere at once. Resolvers around the world cache the old value for the length of its TTL (time to live), so the new record “propagates” outward over time. This checker queries resolvers in 20+ locations simultaneously so you can see exactly where your change has landed and where it's still cached.
How to use this checker
- Enter the domain you want to check (e.g. example.com).
- Pick the record type: A, AAAA, CNAME, MX, TXT, or NS.
- Optionally enter the value you expect to confirm every location has it.
- Hit Check and read the per-location results and consensus.
Frequently asked questions
What is DNS propagation?
DNS propagation is the time it takes for a DNS record change to be reflected across resolvers worldwide. Because resolvers cache records for the duration of their TTL, a change can appear instantly in one region and take minutes or hours to show up in another.
How long does DNS propagation take?
It depends on the record's TTL (time to live) and how long ago you made the change. Most changes propagate within minutes to a few hours; large TTLs can extend this to 24-48 hours. Lowering the TTL before a planned change makes propagation faster.
Why do different locations show different results?
Different results can be normal (anycast or GeoDNS routing each region to a nearby edge server) or a sign of in-progress propagation after a record change. This checker flags which case it is by analyzing the IP subnets and consensus across locations.
Which record types can I check?
A, AAAA, CNAME, MX, TXT, and NS records. Enter a domain, choose the record type, and optionally provide an expected value to confirm whether every location has picked up your change.