DNS Gurus
Cached · just now
87/100 SECURITY SCORE

Certificate Information

Subject
CN=www.amazon.com.co
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
November 07, 2025
Valid Until
August 24, 2026 217 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
08:8C:28:F0:7F:8E:B5:5F:6F:5A:10:4F:EC:2E:56:C9:F2:50:5A:04:9C:53:8A:D0:B4:4F:98:8D:F6:B0:80:3B
Alternative Names
3 domains

Security Configuration

TLS Protocols
TLS 1.0 TLS 1.1 TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)
Warnings
  • • TLS 1.1 is deprecated and should be disabled
  • • TLS 1.0 is deprecated and should be disabled

HTTP Security Headers

Status
Strict-Transport-Security
Excellent
max-age=47474747; includeSubDomains; preload
Content-Security-Policy
Weak
upgrade-insecure-requests; report-uri
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Significantly strengthen CSP directives
  • • 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