DNS Propagation Checker

Instantly verify if your DNS changes have propagated worldwide. Check any record type across 30+ global locations in real time.

30+ global locations Real DNS lookups No signup required 100% free
MX
  • A
  • AAAA
  • MX
  • TXT
  • CNAME
  • NS
  • SOA
  • CAA
  • PTR
  • SRV
Filter:
0 propagated
0 different
0 no record
-
Propagated
Different
No record
Checking

How to Check DNS Propagation Worldwide

Our free DNS propagation checker queries real DNS resolvers across 30+ global locations simultaneously - no account needed, results in seconds.

1

Enter your domain

Type the domain name and select the DNS record type - A, MX, TXT, CNAME, NS, and more.

2

Run the propagation check

We simultaneously query DNS servers across North America, Europe, Asia Pacific, South America, the Middle East, and Africa.

3

Read your global DNS results

Each location shows its resolved value. Instantly spot where your DNS changes haven't propagated yet.

Understanding Your DNS Propagation Results

Each location returns one of four statuses. Here's exactly what each means and what action to take.

Propagated

This resolver has the latest version of your DNS record. The value matches the reference result - your change has reached this region. No action needed.

Different

This resolver returned a value that doesn't match the reference - it's serving a cached old record. Normal during propagation. Wait for the TTL to expire and it will refresh automatically.

No record

The resolver returned NXDOMAIN or an empty response. Either the record doesn't exist yet, it was deleted, or it hasn't propagated to this location. Verify your record exists at your DNS provider.

Timeout

The resolver didn't respond in time. Usually caused by a temporary network issue. Try running the check again - timeouts are rarely permanent.

How the reference value is determined

The first successful DNS response sets the reference value. All subsequent results are compared against it. Locations showing a different value are still serving a cached old record - the TTL on each result card shows how long that cache will persist.

DNS Record Types You Can Check for Propagation

Check DNS propagation for all major record types - from website routing and email delivery to domain security and SSL certificates.

A

Address record

Maps a domain to an IPv4 address. The most common record for website and server hosting.

MX

Mail exchanger

Defines which mail servers accept email for your domain. Critical for email delivery and authentication.

TXT

Text record

Stores SPF, DMARC, and DKIM data. Essential for email security and domain verification.

CNAME

Canonical name

Creates an alias from one hostname to another. Used for www subdomains and CDN configuration.

NS

Name server

Identifies the authoritative DNS servers responsible for your domain zone.

AAAA

IPv6 address

Maps a domain to an IPv6 address. Increasingly important for modern network infrastructure.

CAA

Certificate authority

Restricts which Certificate Authorities can issue SSL/TLS certificates for your domain.

SOA

Start of authority

Contains zone admin info including serial number, TTL defaults, and responsible nameserver.

What Is DNS Propagation?

DNS propagation is the time it takes for DNS changes to spread across all DNS servers worldwide. When you update a DNS record - for example changing your A record to point to a new server, or adding a TXT record for SPF or DMARC - that change doesn't take effect everywhere instantly.

The Domain Name System (DNS) translates human-readable domain names like powerdmarc.com into IP addresses that computers use to communicate. Every DNS resolver around the world caches these records for a period defined by the record's TTL (Time to Live) value. Until that cache expires, the resolver returns the old value - even after you've made changes at your authoritative nameserver.

This is why you may see the new record immediately on your own computer while users in other regions are still getting the old value. It's not a bug - it's how the distributed caching architecture of DNS is designed to work.

How Long Does DNS Propagation Take?

DNS propagation typically completes within 24 to 48 hours, though many changes are visible within a few hours. The main factors that affect propagation time are:

TTL value

The Time to Live directly controls how long resolvers cache the old record. A TTL of 86400 (24h) means changes can take a full day to propagate. Lowering it beforehand speeds this up significantly.

ISP caching

ISPs cache DNS results for many users at once. Some ignore TTL values entirely and keep records cached longer than they should, causing unexpected propagation delays.

Registrar updates

Changing nameservers requires the new NS records to propagate through the TLD nameserver (e.g. .com, .net), adding an extra layer of delay beyond a standard record change.

How to Speed Up DNS Propagation

The most effective technique is to lower your TTL several days before making changes - set it to 300 seconds (5 minutes). Once resolvers refresh their cache and pick up the low TTL, your change will propagate much faster. Increase the TTL again after propagation is complete.

If you need a quicker workaround, try flushing your local DNS cache or switching to a public resolver like 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) to see fresher results sooner.

Frequently Asked Questions

Each DNS resolver caches records independently based on the TTL. Until a resolver’s cache expires and it fetches the updated record from the authoritative server, it returns the old value. This is why you may see “Propagated” in some regions and “Different” in others — the old cache hasn’t expired at those locations yet.

 

A “No record” result means the resolver returned NXDOMAIN or an empty answer for that record type. This may mean the record hasn’t been created yet, was deleted, or the new record hasn’t reached that resolver’s cache. Compare with other locations — if most show a value and only a few show “No record”, propagation is still in progress there.

Your local DNS resolver or ISP has cached the old record and the TTL hasn’t expired yet. Try flushing your local DNS cache, or use a public resolver like 1.1.1.1 or 8.8.8.8 to see updated results faster. If your record is already updated at the authoritative nameserver, you simply need to wait for the TTL to expire globally.

Yes. Our tool performs real DNS lookups using DNS over HTTPS (DoH) from each location’s resolver — not simulated or cached results from our own servers. Every result reflects an actual live query to that resolver at the time you run the check. The specific resolver and IP are shown on each result card.

 

A standard DNS lookup queries only your local resolver, which may return a cached result. A global propagation check queries multiple resolvers in different geographic regions simultaneously, showing you how DNS is actually resolving for users in each part of the world right now — not just what your local network sees.

Protect Your Domain with DMARC, SPF & DKIM


DNS is the foundation of email security. Use PowerDMARC to monitor your DMARC, SPF, and DKIM records — and make sure every change propagates correctly.