DNS Gurus

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

Cached · just now
88/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=Indiana, O=Elevance Health, Inc., CN=wellpoint.com
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA OV R40
Valid From
December 02, 2025
Valid Until
December 02, 2026 335 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
7A:B8:B3:B7:B0:A4:A5:C3:5D:73:B0:53:E6:E4:9A:19:D3:F4:DC:40:79:0E:59:DE:C6:1A:44:89:95:83:38:BA
Alternative Names
44 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
Present
max-age=63072000; includeSubdomains;
Content-Security-Policy
Weak
frame-ancestors
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Significantly strengthen CSP directives
  • • 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
Authorized (Matches CAA policy)
Authorized CAs
digicert.com symantec.com sectigo.com entrust.net
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • You have authorized 4 CAs - consider limiting to only the CAs you actively use
  • • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
  • • Consider adding 'issuewild' records to control wildcard certificate issuance