Open
Cached
·
just now
93/100
SECURITY SCORE
Certificate Information
Subject
CN=cactus.chat
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
December 06, 2025
Valid Until
March 06, 2026
69 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
25:FC:F8:03:68:01:4A:9E:1E:76:B4:53:A6:C2:A7:03:42:19:90:04:CE:22:E2:BE:1C:95:D0:B1:85:C7:F9:75
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; frame-ancestors; manifest-src; +6 more
default-src 'self'; frame-ancestors https://jamstackthemes.dev; manifest-src 'self'; connect-src *; font-src 'self'; img-src * data:; script-src 'self' https://*.cactus.chat 'unsafe-inline'; style-src 'self' https://*.cactus.chat 'unsafe-inline'; frame-src 'self' https://www.youtube.com/embed/
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
- • 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