Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
AWS
Active incidents
Amazon S3
DigiCert
Drift
Active incidents
Fullstory
Google Analytics
Google API JS Client
Google Fonts
Google reCAPTCHA
Google Search
Google Sign-In
Intercom
Mixpanel
Active incidents
Pendo
Active incidents
Qualtrics
Vimeo
Visual Website Optimizer
Wistia
YouTube
Google Cloud Storage
Certificate Information
Subject
C=US, ST=California, L=Walnut, O=ChargeBee Inc., CN=*.chargebee.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
February 11, 2026
Valid Until
March 14, 2027
305 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
AB:72:01:FB:83:8A:47:99:2B:FF:C3:7B:A1:26:ED:21:1D:B7:B9:FF:B3:58:E9:47:82:2E:51:3F:AB:04:2F:F9
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=31536000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Content-Security-Policy header to prevent XSS attacks
- • 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