Skip to content

DNS Propagation Check

Queries the same record from public DoH resolvers — Google, Cloudflare, Quad9, OpenDNS, AdGuard, NextDNS, Mullvad, DNS.SB, AliDNS — and shows which still hold the old answer.

Asks the same DNS question of 9 named public resolvers at once and puts their answers side by side. When they disagree, you are watching a change work its way out of caches — which is the real shape of what people call propagation.

☁️ Uses our serverdnspropagationglobal

Our server sends the same query to nine public DoH resolvers at once (RFC 8484). Only the domain name is sent. Korean ISP resolvers do not publish a DoH endpoint, so they are not in the list.

DNS does not "propagate" — caches hold the old answer for as long as its TTL. This table shows which caches are still giving it.

How to use it

  1. Enter the exact name you changed

    www.example.com and example.com are separate names with separate caches. Ask about the one you edited.

  2. Pick the record type

    A for a site move, MX for mail, TXT for a verification string or an SPF change, CNAME for a subdomain pointed elsewhere.

  3. Read the groups, not the rows

    Resolvers giving the same answer are grouped together. One group means everyone agrees; two means some caches still hold the old value and the TTL column tells you roughly how long they will.

Common questions

Which resolvers are these?

The table lists 9 named public DoH resolvers — Cloudflare, Google, Quad9 and the like — each with its operator. They are specific caches rather than "the internet", and a sample that size cannot tell you what a particular visitor’s ISP is serving.

Why is my ISP not in the list?

Korean carriers publish no DNS-over-HTTPS endpoint, and a browser cannot send plain DNS. To see what your own ISP answers, run nslookup or dig against its resolver from your machine.

Everyone agrees but my computer still sees the old address

Your own machine caches too — the OS resolver, and the browser on top of it. Flush the OS cache, restart the browser, and remember a page you have open may hold a connection to the old address until it is closed.

How long should I wait?

At most the TTL the record had before you changed it — not the TTL it has now. That is why lowering the TTL a day before a migration is the thing that makes the migration quick.

Feed it from

Next

These accept what this tool produces, so the result can go straight in.