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 autoconfig.server.chatrium.com, autodiscover.server.chatrium.com, cpanel.server.chatrium.com, cpcalendars.server.chatrium.com, cpcontacts.server.chatrium.com, ipv6.server.chatrium.com, mail.server.chatrium.com, server.chatrium.com, webdisk.server.chatrium.com, not for ns1.chatrium.com

Cached · just now
76/100 SECURITY SCORE

Certificate Information

Subject
CN=server.chatrium.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
November 29, 2025
Valid Until
February 27, 2026 29 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
19:DA:38:D2:C7:D6:BA:E9:16:1A:82:D0:AA:ED:10:5A:4B:60:59:20:1D:13:61:44:EC:D7:A6:1B:E6:F0:82:13
Alternative Names

Security Configuration

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

HTTP Security Headers

Status
Strict-Transport-Security
Excellent
max-age=31536000; includeSubDomains; preload
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
  • 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
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