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

Detected Technologies

See all in URL Inspect 11

Amazon S3

Google Analytics

Google DoubleClick

Google Pay

Google reCAPTCHA

Google Search

Google Static File Front End

LaunchDarkly

Sectigo

Google Cloud

Google Cloud Storage

Certificate Information

Subject

C=US, ST=Ohio, O=Bread Financial Holdings, Inc., CN=my.comenity.com

Issuer

C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA OV R36

Valid From

March 10, 2026

Valid Until

September 25, 2026 138 days

Public Key

RSA 2048 bit Adequate

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

A0:3E:13:86:86:6A:19:2F:FC:D4:69:7E:A9:BF:BC:3E:17:6A:42:56:86:10:C2:90:F6:1B:B2:2F:36:4B:24:1D

Alternative Names

2 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

Good

max-age=31536000; includeSubDomains

Content-Security-Policy

Good

default-src; script-src; style-src; +9 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

Present

document-domain=()

Recommendations

• Consider adding 'preload' to HSTS for maximum security
• Strengthen CSP by removing 'unsafe-eval'

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

Subject Alternative Names

2 domains

my.comenity.com www.my.comenity.com