Skip to content
JustTools

DNS Propagation Checker

Changed a DNS record? See what public DNS servers and networks around the world answer right now, how far the new value has spread, and when the rest will update.

Looks up public records Free · no sign-up

At a glance

  • Checks A, AAAA, CNAME, MX, NS, TXT, CAA and SOA records on 25 DNS servers and networks at once.
  • 7 public DNS networks — Google, Cloudflare, DNS.SB, Control D, CleanBrowsing, IIJ (Japan) and dnsforge (Germany) — each with its own cache.
  • 18 ISP networks in 15 countries, including Jio, Airtel and ACT in India, answered by Google Public DNS as it would for their users (EDNS Client Subnet) — this shows where CDNs and GeoDNS send visitors.
  • Enter the expected value to see the percentage of servers already showing it, and roughly how long the rest may keep the old answer (their remaining TTL).
  • Identical answers are grouped and colour-coded, so you can spot the odd one out.
  • Can re-check automatically every minute while you wait. Queries go from your browser over encrypted DNS-over-HTTPS; only the domain and record type are sent.

Step by step

How to check DNS propagation

  1. 1

    Enter your domain

    Type the domain or subdomain you changed, such as www.example.com.

  2. 2

    Choose the record type

    Pick A for a new server IP, CNAME for an alias, MX for email, NS for new name servers or TXT for verification codes.

  3. 3

    Add the new value

    Optionally type the value you set, so each server is marked as updated or not.

  4. 4

    Check

    Click Check. Results fill in within seconds; switch on auto-refresh to follow the change.

Features

Everything you need, nothing you don’t

Know when it’s live

Type the new IP, CNAME target or TXT value and watch the percentage climb to 100% as servers pick up the change.

When will it finish?

Servers still showing the old value report how long they’ll keep it. The tool tells you the longest wait left.

Worldwide view

Public DNS networks plus ISP networks across India, the Americas, Europe, the Middle East, Africa and Asia-Pacific.

CDN and GeoDNS aware

See which server address visitors in each country get from services such as CloudFront, Akamai or Google.

Auto-refresh

Switch on “Check again every minute” and leave the tab open — no need to keep clicking.

Shareable

Copy a link with the domain, record type and expected value, and send it to your developer or hosting support.

How long does DNS propagation take?

There is no single “propagation” process: every DNS server keeps a cached copy of your old record until its TTL (time to live) runs out, then fetches the new one. So a change is visible everywhere after at most the old record’s TTL — often 5 minutes to 1 hour, sometimes up to a day.

New name servers (NS) take longer: the registry for your domain’s ending (.com, .in…) publishes them, and resolvers may keep the old delegation for up to 48 hours. To make planned changes fast, lower the record’s TTL to 5 minutes a day before the change, then raise it again afterwards.

Reading the results

You seeWhat it means
Updated (green tick)The server returns the value you expect.
Different value (red)The server still has the old answer cached — wait for its TTL to run out.
No recordThe name exists but has no record of this type on that server (possibly cached).
Domain not foundThe server believes the name doesn’t exist — common just after registering or adding a subdomain.
Different answers by countryNormal for sites on a CDN or GeoDNS: visitors are sent to their nearest server.
No answerThat server couldn’t be reached from your network (it may be blocked by a firewall or ad blocker).

FAQ

Frequently asked questions

Why do I still see the old website after the checker shows 100%?

Your computer, router or browser can cache DNS too. Try another browser or a private window, restart the router, or switch your device to a public DNS such as 1.1.1.1 or 8.8.8.8. On Windows, ipconfig /flushdns clears the system cache.

Can I speed up DNS propagation?

You can’t force other servers to drop their cache, but you can plan ahead: lower the TTL well before a change. Google and Cloudflare also offer web pages to purge their cached copy of a name.

Are these servers really in different countries?

The public DNS networks are global: each answers from its site nearest to you, with its own cache. The country rows ask Google Public DNS to answer as it would for users of each ISP network, using EDNS Client Subnet — accurate for CDN and GeoDNS answers, but served from Google’s cache near you.

Why do different countries get different IP addresses?

Sites on a CDN (Cloudflare, CloudFront, Akamai, Fastly) or with GeoDNS deliberately give visitors the address of a nearby server. That’s expected and not a propagation problem.

Why does it say “Domain not found” for a domain I just registered?

New domains can take from minutes to a few hours to appear, and servers that asked before it existed remember the “not found” answer for the zone’s negative-cache time (shown as TTL).

What is sent, and to whom?

Only the domain and record type, sent from your browser over encrypted DNS-over-HTTPS to the DNS services listed on the page. JustTools doesn’t receive or store your checks.

Keep going

Browse every tool

Last updated Report a problem or suggest a feature