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

Detected Technologies

See all in URL Inspect 1

Sectigo

Certificate Information

Subject

CN=production.saffire.com

Issuer

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

Valid From

July 20, 2025

Valid Until

July 20, 2026 83 days

Public Key

RSA 2048 bit Adequate

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

95:47:31:FD:39:AE:B1:5B:9F:CF:D4:16:A5:15:93:6E:04:B2:B1:6E:5A:B9:0D:57:EE:2D:D7:40:66:7F:0A:E6

Alternative Names

79 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

Present

max-age=31536000;

Content-Security-Policy

Basic

default-src Analyze

Content-Security-Policy-Report-Only

Missing

Not configured Analyze

X-Frame-Options

Good

SAMEORIGIN

X-Content-Type-Options

Good

nosniff

Referrer-Policy

Missing

Not configured

Permissions-Policy

Missing

Not configured

Recommendations

• Increase HSTS max-age to at least 1 year and add includeSubDomains
• Improve CSP by adding more specific directives and removing 'unsafe-inline'
• 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