Online AI Tools
Submit
Free Updated 2026-11-13 Web & Internet

DNS Checker

Ask dozens of resolvers the same question and see the answers on a map.

83 out of 100 6 of 6 dimensions

What it is

This is the tool you open in a panic after changing a nameserver: type the domain, get a world map of which resolvers already return the new record and which are still serving the old one. No account, no quota, no upsell — the whole site is free and funded by ads. It answers propagation questions better than a single nslookup ever can, because the point of propagation is that different places disagree. For reading one record on your own machine, the command line is faster; use this when the question is "is it everywhere yet".

Pricing updated 2026-11-13

Free
$0

Every tool on the site, no account and no quota; the site is ad-supported

Open pricing

DNS Checker pricing explained

There is no pricing to read because there is no paid product: every tool on the site is free, requires no account and has no stated quota. The trade is advertising, which adds weight to the first load and occasionally pushes content down the page. For a workflow that needs a programmatic check on every deploy, the missing API is the real limitation, not the price — that use case needs a different tool with a paid tier.

Free-tier limits are taken from the official pricing page on the update date above. They change often — confirm before you commit to an annual plan.

DNS Checker key features

Propagation across many resolvers

One query is sent to resolvers in dozens of locations, and the answers are grouped so a stale cache stands out immediately.

Record type filter

A, AAAA, CNAME, MX, TXT, NS and more can be asked for by name, which matters when the CNAME resolves but the TXT record does not.

A map instead of a table

Locations that already serve the new record are coloured differently from those still on the old one, which is the fastest read of the situation.

CDN flag

Answers proxied through a CDN are marked, so an unexpected IP is not mistaken for a misconfigured origin.

Public DNS list

A reference list of resolvers by provider and location, useful for comparing one resolver against another when a report disagrees.

Adjacent diagnostics

Reverse IP, PTR, CAA, SOA and health checks sit on the same site, so a single incident does not need four bookmarks.

DNS Checker: how it works

01

Queries fan out from distributed nodes

The check is not a lookup from one machine but a set of lookups from many, which is the only way the answer can show geographical disagreement.

02

No account means no history

Results are rendered per request and not stored against a user, which is why before-and-after comparison has to be done by hand.

03

Advertising funds the whole site

There is no paid tier and no API, so the tool stays free at the cost of ad weight on first load.

DNS Checker core strengths

It answers the real question

A single nslookup says what one server thinks; this says where the record has and has not reached, which is what a change window is about.

Zero friction during an incident

No signup, no quota, no login wall — the page loads and answers, which is exactly the property needed at 2 a.m.

The resolver list is diagnostic

Seeing one provider return the old record while others return the new one points at that provider cache rather than at the zone.

DNS Checker compared with alternatives

Tool DNS Checker Ahrefs Perplexity
Best for DNS records and propagationSEO and backlink dataAnswering questions with sources
Account needed NoYesNo
Free tier Everything, ad-supportedOwn verified site only$0 with daily limits
Bulk checks Yes, through the tool listPlan-dependentNo
Starting cost $0$129/mo$20/mo

Written from the official product pages listed under Sources, not copied from another directory. Prices and limits reflect the update date above; features ship faster than reviews, so treat the list as a starting point and confirm on the official site.

Pros and cons

Strengths

  • Answers the actual propagation question — where has it not updated yet
  • Nothing to sign up for, which matters during an incident
  • The resolver list doubles as a way to spot a poisoned or cached answer

Limitations

  • Advertising is heavy enough to slow the first load
  • No stored history, so comparing before and after means two screenshots
  • No API, so it cannot be wired into a deploy check

DNS Checker use cases

After a nameserver change

An admin switches nameservers and watches the map until no location still returns the old record before telling the client it is live.

Debugging a mail record

A marketer checks MX and TXT across resolvers and finds one provider caching an old SPF record that is failing delivery.

Verifying a domain migration

An agency moves a site to a new host and uses the CDN flag to confirm traffic is hitting the new edge rather than an old cache.

Checking a suspicious subdomain

A developer looks up A and CNAME records to see whether a subdomain points somewhere it should not.

Confirming DNS before a launch

Before a campaign, a team checks that regional resolvers all return the new landing page address.

Tools similar to DNS Checker