SSL Certificate Analysis for pmc-redirect.certiport.com - Security Grade & TLS Configuration

SSL Verification Bypassed

The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.

Reason:

Unknown Certificate Authority - the server's certificate is not trusted

Open Cached · just now

81/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 29

Akamai Active incidents

Akamai mPulse

Algolia

AppNexus (Xandr)

Microsoft Advertising

Demandbase

Facebook

Google AdSense

Google Analytics

Google DoubleClick

Google Fonts

Hotjar

jsDelivr

LaunchDarkly

New Relic

OneTrust

Quora

Salesforce Pardot

Salesforce Sites

Sectigo

Snapchat

Spotify

TikTok Analytics

The Trade Desk

Twitter

Visual Website Optimizer

YouTube

Certificate Information

Subject

C=GB, ST=London, O=Pearson PLC, CN=sancert1-pmc-tempdomains.pearson.com

Issuer

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

Valid From

March 25, 2026

Valid Until

September 21, 2026 168 days

Public Key

RSA 2048 bit Adequate

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

7F:AA:87:46:F3:97:AC:16:A2:2C:57:84:BC:FB:49:D4:0E:4C:90:C5:4F:4E:3C:97:7C:45:82:66:88:70:88:9F

Alternative Names

102 domains

Security Configuration

TLS Protocols

TLS 1.2

Forward Secrecy

Limited (Check cipher configuration)

Warnings

• TLS 1.3 is not supported (recommended)

HTTP Security Headers

Status

Strict-Transport-Security

Present

max-age=31536000 ; preload

Content-Security-Policy

Missing

Not configured Analyze

Content-Security-Policy-Report-Only

Basic

default-src; frame-ancestors 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
• Add Content-Security-Policy header to prevent XSS attacks
• 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