DNS Propagation Checker
Verify records across global resolvers
See what major public DNS servers return for your domain. Detect stale caches, partial updates, or mismatched records quickly.
Resolvers checked:
Enter a domain to see propagation.
We will query multiple global DNS resolvers and show where records agree or diverge.
What this checker does
We query multiple public DNS resolvers to spot differences in cached answers. Use it after updates to confirm records are visible worldwide and to identify regions still serving stale data.
- Validate A/AAAA, CNAME, MX, TXT, and NS changes
- Watch TTL-driven propagation and mismatched caches
- Compare resolver-specific behavior when debugging outages
Understanding DNS propagation
What is DNS propagation and why does it take time?
DNS propagation is the process of updating DNS records across the internet. Learn how it works, typical timeframes, and how to troubleshoot common issues.
What is DNS propagation?
DNS propagation is simply the time it takes for changes to your DNS records to spread across the internet. Think of it like updating your phone number—when you change it, you need to tell everyone who has your old number, and it takes time for everyone to update their contacts.
When you update DNS records (like changing where your website points), DNS servers around the world gradually pick up the new information. Until they do, different people might see different versions of your DNS records depending on which server they're using.
How long does it take?
Typical timeframe:
Usually 5 minutes to 48 hours, but most changes appear within a few hours.
Factors that affect speed:
- TTL value (Time To Live) — lower = faster updates
- DNS provider — some update faster than others
- ISP caching — your internet provider may cache longer
Understanding TTL (Time To Live)
TTL is like an expiration date on DNS records. It tells DNS servers how long to remember (cache) your DNS information before checking back for updates.
Low TTL
300s (5 min)
Changes spread faster but creates more DNS traffic. Good for testing or when you plan frequent updates.
Medium TTL
3600s (1 hour)
Balanced approach. Most common setting for production websites with occasional updates.
High TTL
86400s (24 hours)
Changes take longer but reduces DNS queries. Best for stable sites that rarely change.
Pro tip: If you're planning a DNS change (like moving to a new server), lower your TTL to 300 seconds a day or two before the change. This way, when you make the actual update, it will propagate much faster across the internet.
Common issues and troubleshooting
❓ Changes aren't showing up for me
Your computer or router might be caching the old DNS records.
Quick fix:
- Windows: Open Command Prompt and run
ipconfig /flushdns - Mac: Open Terminal and run
sudo dscacheutil -flushcache - Linux: Run
sudo systemd-resolve --flush-caches(on systemd-based systems) - Try a different DNS server like Google (8.8.8.8) or Cloudflare (1.1.1.1)
- Use an incognito/private browser window
⚠️ Some locations see old records, others see new
This is normal during propagation! Different DNS servers update at different times.
What to do:
- Use this DNS Propagation Checker to see which servers have updated
- Wait for the TTL period to pass (check your DNS records for the TTL value)
- Be patient — full global propagation can take up to 48 hours in rare cases
🔄 Planning a server migration?
Minimize downtime by preparing ahead of time.
Migration checklist:
- 48 hours before: Lower TTL to 300 seconds (5 minutes)
- 24 hours before: Verify the TTL change has propagated
- Migration day: Update DNS records to point to new server
- Monitor: Use this checker to watch propagation in real-time
- After 24-48 hours: Restore TTL to normal (3600 or higher)
- Keep old server running for at least 48 hours after the change
✅ How to verify propagation is complete
- Check this page regularly — when all resolvers show the same answer, you're done
- Test from different devices and networks (home WiFi, mobile data, etc.)
- Wait for at least 2x your old TTL value before considering it "done"
- Monitor your website/service logs for traffic patterns returning to normal
Real-world examples
Example 1: Moving your website to a new host
You're moving example.com from Server A (IP: 192.0.2.1) to Server B (IP: 198.51.100.5).
- Your old A record has TTL of 86400 (24 hours) — this means DNS servers will cache it for a full day
- You lower the TTL to 300 (5 minutes) and wait 24 hours for old caches to expire
- You update the A record to point to 198.51.100.5
- Within 5 minutes, new DNS queries get the new IP. Old caches expire quickly now
- After an hour, most users see the new server. After 48 hours, everyone does
Example 2: Fixing an email deliverability issue
Your emails are going to spam because your SPF record is incorrect.
- You update your TXT record with the correct SPF policy
- Your TXT records have a TTL of 3600 (1 hour)
- Within an hour, most email servers will see the new SPF record
- Use this checker to verify all major DNS providers have the new TXT record
- Email deliverability improves as the change propagates globally
Example 3: Emergency DNS change during an outage
Your hosting provider is down, and you need to quickly redirect traffic to a backup server.
- Unfortunately, your TTL is set to 86400 (24 hours) 😞
- You update DNS to point to your backup server immediately
- New visitors will reach the backup within 5-10 minutes (after upstream servers update)
- However, cached visitors might be stuck for up to 24 hours
- Lesson learned: Keep TTL at 3600 or lower for critical services
Quick reference: Propagation timeline
| Timeframe | What's happening | What you'll see |
|---|---|---|
| 0-5 minutes | Your DNS provider's servers update | Direct queries to your DNS provider show new records |
| 5-60 minutes | Major public DNS resolvers refresh | Google DNS, Cloudflare, OpenDNS start showing changes |
| 1-4 hours | Most ISPs and local resolvers update | Majority of users worldwide see new records |
| 4-24 hours | Stragglers and aggressive cachers refresh | Nearly all users see new records |
| 24-48 hours | Final propagation complete | 100% propagation across all global DNS servers |
Note: This timeline assumes typical TTL values (300-3600 seconds). Higher TTL values will extend these timeframes.