DNS Propagation

Query 9 public resolvers at once and see whether your DNS change is visible everywhere.

Domain or subdomain (www.example.com, _dmarc.example.com…).

To see who already has the new value.

Try with

Queries go from your browser to the public resolvers listed above (DNS-over-HTTPS). The site does not relay them and stores nothing.

What the tool does

  • 9 independent resolvers

    Cloudflare, Google, Quad9, DNS.SB, DNSForge, CZ.NIC, Control D, IIJ and AliDNS: each has its own cache. If they all agree, your change is visible everywhere.

  • Expected value

    Enter the new value after a change: each resolver is marked "expected value" or "different", and the verdict says how many already have it.

  • Common types

    A, AAAA, CNAME, MX, NS, TXT, SOA and CAA, for a domain or a subdomain (www, _dmarc, a DKIM selector…).

  • Live follow-up

    Results arrive as they come; the automatic re-check every 30 seconds stops as soon as the expected value is everywhere. The page link can be shared.

How to read the result

Each row is a public resolver. "Same" or "Expected value": it returns the same answer as the majority or the value you entered. "Different": its cache still holds something else, or the domain answers differently by region. The TTL is the remaining lifetime of the answer in its cache.

FAQ

How long does DNS propagation take?

A change is visible as soon as caches expire, so at most the old record's TTL (usually 300 s to 24 h). Lowering the TTL 24 to 48 h before a migration shortens the wait. A name server change at the registry can take longer.

Why does a resolver still show the old value?

It cached the answer and keeps it until its TTL ends. Check again later: each resolver expires its cache at its own pace.

Why not a world map by country?

From a browser you can only query public resolvers reachable over HTTPS, which answer from their point of presence closest to you. The tool therefore compares different operators (so different caches), not countries.

The answers differ but I changed nothing, is it a problem?

Not necessarily: a domain that load-balances or adapts its answer to the region (CDN, geo DNS) legitimately returns different addresses depending on where you ask. For a TXT, MX or NS record, a difference is unusual.

Search