Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
Google AdSense
Google Tag Manager
Bugsnag
Bing
G2
AppNexus (Xandr)
Google DoubleClick
Google Analytics
Microsoft Advertising
Google Conversion Tracking
Pusher
6sense
Google Static File Front End
Google Fonts
Vidyard
Grafana
Active incidents
Algolia
LinkedIn
BrightTALK
ZoomInfo
Google Search
Adobe Marketo
Qualified
Facebook
Impartner
OneTrust
Adobe Fonts (Typekit)
Contentstack
AWS Certificate Manager
Visual Website Optimizer
YouTube
Microsoft Clarity
Google Cloud
Certificate Information
Subject
CN=www.rapid7.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
September 30, 2025
Valid Until
October 29, 2026
182 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
5A:19:C4:22:13:B6:84:10:E8:19:C0:9C:73:59:B3:BD:1F:7A:81:2A:C1:8E:21:0B:4E:2A:83:EE:C6:8B:F7:7B
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=63072000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-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