86/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=Pennsylvania, O=Highmark Health, CN=auth.highmark.com
Issuer
C=CA, O=Entrust Limited, CN=Entrust OV TLS Issuing RSA CA 2
Valid From
December 02, 2025
Valid Until
December 02, 2026 338 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
8D:F0:E7:7E:E6:30:D2:95:6C:70:02:38:85:8A:1F:14:11:BC:01:51:A3:04:60:3D:E2:A8:9C:97:BA:15:22:87
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
Good
default-src; style-src-elem; style-src; +9 more
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • Consider adding 'preload' to HSTS for maximum security
  • Strengthen CSP by removing 'unsafe-eval'
  • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
  • 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