Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=l7bear.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
October 09, 2025
Valid Until
January 07, 2026
55 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
04:9E:19:ED:BE:E3:28:DE:AB:65:AD:C7:A3:E1:47:1F:84:29:47:5C:1F:E4:82:0A:E0:A9:41:8C:AE:79:AD:0C
Alternative Names
Security Configuration
TLS Protocols
TLS 1.0
TLS 1.1
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
Warnings
- • TLS 1.1 is deprecated and should be disabled
- • TLS 1.0 is deprecated and should be disabled
HTTP Security Headers
Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Weak
frame-ancestors
X-Frame-Options
Present
ALLOW-FROM https://app.kajabi.com https://app.vibely.io https://communities.kajabi.com https://communities-widget.kajabi.com *.mykajabi.com https://communities.newkajabi-staging.com https://communities-widget.newkajabi-staging.com https://www.forkedstories.com https://www.l7bear.com
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
- • 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