Skip to main content
wp-config.org

Search tools

DNS and IP addresses

Free DNS propagation checker

Changed a DNS record, moved your WordPress site to a new host or set up email, and not sure everyone sees it yet? Enter the name and record type: this tool asks your domain’s own nameservers what is set now, then asks well-known public resolvers such as Google, Cloudflare and Quad9 what they have cached, and tells you how long until each one refreshes.

  • A, MX, TXT and more
  • Your nameservers first
  • Cache time left
  • Free

Free, no sign-up. Nothing you check is saved.

This tool needs JavaScript. Turn JavaScript on and reload the page.

DNS propagation checker

Check whether a DNS change has reached the big public resolvers. Enter a name and a record type: this asks your domain's own nameservers what is set now, then asks 15 public resolver addresses what they have cached, and how long until each one refreshes.

How this check works, and what it cannot see

  • Your DNS host's own (authoritative) nameservers are asked first: they show what is set now. Every public resolver is then compared with them.
  • Public resolvers keep each answer for its TTL (time to live). The TTL a resolver returns counts down, so it is the time left until that resolver asks your DNS host again: "refreshes in".
  • Most public resolvers are anycast: one address answered from many places, and you reach the nearest. This check runs from one server, so each resolver answers from the instance nearest that server. People in other countries can reach other instances with their own caches, which is why the time left in each cache matters more than a map.
  • Your internet provider's resolver, your router, your computer and your browser keep their own caches, which no website can see. They expire within the record's old TTL; the help above shows how to clear the ones you control.
  • The resolvers asked: Google Public DNS, Cloudflare 1.1.1.1, Quad9, OpenDNS (Cisco), AdGuard DNS, Control D, CleanBrowsing, DNS.SB, DNS4EU, Gcore Public DNS, AliDNS (Alibaba Cloud). Each links to the operator's own page with its addresses.

What you can do

  • Check A, AAAA, CNAME, MX, TXT, NS, CAA and SOA records

  • See what your DNS host’s own nameservers say right now

  • Compare 15 public resolver addresses from 11 operators

  • See how long each resolver keeps its cached answer

  • Enter the value you expect and see where it has arrived

  • Clear Cloudflare’s, Google’s and your own DNS cache

How to check DNS propagation

  1. Enter the name and record type

    Enter the full name of the record, such as example.com, www.example.com or _dmarc.example.com, and choose its type. Add the new value if you want to see exactly where it has arrived.

  2. Run the check

    A quick Cloudflare security check runs first. The server then asks your domain’s own nameservers and every public resolver at the same time, which usually takes a few seconds.

  3. Read the result

    “Matches” means a resolver already has what your DNS host has. An old value or “no record” is still cached: the time shown is when that resolver asks again. Press Check again later, or clear Cloudflare’s and Google’s caches with the links under the result.

What DNS propagation really is

DNS changes do not travel across the internet. Your DNS host updates its own nameservers, usually within seconds or minutes, and from then on every resolver that asks gets the new answer. What takes time is the caches: each resolver keeps the answer it already has for the record’s TTL (time to live), set in your DNS zone and often between five minutes and a day. Until that time runs out, people using that resolver still see the old answer. A record that did not exist when someone last looked is cached as “no record” too, for as long as your zone’s SOA record says.

Why your own nameservers come first

The domain’s authoritative nameservers are the source of truth. If they already give the new value, the change is done and the rest is waiting for caches. If they do not, waiting will not help: the record was not saved, was added at the wrong name, or was changed at a DNS host your domain no longer uses. The result says which. When the name is an alias (CNAME) of a name at your host, the check follows it to the nameservers of that name’s own zone too, so the final value comes from the source as well.

What “refreshes in” means

A resolver returns the time its cached copy has left, not the full TTL. That is how long until it asks your DNS host again, so it is the honest answer to “when will this resolver see my change?”

Why there is no world map

Google, Cloudflare, Quad9 and most other public resolvers are anycast: one address answered from many places, and every question reaches the nearest. This check runs from one server, so each resolver answers from the instance closest to that server, and people in other countries may reach another instance with its own cache. A map with a city for each answer would suggest something no single server can measure, so this tool labels each resolver by its operator and address only, and shows the time left in its cache instead. Your internet provider’s resolver, your router and your own computer have caches of their own, which no website can see; they all expire within the old record’s TTL.

Moving a WordPress site

Before you move a site to a new host, lower the TTL of its A and AAAA records (and www) to five minutes at least one old TTL before the move (a day ahead if the TTL is a day), so the switch reaches everyone quickly, and keep the old server running until the old TTL has passed. If your site is behind Cloudflare’s proxy, public resolvers show Cloudflare’s addresses rather than your server’s: the change to your origin happens in Cloudflare’s dashboard instead. To check the new server’s certificate once the name points to it, use the SSL checker; for every record of a domain at once, the DNS lookup; and for MX, SPF, DKIM and DMARC, the Email DNS tool.

Frequently asked questions

How long does DNS propagation take?

For any cache that held the old answer, at most the old record’s TTL. With a TTL of 300 seconds that is five minutes; with 86,400 it is a day. DNS hosts often quote “up to 48 hours” to be safe, but resolvers follow the TTL. A brand new record shows as soon as cached “no record” answers expire, which your zone’s SOA record sets.

Is the DNS propagation checker free?

Yes. There is no sign-up. A limit on how many checks one visitor can run keeps the tool available for everyone; it shares the DNS lookup’s limit.

Which resolvers does it check?

Google Public DNS, Cloudflare 1.1.1.1, Quad9, OpenDNS, AdGuard DNS, Control D, CleanBrowsing, DNS.SB, DNS4EU, Gcore Public DNS and AliDNS: 15 addresses in all, each taken from the operator’s own page, which the result links to. Where an operator offers an address without filtering, that is the one used, so a block list cannot look like a missing record.

Why do different resolvers show different answers?

Each one cached the record at a different moment, so each one’s copy runs out at a different time. That is normal during a change. If a resolver still shows the old value after its “refreshes in” time, check again: most are anycast, so the next question may reach another of its servers with its own cache.

Can I make a resolver update sooner?

For two of them, yes: Cloudflare (one.one.one.one/purge-cache) and Google (dns.google/cache) let anyone clear a name from their cache. The others cannot be cleared from outside. You can always clear your own browser’s and computer’s cache; the commands are under the result.

My nameservers show the old value. What now?

Then the change is not live at your DNS host yet. Check that you saved the record, that its name is right (many DNS hosts add your domain for you, so www.example.com.example.com is a common mistake) and that you edited the DNS host your domain actually uses: the nameservers in the result, which you can also see in the WHOIS lookup.

Why does my record show a different IP address than my server’s?

If the record is proxied through Cloudflare (orange cloud) or another CDN, everyone gets the CDN’s addresses, not your server’s. That is expected. Your DNS host’s own nameservers give the same CDN addresses, so the result still shows whether the change has spread.

Is what I check stored?

The result is not saved. To count how the tool is used, this site keeps the name you checked (never the record type or the expected value) for 12 months, with the time, the outcome, your approximate location (country, region and city), the site you came from and your type of device and browser, but no IP address. The name is sent to the domain’s own nameservers, to the public resolvers listed above, and to Google’s or Cloudflare’s DNS over HTTPS to find the nameservers. The privacy policy has the details.

Related tools

  • Look up DNS records and check SPF, DMARC, DKIM and DNSSEC.

  • Email DNS

    New (added recently)

    Build and test MX, SPF, DKIM, DMARC, MTA-STS and BIMI records, with the exact values for Google Workspace, Microsoft 365 and over 25 email services.

  • SSL checker

    New (added recently)

    Check a website’s SSL certificate, chain, expiry and TLS versions, with fixes for each problem.

  • Look up a domain’s registrar, status and dates through official RDAP services.