Identity
4
D
ovhcloud.com
Posture Score: 63/100
Scanned May 8, 2026 at 8:09 AM UTC
Attack Surface
88
Reputation
96
Identity Findings
No DKIM records found
No DKIM records were found for any common selector. Email may not be authenticated.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.ovhcloud.com
No STARTTLS support on mx3.mail.ovh.net:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mx1.mail.ovh.net:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mx0.mail.ovh.net:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mx2.mail.ovh.net:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mx3.mail.ovh.net
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mx1.mail.ovh.net
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mx0.mail.ovh.net
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mx2.mail.ovh.net
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
DMARC policy is monitoring-only (p=none)
The p=none policy only monitors; it does not instruct receivers to quarantine or reject unauthenticated mail.
💡 Upgrade to p=quarantine or p=reject after reviewing aggregate reports.
No MTA-STS record found
Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.
💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.ovhcloud.com/.well-known/mta-sts.txt
BIMI requires DMARC p=quarantine or p=reject
Current DMARC policy is p=none. BIMI logos will not display without enforcement.
💡 Upgrade DMARC policy to p=quarantine or p=reject.
STARTTLS without MTA-STS or DANE protection
STARTTLS alone is vulnerable to downgrade attacks. Neither MTA-STS nor DANE is configured to enforce encryption.
💡 Deploy MTA-STS and/or DANE to protect against STARTTLS stripping attacks.
No CAA records found
No CAA records are configured. Any certificate authority can issue certificates for this domain.
💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"
No TLS-RPT record found
Without TLS-RPT, you will not receive reports about TLS negotiation failures.
💡 Publish a _smtp._tls TXT record (e.g. "v=TLSRPTv1; rua=mailto:tls-reports@ovhcloud.com").
ARC support not detected
No evidence of ARC (Authenticated Received Chain) support on MX servers. Forwarded messages may lose authentication.
💡 Consider enabling ARC signing on your mail servers to preserve authentication through forwarding.
Very low TTL on A record: 60s
The A record has a TTL of 60s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 16s
The DMARC record has a TTL of 16s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
IPv6 readiness is good
IPv6 records are present and properly configured.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
DKIM2 not detected
No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
DMARCbis np tag absent
The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.
Deprecated DMARCbis tags found: pct, rf
The DMARC record contains tags deprecated in DMARCbis: pct, rf. Consider removing these for forward compatibility.
DMARCbis psd tag absent
The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
Open mail ports on mx3.mail.ovh.net
Detected open mail-related ports: 25
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
MX IP network diversity
MX IPs span 4 different /16 networks, providing good diversity.
SOA record parameters
Serial: 2078059948, Refresh: 86400s, Retry: 3600s, Expire: 3600000s, Min TTL: 300s
Attack Surface Findings
Non-responsive IP for blog.ovhcloud.com: 2001:41d0:301::25
The subdomain blog.ovhcloud.com resolves to 2001:41d0:301::25 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2001:41d0:301::25 is operational or remove the DNS record for blog.ovhcloud.com.
Domain enumerability: medium
The domain has moderate enumerability. CT logs and DNS records reveal significant information about the domain structure.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
DNSSEC is not enabled
No DNSKEY or DS records were found. DNS responses are not cryptographically authenticated.
💡 Enable DNSSEC by generating DNSKEY records and publishing DS records at the registrar.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
5 subdomain(s) discovered for ovhcloud.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for ovhcloud.com and its subdomains. Each certificate reveals subdomain names.
1 email SRV record(s) found
Email service SRV records expose mail server configuration for automatic client setup.
Reputation Findings
Missing Strict-Transport-Security on ovhcloud.com
The Strict-Transport-Security header is not set on https://ovhcloud.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
security.txt present
Found security.txt at https://ovhcloud.com/.well-known/security.txt.
TLS certificate valid for 59 days
Certificate for ovhcloud.com expires on 2026-07-06.
Certificate issued by R12
The certificate for ovhcloud.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for ovhcloud.com uses an acceptable signature algorithm.
RSA key: 4096 bits
The certificate for ovhcloud.com uses an adequate RSA key of 4096 bits.
SCTs present in certificate
The certificate for ovhcloud.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on ovhcloud.com.
Domain valid for 2392 days
Domain ovhcloud.com expires on 2032-11-24.
Domain transfer and delete locks enabled
Domain ovhcloud.com has clientTransferProhibited and clientDeleteProhibited locks.
Google Safe Browsing DNS check — no flag detected
DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.
Abuse contact lookup failed
Could not query abuse contact information.
PhishTank — API key required
PhishTank phishing database check requires an API key.
Sender Score — API key required
Sender Score reputation check requires an API key.
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
Could not connect to webmail.ovhcloud.com
HTTPS request to https://webmail.ovhcloud.com failed or timed out.
WHOIS registration data
Registrar: OVH sas | Created: 2011-11-24 | Expires: 2032-11-24 | Updated: 2024-03-27
WHOIS privacy protection enabled
Domain ovhcloud.com has WHOIS privacy/redaction enabled.
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record found and configured
→
DMARC Policy
DMARC policy: none
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature missing
→
DMARC Policy
DMARC policy: none
⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.
Mail Server Identity: mx3.mail.ovh.net
PTR record proves mail server legitimacy
MX: mx3.mail.ovh.net
Mail server at 91.121.53.175
→
PTR Record
Reverse DNS: mx3.mail.ovh.net
Mail Server Identity: mx1.mail.ovh.net
PTR record proves mail server legitimacy
MX: mx1.mail.ovh.net
Mail server at 188.165.36.237
→
PTR Record
Reverse DNS: mx1.mail.ovh.net
Mail Server Identity: mx0.mail.ovh.net
PTR record proves mail server legitimacy
MX: mx0.mail.ovh.net
Mail server at 178.33.252.245
→
PTR Record
Reverse DNS: mx0.mail.ovh.net
Mail Server Identity: mx2.mail.ovh.net
PTR record proves mail server legitimacy
MX: mx2.mail.ovh.net
Mail server at 87.98.160.167
→
PTR Record
Reverse DNS: mx2.mail.ovh.net
Mail Server Reputation: mx3.mail.ovh.net
RBL check ensures server is not blacklisted
MX: mx3.mail.ovh.net
Mail server at 91.121.53.175
→
RBL Status
Not blacklisted
Mail Server Reputation: mx1.mail.ovh.net
RBL check ensures server is not blacklisted
MX: mx1.mail.ovh.net
Mail server at 188.165.36.237
→
RBL Status
Not blacklisted
Mail Server Reputation: mx0.mail.ovh.net
RBL check ensures server is not blacklisted
MX: mx0.mail.ovh.net
Mail server at 178.33.252.245
→
RBL Status
Not blacklisted
Mail Server Reputation: mx2.mail.ovh.net
RBL check ensures server is not blacklisted
MX: mx2.mail.ovh.net
Mail server at 87.98.160.167
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
TLS not verified or unsupported
→
MTA-STS Policy
MTA-STS not configured
⚠️ TLS support could not be verified. MTA-STS requires TLS to enforce encrypted connections. Without TLS, MTA-STS cannot function.
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC not enforced (p=none or missing)
→
BIMI Record
Brand logo configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
TLS not verified or unsupported
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS support could not be verified. TLS-RPT reports on TLS connection failures, but without TLS support, there's nothing to monitor. You need working TLS encryption before TLS-RPT can provide value.
Security Checks
MX Records
✓
SPF Record
✓
DKIM Record
✗
DMARC Policy
✓
BIMI Record
✓
CAA Records
✗
DNSSEC
✗
MTA-STS
✗
TLS-RPT
✗
Embed Badge
Display your domain's security grade on your website or README:
<img src="https://scan.ractermx.com/badge/ovhcloud.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan ovhcloud.com Again