About DNS Propagation Checker
After a server move, a name server switch or an MX record change, some visitors keep reaching the old address for a while. The DNS propagation checker shows how far the change has got by asking 14 public resolvers at the same time: Google, Cloudflare, Cisco OpenDNS, NextDNS, Control D, AdGuard, DNS.SB, Brahma World, LibreDNS, RethinkDNS, IIJ in Japan, and AliDNS, DNSPod and 360 in China. If the domain uses DNSSEC, run the DNSSEC Checker after a name server change, since a mismatched DS record stops it resolving.
Choose A, AAAA, CNAME, MX, NS, TXT, CAA or SOA. Each resolver's answer is listed with its response time, a country flag and any CNAME it followed. Type the new IP or text into Expected value and the resolvers that already return it get a tick, while the others are flagged. Resolvers keep an old answer until its TTL runs out, so lower the TTL well before a planned move. These are public resolvers from different countries, not probes in every city, and your internet provider's own resolver may lag behind them. For one full answer with TTLs, use DNS Lookup.
How to use DNS Propagation Checker
- 1Enter the domain
Type the domain or host name you changed, such as www.example.com.
- 2Pick the record type
Choose A, AAAA, CNAME, MX, NS, TXT, CAA or SOA.
- 3Add the expected value
Optionally type the new IP or text, so resolvers that already return it are marked.
- 4Check propagation
Click Check propagation, and run it again later to watch the change spread.
Why use Cubfile for this
- 14 resolvers at once
Global services plus AliDNS, DNSPod and 360 in China, all asked in parallel.
- Expected-value matching
Enter the new value and see at a glance which resolvers already have it.
- Answer, time and country
Every resolver's reply comes with its response time and a country flag.
- Eight record types
A, AAAA, CNAME, MX, NS, TXT, CAA and SOA, for site moves and email changes alike.