DNS Propagation Checker
Changed a DNS record and wondering when the world will see it? This checker queries 30 public resolvers across the globe simultaneously and shows which ones return your new value and which still serve the old one.
How to use
- Enter your domain name.
- Select the record type you changed (A, MX, TXT…).
- Click Run to fan out to 30 resolvers worldwide and compare their answers.
DNS 'propagation' is really cache expiry. When you change a record, authoritative nameservers answer with the new value immediately, but millions of recursive resolvers worldwide keep serving their cached copy until the record's TTL runs out. Different resolvers cached at different moments, so for a while the internet disagrees about your domain: users behind one ISP reach the new server while others still hit the old one.
This checker makes that state visible by querying a spread of public resolvers, Google, Cloudflare, Quad9, OpenDNS, and regional resolvers across continents, in parallel. Consistent answers everywhere means propagation is done. A mix means you are mid-transition.
Practical guidance: before a planned migration, lower the TTL (to 300 seconds, say) a day in advance while the old TTL drains, make the change, then raise the TTL back once verified. If a specific resolver stubbornly serves stale data long past TTL, it may implement TTL floors, some resolvers refuse to honor very low TTLs.
Remember that your own machine adds two more cache layers, the OS and the browser. If this tool shows the new value everywhere but your browser still hits the old server, flush local DNS or test from a private window. The problem is on your device, not the internet.
Examples
Input: example.com (A)
Output: 30/30 resolvers return 93.184.215.14, propagation completeInput: yourdomain.in (A) after a change
Output: 22/30 resolvers return the new IP, 8 still serve the old value (cache TTL remaining)Frequently asked questions
How long does DNS propagation take?
Up to the record's TTL in the worst case, often minutes to a few hours in practice. The '24-48 hours' figure is outdated folklore except for nameserver (NS) changes at the registry level, which genuinely can take that long.
Can I speed up propagation?
Not after the fact, caches expire on their own schedule. Before the change, though, you can lower the TTL in advance so the world checks back more often once you flip the record.
Why do I still see the old site when this tool shows the new IP everywhere?
Your OS and browser cache DNS separately from public resolvers. Flush your local DNS cache (ipconfig /flushdns on Windows) or test in a fresh private window.
Which resolvers does the checker query?
30 well-known public resolvers spread across providers and regions, including Google (8.8.8.8), Cloudflare (1.1.1.1), Quad9, and OpenDNS, queried in parallel so a slow one does not delay the rest.
Related tools
Velona is India's INR-native AI API gateway with 300+ models, UPI top-up from ₹10, no foreign card needed. These tools are free forever.