DNS Propagation Checker
Check if your DNS records have propagated globally. We query 4 public DNS resolvers in parallel — Google, Cloudflare, Quad9, and AdGuard — and surface any drift between them.
Want details on each resolver? Compare public DNS resolvers
Why this matters: DNS changes don't propagate instantly. After updating a record at your registrar, different resolvers around the world may see the old value for minutes to hours.
If all 4 resolvers return the same records, your change has fully propagated. If any rows show drift (red), wait and re-check.
Frequently asked
Why do DNS changes take so long to propagate?
Every resolver caches records for the duration of their TTL (time-to-live), which is set when the record was created. If a record had a 24-hour TTL when a resolver fetched it, that resolver will keep returning the old value for up to 24 hours after you change it, regardless of what your registrar shows. Global "propagation" is really a sum of every resolver's cache expiring independently.
What is TTL?
TTL (time-to-live) is the number of seconds a resolver is allowed to cache a record before re-fetching it. Common values: 300 (5 min) for records that change often, 3600 (1 hr) for typical use, 86400 (1 day) for stable records. Lower TTLs mean faster propagation but more queries against your authoritative DNS. For a migration, drop the TTL 24-48 hours BEFORE the change so old caches expire by the time you flip the record.
Why do different resolvers show different records?
Three reasons. (1) The TTL above — some resolvers still hold the old record. (2) GeoDNS — your authoritative DNS may return different IPs to different resolvers based on their location. (3) DNS-based load balancing — some setups rotate IPs at the DNS layer per request. If you see drift on this page, wait a TTL window and re-check; if drift persists, your DNS host may be configured to return location-specific answers on purpose.