What a DNS lookup tells you
Every domain has a set of DNS records: small entries that tell the rest of the internet where its website lives, which servers take its email and who answers for it. A DNS lookup asks for those records and shows you the answers exactly as other computers see them. It is the first thing to check when a site won't load, mail stops arriving or a change you made doesn't seem to take effect.
We ask our own resolver for every record type at once and show each answer as it comes back, so a slow type never holds up the others. Each record comes with its TTL, the number of seconds other servers may keep a copy before they ask again. A long TTL explains why a change can take hours to show everywhere.
The records you'll see
- A and AAAA give the domain's IPv4 and IPv6 addresses: where browsers connect.
- CNAME makes a name an alias of another name. If the name you check is an alias, we follow it up to 8 steps and show each one, so you can see where it really ends up.
- MX lists the servers that receive the domain's email, in order of preference. We also look up each mail server's addresses, because an MX record that points at a name with no address means lost mail.
- NS names the servers that answer for the domain. We look up their addresses too.
- TXT holds text for other services: SPF rules for email, ownership checks from Google or Microsoft, and more.
- SOA describes the zone itself: its primary server, its serial number and its timers.
- CAA says which certificate authorities may issue certificates for the domain.
You can add PTR, SRV, DS, DNSKEY, HTTPS, SVCB, TLSA and NAPTR from the record types list when you need them.
DNSSEC in one paragraph
DNSSEC adds signatures to DNS answers, so a resolver can prove an answer wasn't changed on the way. We report whether the domain is signed and whether its signatures check out. A domain that is signed but fails validation is a real problem: resolvers that check signatures will refuse to answer for it at all, so for their users the domain simply disappears. An unsigned domain still works everywhere; signing is worth doing, but its absence is not an outage.
How to read the findings
Under the records you'll find findings, sorted with problems first. Each one says what we saw, why it matters and what to change. A few examples:
- The domain doesn't exist. The registry has no record of it, or it was never delegated to name servers. Check the spelling, then check the registration.
- An alias at the top of the domain. A CNAME on the bare domain clashes with the records every domain needs there, such as NS and SOA. Most DNS hosts offer a flattened alias for this case.
- A mail server that is an alias or an address. MX records must name a host with its own address records, not an IP address and not a CNAME.
- No IPv6 or CAA records. Shown as information: worth knowing, never urgent.
Where a fix guide exists, the finding links to it with step-by-step instructions for the common DNS hosts.
Running the same lookup from code
Every check on this page works the same way through our API and from AI agents over MCP. Under each result
you'll find a ready-made curl command and the MCP tool call with the same name and record types, so you can
repeat the lookup from a script, a monitoring job or a chat with your agent. API lookups cost 1 credit each,
cached answers included, and failed lookups are free.
Why answers can differ between tools
DNS is cached at every step. Your computer, your router and your internet provider may each hold an older copy of a record until its TTL runs out. We ask a fresh resolver and honour the TTLs, so what you see here is what a typical resolver would hand out right now. If you just changed a record and still see the old value, the TTL on the old record tells you the longest you might wait.