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

Detected Technologies

See all in URL Inspect 8

Google Trust

Cloudflare Web Analytics

Google API JS Client

Google Fonts

Google Static File Front End

jsDelivr

Google Cloud

Google Cloud Storage

Certificate Information

Subject

CN=hlebe.com

Issuer

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

Valid From

August 18, 2026

Valid Until

November 16, 2026 70 days

Public Key

ECDSA 256 bit (P-256) Adequate

Signature Algorithm

ECDSA-SHA256

SHA-256 Fingerprint

70:44:1C:31:76:76:AE:65:81:3E:F9:70:38:D3:C0:B7:93:7C:76:F5:3C:93:25:64:98:D8:86:48:9D:64:DD:86

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

Present

max-age=31556926

Content-Security-Policy

Good

default-src; script-src; style-src; +7 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=(); +2 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

2 domains

hlebe.com *.hlebe.com