A · AAAA · CNAME · MX · NS · TXT
DNS propagation checker
Changed a DNS record? See which public resolvers already return the new value and which still serve the old one from their cache. Every resolver is asked live.
How does the propagation check work?
- The record is asked from 19 public resolvers of different operators in the US, Europe, Russia, China, Korea and Japan at the same moment.
- The same question goes to the domain's own (authoritative) nameservers. Their answer is the current value; a resolver that returns it is up to date.
- The TTL column shows how many more seconds a resolver keeps the cached answer before asking again.
- Big anycast services (Google, Cloudflare, Quad9…) answer from the site nearest to our server; their other sites may still hold a different cache.
Frequently asked questions
›How long does DNS propagation take?
As long as the old record's TTL: resolvers keep a cached answer for that many seconds. With a 300-second TTL most resolvers update within minutes; with 86400 it can take a day. Lower the TTL before a planned change.
›Why do some resolvers still show the old value?
They cached the answer before the change and will ask again when its TTL runs out. Nothing can force a public resolver to forget it earlier, though Google and Cloudflare offer cache-flush pages.
›Why do resolvers return different IP addresses?
Sites on a CDN or with GeoDNS answer each resolver with the address of the nearest server. Compare with the authoritative answer and the CNAME target, not only the IP.
›Does the check store anything?
No. Every check asks the resolvers live; the result is not cached or stored.