Open
Cached
·
just now
78/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=docs.chambers.com
Issuer
C=US, O=Certainly, CN=Certainly Intermediate R1
Valid From
February 16, 2026
Valid Until
March 18, 2026
25 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
A8:84:82:EC:F3:A0:CB:C8:54:76:43:C6:70:BD:2C:07:E0:4B:6C:4B:48:F5:3C:8C:B3:62:F4:A2:76:4E:FB:C1
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Good
max-age=31536000; includeSubDomains
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Present
geolocation=(), microphone=(self "https://app.vidyard.com" "chrome-extension://jiihcciniecimeajcniapbngjjbonjan"), camera=(self "https://app.vidyard.com" "chrome-extension://jiihcciniecimeajcniapbngjjbonjan"); +2 more
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
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