Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Akamai
Active incidents
Microsoft Advertising
Canny
Fullstory
Google Analytics
Google reCAPTCHA
Google Static File Front End
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot CMS
HubSpot Forms
Intercom
jsDelivr
LinkedIn
Loom
Microsoft Clarity
Sentry
Stripe
Vimeo
Wistia
YouTube
Google Cloud
Certificate Information
Subject
CN=feedback.hyra.io
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
April 28, 2026
Valid Until
July 27, 2026
88 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
5F:90:81:4A:65:44:2F:34:41:D9:99:D7:75:53:3D:C2:8F:19:B6:69:BC:3D:3E:62:BF:5A:27:AF:77:B2:7A:A1
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