DNSChecker Alternative: DNS Propagation Check With an ETA

Pick a record type — A, AAAA, MX, NS, CNAME, TXT or SOA — and the tool queries Google, Cloudflare, Quad9, OpenDNS, Dyn, Yandex, Rostelecom, AdGuard, DNS.Watch, SafeDNS, CleanBrowsing, Baidu, AliDNS, DNSPod, 114DNS, CNNIC and DNS.SB, among others. Each answer is compared with the majority answer:

• resolvers that disagree with the majority are marked stale;
• their remaining cache TTL gives a best-case, expected and worst-case time to full propagation;
• resolvers that do not answer are left out of the percentage instead of counting as failures.

Results are cached for two minutes, so refreshing during a change shows fresh data quickly. On paid plans you can subscribe to an email that fires once every resolver returns the same answer.

The check is available without a key, which is handy in a deploy script that waits for DNS:

curl "https://enterno.io/api/open/propagation?q=example.com"

With an API key, REST API v4 exposes the same tool as propagation with a record type parameter. The free plan includes 200 calls a day. For a single authoritative answer rather than a spread of resolvers, use the DNS lookup; to plan a change, the TTL calculator shows how long old answers can survive.

• More vantage points. DNSChecker.org lists 100+ public DNS servers and lets you filter by continent or country. Enterno queries 22.
• More record types: PTR, SRV, CAA, DS and DNSKEY in addition to the common ones.
• Expected value matching by exact match, contains or regular expression, plus auto-refresh.
• Custom DNS servers: add your own resolver to the check.
• Map view, Chrome extension and Android app.

• You need to know when the change will finish, not only that it has not finished yet.
• You check propagation from a script or CI job and want a stable endpoint.
• You care about resolvers inside Russia and China, which are well represented in the list.
• You want to be emailed when propagation completes instead of refreshing a page.

Another single-purpose checker is covered in WhatsMyDNS alternatives.

Most slow propagation is caused by a long TTL that was cached before the change, not by the change itself. A short checklist keeps the window small:

1. A day before the change, lower the TTL of the record you will edit, for example from 86400 to 300 seconds.
2. Wait at least one old TTL so every resolver has picked up the short value.
3. Make the change and run the propagation check. Stale resolvers should flip within minutes.
4. Once every resolver agrees, raise the TTL back to its normal value.

Nameserver changes are slower: the NS records at the registry often carry a TTL of a day or two that you cannot lower. Keep the old DNS provider serving the same zone until the check shows the new nameservers everywhere.