DNS Checker

A complete, live snapshot of any domain's DNS: A, AAAA, MX, NS, TXT, SOA and CAA records, plus where its mail actually goes.

Why a DNS snapshot is the first diagnostic step

Almost every "my website is down" and "my email stopped working" incident is a DNS story. Records were edited during a migration and one was missed; an old A record still points at a decommissioned server; the MX records point at a host that no longer resolves. A complete snapshot — taken live, not from a cache — is how you see the domain the way the rest of the internet sees it, which is often different from how it looks inside your own panel.

Read it in this order. A/AAAA tell you where the website lives; two different IPs across resolvers usually means a change is still propagating. MX tells you who receives mail — verify those hosts resolve (the mail routing table above does it for you) because an MX pointing at a name with no A record accepts mail into a void. NS tells you who is authoritative; if the nameservers listed here are not the provider you edit records in, you have been editing a zone nobody reads. TXT is where the email-authentication records live — verify them individually with the SPF, DKIM and DMARC checkers. CAA restricts which certificate authorities may issue for the domain; a mismatch there is a classic cause of failed renewals.

DNS Checker — frequently asked questions

I changed a record but the checker still shows the old value. Why?

Propagation. Every record carries a TTL (time to live) and resolvers cache the old answer until it expires. Lower the TTL a day before a planned migration; afterwards, most changes settle within the old TTL window.

What does it mean if MX hosts have no IP addresses?

The MX target hostname does not resolve to any A record — mail to the domain will bounce or queue. Either the target's own DNS is broken or the MX record names a host that no longer exists.

Why do I see records I never created?

Hosting panels and services (Microsoft 365, Google Workspace, Cloudflare) add records during verification and setup. An unfamiliar record is worth identifying before deleting — but a TXT record naming a service you cancelled years ago is exactly the kind of leftover worth cleaning up.

How is this different from the Full Site Health Check?

This page shows raw records. The Full Site Health Check interprets them — it validates SPF/DMARC/DKIM, checks blacklists and SSL, and tells you what is actually wrong.