Open
Cached
·
just now
91/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
YouTube
AWS
AWS Certificate Manager
Amazon S3
ClearBit
Cloudflare CDNJS
Figma
G2
Google API JS Client
Google Cloud Storage
Google Static File Front End
Highspot
jsDelivr
LaunchDarkly
LinkedIn
Microsoft 365
Mixpanel
Okta
Pendo
PubNub
Salesforce Sites
Segment
Sentry
Vidyard
Vimeo
Zendesk
Zscaler
Google Cloud
Certificate Information
Subject
CN=app.clari.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
September 11, 2025
Valid Until
October 09, 2026
158 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
EC:B7:46:65:1D:91:CB:26:3A:C9:40:18:A5:61:E5:24:69:27:DC:2A:47:7B:F3:C2:58:EB:2C:75:BD:98:FA:68
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; includeSubdomains
X-Frame-Options
Excellent
DENY
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
- • Strengthen CSP by removing 'unsafe-eval'
- • 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