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

Detected Technologies

See all in URL Inspect 8

Let's Encrypt Active incidents

Cloudflare CDNJS

Cloudflare Web Analytics

Google Analytics

Google DoubleClick

Google Fonts

Google Tag Manager

Stripe

Certificate Information

Subject

CN=synapix.com

Issuer

C=US, O=Let's Encrypt, CN=E8

Valid From

April 27, 2026

Valid Until

July 26, 2026 31 days

Public Key

ECDSA 256 bit (P-256) Adequate

Signature Algorithm

ECDSA-SHA384

SHA-256 Fingerprint

F4:BF:03:11:BE:50:80:72:3D:A6:AF:0F:F0:63:53:5A:CF:71:85:D2:13:BD:03:29:40:A6:0F:49:41:CA:76:2E

Alternative Names

1 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

Good

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

geolocation=(), microphone=(), camera=(); +1 more

Recommendations

• Increase HSTS max-age to at least 1 year and add includeSubDomains
• 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

1 domain

synapix.com