DNS Gurus
Cached · just now
89/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1
AWS Certificate Manager logo AWS Certificate Manager

Certificate Information

Subject
CN=account-status.amazon.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
November 13, 2025
Valid Until
December 12, 2026 107 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
39:4E:66:E9:D0:99:00:22:6C:F1:87:49:29:08:7E:98:B0:BD:20:77:98:61:91:A1:D7:A3:83:84:80:66:B3:04
Alternative Names
4 domains

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=47474747; includeSubDomains; preload
Content-Security-Policy
Weak
upgrade-insecure-requests; report-uri Analyze
Content-Security-Policy-Report-Only
Basic
default-src; report-uri Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Present
ch-dpr=(self "https://m.media-amazon.com" "https://images-na.ssl-images-amazon.com"), ch-viewport-width=(self "https://m.media-amazon.com" "https://images-na.ssl-images-amazon.com"), ch-downlink=(self "https://m.media-amazon.com" "https://images-na.ssl-images-amazon.com"); +1 more
Recommendations
  • • Significantly strengthen CSP directives
  • • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)

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