SSL Certificate Analysis for purple.ai - Security Grade & TLS Configuration

Detected Technologies

See all in URL Inspect 19

AWS CloudFront

Google Trust

Cookiebot

Elfsight

Google Analytics

Google Conversion Tracking

Google DoubleClick

Google Fonts

Google reCAPTCHA

Google Search

Google Static File Front End

Google Tag Manager

HubSpot

HubSpot Forms

Supabase

Vimeo

YouTube

Google Cloud

Certificate Information

Subject

CN=purple.ai

Issuer

C=US, O=Google Trust Services, CN=WR3

Valid From

April 09, 2026

Valid Until

July 08, 2026 63 days

Public Key

RSA 2048 bit Adequate

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

45:61:E4:2D:26:E1:C6:69:F0:63:86:52:B3:5A:39:CA:D5:46:C6:09:EC:21:C2:A8:B5:DD:EE:04:CC:C7:50:26

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; script-src; style-src; +5 more Analyze

Content-Security-Policy-Report-Only

Missing

Not configured Analyze

X-Frame-Options

Excellent

DENY

X-Content-Type-Options

Good

nosniff

Referrer-Policy

Good

strict-origin-when-cross-origin

Permissions-Policy

Present

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

Recommendations

• Strengthen CSP by removing 'unsafe-eval'

CAA Records (Certificate Authority Authorization)

CAA Records

Configured (Restricts certificate issuance)

Current Issuer

Authorized (Matches CAA policy)

Authorized CAs

amazon.com amazonaws.com letsencrypt.org pki.goog

Incident Reporting

mailto:[email protected]

Recommendations

• Consider using critical flag (flags=128) for stricter CAA enforcement
• You have authorized 4 CAs - consider limiting to only the CAs you actively use
• Consider adding 'issuewild' records to control wildcard certificate issuance

Subject Alternative Names

2 domains

purple.ai www.purple.ai