DNS Propagation Checker
Changed a DNS record? Ask 19 public DNS resolvers in the US, Europe and Asia at once and see which ones already return the new value.
- Checked liveReal-time results fetched from the public internet
- Nothing storedWe don't keep what you check or the results
- 100% freeNo signup, no trial, no hidden limits
- No accountOpen the page and get your answer
How to use the DNS Propagation Checker
- Enter the domain or subdomain you changed (for example www.example.com).
- Choose the record type: A, AAAA, CNAME, MX, NS or TXT.
- Optionally type the value you expect, such as your new server IP.
- Click Check propagation: the result shows how many resolvers agree, a ✓ or ✗ for every resolver with its location and answer, and a world map with a pin for each one.
- Waiting for a change? Turn on Re-check every minute: it checks again by itself and stops once every resolver agrees. Copy the results or the link to share them.
Guides for DNS Propagation Checker
All →
Website ToolsWhy your emails go to spam, and how to fix it
Emails going to spam? Learn how SPF, DKIM and DMARC, reverse DNS, Gmail and Yahoo sender rules, content and list hygiene decide the inbox…
12 Nov 20266 min read
SEO & MarketingWhy LinkedIn shows no preview for your link
LinkedIn post preview not showing? Learn which og: tags LinkedIn needs, its image size rules, why it may be blocked, and how Post Inspector…
12 Nov 20265 min read
SEO & MarketingHow to make Facebook refresh an old link preview
Use a Facebook Sharing Debugger refresh to update an old link preview: the exact steps, why the old image can stick, and what to do when…
12 Nov 20264 min readFrequently asked questions
How long does DNS propagation take?
Usually minutes to a few hours. A resolver keeps a cached record until its TTL expires, so the worst case is roughly the old record's TTL — up to 24–48 hours if it was set very high. Lowering the TTL a day before a planned change speeds things up.
Why do some resolvers still show the old value?
They cached the record before you changed it and will keep serving it until the cached TTL runs out. There is nothing to fix — check again later, or compare the TTL column to see how long remains.
Why do resolvers return different IPs even though I didn't change anything?
Services behind a CDN or geo-DNS (Cloudflare, AWS, Google and many others) deliberately return different addresses depending on where the request comes from. Different answers are only a problem if one of them is your old server.
Can I make DNS propagate faster?
You can't flush other people's caches, but you can lower the record's TTL (e.g. to 300 seconds) well before a change, make the change, and raise the TTL again once everything has updated. Some public resolvers, like Google and Cloudflare, also offer a cache purge page.
What does NXDOMAIN or "No answer" mean here?
NXDOMAIN means the resolver believes the name doesn't exist — common right after registering a new domain or adding a new subdomain. "No answer" means the name exists but has no record of the type you chose.