NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM — certificate signed with SHA-1 or MD5
The browser rejects a certificate (or a chain certificate) signed with a weak hash like SHA-1.
certificate signed with SHA-1 rejectedSHA1 certificate not trusted browserweak signature algorithm certificate Meaning
Reissue the certificate with SHA-256 or better, and make sure no intermediate in the served chain is SHA-1-signed. Old internal CAs and legacy appliances are the usual culprits.
Common causes
- Leaf certificate signed with SHA-1
- Legacy intermediate in the chain
- Old internal CA still issuing SHA-1
- Appliance with an old built-in certificate
- Cached old chain on the server
⚡ Quick fix
- Reissue with SHA-256/ECDSA
- Check the chain:
openssl s_client -connect host:443 -showcerts - Replace the old appliance/internal CA certificate
Detailed fix by platform
Shell
openssl x509 -in cert.pem -noout -text | grep "Signature Algorithm"
How to diagnose
- Signature — SHA-1?
- Intermediate — Modern?
- CA — Updated?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- ca md too weak / ee key too small OpenSSL: error:0A00018E:SSL routines::ca md too weak / error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small
- cert mismatch SMTP TLS certificate verification failed: hostname mismatch / unable to get local issuer (mail client or library)
- clock Certificate error caused by a wrong device clock (NET::ERR_CERT_DATE_INVALID, "your clock is ahead/behind")
Most viewed in SSL / TLS
- HTTPSConnectionPool: Max retries exceeded (SSLError) Python requests: HTTPSConnectionPool(host='api.example.com', port=443): Max retries exceeded with url: /v1 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] ...')))
- DST Root CA X3 expired (old clients fail) Old clients: certificate has expired — Let's Encrypt chain uses expired DST Root CA X3 (OpenSSL 1.0.x, Android < 7.1.1)
- Keystore was tampered with, or password was incorrect Java keytool: java.io.IOException: Keystore was tampered with, or password was incorrect
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026