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

Detected Technologies

See all in URL Inspect 16

Gravatar

YouTube

Microsoft Advertising

Facebook

Google AdSense

Google Analytics

Google Conversion Tracking

Google DoubleClick

Google Search

Google Tag Manager

Sectigo

Spotify

TikTok Analytics

Twitter

Zoho Mail

Certificate Information

Subject

CN=*.cdmon.com

Issuer

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

Valid From

April 24, 2026

Valid Until

November 08, 2026 193 days

Public Key

RSA 4096 bit Strong

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

D2:84:67:D6:5D:60:0E:F4:34:5E:C0:74:FF:03:00:F4:54:48:E8:F9:4B:4E:72:02:69:C3:34:12:C3:45:58:57

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

Excellent

max-age=63072000; includeSubDomains; preload

Content-Security-Policy

Good

default-src; font-src; script-src; +9 more Analyze

Content-Security-Policy-Report-Only

Missing

Not configured Analyze

X-Frame-Options

Excellent

DENY

X-Content-Type-Options

Good

nosniff

Referrer-Policy

Present

origin-when-cross-origin

Permissions-Policy

Present

camera=(), microphone=(), geolocation=()

Recommendations

• 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

cdmon.com *.cdmon.com