SEOlust logo SEOlust
Domain, DNS & IP

DNS Propagation Checker

Check whether a DNS change has propagated across Cloudflare and Google resolvers. A, AAAA, CNAME, MX, TXT, NS. Runs in your browser. Free.

All tools

💡 How it works

  • Queries two major public resolvers — Cloudflare and Google — over encrypted DNS-over-HTTPS, straight from your browser.
  • If both resolvers return the same answer, your DNS change has propagated to them. Differences mean it is still rolling out or cached.
  • No server or API key involved — the lookups run entirely in your browser, with an 8-second timeout so it never hangs.

Free DNS Propagation Checker (Multi-Resolver)

Check whether a DNS change has propagated by querying two major public resolvers at once — Cloudflare and Google. Look up A, AAAA, CNAME, MX, TXT, or NS records and instantly see whether they agree. Free, no sign-up, and the lookups run right in your browser.

What this tool does

When you change a DNS record — pointing a domain to a new server, updating MX for email, or adding a TXT record for verification — the change does not reach every resolver instantly. This tool asks two widely used public resolvers (Cloudflare and Google) for the same record at the same time and shows their answers side by side, so you can tell whether your update has spread or is still rolling out.

How to use it

It is instant:

  • Enter your domain (with or without https://).
  • Pick the record type: A, AAAA, CNAME, MX, TXT, or NS.
  • Click Check.
  • Compare each resolver's answer and the overall match status.

Reading the results

Each resolver gets its own card showing the records it returned. If every resolver returns the same values, you will see a "consistent across resolvers" badge, which means your change has propagated to them. If the answers differ, the change is still spreading or an old value is cached — usually a matter of waiting for the record's TTL to expire.

Why DNS takes time to propagate

DNS relies on caching for speed: resolvers store a record for the length of its TTL (time to live) and keep serving the cached value until it expires. So after you edit a record, resolvers that cached the old value keep returning it until their cache times out. Lowering a record's TTL before a planned change makes future updates propagate faster.

Record types you can check

A and AAAA map a domain to IPv4 and IPv6 addresses; CNAME points one name at another; MX directs email to mail servers; TXT holds verification strings and policies like SPF; and NS lists the domain's authoritative name servers. Checking the right type helps you confirm exactly the change you made — for example verifying MX after switching email providers.

Privacy and how it works

The lookups are made directly from your browser to public DNS-over-HTTPS endpoints — there is no server in the middle and no API key. Nothing about your query is stored or logged by this tool. Because it queries global anycast resolvers rather than dozens of country-specific ones, treat it as a fast multi-resolver consistency check rather than a full worldwide map.

FAQ

Is this DNS propagation checker free?
Yes. It is completely free, needs no account, and runs the lookups directly in your browser.
Which resolvers does it query?
Two major public resolvers — Cloudflare (1.1.1.1) and Google (8.8.8.8) — over encrypted DNS-over-HTTPS, the two most reliable resolvers to query directly from a browser.
What does it mean when the answers match?
If all resolvers return the same records, your DNS change has propagated to them. Differences mean it is still spreading or an old value is cached.
How long does DNS propagation take?
It depends on the record's TTL and caching along the way — often minutes, but sometimes up to 24–48 hours. Lowering the TTL before a change speeds up future updates.
Which record types can I check?
A, AAAA, CNAME, MX, TXT, and NS records.
Does it need an API key?
No. It uses free public DNS-over-HTTPS endpoints directly from your browser, with no key or sign-up.
Why does my domain show "No CNAME record found"?
Because root or apex domains (like example.com) cannot have a CNAME record — the DNS specification forbids it, since the apex already holds SOA and NS records. CNAMEs live on subdomains, so check something like www.example.com or cdn.example.com instead of the bare domain.
Is this a full global propagation map?
It checks major global resolvers for a fast consistency check. It is not a country-by-country map, but for most changes it is enough to confirm propagation.

Related tools

Pro tip: pair this tool with Whois Lookup and Hyphen & Number Domain Checker for a faster SEO workflow.