SSL Verification Bypassed
The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.
Reason:
Expired Certificate - the server's certificate has expired
Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=staging.login.highmark.com
Issuer
C=US, O=Google Trust Services, CN=WR3
Valid From
January 16, 2026
Valid Until
April 16, 2026
73 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
4A:6D:CC:69:F6:A8:00:8D:79:6E:8C:0C:AA:E9:A4:45:03:EB:19:6C:64:48:05:3F:BC:77:AE:58:DD:09:FD:B4
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
default-src 'self' https://*.cdn.highmark.com; style-src-elem 'self' 'unsafe-inline' https://fonts.googleapis.com https://*.salemove.com; style-src 'self' 'unsafe-inline' https://cdn.highmark.com https://*.salemove.com; font-src 'self' https://fonts.gstatic.com https://*.cdn.highmark.com; img-src 'self' https://*.highmark.com https://cdn.highmark.com; manifest-src 'self'; script-src 'self' 'unsafe-inline'; script-src-elem 'unsafe-inline' 'self' https://*.cdn.highmark.com https://code.jquery.com https://api.glia.com https://*.salemove.com; connect-src 'self' https://*.highmark.com https://api.highmark.com https://*.hmhs.com https://*.googleapis.com https://api.glia.com https://*.salemove.com wss://*.salemove.com ; frame-ancestors 'none'; worker-src 'self'; report-uri https://csp-report-owsvbbx4fq-uc.a.run.app/api/v1/
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