Nomlen logo
dns propagation· 4 resolvers · 6 record types · free

DNS propagation checker

Check DNS records across Google, Cloudflare and Quad9 resolvers — and spot stale caches.

Queries Google, Cloudflare, Quad9 and our server resolver for A, AAAA, CNAME, MX, TXT and NS records — 10 free checks per day.

Enter a domain

Type any domain name above and hit check.

We query 4 resolvers

Google, Cloudflare, Quad9 and our own server, live.

Spot mismatches

See instantly which resolvers still serve stale DNS.

What you get

See your DNS from everywhere.

After a DNS change, different servers answer differently for hours. Check all major resolvers side by side and know exactly when your change is live worldwide.

4 global resolvers

Queries Google Public DNS, Cloudflare, Quad9 and our own server resolver — so you see what users in different networks actually get.

6 record types

A, AAAA, CNAME, MX, TXT and NS records in one view. Switch tabs to inspect mail routing, verification tokens, or nameservers.

Mismatch detection

If resolvers disagree on your A records, we flag it immediately — the classic sign that propagation is still in progress.

Free, no signup

Ten full propagation checks per day, completely free. No account, no email, no tracking — just answers.

Keep exploring

Related free tools

Bulk Domain Search

Check availability for hundreds of domains at once.

Try it

Bulk WHOIS Check

WHOIS data for many domains in one pass.

Try it

DNS Checker

Look up A, MX, TXT, NS and more DNS records instantly.

Try it
Stop second-guessing.

Find your domain in the next 30 seconds.

Free forever. No login required. 1,100+ TLDs in one query — plus AI suggestions and the premium marketplace.

Start checking now Learn more
1,147
TLDs
200ms
Avg lookup
100
Suggestions/query
FAQ

DNS propagation, explained.

When you change a DNS record, the update has to spread to thousands of servers worldwide. Each server caches the old value until its TTL expires, so different resolvers can return different answers for hours — that's propagation.
Typically minutes to a few hours, but it can take up to 48 hours in the worst case. It depends on the TTL you set on the old record, the resolver's caching policy, and your ISP. Lower TTLs before a planned change speed things up.
Each resolver caches independently. Google's resolver may have picked up your new IP while Cloudflare's still serves the cached old one. If all resolvers agree, your change is fully live; if they disagree, propagation is still in progress.
A (IPv4), AAAA (IPv6), CNAME (aliases), MX (mail servers), TXT (verification and SPF/DKIM records) and NS (nameservers) — the six records people check most after a DNS change.
Your browser, operating system, or ISP may be caching the old DNS result or the old page itself. Try a hard refresh, clear your DNS cache (ipconfig /flushdns on Windows, dscacheutil -flushcache on macOS), or check from a different network.
Ten full propagation checks per day per visitor, free, with no account required. Each check runs live queries against four resolvers, which is why the limit exists.
You cannot force other servers to update early, but lowering the record's TTL a day or more before a planned change makes the next change take effect much faster.
Yes, if you change MX or email-authentication records. Until resolvers pick up the new records, some mail can route to the old server or fail authentication checks.
It means propagation is still in progress: those resolvers have refreshed their cache while others still hold the old value until its TTL expires. It normally resolves on its own.
Yes, if you can plan ahead. Dropping the TTL to a low value (for example 300 seconds) at least one full old-TTL cycle before the change makes the switch visible worldwide much sooner.