DNS Diagnostics
Global DNS Propagation Checker & World Map
Monitor live DNS propagation across 25+ Anycast and regional DNS resolver nodes spanning North America, Europe, Asia-Pacific, Latin America, and the Middle East. When you update DNS records, changes don't instantly reach all resolvers worldwide — propagation depends on your previous record's TTL value and how quickly each resolver refreshes its cache. Verify DNS record updates globally with real-time SSE streaming.
Key Capabilities & Features
dnsfyi combines high-speed global Anycast DNS queries with comprehensive security auditing into a unified diagnostic suite.
- • Live Server-Sent Events (SSE) streaming with sub-second node updates
- • 25+ worldwide resolver nodes across 5 continents
- • Interactive SVG world map with match/stale visual indicators
- • Filter by record type (A, AAAA, MX, CNAME, TXT, NS)
- • Expected vs actual value comparison with diff highlighting
- • Export propagation results as JSON for audit documentation
How to Use This Tool
To audit any domain or IP address, enter the hostname into the search box to run an instant parallel multi-resolver inspection.
- Enter the domain name and select the DNS record type you want to track (A, MX, TXT, etc.).
- Enter the expected value you're waiting for (the new IP address or record value after your DNS change).
- Click Start — nodes across 25+ global locations will be queried in real time.
- Green nodes have already received the updated record. Gray nodes still show the old value.
- Wait until all (or most) nodes turn green to confirm global propagation is complete.
Frequently Asked Questions
Find direct answers about dnsfyi's multi-resolver query engine, privacy policy, domain security checks, and free REST API.
- How long does DNS propagation take?
- DNS propagation time depends entirely on the TTL (Time To Live) value of the record being changed. If your old record had a TTL of 86400 (24 hours), resolvers can cache the old value for up to 24 hours before querying again. To speed up propagation, lower your TTL to 300 seconds at least 24 hours before making the change.
- My DNS change shows propagated in some countries but not others — is that normal?
- Yes, this is completely normal. Different resolvers refresh their cache at different times based on when they last queried your record relative to the TTL expiry. Geographic distance and network topology also play a role. Partial propagation is expected during the transition window.
- What is GeoDNS and how does it affect propagation checking?
- GeoDNS (geographic DNS) intentionally returns different IP addresses based on the resolver's geographic location. For example, US users might get a US server IP while EU users get a Frankfurt IP. This is not a propagation issue — it's by design. Your propagation checker results will legitimately vary by region.
- Why do I still see the old IP after 48 hours?
- If propagation hasn't completed after 48 hours: (1) Verify the change was actually saved at your DNS registrar/provider. (2) Check if there's a secondary DNS server not receiving the zone update. (3) Some ISPs override TTL and aggressively cache records. (4) Try querying with 'dig @1.1.1.1 yourdomain.com' to bypass your local resolver.