Server accepted a deprecated TLS protocol in ShipReady's handshake probe
ShipReady completed a TLS handshake using a deprecated protocol version.
Why it matters
This is bounded technical evidence and should be reviewed in the context of the deployment.
How ShipReady detects it
What it inspects
ShipReady makes passive TLS handshake probes for its supported deprecated protocol versions.
What triggers a finding
A supported deprecated protocol handshake completed.
What the evidence shows
The server accepted that protocol in the observed handshake.
Limits of this check
ShipReady does not send HTTP data, test every network path or client, demonstrate a downgrade attack, or establish compliance.
How to fix it
Disable the observed deprecated protocol
Update the TLS configuration at the origin, load balancer, CDN, or other terminating layer so it no longer accepts the deprecated protocol ShipReady observed. Keep modern protocols enabled and review the change with the team responsible for TLS termination.
How to verify the change
Repeat a protocol-specific handshake check
After deployment, use a TLS-capability test from an appropriate network path to confirm the observed deprecated protocol handshake is rejected while supported clients can still connect.
Expected: The previously accepted deprecated protocol no longer completes a handshake in the verification probe.