TOOLS

DNS Propagation Checker

Check if your DNS changes have propagated worldwide. Query DNS records from multiple global DNS servers and verify your domain's DNS configuration. Free to use. No signup required.

We'll query DNS records from 12+ global DNS servers including Google, Cloudflare, OpenDNS, and more.

Records for

Queried from DNS servers worldwide

Propagation Status

Records Found:

DNS Server Location Status Records TTL

OTHER TOOLS

Try our other free tools!

Global Ping Test

Test website latency from 70+ locations worldwide.

Try it free →

HTTP Response-Time

Measure TTFB and response time from multiple continents.

Try it free →

DNS Propagation

Check DNS propagation from global DNS servers.

You're here

SSL Checker

Verify SSL certificates and check expiration dates.

Try it free →

Header Analyzer

Analyze HTTP headers for security & SEO issues.

Try it free →

IP Geolocation

Find IP location, ISP, and CDN detection.

Try it free →

Outage Map

Live map of global internet outages.

Try it free →

Need continuous DNS monitoring?

Monitor your DNS records 24/7 from all 70+ locations with instant alerts when records change or issues occur.

Start monitoring for $5/month

FAQs

What is DNS propagation?
DNS propagation is the time it takes for DNS changes to spread across all DNS servers worldwide. When you update DNS records, it can take up to 24-48 hours for all servers to reflect the new values due to caching.
How long does DNS propagation take?
Typically 1-48 hours, depending on your TTL (Time To Live) settings. Lower TTL values speed up propagation. Most changes propagate within a few hours for records with short TTLs.
What DNS record types can I check?
We support A (IPv4), AAAA (IPv6), CNAME (aliases), MX (mail), TXT (text records like SPF/DKIM), NS (nameservers), SOA (authority), CAA (certificate authority), and PTR (reverse DNS) records.
Why do different DNS servers show different results?
DNS servers cache records based on TTL. Different servers may have queried your domain at different times, so they could have older cached values. This is normal during propagation.