Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Active incidents
PayPal
Adyen
Cloudinary
DocuSign
Google Analytics
Google API JS Client
Google DoubleClick
Google Fonts
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
HubSpot
Mixpanel
Okta
OneTrust
Salesforce Cloud
Salesforce Sites
6sense
Slack
Twitter
Vimeo
YouTube
Zscaler
Google Cloud
Certificate Information
Subject
CN=help.circle.com
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
March 30, 2026
Valid Until
June 28, 2026
47 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
87:BD:BC:BB:74:8F:73:6C:D1:48:B7:21:33:3F:D0:5B:EF:A1:21:9A:55:5E:87:DC:D6:D0:3C:87:6B:DE:21: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
Good
max-age=63072000; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Significantly strengthen CSP directives
- • 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