quad9.netDNS health report
Testing every nameserver. This takes a few seconds.
Testing every nameserver. This takes a few seconds.
Failures and warnings, most serious first, each with what to do.
Some nameservers reveal their software version, which helps attackers pick exploits.
How to fix: Hide the version string (in BIND: version "none"; in the options block).
The .net zone lists 4 nameservers for quad9.net.
4 nameservers are listed. At least two are required.
Every nameserver that needs a glue record has one.
Every nameserver name resolves to an address.
Some nameservers reveal their software version, which helps attackers pick exploits.
How to fix: Hide the version string (in BIND: version "none"; in the options block).
All 4 nameserver addresses answered over UDP.
All reachable nameservers answered over TCP.
Every reachable nameserver answers authoritatively for the zone.
The zone's SOA record.
All nameservers have serial 2026111600.
The primary nameserver secondary1.xzrh1.infra.6panb.ch is one of the listed nameservers.
Refresh is 10800 s (3 hours), within the usual range.
The domain has 1 MX record.
All nameservers return the same MX records.
Every mail server resolves to an address.
No MX record points to a CNAME.
Some mail server addresses have no reverse DNS record. Receiving works without it, but if the same hosts also send mail, many receivers will reject it.
The domain has one SPF record.
Checking this record takes 5 of the 10 DNS lookups a receiver allows, includes within includes counted.
Mail from servers the record does not list fails SPF (~all).
The domain has a DMARC record.
www.quad9.net resolves.
quad9.net resolves.
The website has an AAAA record and is reachable over IPv6.
Report generated in 2422 ms.
Every nameserver has an IPv6 address.
The parent zone publishes a DS record, so DNSSEC is enabled for this domain.
The NS records at the parent and in the zone match.
No nameserver offers recursion to the public.
Nameservers are spread over 2 IPv4 networks.
Retry is 3600 s (1 hour), within the usual range.
Expire is 172800 s (2 days), outside the usual range of 2 to 4 weeks. This matters only if your secondary nameservers copy the zone with zone transfers.
Minimum (negative cache TTL) is 600 s (10 minutes), within the usual range.
How to fix: If these hosts send mail, ask the owner of the IP address (your hosting provider) to set a PTR record.
There is a single MX record. That is fine if the host is itself redundant; senders retry for several days anyway.
Mail that fails both SPF and DKIM goes to spam (p=quarantine).
Receivers send aggregate reports to the address in the rua tag.
Found 2 DKIM keys under the common selectors.