Open
Cached
·
just now
85/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=auth.hypernode.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
March 28, 2026
Valid Until
June 26, 2026
50 days
Public Key
ECDSA
384 bit
(P-384)
Strong
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
F8:A1:69:35:F3:25:B7:8B:4D:2C:3F:B0:B8:46:A0:AA:27:99:30:22:F0:DA:05:5B:61:2E:DD:72:E5:2B:42:E0
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=2592000; includeSubDomains; preload, max-age=15778463
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Add Content-Security-Policy header to prevent XSS attacks
- • 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