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 cpanel.marksdiamonds.com, cpcalendars.marksdiamonds.com, cpcontacts.marksdiamonds.com, mail.marksdiamonds.com, marksdiamonds.com, webdisk.marksdiamonds.com, webmail.marksdiamonds.com, whm.marksdiamonds.com, www.marksdiamonds.com, not for ipv6.node220.myfcloud.com

81/100 SECURITY SCORE

Certificate Information

Subject
CN=webmail.marksdiamonds.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
November 26, 2025
Valid Until
February 24, 2026 29 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
21:24:59:8F:60:1F:E0:34:4B:C6:B1:5D:4D:B1:53:9A:98:50:E6:16:62:36:E9:E4:38:94:AF:66:EB:39:57:77
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
Present
max-age=31536000
Content-Security-Policy
Weak
upgrade-insecure-requests
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Significantly strengthen CSP directives
  • 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