Free DNS propagation checker

DNS propagation checker

Check whether a DNS change has spread. Four public resolvers are asked at once, with the TTL left on each answer.

CloudflareNorth AmericaGoogleEuropeAliDNSAsiaDNS.SBEurope!A record for example.com3 of 4 resolvers show the new value. DNS.SB updates in 42 min.

TTL

How long a change can take

You change the recordCloudflareGoogleAliDNSDNS.SBOld answer still cachedNew answer, once the TTL runs out
TTL on the old recordLongest a resolver can show the old answer
300 seconds5 minutes
3,600 seconds1 hour
14,400 seconds4 hours
86,400 seconds1 day
New nameservers at the registrarUp to 48 hours

Resolvers

The resolvers this checker asks

ResolverAddressNetwork
Cloudflare1.1.1.1Global anycast
Google Public DNS8.8.8.8Global anycast
AliDNS223.5.5.5Alibaba Cloud, China
DNS.SB185.222.222.222Independent, Europe

Each one is asked directly from your browser over HTTPS, so the answers are the ones those resolvers would give anyone right now.

DNS tools

More DNS tools

Look up every DNS record for a domain, or check the MX records that receive its mail.

FAQ

DNS propagation checker, answered

Anything we have not answered here, ask us directly. A senior engineer replies.

What is DNS propagation?

After you change a DNS record, resolvers around the world keep serving the old answer until their cached copy expires. Propagation is the time it takes for all of them to fetch the new one. Nothing is pushed out: each resolver updates when its TTL runs out.

How long does DNS propagation take?

Up to the TTL of the old record, which is often 5 minutes to 1 day. A change of nameservers at the registrar can take up to 48 hours, because the top-level domain servers cache the delegation too.

How do I check DNS propagation?

Enter the domain, choose the record type you changed, and press Check. The tool asks four public resolvers at once and shows whether they agree, with the TTL left on each cached answer.

Why do resolvers show different IP addresses for a big site?

Large sites and CDNs answer with a different address in each region on purpose, to send visitors to a nearby server. For those, a difference in A or AAAA records is normal and not a propagation problem.

Can I make DNS propagate faster?

Plan ahead. A day before the change, lower the TTL on the records you will change to 300 seconds. After the change, every resolver picks up the new value within 5 minutes. Raise the TTL again afterwards.

Dude Lemon

Contact Dude Lemon

Dude Lemon is a software development company. We build web apps, mobile apps and AI software for businesses.