DNS Propagation Checker - DNS Spy

What is DNS and How Does It Work?

The Domain Name System (DNS) is the internet's address book. It translates human-readable domain names like example.com into machine-readable IP addresses like 93.184.216.34. Without DNS, you'd need to memorize a string of numbers for every website you visit.

When you type a domain name into your browser, your device initiates a DNS lookup — a chain of requests that passes through several types of servers to find the correct IP address. The process involves four key server types:

Once the IP address is resolved, it's cached by the recursive resolver for the duration specified by the record's Time to Live (TTL). This caching is what makes DNS fast — but it's also what causes DNS propagation delays when records change.

What Happens When You Visit a Website? (DNS Lookup Step by Step)

Here's the full chain of events when a user visits www.example.com for the first time, with no cached DNS data. Each step is a potential point where DNS propagation delays can occur:

On subsequent visits, steps 3–8 are skipped entirely — the recursive resolver returns the cached answer immediately. This is why DNS changes aren't instant: the cached answer is served until the TTL expires.

What is DNS Propagation?

DNS propagation is the process by which updated DNS records spread across the worldwide network of recursive resolvers. When you change a DNS record — such as updating an A record to point to a new IP address, switching MX records to a new email provider, or changing nameservers entirely — that change doesn't take effect everywhere at once.

The update starts at your authoritative DNS server and gradually spreads as cached copies of your old records expire on recursive resolvers around the world. Each resolver holds onto the previous version of your DNS records until the cached copy reaches the end of its Time to Live (TTL), at which point it fetches the fresh record from the authoritative server.

During this propagation window, some users will see the new records while others still receive the old ones — depending on which resolver they use and whether that resolver's cache has expired. This is why a website migration can appear to work for some visitors but not others, or why email starts flowing to the new server for some recipients while others still deliver to the old one.

While technically DNS records don't "propagate" in the traditional sense (they're not pushed out to servers), the term DNS propagation is universally used to describe this cache-expiry-and-refresh cycle. A DNS propagation checker lets you see exactly which resolvers around the world have picked up your changes and which are still serving stale cached data.

How Long Does DNS Propagation Take?

DNS propagation typically takes anywhere from a few minutes to 48 hours, though most changes propagate within 1–4 hours. The actual time depends on several factors:

💡 Rule of thumb: Simple A record changes with a low TTL propagate within minutes. MX and TXT record changes typically complete within 1–4 hours. Nameserver changes at the registrar level can take up to 48 hours. Use this DNS propagation checker to monitor progress in real-time rather than guessing.

How Does This DNS Propagation Checker Work?

DNS Spy's propagation checker queries your domain against 40+ public DNS resolvers distributed across the globe. Each resolver is queried independently and in parallel from multiple geographic vantage points, giving you a comprehensive, real-time view of how your DNS changes are spreading worldwide.

For each resolver, we show you:

• ✅ Resolved value — the IP address, hostname, or other record data returned
• ⏱️ TTL remaining — how long until this resolver's cache expires and fetches fresh data
• ⚡ Response time — how fast the resolver responded, in milliseconds
• 🌍 Geographic location — city, country, and provider for each resolver
• 🔄 Per-resolver refresh — re-check any individual resolver without re-running the entire global check

Results are displayed on an interactive world map with color-coded markers so you can see geographic propagation patterns at a glance. Unlike other propagation checkers that query resolvers from a single server, DNS Spy queries from multiple geographic vantage points worldwide — giving you a more accurate picture of what users in different regions are actually experiencing.

Which DNS Record Types Can Be Checked?

DNS uses different record types to store different kinds of information about a domain. You can check propagation for all of the following record types and more:

These 10 common types are shown by default. Click "Show all record types" to access 35+ additional types including DNSKEY, DS, TLSA, SSHFP, HTTPS, SVCB, and more — making this the most comprehensive DNS propagation checker available.

Why Is My DNS Not Propagating?

If your DNS changes aren't showing up after the expected time, here are the most common causes and how to fix them:

How to Speed Up DNS Propagation

While you can't force every resolver in the world to update simultaneously, these proven strategies minimize propagation time:

1. 1

   Lower your TTL in advance

   24–48 hours before making a DNS change, reduce the TTL to 300 seconds (5 minutes). By the time you make the actual change, most resolvers will already have short-lived caches. This is the single most effective technique.

2. 2

   Verify the change at the source

   Before waiting for propagation, query your authoritative nameserver directly to confirm the new record is actually live. If it's not correct at the source, it can't propagate anywhere.

3. 3

   Monitor with a propagation checker

   Use this tool to watch which resolvers have updated in real-time. You may find propagation is effectively complete even if 1–2 outlier resolvers still cache old data.

4. 4

   Flush your local DNS cache

   If global propagation looks complete but your machine still shows old results, flush your local DNS cache and restart your browser. Your device's cache is separate from the resolver network.

5. 5

   Raise TTL back after propagation

   Once propagation is complete and the new records are working correctly, raise your TTL back to a reasonable value (3600–86400) to reduce query load on your nameservers and improve resolution speed for end users.

Make Sure to Check All Your DNS Records

When verifying DNS changes, remember that most domains have multiple record types that need to be correct. A website migration might involve changing A records, but you'll also want to verify:

• A and AAAA records for both the root domain (example.com) and www subdomain
• MX records if you're also migrating email services
• TXT records for SPF, DKIM, and DMARC email authentication
• CNAME records for any subdomains (blog, app, api, etc.)
• NS records if you changed nameservers at the registrar
• CAA records if you need to ensure SSL certificate issuance works with the new provider

Use the record type dropdown above to check each type independently. You can also use our free domain scanner to get a complete overview of all DNS records for any domain, or our CAA record validator to verify your certificate authority authorization setup.

Frequently Asked Questions

Stop Checking Manually — Let DNS Spy Monitor Your Domains 24/7

This free DNS propagation checker gives you a snapshot at a point in time. But what about the other 23 hours a day when you're not watching? DNS records can change unexpectedly due to misconfigurations, expired domains, hijacking attempts, or provider outages — and you might not find out until customers start complaining.

DNS Spy continuously monitors your domains and alerts you the moment any DNS record changes — before your customers notice. Track A, AAAA, MX, NS, TXT, CAA, and dozens of other record types across all your domains with automatic change detection, security checks, SSL certificate monitoring, and detailed history.