Skip to main content
Home › Tools › DNS Propagation Checker
🌐 Network & DNS ✅ 100% Free ⚡ Live Check

DNS Propagation Checker

Instantly check DNS propagation across 20+ global DNS servers. Verify that your DNS record changes have fully propagated worldwide — supports A, AAAA, CNAME, MX, NS, TXT, SOA, and more.

Querying DNS servers worldwide…
⚠️
Check Failed
An error occurred.
— Propagated
—
—
Type: — Servers: — —
Global Propagation —
🌍 Results by DNS Server
📊 Propagation Stats
—
Found
—
Not Found
—
Propagated
—
Servers
📖 Record Types
AMaps domain to IPv4 address
AAAAMaps domain to IPv6 address
CNAMEAlias pointing to another domain
MXMail server for the domain
NSAuthoritative nameservers
TXTText records (SPF, DKIM, etc.)
SOAStart of Authority record
💡 DNS Tips
⏱️
Propagation takes time — DNS changes can take up to 48 hours to spread globally, depending on TTL.
🔢
Lower your TTL before making changes (e.g. 300s) so old records expire faster.
🌍
Partial propagation is normal — different regions update at different speeds.
🔄
Flush your local cache with ipconfig /flushdns (Windows) to see fresh results.

What is DNS Propagation?

DNS propagation is the process by which updated DNS records spread across the internet's network of DNS servers worldwide. When you change a DNS record — such as pointing a domain to a new server's IP address — that change doesn't instantly appear everywhere. Instead, it gradually propagates from your authoritative nameserver outward to resolvers and caches globally.

This tool performs a live, real-time check against 20+ real DNS resolvers located across North America, Europe, and Asia-Pacific, so you can see exactly which regions have already received your updated record and which are still showing old data.

How Long Does DNS Propagation Take?

DNS propagation time depends primarily on the TTL (Time To Live) value set on your DNS record. TTL tells resolvers how long (in seconds) to cache a record before re-fetching it. Common propagation scenarios:

  • TTL = 300 (5 minutes) — Most resolvers update within 5–10 minutes. Ideal for migrations.
  • TTL = 3600 (1 hour) — Full propagation within 1–2 hours globally. The most common default.
  • TTL = 86400 (24 hours) — Can take up to 48 hours for all resolvers worldwide to update.
  • Registrar propagation — Changing nameservers at the domain registrar adds an extra 24–48 hours on top of TTL.

Pro tip: If you know you'll be making DNS changes, reduce your TTL to 300 seconds at least 24 hours before the change. Then raise it back after propagation is confirmed.

Why Check DNS Propagation?

  • Website migration — Confirm your new server's A record is live before decommissioning the old one.
  • Email deliverability — Verify MX records and TXT records (SPF, DKIM, DMARC) have propagated before sending campaigns.
  • CDN setup — Ensure CNAME records pointing to a CDN have reached all regions.
  • Nameserver changes — Confirm NS record updates after moving to a new DNS provider.
  • Troubleshooting — Diagnose why some users see an old site while others see the new one.

Frequently Asked Questions

Each DNS resolver independently caches records for the duration of their TTL. When you make a DNS change, resolvers only see the update after their cached copy expires and they re-query the authoritative nameserver. Resolvers in different regions or with different caching policies will update at different times — which is exactly what this tool shows you.
NXDOMAIN (Non-Existent Domain) means the DNS server returned a negative response — it has no record of that domain or record type. This could mean the record doesn't exist yet, the change hasn't propagated to that server, or the record genuinely doesn't exist. For a newly created record, NXDOMAIN at some servers is expected during propagation.
You can't force external resolvers to flush their caches, but you can minimise wait time by: (1) setting a low TTL (300s) 24+ hours before your planned change, (2) making the DNS change as quickly as possible once TTL is low, and (3) flushing your own local DNS cache with `ipconfig /flushdns` (Windows) or `sudo dscacheutil -flushcache` (macOS). After propagation, raise your TTL back to a higher value like 3600.
TTL (Time To Live) is a value in seconds that tells DNS resolvers how long to cache your record. A TTL of 3600 means resolvers keep the cached copy for 1 hour before re-fetching. Lower TTL = faster propagation but slightly higher DNS server load. Higher TTL = slower propagation but better performance and resilience to nameserver outages.
Even after DNS propagates, your browser, operating system, or ISP may still have a local cache of the old result. Try: flushing your local DNS cache, using an incognito/private browser window, trying a different network (mobile data vs. WiFi), or using an online proxy to check from a different location. The issue is almost always a local cache, not the DNS propagation itself.
Copied!

Enjoying this tool?

Every tool here is free, forever — no signup, no paywall. If this one just saved you real time, a small tip keeps them free and ad-light.

☕ Support This Tool →

Need something built, not just formatted?

This toolbox is free. If your business needs custom software, AI integration, or a system built around this kind of tooling, that's what I do for a living.

Explore Software → Book a Consultation →

About This DNS Propagation Checker

A single syntax error or misconfiguration can break an entire application or cause security vulnerabilities. This free online DNS Propagation Checker lets you instantly verify your DNS Propagation for errors, mismatches, and invalid syntax before deploying or using it in production.

How to use

  1. Paste or type your DNS Propagation input into the tool.
  2. Click Validate or the check button.
  3. Review any errors or warnings highlighted in the output.

Why validate online?

Use this tool regularly during development to maintain high-quality, error-free DNS Propagation and catch problems early in the workflow.

Frequently Asked Questions

Is this DNS Propagation Checker free to use? +
Yes, completely free. No signup, no account, no payment required. Just paste your input and use it directly in your browser.
Does this tool store or send my data anywhere? +
No. Everything runs entirely in your browser using JavaScript. Your data never leaves your device or gets sent to any server.
What browsers does this tool support? +
It works in all modern browsers — Chrome, Firefox, Safari, Edge, and Opera — on both desktop and mobile.
Can I use this tool offline? +
Once the page is loaded, the tool runs locally in your browser without needing an active internet connection for most operations.
🔧
Custom Development

Need a Custom Version of This Tool?

This DNS Propagation Checker works for most use cases — but if you need batch processing, API access, private hosting on your own domain, or a completely bespoke tool built around your workflow, I can build it.

Request Custom Build → Typical turnaround: 3–7 days