SSL Certificate Analysis for psc.to - 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 140 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

Basic

default-src; script-src; style-src; +11 more Analyze

Content-Security-Policy-Report-Only

Missing

Not configured Analyze

X-Frame-Options

Good

SAMEORIGIN

X-Content-Type-Options

Good

nosniff

Referrer-Policy

Good

strict-origin-when-cross-origin

Permissions-Policy

Missing

Not configured

Recommendations

• Improve CSP by adding more specific directives and removing 'unsafe-inline'
• 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