NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM SSL / TLS Origin: Network OSI layer 6 · Presentation Last updated 18 Nov 2026

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.

Exact message you may see certificate signed with SHA-1 rejectedSHA1 certificate not trusted browserweak signature algorithm certificate
Seen on: Chrome SSL Browser

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

  1. Reissue with SHA-256/ECDSA
  2. Check the chain: openssl s_client -connect host:443 -showcerts
  3. Replace the old appliance/internal CA certificate

Detailed fix by platform

Shell

  1. openssl x509 -in cert.pem -noout -text | grep "Signature Algorithm"

How to diagnose

  1. Signature — SHA-1?
  2. Intermediate — Modern?
  3. 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:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

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 (SSL / TLS)ca md too weak / ee k…cert mismatch — SMTP TLS certificate verification failed: hostname mismatch / unable to get local issuer (mail client or library) (Email / SMTP)cert mismatchclock — Certificate error caused by a wrong device clock (NET::ERR_CERT_DATE_INVALID, "your clock is ahead/behind") (SSL / TLS)clockCORS — CORS: Private Network Access preflight blocked (public site calling localhost/intranet) (HTTP)CORSCT — NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED — certificate not logged in Certificate Transparency (SSL / TLS)CTDjango — Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port) (Email / SMTP)DjangoERR_SSL_KEY_USAGE_INCOMPATIBLE — Chrome: ERR_SSL_KEY_USAGE_INCOMPATIBLE — the certificate's key usage doesn't allow the negotiated cipher (SSL / TLS)ERR_SSL_KEY_USAGE_INC…expiry — Certificate expired unexpectedly — manual renewal missed or automation failing silently (SSL / TLS)expiryNET::ERR_…

Explore the map of this error Full error map →

🧠 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.