Free Tool

Free DNS Propagation Checker

Check if your DNS changes have propagated worldwide. Verify DNS records from multiple global locations instantly.

Free Tool · No signup required · Check from 12+ global regions

What is DNS Propagation?

DNS propagation is the process of updating DNS records across all DNS servers worldwide. When you change a DNS record (like pointing your domain to a new server), that change doesn't happen instantly everywhere.

Your DNS changes start at your authoritative nameserver (usually your domain registrar or DNS provider). From there, the new records gradually spread to DNS resolvers and caching servers around the world. Each server holds onto records based on the TTL (Time To Live) setting, only checking for updates when that timer expires.

This is why some users might see your new server while others still reach the old one. Propagation typically takes anywhere from a few minutes to 48 hours, though most changes complete within 1-4 hours. Higher TTL values mean slower propagation but fewer DNS queries overall.

Understanding propagation helps you plan DNS changes properly: lower your TTL ahead of time, make the change, verify propagation, then raise TTL again for production performance.

How to Use This Tool

1

Enter your domain name

Type the domain you want to check, like "example.com" or "subdomain.example.com". Don't include http:// or https://.

2

Select the DNS record type

Choose the record type you want to verify: A (IPv4), AAAA (IPv6), CNAME (alias), MX (mail), TXT (text), NS (nameserver), or SOA (authority).

3

Click "Check DNS"

We'll query DNS servers from 12+ global locations simultaneously and show you the results.

4

Review results from all locations

Green means the record matches the expected value. Yellow means a different value was found. Red means no record found.

5

Wait and re-check if needed

If propagation isn't complete, wait a few minutes or hours and check again. Full propagation can take up to 48 hours.

DNS Record Types Explained

Maps a domain name to an IPv4 address (like 192.168.1.1). This is the most common record type. When someone types your domain in a browser, the A record tells them which server to connect to.
Maps a domain name to an IPv6 address (like 2001:0db8:85a3::8a2e:0370:7334). As IPv4 addresses become scarce, AAAA records enable your site to work with the newer, larger IPv6 address space.
Creates an alias that points one domain to another. For example, www.example.com might have a CNAME pointing to example.com. Useful for CDNs, subdomains, and services that give you a hostname to point to.
Specifies which mail servers handle email for your domain. MX records have a priority number - lower numbers are tried first. Essential for email delivery to work correctly.
Stores text data for various purposes. Common uses include SPF records (email authentication), DKIM keys, domain verification for services like Google Workspace, and custom metadata.
Specifies which DNS servers are authoritative for your domain. When you change hosting providers or use a DNS service like Cloudflare, you update NS records to point to their nameservers.
Contains administrative information about the zone: primary nameserver, admin email, serial number (for tracking changes), and timing parameters for how secondary servers should sync. Every DNS zone has exactly one SOA record.

When to use a DNS propagation checker

Frequently Asked Questions

Everything you need to know about DNS propagation.

DNS propagation typically takes anywhere from a few minutes to 48 hours, depending on TTL settings and how aggressively DNS servers cache records. Most changes propagate within 1-4 hours. If you lowered your TTL before making changes, propagation will be faster.
DNS is distributed globally. When you make a change, it starts at your authoritative nameserver and gradually spreads to DNS resolvers worldwide. Each resolver caches records based on TTL, so they update at different times. This is normal during propagation.
TTL (Time To Live) tells DNS resolvers how long to cache a record before checking for updates. A TTL of 300 means the record is cached for 5 minutes (300 seconds). Lower TTL = faster propagation but more DNS queries. Higher TTL = better performance but slower updates.
You can't force global propagation, but you can prepare: lower your TTL to 300 seconds a day before making changes. This ensures cached records expire quickly. After making your change and verifying propagation, raise the TTL again for better performance.
Common causes: incorrect record format, typos in values, conflicting records at your registrar, or DNS cache on your local machine. Try flushing your local DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on Mac) and verify records at your registrar's control panel.
Yes, completely free. No signup required. Check unlimited domains from 12+ global locations. For continuous DNS monitoring with alerts when records change, consider signing up for PerkyDash.

More Free Tools from PerkyDash

Free Uptime Checker

Check if a website is down and measure response time instantly.

Status Page Generator

Create a beautiful public status page for your service.

Emergency Status Page

Create an instant incident page in 60 seconds. No signup.

Downtime Cost Calculator

Calculate how much revenue you lose during checkout outages.

Related Guides

Ready for 24/7 DNS monitoring?

Get instant alerts when DNS records change, domains expire, or SSL certificates need renewal.

Start Free Trial See Pricing

14-day Pro trial. No credit card required.