Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=*.aven.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M03
Valid From
August 02, 2025
Valid Until
August 29, 2026
244 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
B0:A8:A1:4B:90:9F:2E:F9:54:67:79:DB:91:03:F4:E2:2E:A4:BB:0C:ED:2C:FA:65:D8:8C:E2:A8:8C:CB:7C:9E
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
Present
max-age=31536000; preload
Content-Security-Policy
Basic
default-src; child-src; img-src; +4 more
default-src 'self' blob: data: https: wss: *.aven.com; child-src https: blob: *.aven.com; img-src 'unsafe-inline' blob: data: *.aven.com https:; script-src 'self' 'unsafe-inline' 'unsafe-eval' blob: https: *.aven.com; style-src 'self' 'unsafe-inline' https: *.aven.com; frame-ancestors 'self' https://*.aven.com; upgrade-insecure-requests;
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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