DNS Propagation Checker - Check DNS Records Instantly Free

????? ?????? ?????
  1. Home
  2. Developer Tools
  3. DNS Propagation Checker
Share: Report

DNS Propagation Checker

100% free · Runs 100% in your browser · Google, Cloudflare & Quad9 resolvers only · No signup needed

Results appear here after you check.

This tool checks Google, Cloudflare and Quad9 public resolvers only — it is NOT a worldwide ISP propagation map, and TTL caching means resolvers legitimately disagree for a while after a DNS change. Wait out the record TTL before concluding a change has failed, and compare answers across resolvers rather than trusting one alone.

Try an example: example.com, A records

?? ?????? DNS Propagation Checker

When you change a DNS record for a website, email service, or online application, the change does not reach every visitor at the same moment. Some people see the new address right away, while others keep reaching the old server for hours. That delay is called DNS propagation, and it can be confusing when you are waiting for a site to go live, fixing email delivery, or moving hosting. The DNS Propagation Checker helps you see what is actually happening by asking several well-known public resolvers for the same record and showing their answers side by side, so you can compare results instead of guessing whether your change has taken effect.

Using the tool is simple. Enter a domain name, choose the record type you want to check, and run the test. The tool sends DNS-over-HTTPS queries, often called DoH, to public resolvers operated by Google, Cloudflare, and Quad9, and displays the answers each resolver currently returns. DNS-over-HTTPS simply means the DNS question is sent over a secure web connection, which keeps the query private from networks in between and avoids some forms of interference. Because the checks run in your browser, you get a fast, readable comparison without installing software, creating an account, or waiting for a report to be emailed to you.

An honest note about what this tool does and does not do is important. This checker queries those public resolvers only, so it is not a worldwide map of every internet provider, and it cannot show what every visitor on every network will see. Different resolvers, internet providers, offices, and home routers keep their own cached copies of DNS records, and those caches expire at different times. That means resolvers can legitimately disagree for a while after a DNS change, even when your new record is perfectly correct. Think of the results as a useful sample from major public resolvers, not as proof that propagation is complete everywhere.

The most common record types start with A and AAAA records, which point a domain name to a server. An A record holds an IPv4 address, the familiar four-part number such as 192.0.2.1, while an AAAA record holds an IPv6 address, the longer format used by the newer internet protocol. When someone types your domain into a browser, the browser asks for the A or AAAA record and then connects to that address. If you move a website to a new host, you usually update the A or AAAA record, and until caches expire, some visitors will still be sent to the old address. Checking both record types is useful because a site can work over IPv4 while IPv6 still points somewhere else.

MX records control where email for a domain is delivered, and TXT records carry text information that other services read to verify ownership or enforce policy. An MX record names the mail server that should receive messages for your domain, and it includes a priority number so backup servers can take over if the main server is unavailable. TXT records are used for sender verification methods such as SPF, DKIM, and DMARC, which help receiving mail systems decide whether a message is genuine. A single typo in an MX or TXT record can break email or weaken spam protection, so comparing the answers from several resolvers after an edit is a sensible step before declaring the job finished.

CNAME and NS records explain how a domain is organized rather than pointing directly to a single server address. A CNAME record makes one name an alias of another name, which is handy for pointing a subdomain such as www to your main domain without duplicating an IP address. NS records name the authoritative name servers for a domain, meaning the servers that hold the official copy of its DNS zone. If you change name servers, for example when moving DNS management to a new provider, the NS change itself must propagate before the new records are widely trusted. Checking NS answers alongside the record you changed often explains why a website still behaves oddly after an update.

TTL, short for time to live, is the setting that controls how long a resolver may cache a DNS record before asking again. TTL is measured in seconds, so a TTL of 3600 means one hour, while a TTL of 300 means five minutes. A long TTL reduces repeated lookups and can make a site slightly faster, but it also slows down changes, because cached copies remain valid until they expire. A short TTL makes changes spread faster, but it increases DNS traffic. The practical tip is to lower the TTL well before a planned move, ideally at least as long as the old TTL before the change, so that by moving day most caches hold only a short-lived copy of the old record.

Propagation takes time because DNS is a layered, cached system rather than a single database that updates instantly everywhere. Your authoritative name server holds the current record, but resolvers, internet providers, company networks, browsers, and operating systems all cache answers for the TTL period. A visitor whose provider cached the old record yesterday will keep using it until that cache expires, even if your new record is already correct at the source. There is no button that forces every cache on the internet to clear, and that is by design: caching keeps DNS fast and resilient when servers are busy or briefly unreachable.

Reading differing answers is therefore a skill, not a sign that something is broken. If two resolvers return the new address and one still returns the old address, the change is spreading normally and the remaining resolver is simply holding an older cached copy. If all resolvers return the old address, your change may not have been saved at the authoritative server, or you may have edited the wrong zone or record. If resolvers return no answer or an error, check the domain spelling, confirm the domain is active, and confirm the record exists at all. Repeating the check after the TTL period passes gives a clearer picture than refreshing every few seconds, because a cached answer will not change until its TTL expires.

When a check does not match your expectations, work through the basics before changing more settings. First, confirm the record at your authoritative name server, since public resolvers can only repeat what they have cached or fetched from there. Second, look for typos in the name, value, and record type, because a record for the wrong subdomain will not fix the main domain. Third, clear your own browser and operating system DNS cache or test from another network, since a local cache can make a correctly propagated change look broken on one device only. Fourth, remember that email changes need extra care: an MX change affects delivery, so test sending and receiving after the TTL window rather than during it. If you need a simple single-resolver lookup alongside this comparison, try the DNS Lookup tool, and for ownership and registration details use the WHOIS Checker.

If you are launching a new website or moving an existing one, FistHost shared hosting starts at just $0.99/month, and a free domain is included with an annual plan, so you can point your domain, publish your site, and check propagation with this tool without paying a premium for basic hosting. Fast setup, straightforward controls, and affordable pricing make it a practical home for blogs, business sites, and small online stores that are just getting started.

Choosing hosting should not mean choosing between price and reliability, which is why many site owners start with FistHost shared hosting at $0.99/month with a free domain on an annual plan. You get the hosting space to build and grow your site, plus a domain name to match your brand, and you can verify every DNS change with the checker above as your site moves, updates, or expands to new services.

DNS checks fit naturally into a wider website workflow. Before registering a fresh idea, brainstorm names with the Domain Name Generator, and after your site is live, audit its outgoing and internal links with the Website Links Count Checker. Used together, these tools help you launch cleanly, spot broken settings early, and understand why visitors in different places may briefly see different versions of your site. Run a propagation check after any DNS edit, wait out the TTL, and check again, and you will rarely be caught out by a change that only looked complete.

User Reviews

No reviews yet. Be the first to review this tool!

Write a Review

★★★★★

Captcha

Reviews are protected by captcha and moderated before they appear.


Limited Offer

Hosting From $0.99/mo

Use code welcomegift
for extra savings today

Claim Offer
WordPress WordPress Hosting Made Easy One-click installs on fast, · secure servers Launch WordPress