🗺️ DNS Propagation Checker
See a DNS record from many resolvers worldwide and spot stragglers.
Why DNS changes are not instant
When you change a DNS record, nothing is pushed out to the internet. Instead, thousands of resolvers around the world hold a cached copy of your old record, each with a countdown (the TTL) for how long that copy stays valid. Your change has "propagated" only when those caches have expired and re-asked. This checker asks resolvers on several continents the same question at the same moment, so you can see exactly who already has the new answer and who is still serving the old one.
How to read the table
- Every resolver agrees: the change has fully propagated. If a user still sees the old site, their own network or browser cache is the remaining layer.
- Answers differ: either caches are still expiring (normal for the first TTL period, and up to 24 to 48 hours for stubborn networks), or the domain uses round-robin or CDN DNS, where several different addresses are all correct at once.
- No record yet on some resolvers: that resolver has not picked the record up, or the record genuinely does not exist at that provider's view of DNS.
Frequently asked questions
How long should propagation take?
Most changes are visible worldwide within the old record's TTL, commonly 5 minutes to 4 hours. The often-quoted 24 to 48 hours is the worst case for stubborn ISP caches, not the norm. Lowering the TTL a day before a planned change makes the change itself much faster.
My new record shows everywhere except my own connection. Why?
Your ISP's resolver or your router is still caching the old answer. Switching your device to a public resolver (1.1.1.1 or 8.8.8.8), or simply waiting out the TTL, fixes it. The rest of the world likely already sees the new record.
Different IP addresses on different resolvers: is that broken?
Usually not. Large sites answer with several addresses and rotate them (round-robin), and CDNs deliberately answer differently by region. Propagation is about old versus new values, not about every resolver matching character for character.
Can I speed propagation up?
Only in advance: set a low TTL (300 seconds) at least a day before the change, make the change, then raise the TTL again after. There is no legitimate way to force other networks to drop their caches early.