Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=secure16.hostmailserver.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
January 05, 2026
Valid Until
April 05, 2026
81 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
DF:D1:2E:69:F0:8B:05:B1:7A:CB:AE:DA:71:B3:31:A0:E9:E4:C9:99:63:F4:9B:9B:A3:1D:7F:D9:68:82:1C:40
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=15552000
Content-Security-Policy
Basic
default-src; script-src; object-src; +2 more
default-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.gstatic.com ;script-src 'self' 'unsafe-inline' 'unsafe-eval' http://www.google.com https://www.gstatic.com https://cdn.jsdelivr.net https://quickchart.io; object-src 'none';base-uri 'self';img-src 'self' 'unsafe-inline' https://www.gstatic.com https://quickchart.io data:
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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