Changed a DNS record and wondering if it has propagated? Query any domain across 6 global resolvers in real time. No cached results, no account required.
Supports any public domain. Protocol and path are stripped automatically.
Querying resolvers… DNS can take a few seconds
Check failed
Why resolvers disagree
Each resolver caches DNS records independently. Your old TTL determines how long resolvers hold the cached value before re-querying the authoritative server. If your TTL was 86400 before the change, some resolvers can hold the old record for up to 24 hours.
Lower TTL before changes
Best practice: drop your TTL to 300 seconds (5 minutes) a full 24 hours before making a DNS change. Make the change, wait for propagation, then raise TTL again. Most engineers learn this the hard way after a painful migration.
MX and TXT lag
MX records (email routing) and TXT records (SPF, DKIM) tend to propagate more slowly because mail servers cache them aggressively. If email is breaking after a DNS change, check these records first — the old value is likely still cached somewhere.