DNS & Email Security Report for ovh.com

• A record presentcritical

  1 A record(s) found

• AAAA record presentrecommended

  No AAAA records

• MX records presentrecommended

  2 MX record(s) found

• NS records presentcritical

  6 NS record(s) found

• SOA record presentcritical

  SOA record found

• Multiple nameserversrecommended

  6 nameservers configured ✓

• SOA serial formatinfo

  Serial 2081022100 (YYYYMMDDnn format)

• SOA timers validinfo

  Refresh: 86400s ✗, Retry: 3600s ✓, Expire: 3600000s ✗. Refresh should be 1200-43200s (20min-12h). Expire should be 604800-2419200s (1-4 weeks)

• No lame nameserversinfo

  6 NS all responding ✓

• Glue records presentinfo

  No glue needed

• WWW record configuredinfo

  A record matches apex

• MX servers have PTR recordsinfo

  2 MX IPs all have PTR records ✓

• MX servers have FCrDNSinfo

  2 MX IPs have forward-confirmed reverse DNS ✓

• DNSSEC signedrecommended

  DNSSEC not configured. Enable DNSSEC at your domain registrar to protect against DNS spoofing

• DNSSEC validation OKcritical

  Not applicable (DNSSEC not enabled)

• NSEC3 RFC 9276 compliantrecommended

  Not applicable (domain uses NSEC or is not DNSSEC-signed)

• RRSIG signatures validrecommended

  Not applicable (DNSSEC not enabled)

• Modern DNSSEC algorithmoptional

  Not applicable (DNSSEC not enabled)

• DS digest algorithm modernrecommended

  Not applicable (no DS records or DNSSEC not enabled)

• DNSKEY algorithm secureoptional

  Not applicable (DNSSEC not enabled)

• RRSIG TTL saferecommended

  Not applicable (DNSSEC not enabled or no RRSIG data)

• Chain of trust completecritical

  DNSSEC not enabled

• Website reachable via IPv6recommended

  No IPv6 for website. Add AAAA record pointing to your IPv6 address

• Mail servers reachable via IPv6recommended

  0/2 MX servers have IPv6. Add AAAA records for your mail servers

• Nameservers reachable via IPv6recommended

  4/6 NS server(s) with IPv6 ✓

• SPF record presentcritical

  v=spf1 include:spf.mailjet.com include:mx.ovh.com ~all

• SPF syntax validcritical

  SPF syntax is correct ✓

• SPF policy strict (-all)recommended

  SPF uses ~all or ?all. Change to -all for strict enforcement

• DKIM foundrecommended

  No DKIM found. Configure DKIM signing with your email provider

• DMARC record presentrecommended

  v=DMARC1; p=none; rua=mailto:[email protected]; rf=afrf; pct=100;

• DMARC policy quarantine or betterrecommended

  DMARC policy: none. Set p=quarantine or p=reject

• DMARC policy rejectoptional

  DMARC policy: none. Set p=reject for maximum protection

• BIMI record presentoptional

  BIMI logo: https://vmc.digicert.com/e9b9f593-66be-4cbc-9a49-6811297e9244.svg

• BIMI configuration validoptional

  BIMI correctly configured ✓

• MTA-STS record presentoptional

  No MTA-STS. Add TXT at _mta-sts and host policy at /.well-known/mta-sts.txt

• MTA-STS policy enforcedoptional

  MTA-STS not configured

• MX records validcritical

  2 MX record(s) ✓

• MX domains use DNSSECrecommended

  0/1 MX domain(s) have DNSSEC. Ask your mail provider to enable DNSSEC

• MX DNSSEC validation OKrecommended

  DNSSEC not enabled for MX domains

• Mail servers not blacklistedcritical

  1/1 MX server(s) blacklisted: mx1.ovh.net on UCEPROTECT L3, mx1.ovh.net on JustSpam

• No critical blacklist listingscritical

  No critical listings, but some servers are on blacklists

• CAA records presentrecommended

  No CAA records. Add CAA record to specify allowed certificate authorities

• CAA policy strictoptional

  CAA not strict. Add CAA 0 issue "letsencrypt.org" (or your CA) to restrict issuance

• TLSA records (DANE)optional

  No TLSA/DANE records. Add TLSA at _25._tcp.mail for DANE email encryption

• DANE configuration validoptional

  No DANE configured

• No sensitive info in TXTcritical

  No sensitive data leaked ✓

• Verification records reviewedinfo

  2 verification record(s): Facebook/Meta, Google. Consider if all are still needed

• HTTPS availablecritical

  HTTPS working (status 200) ✓

• Valid certificatecritical

  Certificate chain is valid and trusted ✓

• HTTP redirects to HTTPScritical

  HTTP automatically redirects to HTTPS ✓

• HSTS enabledrecommended

  No HSTS header. Add Strict-Transport-Security header with max-age of at least 31536000 (1 year)

• HSTS max-age >= 1 yearoptional

  HSTS not enabled

• X-Frame-Options headerrecommended

  X-Frame-Options: SAMEORIGIN ✓

• X-Content-Type-Options headerrecommended

  X-Content-Type-Options: nosniff ✓

• Content-Security-Policy headerrecommended

  No Content-Security-Policy header. Add CSP to prevent XSS and other injection attacks

• Referrer-Policy headerrecommended

  No Referrer-Policy header. Add Referrer-Policy: strict-origin-when-cross-origin

• security.txt presentoptional

  Contact: [email protected]

• security.txt validoptional

  security.txt missing required fields. Must have Contact: and Expires: per RFC 9116

• HTTP/3 (QUIC) supportedoptional

  No HTTP/3 support detected No h3 in Alt-Svc header No HTTPS DNS record (type 65) QUIC probe inconclusive (Inconclusive - no QUIC reply (trigger may be dropped or UDP/443 filtered)) — not a negative signal

• QUIC UDP reachableinfo

  QUIC probe inconclusive (no reply — trigger may be dropped or UDP/443 filtered). Not a negative signal; h3 is judged from Alt-Svc / HTTPS record

• HTTPS DNS record (SVCB)optional

  No HTTPS DNS record (type 65). Add HTTPS record for faster HTTP/3 discovery: ovh.com IN HTTPS 1 . alpn="h3,h2"

Implement DNSSEC

Activate DNSSEC with your domain registrar and add the DS records to your parent zone. This protects against DNS spoofing attacks.

Impact: Significantly increases security and prevents DNS manipulation

Strengthen DMARC policy

Change your DMARC policy from "none" to "quarantine" or "reject" for better protection.

Impact: Increases email security and prevents abuse

Implement DKIM

Configure DKIM signing with your email provider and publish the DKIM public key in DNS.

Impact: Improves email deliverability and prevents spoofing

Add IPv6 support

Request AAAA records from your hosting provider for your website. IPv6 is becoming increasingly important.

Impact: Makes your website accessible to IPv6-only networks

Add CAA records

Define which Certificate Authorities may issue SSL certificates, for example: "0 issue letsencrypt.org"

Impact: Prevents unauthorized certificate issuance

IPv6 for mail servers

Add AAAA records for your MX servers to support email via IPv6.

Impact: Improves email reachability for IPv6 networks

Enable HTTP/3 (QUIC)

Enable HTTP/3 for faster page loads and improved connection resilience. Nginx: add "listen 443 quic reuseport;" and "add_header Alt-Svc 'h3=":443"; ma=86400'". Caddy: HTTP/3 is enabled by default. Cloudflare: Enable under Speed → Protocol Optimization. Also add an HTTPS DNS record: example.com IN HTTPS 1 . alpn="h3,h2" Ensure UDP port 443 is open in your firewall (QUIC uses UDP, not TCP).

Impact: Faster page loads (0-RTT), better mobile performance, and connection migration between networks