Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
Google Tag Manager
Integrate
UserSnap
Google DoubleClick
Microsoft Advertising
Adobe Audience Manager
6sense
Baidu Analytics
Basis Technologies
Google Fonts
Clickagy
Twitter
Qualtrics
Hotjar
LinkedIn
ZoomInfo
Contentsquare
Drift
TrustRadius
Adobe Marketo
Adobe Dynamic Tag Management
Facebook
Cloudflare CDNJS
Oracle Eloqua
Dun & Bradstreet DirectPlus
Active incidents
MNTN
TrustArc
Intercom
YouTube
Font Awesome
Sentry
Certificate Information
Subject
CN=stackrox.com
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
April 03, 2026
Valid Until
July 02, 2026
56 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
85:5D:7D:73:B5:6A:1F:8C:EA:0B:3A:BB:F9:93:52:CC:C8:7F:3A:10:B2:AB:E9:68:50:87:B9:09:B4:E9:69:D3
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=31536000, max-age=31536000
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
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 Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • 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