DNS Propagation Checker
Asks Cloudflare, Google, DNS.SB and AdGuard for the same record at the same moment, so you can see whether a change has reached everyone or only your own resolver.
About
When you change a DNS record, the change reaches resolvers gradually as their caches expire. This tool asks four independent public resolvers for the same record at the same moment, so you can see whether everyone has the new answer or only some of them do.
How to use
- Enter the hostname and choose the record type you changed.
- Submit to query all four resolvers in parallel.
- Compare the answers and the TTLs: matching answers mean the change has spread.
Frequently asked questions
Why do the TTLs differ between resolvers?
Each resolver counts down from the TTL it was given when it cached the record, so a resolver that fetched the record earlier shows less time remaining.
My own computer shows a different result. Why?
Your machine uses your network resolver, which may be a private cache or a filtering service. These four resolvers show the public view; a local override or split-horizon DNS explains the difference.
How long does propagation take?
At most the old TTL, measured from when each resolver last cached the record. Lowering the TTL a day before a planned change is the usual way to make it quick.