What a DNS check tool actually does
DNS — the Domain Name System — is the internet’s address book. It turns a name people can remember (example.com) into the numeric address a machine needs to connect. When you set up a website or email, you publish a handful of DNS records that say “this name points here”.
A DNS check tool queries those published records and shows you exactly what is live right now. That sounds trivial until you hit the gap that catches almost everyone: what you entered in your dashboard and what the world can see are not always the same thing. Changes take time to spread, dashboards can silently reject a malformed entry, and a stray trailing space or a record set on the wrong subdomain will happily break your site while looking correct at a glance.
If I saved the record in my registrar's control panel, it's live.
Saving it publishes it, but the rest of the internet caches the old value until it expires. A DNS check tool queries the public system directly, so it shows you what visitors actually get — which is the only view that matters when something is broken.
The records you will actually check
There are a dozen-plus record types, but four cover the overwhelming majority of real problems. Learn to recognise these and most DNS troubleshooting becomes a process of elimination.
| Record | What it does | What breaks if it is wrong |
|---|---|---|
| A | Points a domain at a server’s IPv4 address (the numeric one). | The site does not load, or loads the wrong site. |
| CNAME | Points one name at another name (e.g. www at your host’s address). | A subdomain like www fails while the bare domain works, or vice versa. |
| MX | Says which mail server receives email for the domain. | Incoming email bounces or silently disappears. |
| TXT | Holds text: SPF and DKIM (email authentication) and verification strings. | Your outgoing email lands in spam, or a service refuses to verify the domain. |
| NS | Names the authoritative servers in charge of the whole zone. | Nothing resolves at all — the domain has no working DNS. |
The free tools worth using
You do not need to pay for DNS checking. These are the free tools that professionals actually reach for, and what each is best at.
| Tool | Best for | Worth knowing |
|---|---|---|
| Google Admin Toolbox Dig | A clean, fast lookup of any single record type. | Run by Google, no ads, no signup. Shows the raw answer the way a network engineer would read it. |
| MXToolbox | Email problems — MX, SPF, DKIM, and blacklist checks in one place. | The go-to for “why is my email bouncing”. Free for lookups; paid monitoring exists but you rarely need it. |
| whatsmydns.net | Seeing whether a change has propagated worldwide. | Queries dozens of servers across the globe at once and shows a map of who has the new value yet. |
| dig / nslookup (command line) | Fast checks if you are already in a terminal. | Built into macOS and Linux (nslookup is on Windows too). No install, but you read raw output. |
There is a lot of overlap. For a beginner, the honest advice is: use a propagation checker when you have just made a change and are waiting for it to take, and use a straight lookup (ours, Google’s, or MXToolbox) when you want to confirm what a record currently says. Everything else is a refinement.
The propagation trap explained
The single most common DNS confusion is propagation, so it is worth understanding properly — it will save you from “fixing” something that was never broken.
When you change a record, your DNS provider publishes the new value immediately. But every other server that looked up the old value cached it, and will keep serving that cached copy until it expires. How long that takes is set by the record’s TTL (time to live) — a number of seconds attached to each record. A one-hour TTL means the old value can linger for up to an hour after you change it; some resolvers hold on a little longer.
Propagation can take 24 to 48 hours, so I just have to wait two days.
48 hours is the safe worst case, not the norm. Most changes are visible in minutes to a couple of hours, governed by your TTL. If a checker shows the new value on most servers but your own browser still shows the old site, the culprit is usually your local machine or router cache — not global propagation.
How to troubleshoot the common failures
Almost every DNS problem a normal site owner hits falls into one of a few buckets. Here is the order to check them in.
- 1
Confirm the NS records first
Look up the domain’s NS records. Do they point at the provider whose dashboard you have been editing? If not, you have been editing the wrong zone — a surprisingly common cause of “my changes do nothing”. Fix this before touching anything else. - 2
Check the A or CNAME for the exact hostname failing
Ifwww.example.comworks butexample.comdoes not (or the reverse), you are missing a record for one of them. The bare domain usually needs an A record;wwwis often a CNAME. Check each hostname separately — they are independent. - 3
For email, check MX then SPF/DKIM
Email not arriving? Confirm the MX records point at your mail provider. Email arriving but landing in spam? That is an authentication problem — check the SPF and DKIM TXT records against what your provider tells you they should be. MXToolbox reports all three in one view. - 4
Rule out caching before assuming it is broken
If a global propagation checker shows the correct value but your machine still does not, the record is fine — your local DNS cache is stale. It clears on its own, or sooner if you flush it and restart your browser. Do not keep re-editing a record that is already correct.
Using our free DNS lookup
Our DNS lookup tool covers the everyday cases without a signup. Enter a domain, pick the record type — A, MX, TXT, CNAME, or NS — and it returns what is currently published, with a propagation check so you can see whether a recent change has spread. It is the fastest way to answer the two questions you will ask most: “what does this record say right now?” and “has my change taken effect yet?”
Once your records are right, the next practical step is usually managing them well — and that starts with a registrar that gives you clean, free DNS control. See Best domain registrar, and if you are still setting things up, how to register a domain.
DNS check tools — common questions
- What is the best free DNS check tool?
- There is no single best — they specialise. For a fast single-record lookup, Google Admin Toolbox Dig or our own DNS lookup tool. For email problems (MX, SPF, DKIM, blacklists), MXToolbox. For checking whether a change has spread worldwide, a propagation checker like whatsmydns.net. All are free.
- How long does DNS take to update?
- It depends on the record’s TTL (time to live). Most changes are visible within minutes to a couple of hours. The often-quoted 24 to 48 hours is a safe worst case, not the norm. Lowering the TTL a day before a planned change makes the update propagate much faster.
- Why does my website work for me but not for other people?
- Almost always caching. Your machine or network still holds the old DNS value while others have already picked up the new one — or vice versa. Confirm with a global propagation checker: if it shows the correct value on most servers, the record is fine and your local cache just needs to clear.
- Why is my email not arriving?
- Check the MX records first — they name the server that receives your mail, and if they point at the wrong place (or nowhere), incoming email bounces or vanishes. If mail arrives but lands in spam, that is a separate authentication issue: check the SPF and DKIM TXT records against what your email provider specifies.
- Do I need to pay for a DNS checker?
- No. Every check a normal site owner needs — record lookups, propagation, email diagnostics — is available free. Paid tiers exist mainly for continuous monitoring and alerting, which matters for larger operations but is overkill for a single site.
- What is the difference between an A record and a CNAME?
- An A record points a name directly at a numeric IP address. A CNAME points one name at another name (an alias), and whatever that target resolves to is used. Rule of thumb: use an A record for the bare domain, and a CNAME when you want a subdomain like www to follow another host’s address.