SSL Certificate Analysis for webmail.ioc.olympic.org - Security Grade & TLS Configuration

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 graph.windows.net, *.aadg.windows.net, *.aadkds.ppe.reporting.msidentity.com, *.aadkds.prd.reporting.msidentity.com, *.accesscontrol.aadtst3.windows-int.net, *.accesscontrol.windows-ppe.net, *.accesscontrol.windows.net, *.adls.aadkds.ppe.reporting.msidentity.com, *.adls.aadkds.prd.reporting.msidentity.com, not for webmail.ioc.olympic.org

Open Cached · just now

82/100 SECURITY SCORE

Certificate Information

Subject

C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=graph.windows.net

Issuer

C=US, O=DigiCert Inc, CN=DigiCert SHA2 Secure Server CA

Valid From

October 28, 2025

Valid Until

April 26, 2026 144 days

Public Key

RSA 2048 bit Adequate

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

66:32:54:B2:C2:F6:0F:1D:DE:55:F3:F7:B6:F3:A4:E3:C0:16:96:FD:29:3B:B8:EB:5E:9A:2A:C4:A3:CC:EE:6E

Alternative Names

63 domains

Security Configuration

TLS Protocols

TLS 1.2

Forward Secrecy

Limited (Check cipher configuration)

Warnings

• TLS 1.3 is not supported (recommended)

HTTP Security Headers

Status

Strict-Transport-Security

Good

max-age=31536000; includeSubDomains

Content-Security-Policy

Missing

Not configured

X-Frame-Options

Excellent

DENY

X-Content-Type-Options

Good

nosniff

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 Referrer-Policy header (recommended: strict-origin-when-cross-origin)
• Consider adding Permissions-Policy to control browser features

CAA Records (Certificate Authority Authorization)

CAA Records

Not Configured (Any CA can issue certificates)

CAA Issues

• No CAA records configured - any CA can issue certificates

Recommendations

• Implement CAA records to restrict which CAs can issue certificates for your domain
• This adds an extra layer of security against unauthorized certificate issuance
• Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
• Consider adding 'iodef' record to receive security incident reports