DNS Propagation Checker — Check DNS Propagation Worldwide
Free DNS propagation checker to test DNS changes across 30+ global servers. Monitor DNS propagation time, verify updates, and see how long DNS propagation takes with our interactive world map.
Advertisement
Fastest Public DNS Providers
Top 6 DNS servers ranked by average query speed
Google DNS9.96ms
Google DNSPrimary:
8.8.8.8
Secondary:
8.8.4.4
Comodo DNS12.66ms
Comodo DNSPrimary:
8.26.56.10
Secondary:
8.26.56.26
OpenDNS15.6ms
OpenDNSPrimary:
208.67.220.220
Secondary:
208.67.222.220
Alibaba15.98ms
AlibabaPrimary:
223.6.6.6
Secondary:
223.5.5.5
Quad9 DNS21.99ms
Quad9 DNSPrimary:
149.112.112.13
Secondary:
9.9.9.9
Cloudflare25.47ms
CloudflarePrimary:
1.1.1.1
Secondary:
1.0.0.1
DNS Propagation Checker — Monitor DNS Changes Worldwide
DNS Robot is a free DNS propagation checker that lets you verify how DNS record changes are spreading across the internet. When you update your domain’s DNS records — whether changing A records, MX records, nameservers, or any other DNS record — those changes don’t appear instantly worldwide. Our DNS propagation checker queries 30+ DNS servers across 6 continents to show you exactly where your changes have propagated and where they haven’t.
Unlike basic DNS lookup tools that query a single server, DNS Robot performs a global DNS check with simultaneous queries to Google DNS (8.8.8.8), Cloudflare (1.1.1.1), OpenDNS, Quad9, and regional ISP resolvers across North America, Europe, Asia, South America, Africa, and Oceania. Each result includes the actual response time in milliseconds, giving you a comprehensive view of worldwide DNS propagation status.
Why Use DNS Robot for DNS Checking?
30+ Global DNS Servers
Query DNS servers across North America, Europe, Asia, South America, Africa, and Oceania simultaneously
Real-time Response Times
See actual DNS response times in milliseconds from each server for performance monitoring
12 DNS Record Types
Check A, AAAA, CNAME, MX, NS, TXT, SOA, PTR, SRV, CAA, DNSKEY, and DS records
Interactive World Map
Visualize DNS propagation status on an interactive map showing each server location
How to Check DNS Propagation
1
Enter Your Domain
Type the domain name you want to check (e.g., example.com). For PTR lookups, enter an IP address instead.
2
Select DNS Record Type
Choose the record type: A, AAAA, CNAME, MX, NS, TXT, SOA, PTR, SRV, CAA, DNSKEY, or DS. Default is A record for IP address lookup.
3
View Propagation Results
See results from 30+ DNS servers worldwide with response times, resolved IPs, and propagation status on an interactive map.
How Long Does DNS Propagation Take? (Complete Guide)
DNS propagation typically takes 24 to 48 hours, though most changes propagate within 4–24 hours. The exact DNS propagation time depends on three factors: (1) the old TTL value cached by resolvers, (2) ISP caching behavior, and (3) whether you changed nameservers (24–48 hours) or individual records (minutes to hours). A record change with a 3,600-second (1 hour) TTL typically finishes propagating within 1–2 hours worldwide.
DNS propagation time varies by the type of change, TTL values, and worldwide DNS resolver caching. Here’s a complete breakdown of typical DNS propagation times by record type:
A / AAAA Record Change (5 minutes – 24 hours)
Changing your domain’s IP address typically propagates within the old TTL period. If your TTL was 3600s (1 hour), most servers will update within 1-2 hours. Use a low TTL before migrating servers.
Check Domain IPMX Record Change (1 – 24 hours)
Mail server changes follow TTL-based propagation. During propagation, emails may be delivered to both old and new servers. Always verify with our propagation checker before decommissioning old servers.
MX LookupNameserver Change (24 – 48 hours)
Nameserver changes require TLD registry updates, which is the slowest type of DNS propagation. The .com/.net registry updates every 15 minutes, but ISP caching adds significant delay.
NS LookupTXT Record (SPF/DKIM/DMARC) (5 minutes – 4 hours)
Email authentication records typically have lower TTL values. Verify propagation before enforcing strict DMARC policies to avoid email delivery failures.
SPF CheckerCNAME Record Change (5 minutes – 24 hours)
Alias record changes propagate at the TTL rate. Note that CNAME chains add latency — each hop requires a separate DNS resolution during propagation.
CNAME LookupNew Domain Registration (12 – 48 hours)
Newly registered domains need time for the registrar to create zone files and for root nameservers to recognize the new domain across the global DNS infrastructure.
Domain CheckerDNS Propagation Time by Registrar
Each registrar uses slightly different TTL defaults and zone update intervals. Below are typical DNS propagation times by provider — minimum, typical maximum, and notes. Actual times depend on TTL set on your records.
| Registrar | Min Time | Typical Time | Notes |
|---|---|---|---|
| GoDaddy | 1 hour | 4–24 hours | Default TTL is 1 hour. Nameserver changes can take 24–48 hours. |
| Namecheap | 30 min | 4–8 hours | Fast on record changes; nameserver updates take up to 48 hours. |
| Cloudflare | < 5 min | 5–15 min | Record changes propagate within minutes thanks to 5-minute TTL defaults and Cloudflare’s global anycast. |
| Google Domains / Squarespace | 1 hour | 1–24 hours | Default TTL is 1 hour. Nameserver changes use standard 24–48 hour window. |
| AWS Route 53 | 1 min | 2–10 min | Route 53 uses 60-second TTL on many records; propagation is among the fastest in the industry. |
| Namesilo | 1 hour | 2–24 hours | 3,600-second default TTL. Record changes usually live within a few hours. |
| Porkbun | 10 min | 10 min – 2 hours | 600-second default TTL makes Porkbun record updates very fast. |
| Name.com | 1 hour | 4–24 hours | Standard 3,600-second TTL; nameserver migration takes the full 24–48 hour window. |
| Hover | 30 min | 4–12 hours | Moderate TTL defaults. Good for most small-site migrations. |
| IONOS / 1&1 | 1 hour | 4–24 hours | Default TTL is 3,600 seconds. Some users report slower-than-average propagation on nameserver changes. |
How to Speed Up DNS Propagation
You cannot directly force global DNS resolvers to drop their caches, but you can speed up DNS propagation for your own changes by lowering TTL before the migration and flushing caches afterwards.
- Lower TTL 48 hours before the change
Set your record TTL to 300 seconds (5 min) at least 48 hours before making DNS changes. Resolvers will cache the low-TTL value, so when the real change lands, it propagates within minutes instead of hours.
- Wait for the old TTL to expire
If the old TTL was 86,400s (24 hours), you must wait the full 24 hours for resolvers to re-request your records. Don’t change records until this window passes — otherwise some resolvers serve stale data until the old TTL expires.
- Make the DNS change
Update your A record, MX record, nameservers, or other record at your registrar. The new value is now authoritative.
- Flush your local DNS cache
Your own machine caches DNS queries too. Run
ipconfig /flushdns(Windows),sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder(macOS), orsudo systemd-resolve --flush-caches(Linux) to see the new records immediately. - Verify with our DNS propagation checker
Use the checker above to confirm that 30+ global servers return the new value. Green markers = propagated, yellow = variant, red = still serving old or unreachable.
- Raise TTL back to normal after propagation
Once all servers show the new value, raise TTL back to 3,600s or 86,400s to reduce DNS query overhead. Leaving TTL at 300s wastes resolver bandwidth and can slow page-load times slightly.
How to Force DNS Propagation (Flush Your DNS Cache)
Your computer and router both cache DNS responses. When you update a domain and the old value keeps showing, the cache is usually at fault — not global propagation. Use these commands to force DNS propagation locally by flushing your DNS cache:
Windows (Command Prompt)
ipconfig /flushdnsOpen Command Prompt as Administrator, then run the command. You should see “Successfully flushed the DNS Resolver Cache.”
macOS (Terminal)
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderRun both commands together. macOS requires restarting `mDNSResponder` for the flush to take effect. Enter your admin password when prompted.
Linux (systemd-resolved)
sudo systemd-resolve --flush-cachesFor Ubuntu 18.04+, Fedora, and other systemd-based distros. Older systems using nscd: `sudo service nscd restart`.
Linux (dnsmasq)
sudo systemctl restart dnsmasqIf your system uses dnsmasq (common on Raspberry Pi or older setups), restart the service to flush all cached DNS records.
Google Chrome
chrome://net-internals/#dnsPaste into Chrome’s address bar, click “Clear host cache,” then click “Flush socket pools” as well. Chrome maintains its own DNS cache separate from the OS.
Firefox
about:networking#dnsFirefox also caches DNS. Paste the URL and click “Clear DNS Cache.” Restarting the browser works too.
Router
Reboot router (power cycle)Home routers often cache DNS for all devices. A simple reboot clears the router DNS cache. Check your router admin panel for a direct DNS cache flush option.
Why Is My Website Still Showing the Old Version After a DNS Change?
If your DNS propagation checker shows the new record globally but your own browser still loads the old site, DNS isn’t the culprit — it’s caching further down the stack. Check these five layers in order:
- Browser DNS cache
Your browser (Chrome, Firefox, Safari) maintains a separate DNS cache from your OS. Clear it via
chrome://net-internals/#dnsor restart the browser entirely. - Browser page cache
Even after DNS updates, your browser can serve the old HTML/CSS/JS from cache. Hard-refresh with
Ctrl+Shift+R(Windows/Linux) orCmd+Shift+R(Mac) to bypass. - Operating system DNS cache
Windows, macOS, and Linux each maintain a system-level DNS cache. Use the flush commands above to clear it.
- Router DNS cache
Your home/office router caches DNS for all connected devices. Power-cycle the router or flush via its admin panel.
- CDN and reverse-proxy cache
If you use Cloudflare, Fastly, or a CDN, they cache HTML and assets at the edge. Purge the CDN cache through your dashboard (Cloudflare: *Caching → Purge Everything*).
- Server-side / WordPress cache
Page caching plugins (WP Rocket, W3 Total Cache) serve pre-rendered HTML. Clear the plugin’s cache in WP admin after any change.
What Is DNS Propagation and Why Is DNS Not Propagating?
How DNS Propagation Works
When you change DNS records at your domain registrar or hosting provider, the update first goes to your domain’s authoritative nameservers — the servers listed in your domain’s NS records that hold the master copy of your zone file. However, DNS resolvers worldwide (like Google’s 8.8.8.8 or Cloudflare’s 1.1.1.1) cache DNS records based on the TTL (Time To Live) value baked into each record. Until the cached record expires, recursive resolvers continue serving the old data to web browsers and applications that query them.
Every recursive resolver on the internet caches independently. When a user’s web browser requests your domain, its OS asks the configured DNS resolver; if the resolver has a fresh cached record (TTL hasn’t expired), it returns the cached value without re-querying your authoritative nameserver. This is by design — it reduces global DNS query load by 99%+ — but it means your update only becomes visible to each resolver as its individual TTL expires.
DNS propagation is the cumulative process of every resolver’s cache expiring and re-fetching fresh records from your authoritative nameservers. Our DNS propagation checker queries 30+ global resolvers simultaneously so you can see exactly which locations have picked up the new value and which are still serving stale data.
Why Is My DNS Not Propagating?
If your DNS is not propagating, the most common cause is high TTL values. Common TTL values: 300s (5 min) for fast changes, 3600s (1 hour) for standard records, 86400s (24 hours) for stable records. If your old records had a 24-hour TTL, resolvers will serve cached data for up to 24 hours regardless of your update.
Other reasons DNS might not propagate: incorrect record syntax at your registrar (trailing dot missing on CNAME targets is the #1 cause), nameserver delegation issues where the TLD registry hasn’t picked up your NS change yet, or ISPs that ignore TTL values and cache longer than specified (common with large US cable ISPs). Registry processing itself takes 15 minutes on .com/.net but up to 48 hours on country-code TLDs.
Pro tip: Before making DNS changes, lower your TTL to 300 seconds and wait for the old TTL to expire. After confirming propagation with our DNS propagation checker, raise TTL back to a higher value. Also verify your changes saved correctly in the registrar’s control panel — some panels fail silently on syntax errors.
Common DNS Issues and How to Fix Them
Slow DNS Propagation
If changes aren’t showing after hours, check your TTL values. High TTL (86400s) means resolvers can cache old records for up to 24 hours. Lower your TTL before making changes.
Check propagation statusNXDOMAIN — Domain Not Found
This error means the domain doesn’t exist in DNS. Check for typos, verify the domain is registered, and ensure nameservers are properly configured at your registrar.
Check domain availabilityEmail Not Working After DNS Change
Email issues after DNS changes often relate to MX records. Also verify SPF, DKIM, and DMARC records to prevent delivery issues.
Run domain health check50+ Free DNS, Network & Domain Tools
Beyond DNS propagation checking, DNS Robot offers a comprehensive suite of free tools for DNS management, email security, network diagnostics, and more.
DNS Tools
- DNS Lookup — Check all DNS records
- Domain IP Lookup — Find domain IPs
- NS Lookup — Find nameservers
- MX Lookup — Mail server records
- CNAME Lookup — Trace CNAME chains
- Reverse DNS — IP to hostname
- Domain Validation — Validate DNS config
Email Security
- SPF Record Checker — Validate SPF
- DMARC Checker — Check DMARC policy
- DKIM Checker — Verify DKIM records
- SMTP Test — Test mail servers
- Email Header Analyzer
- DMARC Generator — Build DMARC records
- BIMI Checker — Brand logo in email
Network Tools
- Ping Tool — Test latency & packet loss
- Traceroute — Trace network path
- Port Checker — Test open ports
- HTTP Headers Check — Security headers
- SSL Certificate Check — Verify SSL
- What Is My IP — Your public IP
- What Is My ISP — ISP & ASN info
Domain Tools
- Domain Availability — Check if available
- WHOIS Lookup — Registration info
- Domain Health Check — Health score
- Link Analyzer — Check all links
- CMS Detector — Detect website technologies
IP Tools
- IP Lookup — Geolocation & ISP
- IP Blacklist Check — Spam list check
- MAC Address Lookup — Vendor ID
- ASN Lookup — AS number info
- Subnet Calculator — CIDR ranges
- IP to Hostname — Reverse lookup
Utility Tools
- QR Code Scanner — Scan QR codes
- QR Code Generator — Create QR codes
- Morse Code Translator — Encode & decode
- Text to Binary Converter — Convert text
- Password Generator — Secure passwords
Frequently Asked Questions About DNS Propagation
What is a DNS propagation checker?
A DNS propagation checker is a tool that queries DNS servers worldwide to verify whether DNS record changes have spread across the internet. DNS Robot’s DNS propagation checker queries 30+ global DNS servers simultaneously, showing you real-time propagation status with response times for any domain’s A, AAAA, CNAME, MX, NS, TXT, SOA, PTR, SRV, and CAA records on an interactive world map.
How long does DNS propagation take?
DNS propagation typically takes anywhere from a few minutes to 48 hours, depending on TTL (Time To Live) values and the caching policies of different ISPs and DNS resolvers worldwide. Most DNS changes propagate within 4-24 hours. DNS propagation time depends on three factors: the old TTL value, ISP caching behavior, and whether you’re changing nameservers (slower) or individual records (faster). Use our DNS propagation checker to monitor the progress in real-time.
What is DNS propagation time and what affects it?
DNS propagation time is the duration required for DNS record changes to update across all DNS servers worldwide. Key factors affecting DNS propagation time: (1) TTL values — lower TTL (300s) means faster propagation, higher TTL (86400s) means slower, (2) ISP DNS caching — some ISPs cache records longer than the TTL specifies, (3) Registry processing — nameserver changes at TLD level take 24-48 hours, (4) Geographic distance — servers further away may update later. Our DNS propagation checker shows you exactly which servers have updated and which haven’t.
Why is my DNS not propagating?
If your DNS is not propagating, check these common causes: (1) High TTL values — old records may still be cached by DNS resolvers for up to 24-48 hours, (2) Incorrect DNS records — verify your changes are saved correctly at your registrar, (3) Nameserver delegation issues — check that NS records are properly configured, (4) ISP caching — some ISPs ignore TTL and cache longer, (5) Registry lock — some registrars have a delay before changes go live. Use our DNS propagation checker to see which servers show old vs new records.
How do I check DNS propagation globally?
To check DNS propagation globally, enter your domain in our DNS propagation checker above. DNS Robot queries 30+ DNS servers across North America, Europe, Asia, South America, Africa, and Oceania simultaneously. Each result shows the resolved IP, response time, and propagation status. Green markers on the world map indicate successful propagation, while red markers show servers still returning old records.
Why do different DNS servers show different results?
Different DNS servers show different results during DNS propagation because each server caches DNS records independently based on TTL values. When you update DNS records, some servers still have the old cached version while others have fetched the new records. This is normal and resolves once propagation completes. Geographic load balancing by CDNs can also cause legitimate differences between servers.
How can I speed up DNS propagation?
To speed up DNS propagation: (1) Lower your TTL values to 300 seconds at least 48 hours before making changes, (2) Wait for the old TTL to expire before updating records, (3) Verify changes with our DNS propagation checker, (4) Flush your local DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on Mac). Note that you cannot control how quickly third-party DNS servers update their caches.
What is the difference between DNS lookup and DNS propagation checker?
A DNS lookup queries a single DNS server to find records for a domain — use our DNS Lookup tool for that. A DNS propagation checker queries multiple DNS servers across different geographic locations simultaneously to verify whether DNS changes have spread globally. DNS Robot’s propagation checker performs lookups across 30+ servers worldwide to give you a complete propagation picture with an interactive map.
How do I test DNS propagation for my domain?
To test DNS propagation for your domain: (1) Enter your domain name in the DNS propagation checker above, (2) Select the DNS record type you changed (A, MX, NS, TXT, CNAME, etc.), (3) Click Check to query 30+ global DNS servers simultaneously. The results show which servers have updated to the new records and which still serve cached data. Green markers on the world map indicate successful propagation, while red markers show servers that haven’t updated yet.
Is this DNS propagation checker free to use?
Yes, DNS Robot’s DNS propagation checker is 100% free with no signup, registration, or usage limits. You can check DNS propagation as many times as you need for any domain. All 30+ global DNS servers are queried simultaneously with real-time results, response times, and an interactive world map. DNS Robot also offers 50+ additional free tools for DNS management, email security, network diagnostics, and more.