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:
Unknown Certificate Authority - the server's certificate is not trusted
Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
C=US, ST=Indiana, L=Indianapolis, O=Elevance Health, Inc., CN=mpartdcoverage.com
Issuer
C=US, O=SSL Corporation, CN=Entrust OV TLS Issuing RSA CA 1
Valid From
March 11, 2025
Valid Until
April 01, 2026
80 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
43:FE:1F:92:0A:B6:38:01:99:3D:ED:D4:BD:F2:22:CF:C4:62:9E:8D:FF:47:3D:68:84:D7:68:1F:07:2E:EF:E8
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
Excellent
max-age=31536000; includeSubDomains; preload
Content-Security-Policy
Basic
script-src
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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
Configured
(Restricts certificate issuance)
Current Issuer
Not Authorized
(Potential misconfiguration)
Authorized CAs
CAA Issues
- • CRITICAL: Current certificate issuer 'C=US, O=SSL Corporation, CN=Entrust OV TLS Issuing RSA CA 1' is NOT authorized by CAA records. Authorized CAs: digicert.com, sectigo.com, entrust.net
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
- • Consider adding 'issuewild' records to control wildcard certificate issuance