Open
Cached
·
just now
83/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
Adobe Marketo
AWS
Microsoft Advertising
CaliberMind
Contentsquare
Facebook
Google Analytics
Google DoubleClick
Google Search
Google Tag Manager
LinkedIn
Microsoft Clarity
OpenAI
Optimizely
Active incidents
Qualified
Quora
Reddit
6sense
Active incidents
The Trade Desk
Vercel
ZoomInfo
Certificate Information
Subject
CN=www.optimizely.com
Issuer
C=US, O=Let's Encrypt, CN=YR2
Valid From
August 23, 2026
Valid Until
November 21, 2026
89 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
A2:AB:5F:16:D4:1A:BF:3E:A4:FA:02:32:1A:A1:97:8D:72:C0:1E:62:9D:CA:4A:66:6F:74:82:20:73:6A:65:36
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=63072000
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Add X-Content-Type-Options: nosniff
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • You have authorized 4 CAs - consider limiting to only the CAs you actively use
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
- • Consider adding 'issuewild' records to control wildcard certificate issuance