Has my DNS update gone live?
Check if your DNS changes have reached major resolvers around the world.
How long does DNS propagation take?
When you change a DNS record, your old record has a TTL (Time To Live) value — the number of seconds resolvers are allowed to cache it. Until that TTL expires, many resolvers will continue serving the old value. A TTL of 3600 means up to 1 hour; some domains use 86400 (24 hours) or more.
To speed up propagation before a planned change, lower your TTL to 300 seconds (5 minutes) a day or two in advance. Once the change is live and confirmed, you can raise the TTL again for better performance.
This tool checks your DNS record across six independent global resolvers — Google, Cloudflare, Quad9, OpenDNS, AdGuard, and ControlD — and reports the value each one returns. If they all agree, your change has fully propagated. If they show different values, propagation is still in progress.
Frequently Asked Questions
Why do different resolvers show different values?
Each resolver caches DNS records independently based on the TTL at the time they last looked it up. If one resolver cached your old record 10 minutes ago with a 1-hour TTL, it won't fetch the new value for another 50 minutes — even if every other resolver has already updated. This is normal and expected during propagation.
Why is my site down even though propagation looks complete here?
Your ISP or office network may be using a DNS resolver not in our list. You can check the resolver you're personally using by looking at your network settings, or temporarily switch to a public resolver like Google (8.8.8.8) or Cloudflare (1.1.1.1) to see your site with the latest DNS.
What TTL should I use for my DNS records?
For stable records (like an A record pointing to a server that rarely changes), a TTL of 3600 (1 hour) or 86400 (24 hours) reduces DNS lookup overhead. For records that might change during a migration or incident, lower it to 300 (5 minutes) beforehand. Most DNS providers let you change TTL instantly, but the effect only kicks in once the previous TTL expires.
Does DNS propagation affect email as well as websites?
Yes. MX records (which route email) and SPF/DKIM/DMARC records (email authentication) all propagate through DNS in the same way. If you've updated your email provider or added new email authentication records, use this tool with the MX or TXT record type to verify they've propagated globally before expecting email to work reliably.