SSL Certificate Analysis for www.unidata.ucar.edu - Security Grade & TLS Configuration

Detected Technologies

See all in URL Inspect 11

Let's Encrypt

Google Analytics

Google Fonts

Google Search

Google Static File Front End

Google Tag Manager

Google Translate

G Workspace

YouTube

Google Cloud

Google Cloud Storage

Certificate Information

Subject

CN=unidata.ucar.edu

Issuer

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

Valid From

March 30, 2026

Valid Until

June 28, 2026 62 days

Public Key

RSA 2048 bit Adequate

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

FC:F6:AC:01:D9:E5:91:79:AD:E2:7F:D9:8B:78:DB:78:A2:74:00:44:6F:CD:D3:85:3C:1E:BE:AC:5F:07:40:D3

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

Excellent

max-age=31622400; includeSubDomains; preload

Content-Security-Policy

Basic

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

Missing

Not configured

Recommendations

• Improve CSP by adding more specific directives and removing 'unsafe-inline'
• Consider adding Permissions-Policy to control browser features

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

unidata.ucar.edu www.unidata.ucar.edu