Propagation, resolver by resolver
Every resolver keeps its own cache, so a change reaches some parts of the world before others. Green rows already see the new record; grey rows are still serving the old one.
Has your DNS propagated yet?
Check any DNS record against resolvers around the world and see exactly where a change has landed.
- 10 resolvers worldwide
- A, AAAA, CNAME, MX, NS, TXT, SOA and CAA
- Authoritative answer included
- Instant, no sign-up
*Answers come live from each resolver; nothing is cached on our side
What the DNS checker tells you
The authoritative answer
We also ask one of the domain’s own nameservers directly. That is the record as it is set right now, before any cache, so you can confirm a change was saved even while it is still propagating.
Why it takes time
Each record has a TTL (time to live) that tells resolvers how long to keep a copy. Until that timer runs out they answer from memory. Lower the TTL before a planned change and most of the internet will follow within minutes.
Tired of waiting for DNS to propagate?
Our DNS is built so changes land fast and stay reliable:
Global anycast DNS
Your records are served from locations on every continent, so visitors always reach the closest one and answers come back in milliseconds.
Changes within minutes
Low default TTLs and instant updates at our nameservers mean most of the internet sees your change within minutes, not days.
One simple editor
Add A, CNAME, MX, TXT and SRV records from a clean panel with validation, so a typo never takes your email or website down.
DNSSEC and DDoS protection
Sign your zone with one click and rely on always-on protection against attacks that would knock a smaller DNS provider offline.
Engineers who speak DNS
Not sure which record to change? Our support team sets it up with you, by chat or ticket, at any hour.
DNS checker FAQ
When you change a DNS record, the update is saved at your nameservers immediately, but resolvers around the world keep a cached copy of the old record until its TTL expires. Propagation is the period while some resolvers still answer with the old value. This tool shows you which ones have caught up.
Usually from a few minutes to a few hours, and up to 48 hours in the worst case. It depends on the TTL of the record you changed and on how each resolver handles caching. Nameserver (NS) changes at the registry are the slowest because the parent zone’s TTL is often 24–48 hours.
No, that is propagation in progress. As long as the authoritative answer at the top shows the new value, the change was saved correctly and the remaining resolvers will follow when their caches expire.
The resolver answered, but the domain has no record of that type. For example, a domain that only has an A record will show “no record” for AAAA. If you expected a record to exist, check it was added at the right hostname and that you picked the right type.
The resolver did not answer within three seconds, refused the query or is blocked from where our server runs. It is not a problem with your domain; try again in a moment or ignore that row.
A for the IPv4 address of your website, AAAA for IPv6, CNAME for aliases such as www, MX for email delivery, TXT for SPF, DKIM, DMARC and verification codes, NS for your nameservers, SOA for the zone’s serial number and CAA for which certificate authorities may issue SSL for the domain.
Yes. Type the full hostname, for example mail.yourbrand.com or www.yourbrand.com, and pick the record type. The authoritative check finds the right zone automatically.
Lower the TTL of the record to 300 seconds (5 minutes) at least a day before you make the change, wait for the old TTL to expire, then update the record. Most resolvers will pick up the new value within minutes. Raise the TTL again afterwards.
