SSL Certificate Analysis for paysafe.com - Security Grade & TLS Configuration

Detected Technologies

See all in URL Inspect 1

AWS Certificate Manager

Certificate Information

Subject

CN=*.prod.marketing.paysafe.cloud

Issuer

C=US, O=Amazon, CN=Amazon RSA 2048 M04

Valid From

August 26, 2025

Valid Until

September 24, 2026 142 days

Public Key

RSA 2048 bit Adequate

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

D4:8A:87:57:10:17:34:71:EC:0F:36:CC:FD:54:74:F2:C1:47:40:3F:FB:83:DD:9E:87:91:20:50:23:9D:8B:89

Alternative Names

77 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=31536000; includeSubDomains; preload

Content-Security-Policy

Missing

Not configured Analyze

Content-Security-Policy-Report-Only

Missing

Not configured Analyze

X-Frame-Options

Good

SAMEORIGIN

X-Content-Type-Options

Missing

Not configured

Referrer-Policy

Missing

Not configured

Permissions-Policy

Missing

Not configured

Recommendations

• Add Content-Security-Policy header to prevent XSS attacks
• 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

Authorized (Matches CAA policy)

Authorized CAs

letsencrypt.org sectigo.com amazon.com digicert.com

Recommendations

• Consider using critical flag (flags=128) for stricter CAA enforcement
• You have authorized 4 CAs - consider limiting to only the CAs you actively use
• Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
• Consider adding 'issuewild' records to control wildcard certificate issuance