DNS Propagation Checker

Check DNS propagation from your browser: query A, AAAA, CNAME, MX, TXT, NS, SOA or CAA records on Cloudflare, Google, Quad9, AliDNS, DNS.SB and Control D at once, compare answers and TTLs, and see whether they agree. Free, no signup.

Enter a name, pick a record type and click Check propagation.

How to use it

  1. Enter the hostname you changed (for example www.example.com, _dmarc.example.com or selector1._domainkey.example.com) and pick the record type.
  2. Optionally paste the new value you expect, such as the new IP or the start of a TXT record. Resolvers that already return it are marked yes.
  3. Click Check propagation. Six public resolvers are queried in parallel over DNS-over-HTTPS straight from your browser, and their answers, TTLs and response codes are shown side by side with an agree / differ verdict.
  4. A resolver still showing the old value has it cached: it refreshes once the TTL it shows counts down to zero. Answers for CDN or GeoDNS names (many big sites) can differ by design.
  5. To simulate a user in another region, enter a client subnet (like 81.2.69.0/24). Google is then queried a second time with EDNS Client Subnet, which GeoDNS providers use to pick a nearby answer.

Related tools

For every record type at once on one resolver use DNS Lookup. Changed mail records? Run the Email Deliverability Checker, SPF Checker or DMARC Checker once the new value shows up everywhere.

FAQ

How long does DNS propagation take?

There is no single propagation delay. Your authoritative servers update almost instantly; each resolver keeps serving its cached copy until that copy's TTL runs out. With a 300 second TTL most resolvers pick up a change within 5 minutes; with 86400 it can take a day. Lower the TTL a day before a planned change.

Which resolvers does this checker use?

Cloudflare (1.1.1.1), Google Public DNS (8.8.8.8), Quad9 (9.9.9.9), AliDNS (223.5.5.5), DNS.SB and Control D. They are public DNS-over-HTTPS services that allow queries from a web page; Quad9 and Control D are queried in the binary RFC 8484 format, the others in JSON.

Does this check propagation in every country?

No. Each resolver answers from the anycast site nearest to you, so this shows what these six public resolvers currently cache, not what every ISP in every country sees. ISP resolvers and corporate DNS servers keep their own caches. The optional client subnet field asks Google to answer as if the user were in that network, which helps with GeoDNS.

Why do the resolvers show different IP addresses?

If the TTLs are short and every answer looks valid, the name is probably on a CDN or GeoDNS service that returns a nearby address per location. That is normal. If one resolver shows your old IP with a long TTL, it is still caching the old record.

Can I make a resolver pick up my change faster?

Cloudflare (one.one.one.one/purge-cache) and Google (dns.google/cache) have public cache purge pages for single names. Other resolvers and ISPs have to wait for the TTL to expire.

Want the full kit?

Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.