Open
Cached
·
just now
95/100
SECURITY SCORE
Certificate Information
Subject
CN=brand.uhc.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
January 02, 2026
Valid Until
April 02, 2026
60 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
B9:3F:17:25:18:55:AA:2A:48:F3:9D:95:2A:81:EA:43:5D:8E:7A:EF:00:B6:F0:1F:D7:46:0D:A0:28:AA:A9:B9
Alternative Names
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
Strong
default-src; font-src; img-src; +4 more
default-src 'self' https:; font-src 'self' data: use.typekit.net typekit.net ; img-src 'self' https: blob: data:; object-src 'self'; script-src 'self' https: 'nonce-sSmcDmsYV6AjURrvI5cTeg==' *.web.monigle.net *.googleapis.com *.googletagmanager.com *.google-analytics.com *.adobedtm.com; style-src 'self' https: 'nonce-sSmcDmsYV6AjURrvI5cTeg==' use.typekit.net typekit.net p.typekit.net; frame-ancestors 'self';
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
geolocation=()
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
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