Open
Cached
·
just now
91/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Google Trust
Calendly
Datadog
Facebook
Font Awesome
Google AdSense
Google Analytics
Google Cloud Run
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
G Workspace
PostHog
Reddit
YouTube
Google Cloud
Google Cloud Storage
Certificate Information
Subject
CN=clickhelp.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 07, 2026
Valid Until
July 06, 2026
63 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
D9:97:EA:F7:FE:32:B0:AE:8B:8A:12:E1:A8:BC:75:8C:0A:70:DC:6B:BB:66:4E:DB:E6:6A:35:BA:F1:22:82:A4
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
Present
accelerometer=(), camera=(), geolocation=(); +6 more
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
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