ERR_CERT_WEAK_SIGNATURE_ALGORITHM means the SSL certificate is signed with an obsolete algorithm (SHA-1, MD5, MD2). Chrome blocks such certificates since 2017. Fix: reissue with SHA-256 or stronger. All modern CAs (Let's Encrypt, DigiCert) default to SHA-256.
This error is a frequent issue in SSL debugging. We cover the causes and step-by-step fix.
Free online tool — SSL certificate checker: instant results, no signup.
ERR_CERT_WEAK_SIGNATURE_ALGORITHM means the SSL certificate is signed with an obsolete algorithm (SHA-1, MD5, MD2). Chrome blocks such certificates since 2017. Fix: reissue with SHA-256 or stronger. All modern CAs (Let's Encrypt, DigiCert) default to SHA-256.
The error can appear in Chrome, Edge, Opera, Brave (all Chromium-based), and partially in Firefox and Safari. Different browsers display the same code differently, but the underlying issue is the same.
The ERR_CERT_WEAK_SIGNATURE_ALGORITHM error indicates that the SSL certificate uses a cryptographic signature algorithm deemed insecure, such as SHA-1. To resolve this issue, update your SSL certificate to use a stronger signature algorithm like SHA-256 or SHA-384. Ensure your server configuration supports these algorithms and consider obtaining a new certificate from a trusted Certificate Authority (CA) that complies with current security standards.
The ERR_CERT_WEAK_SIGNATURE_ALGORITHM error occurs when a web browser, such as Chrome or Firefox, encounters an SSL certificate that employs a weak signature algorithm. This typically involves algorithms like SHA-1, which have been deprecated due to vulnerabilities that make them susceptible to attacks. As of 2026, modern web standards require the use of stronger algorithms like SHA-256 or SHA-384 to ensure secure communications.
This error can lead to significant issues, including warnings in the browser that discourage users from proceeding to the website. Therefore, it is essential for web administrators and developers to rectify this error promptly to maintain the integrity and security of their sites.
To identify if your SSL certificate is using a weak signature algorithm, you can utilize online SSL checkers or commands such as:
openssl s_client -connect yourdomain.com:443 -servername yourdomain.comIn the output, look for the line that starts with Signature Algorithm:. If it mentions SHA-1 or another weak algorithm, an update is necessary.
To fix the ERR_CERT_WEAK_SIGNATURE_ALGORITHM error, follow these steps:
openssl command as mentioned earlier to verify the signature algorithm of your existing SSL certificate.httpd.conf or ssl.conf files:SSLCertificateFile /path/to/your_domain.crt
SSLCertificateKeyFile /path/to/your_private.key
SSLCertificateChainFile /path/to/chain_file.crtssl_certificate /path/to/your_domain.crt;
ssl_certificate_key /path/to/your_private.key;openssl command again to ensure the weak signature algorithm error is resolved.By following these steps, you can effectively resolve the ERR_CERT_WEAK_SIGNATURE_ALGORITHM error and enhance the security of your web infrastructure.
SSL/TLS is the encryption protocol that protects data between the browser and server. Our tool analyzes the certificate, chain of trust, TLS version, and knownvulnerabilities.
Issuer, validity period, signature algorithm, covered domains (SAN), and validation type (DV/OV/EV).
Full chain verification: from leaf certificate through intermediates to root CA.
Protocol version (TLS 1.2/1.3), cipher suites, Perfect Forward Secrecy (PFS) support.
Set up a monitor — get Telegram and email alerts 30/14/7 days before expiration.
SSL certificate monitoring
TLS config audit
HTTPS as ranking factor
customer trust
www and subdomains.Strict-Transport-Security header forces browsers to always use HTTPS.SSL certificate monitoring, check history and alerts 30 days before expiry.
Sign up freeNo. This error indicates a real SSL certificate problem. Ignoring it (via chrome://flags or "thisisunsafe") makes the connection vulnerable to man-in-the-middle attacks. Fix it on the server side.
Use the <a href="/en/ssl">Enterno.io SSL/TLS checker</a>, or <a href="/en/monitors">set up monitoring</a> with 14-day expiry alerts. Receive an email/Telegram notification before your users see the error.
Sometimes, for transient cached SSL errors. Steps: chrome://net-internals/#sockets → Flush sockets, chrome://net-internals/#hsts → Delete domain security policies (carefully, for debugging only). But if the issue is server-side, cache clearing will not help.
Yes, Let's Encrypt certificates are in every modern trust store (Chrome, Firefox, Safari, Edge). 90-day validity with automatic renewal via certbot. No reason to use a paid CA for a standard website.
Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.