Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Dropbox
Google Trust
AWS CloudFront
Google Maps
Beamer
Google Tag Manager
Google Sign-In
Google reCAPTCHA
Braintree
Mux
Google Translate
Google Analytics
New Relic
Google Static File Front End
Calendly
Google API JS Client
Google Fonts
Vidyard
Wistia
Cloudflare Web Analytics
Qualtrics
Loom
unpkg
Google Search
Amazon S3
Heap
Cloudflare CDNJS
AWS
Vimeo
Akamai
Freshworks
YouTube
Freshdesk
Font Awesome
Sentry
jsDelivr
Google Cloud
Certificate Information
Subject
CN=freshdesk.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
June 24, 2026
Valid Until
September 22, 2026
32 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
F1:A8:FD:39:FB:0E:4C:87:4E:73:E1:6D:E7:67:AB:3F:8C:B7:C1:1A:AA:4A:89:2C:5B:4D:95:70:EB:D4:D3:DC
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
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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