ovh.comDNS 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 is p=none: receivers send reports but still deliver mail that fails the checks, so the domain is not yet protected against forged mail.
How to fix: Read the reports until every service that sends for you passes, then move to p=quarantine and finally p=reject.
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 .com zone lists 6 nameservers for ovh.com.
6 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 10 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 2094993191.
The primary nameserver dns.ovh.net is one of the listed nameservers.
Refresh is 86400 s (1 day), outside the usual range of 20 minutes to 12 hours. This matters only if your secondary nameservers copy the zone with zone transfers.
The domain has 2 MX records.
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 is p=none: receivers send reports but still deliver mail that fails the checks, so the domain is not yet protected against forged mail.
How to fix: Read the reports until every service that sends for you passes, then move to p=quarantine and finally p=reject.
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.ovh.com resolves.
ovh.com resolves.
The website has no AAAA record, so it is reachable over IPv4 only.
Report generated in 227 ms.
The domain is reachable over IPv6, but some nameservers are IPv4-only.
No DS record at the parent zone. The domain is not signed with DNSSEC.
No nameserver reveals its software version.
Nameservers are spread over 5 IPv4 networks.
Retry is 3600 s (1 hour), within the usual range.
Expire is 3600000 s (41.7 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.
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.