Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=mend.io
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
June 30, 2025
Valid Until
July 29, 2026
209 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
8F:A3:8D:C4:E6:A8:9B:5D:BB:92:5B:55:9D:39:B4:D5:15:62:6E:A5:D6:63:4B:8C:A0:F1:D3:D3:52:02:70:A6
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
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
autoplay=*, camera=(self), cross-origin-isolated=*, display-capture=(self), encrypted-media=*, geolocation=*, keyboard-map=*, microphone=(self), payment=(self), sync-xhr=*, fullscreen=*
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
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