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 *.caldav.fastmail.com, *.carddav.fastmail.com, *.fastmail.com, fastmail.com, not for mail.findallmydata.com

95/100 SECURITY SCORE

Certificate Information

Subject
CN=*.fastmail.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
December 02, 2025
Valid Until
March 02, 2026 66 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
1B:54:51:FF:C9:B8:CA:15:F6:7D:EE:51:30:77:40:6F:10:0A:3E:3A:3B:2C:AB:78:6A:B0:85:5C:20:13:2F:C8
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
Good
default-src; connect-src; img-src; +11 more
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
never,no-referrer,same-origin
Permissions-Policy
Present
accelerometer=(), ambient-light-sensor=(), camera=(), document-domain=(), encrypted-media=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), navigation-override=(), sync-xhr=(), usb=(), xr-spatial-tracking=()
Recommendations
  • Strengthen CSP by removing 'unsafe-eval'

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