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

Detected Technologies

See all in URL Inspect 13

AWS CloudFront

Let's Encrypt Active incidents

AWS

ClearBit

Cloudflare CDNJS

Datadog

GIPHY

Google Fonts

HubSpot Forms

Logo.dev

Mixpanel

Sentry

Typeform

Certificate Information

Subject

CN=trust.link11.com

Issuer

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

Valid From

March 23, 2026

Valid Until

June 21, 2026 42 days

Public Key

RSA 4096 bit Strong

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

A1:E8:B6:C2:1A:9D:60:3A:1C:91:9F:D9:06:FD:4A:EF:91:94:90:E4:07:5A:BF:F6:0D:8F:AB:84:5B:A8:58:B9

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

Good

max-age=31536000; includeSubDomains

Content-Security-Policy

Weak

frame-ancestors Analyze

Content-Security-Policy-Report-Only

Good

default-src; connect-src; img-src; +5 more Analyze

X-Frame-Options

Good

sameorigin

X-Content-Type-Options

Good

nosniff

Referrer-Policy

Present

same-origin

Permissions-Policy

Present

accelerometer=(), camera=(), geolocation=(); +5 more

Recommendations

• Consider adding 'preload' to HSTS for maximum security
• Significantly strengthen CSP directives

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

trust.link11.com