DNS Propagation Check — has your change landed everywhere

Compare what four major public resolvers currently return for a record, so you can tell whether a DNS change has propagated or whether you are looking at a stale cache.

Queried against Cloudflare, Google, Quad9 and AdGuard resolvers simultaneously. Disagreement between them normally means a recent change is still working through caches; persistent disagreement usually means a CDN answering by geography, which is not a fault.

Frequently asked

How long should propagation take?

At most the previous TTL of the record. If the old record had a TTL of 3600, a resolver that cached it just before your change will keep serving it for up to an hour regardless of what your registrar says.