Map Extract
Free tool

DNS propagation checker

Changed a record and want to know whether the world can see it yet? Ask five public resolvers in different places the same question, see which ones agree, and spot the ones still holding the old answer in cache.

Runs in your browser. Domain names are looked up through public DNS over HTTPS (Cloudflare, with Google as a fallback); nothing goes to Map Extract.

Checking a change

  1. Enter the name you edited

    The domain or host exactly as you changed it, for example mail.harbourbakery.example if you edited a subdomain rather than the root.

  2. Pick the record type

    A, AAAA, CNAME, MX, TXT, NS or CAA. Choose the one you changed; a new SPF or DMARC value is a TXT record.

  3. Paste the value you expect

    Optional but useful: enter the new address or record. The results then count how many resolvers already return it, rather than only whether they agree with each other.

  4. Compare resolvers

    Cloudflare, Google, Quad9, AdGuard and AliDNS are asked at the same moment. Each row shows the answer, the TTL left on it and how long the reply took.

  5. Wait, then run it again

    Rows marked Different usually show a TTL counting down. When that reaches zero the resolver will fetch your new value; run the check again then.

Example: a bakery moves its website to a new host

Harbour Bakery (fictional) points its A record at a new server, 203.0.113.40, replacing 198.51.100.7. The old record had a TTL of one hour. A few minutes after the change, three resolvers already have the new address because none of them had the old one cached. Two still hold the old address with roughly 50 to 57 minutes of their cache left.

Nothing is broken. Visitors whose provider uses one of the lagging resolvers will see the old site for up to an hour; keep the old server running until then.

Input
Domain: harbourbakery.example   Type: A   Expected: 203.0.113.40
Result
Agree: 3 of 5      With the expected value: 3 of 5
Cloudflare 1.1.1.1         203.0.113.40   TTL 300 s    Same
Google Public DNS 8.8.8.8  203.0.113.40   TTL 300 s    Same
Quad9 9.9.9.9              198.51.100.7   TTL 3412 s   Different
AdGuard DNS                203.0.113.40   TTL 300 s    Same
AliDNS 223.5.5.5           198.51.100.7   TTL 2980 s   Different

Making the next change faster

A little planning before an email or website move saves a lot of anxious refreshing.

  • A day before the move, lower the TTL on the records you will change to 300 seconds, then wait for the old, longer TTL to expire.
  • Make the change, check here with the expected value filled in, and keep the old server or mailbox working until every row says Same.
  • When a new cold outreach domain is set up, confirm SPF, DKIM and DMARC are visible everywhere before the first warm-up message goes out.
  • Raise the TTL again afterwards, typically to an hour or more, so resolvers are not asking constantly.
  • Remember that your own broadband provider's resolver is not in this list and can lag; testing on mobile data is a quick second opinion.

Questions people ask

How long does DNS propagation take?

It depends on the TTL of the record you replaced. A resolver that cached the old answer keeps it for the remaining TTL, so a record that had a one-hour TTL is fully replaced within about an hour, and one with a day-long TTL can take a day. Lowering the TTL in advance shortens the wait for planned changes.

Why do resolvers disagree about my record?

Each resolver caches independently, and they asked your DNS host at different times. Some may have cached the old value just before you changed it, while others had nothing cached and fetched the new one. Differences that show a TTL counting down will clear on their own.

All five agree but my computer still shows the old site. Why?

Your device, router and internet provider each keep their own cache, and the provider's resolver is not one of the five checked here. Wait for the old TTL to pass, or clear your device's DNS cache and restart the browser. Testing on mobile data uses a different resolver and is a quick comparison.

What does NXDOMAIN mean in the results?

NXDOMAIN means the resolver was told that the name does not exist at all. After registering a new domain or creating a new subdomain, some resolvers may have cached that negative answer from an earlier check. It clears when the negative cache time set in the zone's SOA record runs out.

Can I check propagation of a DKIM or DMARC record?

Yes. Both are TXT records on special names. Enter the full name, such as _dmarc.harbourbakery.example or selector._domainkey.harbourbakery.example, choose TXT and paste the expected value to see which resolvers have picked it up.

Where your data goes

The domain and record type are sent from your browser to five public DNS over HTTPS services: Cloudflare, Google, Quad9, AdGuard and AliDNS. Each request is listed under the result. Nothing goes to Map Extract and nothing is stored.

Checked against the tool on

Top