DNS Gurus

SSL Verification Bypassed

The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.

Reason:

Hostname Mismatch - certificate is issued for outlook.live.com, outlook-sdf.live.com, attachment.outlook.office.net, attachment.outlook.officeppe.net, hotmail.com, *.calendar.live.com, *.hotmail.com, *.live.com, *.mail.live.com, not for live.fr

Cached · just now
78/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=outlook.live.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Cloud Services CA-1
Valid From
September 13, 2025
Valid Until
September 12, 2026 216 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
C7:AC:FA:60:C6:BA:D7:F7:8A:69:E6:B0:F2:B4:1A:E0:FC:2B:44:9D:34:0C:EF:91:5A:FB:65:C5:67:6D:D5:19
Alternative Names
14 domains

Security Configuration

TLS Protocols
TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)

HTTP Security Headers

Status
Strict-Transport-Security
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Consider adding 'preload' to HSTS for maximum security
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • Add X-Content-Type-Options: nosniff
  • • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
  • • Consider adding Permissions-Policy to control browser features

CAA Records (Certificate Authority Authorization)

CAA Records
Configured (Restricts certificate issuance)
Current Issuer
Not Authorized (Potential misconfiguration)
CAA Issues
  • • CRITICAL: Current certificate issuer 'C=US, O=DigiCert Inc, CN=DigiCert Cloud Services CA-1' is NOT authorized by CAA records. Authorized CAs:
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts