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

Detected Technologies

See all in URL Inspect 13

Let's Encrypt

Umami Analytics

Amazon S3

Customer.io

Google Analytics

Google DoubleClick

Google Tag Manager

Hotjar

OneTrust

Typeform

YouTube

Zendesk

Certificate Information

Subject

CN=supernova.io

Issuer

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

Valid From

April 21, 2026

Valid Until

July 20, 2026 80 days

Public Key

RSA 2048 bit Adequate

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

01:19:0E:80:ED:AF:31:E6:1E:F8:04:BD:FB:F3:5A:1D:50:FB:5E:9D:DB:3F:83:36:68:AF:5A:A6:76:45:10:9B

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

Basic

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

Recommendations

• Consider adding 'preload' to HSTS for maximum security
• Improve CSP by adding more specific directives and removing 'unsafe-inline'

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

supernova.io