nsone.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.
The policy (p=quarantine) applies to only 25% of failing mail (pct=25). The rest gets the next weaker policy.
How to fix: Raise pct step by step and remove it once it reaches 100.
Some DKIM keys are 1024-bit RSA. They still verify, but are considered weak.
How to fix: Create a 2048-bit key at the mail provider that uses the selector and publish it in place of the old one.
The .net zone lists 4 nameservers for nsone.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.
All 8 nameserver addresses answered over UDP.
All reachable nameservers answered over TCP.
Every reachable nameserver answers authoritatively for the zone.
The NS records at the parent and in the zone match.
No nameserver offers recursion to the public.
The zone's SOA record.
All nameservers have serial 1736533684.
The primary nameserver dns1.p01.nsone.net is one of the listed nameservers.
Refresh is 43200 s (12 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.
Every mail server address has a reverse DNS record.
The policy (p=quarantine) applies to only 25% of failing mail (pct=25). The rest gets the next weaker policy.
How to fix: Raise pct step by step and remove it once it reaches 100.
Some DKIM keys are 1024-bit RSA. They still verify, but are considered weak.
How to fix: Create a 2048-bit key at the mail provider that uses the selector and publish it in place of the old one.
The domain has one SPF record.
www.nsone.net resolves.
nsone.net resolves.
The website has an AAAA record and is reachable over IPv6.
Report generated in 422 ms.
Every nameserver has an IPv6 address.
The parent zone publishes a DS record, so DNSSEC is enabled for this domain.
No nameserver reveals its software version.
Nameservers are spread over 2 IPv4 networks.
Retry is 7200 s (2 hours), within the usual range.
Expire is 1209600 s (14 days), within the usual range.
Minimum (negative cache TTL) is 3600 s (1 hour), within the usual range.
There is a single MX record. That is fine if the host is itself redundant; senders retry for several days anyway.
No mail server has an IPv6 address.
Checking this record takes 4 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.
Receivers send aggregate reports to the address in the rua tag.