Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
AWS Certificate Manager
Chromatic
Facebook
Figma
Google AdSense
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Search
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot Forms
Intercom
IP-API
jsDelivr
LinkedIn
Mailchimp
Microsoft Clarity
Netlify
PostHog
RevenueHero
Segment
Sentry
Stripe
Usercentrics
Vector
YouTube
Certificate Information
Subject
CN=chromatic.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
September 16, 2025
Valid Until
October 15, 2026
169 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
1D:AC:0B:FC:33:C1:80:FA:BD:7D:63:5F:0E:CE:3C:7B:B3:19:37:7F:CB:EB:83:5E:C3:D4:9E:A3:75:08:E7:28
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
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
no-referrer,strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Add Content-Security-Policy header to prevent XSS attacks
- • 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