Check DNS propagation and records across 38+ global DNS servers as they update
DNS propagation is the time it takes for DNS changes to spread across the internet's network of servers. When you update your domain's DNS records—like pointing your website to a new host or changing your email server—those changes don't happen instantly everywhere. Think of it like updating your phone number; it takes time for everyone in your contact list to get the new number.
The delay happens because DNS servers cache your domain information to make the internet faster. Each record has a Time-To-Live (TTL) value that tells servers how long to remember that information before checking for updates. If your TTL is set to 24 hours, some servers might keep showing the old information for a full day before they grab the updated version.
Propagation typically takes anywhere from a few minutes to 48 hours, though most changes spread within a few hours. During this time, different people around the world might see different versions of your DNS records depending on which server their device is asking. That's why our DNS checker is handy—it lets you see exactly what different DNS servers worldwide are reporting for your domain right now.
Type your domain name (like example.com) into the search box. You don't need to include "http://" or "www" - just the domain itself. Select the DNS record type you want to check from the dropdown menu next to the domain field.
Hit the "Search" button and watch as our tool queries DNS servers from over 20 global locations at once. Results pop up as each server responds, showing you DNS propagation status across the world.
Review the results to see which servers have your updated records. Use the continent and country filters to focus on specific regions. Export results as CSV or JSON for documentation, or use the Expected Value feature to highlight matching records.
Moving your website to a new hosting provider? A DNS checker shows you when the switchover is complete. Watch as servers worldwide start pointing to your new host's IP address.
If some users can reach your site but others can't, it's often a DNS issue. Our checker helps identify which regions or servers are still showing old DNS information.
Changed your MX records for email delivery? Verify that mail servers globally can find your new email configuration and prevent missed emails during transitions.
Check DNS records from multiple continents and countries simultaneously. See how your domain resolves in different parts of the world at the same time.
After updating CAA records for SSL certificates, confirm they've propagated correctly across DNS servers to avoid certificate issuance problems.
Use auto-refresh to monitor DNS changes as they happen. Set an interval and watch as your DNS records propagate across global servers automatically.
Maps your domain name to an IPv4 address. When someone types your website URL, the A record tells their browser which server to connect to. This is the most fundamental DNS record type.
Similar to A records but for IPv6 addresses. As the internet transitions to IPv6, these records become increasingly important for ensuring your site is accessible via the newer protocol.
Creates an alias that points one domain to another. Commonly used for "www" subdomains or when you want multiple names to point to the same location without managing multiple A records.
Directs email to the correct mail server. Without proper MX records, emails sent to your domain won't reach their destination. You can have multiple MX records with different priorities for backup servers.
Stores text information for various purposes like domain verification, SPF records for email authentication, DKIM signatures, and site validation. Essential for email security and service verification.
Specifies which nameservers are authoritative for your domain. These servers hold the actual DNS records and are queried when someone looks up your domain information.
When you see a green background with a checkmark, that DNS server successfully resolved your domain and found a record. The displayed value is what that particular server is currently reporting.
A red background with an X means that server couldn't find a DNS record for your query. This could mean the record doesn't exist, hasn't propagated yet, or there's a configuration issue.
The blue spinning circle means we're still querying that DNS server. Results come in progressively, so you'll see this briefly before each server reports back.
The "Resolved DNS" counter shows how many servers successfully found your record. If it's not 100% yet, your changes are still propagating across the global DNS network.
If your DNS changes aren't showing up anywhere after several hours, double-check that you actually saved the changes at your domain registrar or DNS hosting provider. Sometimes changes get entered but not saved. Also verify you're checking the correct domain name.
Seeing some servers with old data and some with new? That's normal during propagation. The servers showing old data will eventually refresh based on your TTL settings. Lower TTL values speed up future propagation but cause more DNS queries.
If every single DNS server returns an error, your domain might not be properly configured. Check that your nameservers are set correctly at your registrar, and that your DNS hosting provider has the records you think they do.
Your computer caches DNS responses too. Even if our checker shows new DNS records everywhere, your local cache might still have old data. Flush your DNS cache (ipconfig /flushdns on Windows, sudo killall -HUP mDNSResponder on Mac) to force your computer to fetch fresh DNS data.
If propagation is taking longer than 48 hours, check your TTL settings. Some providers set very high TTL values (like 86400 seconds, which is 24 hours). Servers will cache your old records for that entire period before checking for updates.