SSL Certificate Analysis for 3306-db.org - Security Grade & TLS Configuration

Detected Technologies

See all in URL Inspect 10

Google Trust

Gravatar

Firebase

Google API JS Client

Google Cloud Functions

Google Fonts

Google Static File Front End

Google Tag Manager

jsDelivr

Google Cloud

Certificate Information

Subject

CN=3306-db.org

Issuer

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

Valid From

August 07, 2026

Valid Until

November 05, 2026 72 days

Public Key

RSA 2048 bit Adequate

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

E7:D5:50:1C:F7:8A:FC:DE:FD:0D:FA:85:86:DF:29:38:43:BA:F5:24:CF:F1:73:78:8B:7D:7F:FF:42:2E:D3:4C

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

Present

max-age=31556926

Content-Security-Policy

Good

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

geolocation=(), camera=(), microphone=(); +5 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

1 domain

3306-db.org