The certificate uses cryptography browsers no longer accept: an RSA key that is too short, or a SHA-1 signature. Browsers stopped trusting SHA-1 certificates in 2017 and require RSA keys of at least 2048 bits from public authorities. The fix is a new certificate.
Your connection is not private NET::ERR_CERT_WEAK_KEY
How 3 other clients word the same error
Firefox, SHA-1
Error code: SEC_ERROR_CERT_SIGNATURE_ALGORITHM_DISABLED — “The certificate was signed using a signature algorithm that is disabled because it is not secure.”
Firefox, small key
Error code: MOZILLA_PKIX_ERROR_INADEQUATE_KEY_SIZE
Chrome, older versions
NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM
| Error | NET::ERR_CERT_WEAK_KEY |
| Usually fixed by | The website |
| SHA-1 | Distrusted by Chrome 56 and Firefox 52 (2017) |
| RSA keys | 2048 bits or more from public authorities (Firefox, Apple) |
| Elliptic curves | P-256, P-384 or P-521 |
Check the certificate a site serves
Enter the site’s domain: we connect the way a browser does and show the certificate, its chain and the TLS versions it offers.
What it means
A short RSA key or a SHA-1 signature can be broken or forged with enough computing power, so browsers refuse them. Chrome now reports a SHA-1 certificate as a generally invalid certificate; the older ERR_CERT_WEAK_SIGNATURE_ALGORITHM code is effectively retired. Firefox rejects RSA keys under 2048 bits on publicly trusted certificates.
Why it happens
- An old certificate, or one generated with outdated defaults (1024-bit keys, SHA-1).
- A device or appliance that generates its own weak certificate.
How to fix it
- Generate a new key — RSA 2048 bits or more, or ECDSA P-256 — and get a new certificate signed with SHA-256; any current certificate authority issues one.
- Install it with its full chain and reload.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- net/cert/cert_status_flags_list.h — chromium.googlesource.com
- Google Online Security Blog: SHA-1 Certificates in Chrome — security.googleblog.com
- The end of SHA-1 on the Public Web — blog.mozilla.org
- TLS security — support.apple.com