Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
Akamai
Active incidents
AWS Certificate Manager
Microsoft Advertising
Canny
Fullstory
Google Analytics
Google reCAPTCHA
Google Static File Front End
Google Tag Manager
HubSpot
Active incidents
HubSpot Analytics
Active incidents
HubSpot CMS
Active incidents
HubSpot Forms
Active incidents
Intercom
jsDelivr
LinkedIn
Loom
Microsoft Clarity
Sentry
Stripe
Vimeo
Wistia
YouTube
Google Cloud
Certificate Information
Subject
CN=canny.io
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
June 27, 2025
Valid Until
July 26, 2026
87 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F3:64:28:F7:9B:77:ED:0C:D9:3A:B5:51:FB:0C:87:CB:71:E5:A0:C2:38:82:AE:C1:61:E0:28:35:C2:14:C5:D6
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
Good
sameorigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
- • 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