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

Detected Technologies

See all in URL Inspect 12

Let's Encrypt Active incidents

Amazon S3

Cloudflare Turnstile

Datadog

DocuSign

Google Cloud Storage

Google Fonts

Google Maps

Google Search

Google Static File Front End

Plaid

Google Cloud

Certificate Information

Subject

CN=apply.htb.com

Issuer

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

Valid From

April 20, 2026

Valid Until

July 19, 2026 67 days

Public Key

RSA 2048 bit Adequate

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

6A:20:70:31:46:B2:84:1A:87:EB:DC:48:E9:8B:D6:E7:08:80:25:ED:A7:69:69:D8:57:50:85:01:60:0C:FF:B1

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

Good

report-uri; default-src; img-src; +5 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

no-referrer-when-downgrade

Permissions-Policy

Present

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

Recommendations

• Consider adding 'preload' to HSTS for maximum security
• 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

apply.htb.com