SSL Certificate Analysis for auth.flockx.io - Security Grade & TLS Configuration

Detected Technologies

See all in URL Inspect 16

Let's Encrypt

Tailwind CSS

Cloudflare Active incidents

Cloudflare CDNJS

Cloudinary

Google Analytics

Google DoubleClick

Google Fonts

Google Search

Google Static File Front End

Google Tag Manager

Hotjar

Mixpanel

Sentry

Vercel Active incidents

Google Cloud

Certificate Information

Subject

CN=auth.flockx.io

Issuer

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

Valid From

February 03, 2026

Valid Until

May 04, 2026 32 days

Public Key

ECDSA 256 bit (P-256) Adequate

Signature Algorithm

ECDSA-SHA384

SHA-256 Fingerprint

CA:93:EB:D0:6B:16:4E:CF:19:E8:EC:6D:3F:90:B4:82:48:83:8E:98:1B:BD:0F:20:0E:8B:05:F7:9A:97:70:EA

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

Excellent

max-age=31536000; includeSubDomains; preload

Content-Security-Policy

Basic

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

Good

strict-origin-when-cross-origin

Permissions-Policy

Present

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

Recommendations

• Improve CSP by adding more specific directives and removing 'unsafe-inline'

CAA Records (Certificate Authority Authorization)

CAA Records

Configured (Restricts certificate issuance)

Current Issuer

Authorized (Matches CAA policy)

Authorized CAs

letsencrypt.org

Recommendations

• Consider using critical flag (flags=128) for stricter CAA enforcement
• Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
• Consider adding 'issuewild' records to control wildcard certificate issuance

Subject Alternative Names

1 domain

auth.flockx.io