Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
Google Trust
AWS CloudFront
Chili Piper
Canny
Google Tag Manager
Bugsnag
G2
Fullstory
Mutiny
HubSpot Forms
Google DoubleClick
Google Analytics
ClearBit
Mixpanel
Sprig
Segment
Google Static File Front End
Google API JS Client
Google Fonts
LinkedIn
Zendesk
Microsoft ASP.NET CDN
Zoom
Stripe
Slack
BootstrapCDN
Adobe Marketo
Microsoft SharePoint
Facebook
Amazon S3
DigitalOcean Spaces
Cloudflare CDNJS
Salesforce Pardot
PostHog
HubSpot
Intercom
YouTube
Sentry
jsDelivr
Google Cloud
Google Cloud Storage
Certificate Information
Subject
CN=chilipiper.com
Issuer
C=US, O=Google Trust Services, CN=WR3
Valid From
January 20, 2026
Valid Until
April 20, 2026
57 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
D5:BC:61:40:A0:88:A4:85:3A:04:F1:FF:E8:A0:8B:34:37:C6:0D:48:35:1E:E8:F8:6B:00:24:34:19:42:4C:B3
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
Excellent
deny
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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