What it means
Each certificate in a chain is signed by the one above it, and the signature uses a hash algorithm. SHA-1 and MD5 are broken: attackers can create forged certificates that match their signatures. The detail says which outdated algorithm the chain uses. Roots are left out of this check, because browsers trust them directly.
Why it matters
Browsers stopped accepting SHA-1 signatures in 2017, so a chain like this fails with a security warning. It usually means a very old certificate, an old intermediate left on the server, or a certificate from an internal tool with outdated defaults.
How to fix it
- Look at the chain section to see which certificate carries the old signature: your own certificate or an intermediate.
- If it's your certificate, request a new one. Every public certificate authority signs with SHA-256 or better today.
- If it's an intermediate, download the current chain file from your authority and replace the old one.
- Install the certificate and chain together and reload the web server.
Internal certificate tools
If you issue certificates yourself, set the signing digest to SHA-256, for example -sha256 with OpenSSL,
and issue the certificate again.
Check it worked
Run the SSL check again. The signature in the card should show SHA-256 or SHA-384, and the finding should be gone.