SSL/TLS Analysis for docs.aws.amazon.com
Analyzed on November 02, 2025 at 13:23 UTC
Security Score
88
/
100
Certificate Information
Subject
CN=docs.aws.amazon.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M03
Valid From
December 08, 2024
Valid Until
January 07, 2026
66 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
CD:8B:51:94:66:A8:AC:41:20:F9:3F:DC:4F:9E:2D:B7:CA:9E:96:34:86:3E:50:3A:92:F8:77:2C:EA:63:CF:C8
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=47304000; includeSubDomains
Content-Security-Policy
Basic
upgrade-insecure-requests; script-src; object-src
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • 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