Open Cached · just now
75/100 SECURITY SCORE

Certificate Information

Subject
CN=chargify.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M02
Valid From
July 10, 2025
Valid Until
August 08, 2026 253 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
D0:AB:50:C2:3F:F2:F0:D5:00:A1:7F:E9:24:FA:89:C7:0E:01:10:FC:98:52:E2:39:CB:AE:71:9A:F3:5D:D2:F4
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
Missing
Not configured
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • Add Strict-Transport-Security header with max-age of at least 1 year
  • Add Content-Security-Policy header to prevent XSS attacks
  • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • Add X-Content-Type-Options: nosniff
  • 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
Configured (Restricts certificate issuance)
Current Issuer
Not Authorized (Potential misconfiguration)
Incident Reporting
CAA Issues
  • CRITICAL: Current certificate issuer 'C=US, O=Amazon, CN=Amazon RSA 2048 M02' is NOT authorized by CAA records. Authorized CAs: letsencrypt.org, pki.goog, awstrust.com, comodoca.com, digicert.com
Recommendations
  • Consider using critical flag (flags=128) for stricter CAA enforcement
  • You have authorized 5 CAs - consider limiting to only the CAs you actively use
  • Consider adding 'issuewild' records to control wildcard certificate issuance

Subject Alternative Names

1 domain