Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
CN=*.trustshare.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
November 07, 2025
Valid Until
February 05, 2026
31 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
E3:DB:07:3F:10:69:02:3C:61:AE:13:FF:10:10:8F:01:8C:4D:C7:19:FF:74:0F:5F:8F:A2:E4:8A:98:FF:F9:A9
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=16070400; includeSubDomains
Content-Security-Policy
Weak
frame-ancestors
X-Frame-Options
Good
sameorigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Significantly strengthen CSP directives
- • 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