DNS Propagation Checker
Query 15 public DNS resolvers at once to see where your DNS change has landed. Useful after updating records, switching nameservers, or moving domains.
About this check
How DNS changes propagate
You edit your record → your nameserver updates immediately → public resolvers fetch the new record the NEXT time their cache expires. If your TTL is 3600, expect up to an hour for global propagation.
Reduce propagation time
Before a planned change, lower the record’s TTL to 60 seconds (at least 24h in advance). After the change propagates, raise the TTL back to 3600+ for caching efficiency.
FAQ
Operator questions, answered.
Why does DNS take time to propagate?+
Each DNS resolver caches answers for the TTL of the record. Until that TTL expires, the resolver returns the old answer even if the authoritative record changed. Lowering the TTL before a change makes propagation faster.
What if resolvers disagree?+
Either (1) your change has not finished propagating, wait for TTL expiry, or (2) you have split-DNS where internal and external resolvers serve different answers. Check both.
Which resolver should I trust?+
All of them equally. If Cloudflare and Google disagree with Yandex, the Yandex user sees the old record until it refreshes. Plan your cutover around the longest cache time, not the shortest.
DNS Propagation Checker is one of 18 plus checks.
A free Cora scan covers TLS, DMARC, SPF, DNS, headers, WHOIS, and breach exposure in a single 90 second submission.