The DNS health check looks at a whole domain the way a DNS administrator would. It asks each authoritative name server directly whether it answers, is authoritative and has the same SOA serial and NS records as the others, then checks the SOA timers, DNSSEC, the records on the bare domain and www, CAA, and whether a wildcard record is set.
It also validates the email records – MX, SPF (including the 10-lookup limit), DMARC and DKIM keys under common selectors – and looks up about 60 common subdomain names such as mail, api, dev or vpn. Everything is done with DNS queries only; no web requests are sent to the subdomains. Each problem comes with a short explanation and a fix.
How to use the DNS Health Check tool
- Enter the main domain, for example
example.com. - Optionally add your DKIM selector if you know it (it is the
s=value in an email's DKIM-Signature header). - Click Scan DNS and wait 5–15 seconds.
- Work through the failed and warning items, then scan again.
Why use ToolOrca DNS Health Check
- Queries every authoritative name server directly (lame delegation, serial mismatch, NS consistency)
- SOA timers checked against RFC 1912 recommendations
- DNSSEC: DS and DNSKEY records and validation status
- MX resolution and port-25 reachability of public mail servers
- SPF with recursive lookup count, DMARC policy, DKIM under ~40 common selectors
- Wildcard detection and DNS-only discovery of ~60 common subdomains
Name server problems this finds
Lame delegation means a name server listed for your domain does not actually host the zone – visitors whose resolver picks that server get errors. Serial mismatch means secondary servers have not copied the latest zone from the primary. Inconsistent NS records means the name servers listed at your registrar differ from those inside the zone.
Running at least two name servers on different networks protects you from a single outage. Most DNS providers (Cloudflare, Route 53, Google Cloud DNS) already do this; self-hosted DNS often does not.
DNSSEC in plain words
DNSSEC signs your DNS records so resolvers can detect forged answers. It needs two parts: DNSKEY records in your zone (published by your DNS host) and a DS record at the registry (added at your registrar). A DS record without matching keys is dangerous: validating resolvers such as 1.1.1.1 and 8.8.8.8 will refuse to resolve the domain at all.
About the subdomain list
The scanner looks up a fixed list of common names in public DNS and shows those that exist. It does not guess thousands of names, read certificate logs or contact the hosts. When the domain has a wildcard record, names that only match the wildcard are left out.
Frequently asked questions
How is the score calculated?
Each check that passes counts fully, a warning counts half and a failure counts nothing. Information items (such as "no DNSSEC") are not scored.
Why does it say port 25 is not reachable?
Either the mail server blocks it, or outgoing port-25 connections from our server are blocked by our ISP. The MX lookup tool shows more detail.
Why was my DKIM key not found?
Your provider may use a selector that is not on our list. Enter it in the selector field; you find it as s= in the DKIM-Signature header of an email you sent.
Can I scan a subdomain?
Scan the main domain: name server and SOA checks only make sense at the zone apex.
Can I check a device on my home or office network?
No. For safety, private and local addresses (192.168.x.x, 10.x.x.x, localhost, .local names and similar) are refused. Our server can only test public hosts on the internet.