Open
Cached
·
just now
87/100
SECURITY SCORE
Certificate Information
Subject
CN=community.simpleanalytics.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
November 27, 2025
Valid Until
February 25, 2026
42 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
2B:4F:DD:F2:8F:83:2D:48:EA:C6:54:AC:09:FF:FE:D6:40:78:C4:69:D5:15:AC:8D:39:9F:1F:9D:D2:DD:89:94
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
Missing
Not configured
Content-Security-Policy
Basic
upgrade-insecure-requests; base-uri; object-src; +3 more
upgrade-insecure-requests; base-uri 'self'; object-src 'none'; script-src 'nonce-I1hY7iickGJRt75E1Xemk0j68' 'strict-dynamic'; frame-ancestors 'self'; manifest-src 'self'
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
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • 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