DNS tests explained
dnsrapor checks a domain with the tests below. Each page explains what the test looks at, why it matters and how to fix it when something is wrong.
Parent
- Domain NS recordsThis row shows which nameservers the parent servers for your TLD (for example gtld-servers.net for .com) report for your domain.
- TLD Parent CheckChecks whether the parent server that was asked has information about your domain's TLD.
- Your nameservers are listedChecks that the parent server reports at least one nameserver for your domain.
- DNS Parent sent GlueA glue record is the IP address the parent sends together with a nameserver's name.
- Nameservers A recordsChecks that every nameserver name listed at the parent resolves to an IPv4 address (an A record).
NS
- NS records from your nameserversYour nameservers listed at the parent are asked directly, and the NS records defined inside your zone are shown.
- Recursive QueriesChecks whether your nameservers also answer anyone for domains they do not host (whether they are open resolvers).
- Same GlueCompares the IP addresses the parent gives for your nameservers (glue) with the A records your nameservers give for the same names.
- Glue for NS recordsChecks whether your nameservers, when asked for the NS records, also include the IP addresses of those servers in the additional section of the answer.
- Mismatched NS recordsThe NS list returned by each nameserver is compared with the others; all are expected to return the same list.
- DNS servers respondedA query is sent to every nameserver listed at the parent to see whether an answer comes back.
- Name of nameservers are validChecks that the values in the NS records are valid hostnames.
- Multiple NameserversCounts how many nameservers the domain has.
- Nameservers are lameA lame nameserver is one that is listed at the parent for your domain but does not answer authoritatively for it.
- Missing nameservers reported by parentChecks for nameservers that are in your zone's NS records but are not listed at the parent.
- Missing nameservers reported by your nameserversChecks for nameservers that are listed at the parent but are missing from your zone's NS records.
- Domain CNAMEsChecks whether the domain itself (example.com, without www) has a CNAME record.
- NSs CNAME checkChecks whether the nameserver names in the NS records are CNAMEs.
- Different subnetsChecks whether the IP addresses of your nameservers are in the same /24 subnet.
- IPs of nameservers are publicChecks that the IP addresses of your nameservers are public, internet-reachable addresses.
- DNS servers allow TCP connectionA query is sent to each nameserver over TCP.
- Different autonomous systemsFinds which network operators (autonomous systems, AS) your nameservers are in and checks whether all of them are with the same operator.
- Stealth NS records sentChecks whether your nameservers also send, in their answers, nameservers that are not listed at the parent.
SOA
- SOA recordThe SOA (Start of Authority) record is the zone's identity card: it holds the primary nameserver, the responsible person's e-mail address, the serial number and the timers that tell secondaries how often to refresh the zone.
- NSs have same SOA serialThe SOA serial number reported by each nameserver is compared.
- SOA MNAME entryChecks whether the primary nameserver name in the SOA record (MNAME) is one of the nameservers listed at the parent.
- SOA SerialChecks whether the SOA serial is in the recommended YYYYMMDDnn format (year, month, day and a daily revision; for example 2026111601).
- SOA REFRESHREFRESH sets, in seconds, how often secondary nameservers ask the primary whether the zone has changed.
- SOA RETRYRETRY sets how long a secondary waits before trying again when it could not reach the primary.
- SOA EXPIREEXPIRE sets how long a secondary keeps serving the zone when it cannot reach the primary at all.
- SOA MINIMUM TTLThe last field of the SOA record today sets how long negative answers ("no such record") are cached by resolvers (RFC 2308).
MX
- MX RecordsMX (Mail Exchanger) records say which servers mail for your domain is delivered to.
- Different MX records at nameserversThe MX records returned by each nameserver are compared; all are expected to return the same records.
- MX name validityChecks that the server names in the MX records are valid names (no disallowed characters, not empty or malformed).
- MX IPs are publicChecks that the server names in the MX records resolve to public, internet-reachable IP addresses.
- MX CNAME CheckChecks whether the names the MX records point to are CNAMEs.
- MX A request returns CNAMEChecks whether a CNAME comes back when the A record of the name in the MX record is looked up.
- MX is not IPChecks whether the value of an MX record is an IP address instead of a hostname.
- Number of MX recordsCounts how many MX records the domain has.
- Mismatched MX AThe mail servers' address is found in two ways: the address your nameservers send along with the MX answer, and the address a public resolver finds for the same name.
- Duplicate MX A recordsChecks whether different MX records resolve to the same IP address.
- Reverse MX A records (PTR)Checks that every IP address of your mail servers has a reverse DNS (PTR, rDNS) record.
WWW
- WWW A RecordLooks up the A record for www.yourdomain and shows which IP addresses it resolves to, together with the CNAME chain if there is one.
- IPs are publicChecks that the IP addresses the www record resolves to are public, internet-reachable addresses.
- WWW CNAMEChecks whether the www record is a CNAME (an alias) and, if so, whether the name it points to resolves to an A record.
Extra checks
- IPv6The IPv6 check looks for AAAA records (IPv6 addresses) for your nameservers, your domain, your www address and your mail servers.
- DNSSECDNSSEC protects DNS answers with digital signatures: a resolver can verify that a record really comes from the domain's owner and was not altered in transit.
- SPF and DMARCSPF is a TXT record (starting with v=spf1) that declares which servers may send mail for your domain.
- DKIMDKIM adds a digital signature to every mail you send; the receiver verifies it with the public key you publish in DNS.