What is DNS propagation and why does it take time?

DNS answers are cached by recursive resolvers for the duration of the record's TTL. After you change a record, every resolver keeps serving the old value until its cached copy expires, then fetches the new one from your authoritative nameservers. Propagation is just that staggered cache expiry playing out across the internet, it is not a single global push.

Why does a resolver show a different value (differs)?

Two reasons. A genuinely stale cache: it kept the old value and will serve it until its TTL counts down (the tool shows that remaining TTL, so 200 seconds left is nothing, while 20+ hours points at a high original TTL). Or a different CDN/GeoDNS edge: large sites answer with different IPs per region, and some national resolvers (for example in China) can return different results due to local DNS policy. That is why the verdict reads differs rather than stale, the value is simply not the one your authoritative servers returned.

How does the tool know the correct (authoritative) value?

The tool queries your domain's authoritative nameservers directly, the servers that publish the zone, so their answer is the source of truth by definition. Every public resolver is then compared against it. If the authoritative servers cannot be reached, the tool falls back to the majority answer across resolvers and labels it as a consensus rather than authoritative.

Why no world map or 30 countries?

Because it would be misleading. The largest public resolvers (Cloudflare, Google, Quad9) are anycast: the same IP is announced from hundreds of cities, so a single server reaches the nearest one, not a chosen country. Rather than fake geographic pins, the tool compares each resolver to your authoritative record, which is the data that actually tells you whether a change is live.

Which record types can I check?

A, AAAA, CNAME, MX, NS, TXT, SOA and CAA. That covers website moves (A/AAAA/CNAME), email setup (MX and the SPF/DKIM/DMARC records under TXT, see also Mail Security), nameserver changes (NS) and certificate issuance (CAA). ANY is intentionally not offered.

Is it free? Any limits?

Free, no signup, rate-limited per IP. You choose only the domain and record type, the resolvers it queries are a fixed curated list of public resolvers, you cannot point the tool at an arbitrary resolver. That is a deliberate security choice, it prevents the tool from being aimed at internal systems or abused as a traffic source.

How can I speed up DNS propagation?

Plan ahead: lower the TTL to 300 seconds 24-48 hours before a planned change, wait for the old TTL to expire, then make the change. After the fact you cannot force resolvers to drop their cache, you can only wait out the TTL. Checking with DNS Lookup and NS Lookup confirms your nameservers are the ones actually serving the record.

DNS Propagation Checker - Check DNS Records Worldwide

What is DNS propagation?

When you change a DNS record, the new value starts at your authoritative nameservers and slowly reaches recursive resolvers across the internet as their old cached copies expire. That spread is DNS propagation, and it is governed almost entirely by TTL (Time To Live).

How this checker works

It reads the record straight from your domain's authoritative nameservers, the source of truth and the new value.
It then asks more than a dozen public resolvers across several regions (Cloudflare, Google, Quad9, Yandex, AliDNS and others) for the same record.
Each resolver's cached answer is compared to the authoritative one: match (serves a current value) or differs (a stale cache or a different CDN edge), alongside the TTL countdown to its next refresh.

Reading the result

match, green: that resolver serves a current value.
differs, orange: it returns a different value, either a stale cache or a different CDN/GeoDNS edge. The TTL shows when a stale cache refreshes.
no record / no answer: the resolver has nothing for that name yet, or did not respond in time.
Propagated X / Y: the headline, how many resolvers are already current.

How long does DNS propagation take?

From a few minutes to 24-72 hours. The single biggest factor is the record's TTL before you changed it: a 3600s TTL means caches can hold the old value for up to an hour after the change, a 24h TTL means up to a day. Some ISP resolvers ignore TTL and hold even longer.

A note on honesty (anycast)

Big resolvers like 1.1.1.1 and 8.8.8.8 are anycast, one IP served from hundreds of locations, so a single checker reaches the nearest one. This tool therefore reports by resolver operator, not by drawing a fake world map of countries. The signal that truly answers "is it live yet?" is your authoritative record vs each resolver's cache, which is exactly what this tool measures. For a single-resolver detail view use DNS Lookup.

Why isn't my DNS propagating?

The old TTL was high, so you are simply waiting it out.
You edited the record at the registrar but the domain uses different nameservers, so the edit went nowhere.
A CNAME points at a target whose own record has not updated.
For CDN or GeoDNS domains, different resolvers legitimately receive different IPs. That is geo-routing, not a propagation fault.

How to use DNS Propagation Checker

Enter your domain
Type the domain whose record you changed, for example example.com. No protocol prefix and no trailing slash.
Pick the record type
A or AAAA for a website move, CNAME for an alias, MX for mail, NS for a nameserver change, TXT for SPF/DKIM/DMARC, SOA for the zone's serial and refresh timers, CAA for certificate authority policy.
Run the check
Hit Check Propagation. The tool reads the authoritative value and queries the public resolvers in parallel, then compares each one.
Compare against authoritative
Each resolver line shows its cached answer and a match or differs verdict against your authoritative record, plus the TTL countdown.
Read the summary and wait the TTL
The Propagated X / Y line tells you how far the change has spread. If some resolvers differ because of a stale cache, wait until the lowest shown TTL expires and re-check.

Frequently Asked Questions

: DNS answers are cached by recursive resolvers for the duration of the record's TTL. After you change a record, every resolver keeps serving the old value until its cached copy expires, then fetches the new one from your authoritative nameservers. Propagation is just that staggered cache expiry playing out across the internet, it is not a single global push.

DNS

DNS Propagation Checker

Input

Terminal

About DNS Propagation Checker