SEC_ERROR_INADEQUATE_KEY_USAGE — Firefox: cert carries a Key Usage extension (keyUsage) but lacks the required bits for server auth. Needed: digitalSignature + keyEncipherment (RSA) or digitalSignature (ECDSA). Or Extended Key Usage (EKU) is missing serverAuth. Fix: reissue via the CA with correct extensions.
Below: causes, fixes, FAQ.
TLS Web Server Authenticationopenssl x509 -in cert.pem -text | grep -A2 "Key Usage"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 freeKey Usage — primary: what the cert can do cryptographically (sign, encrypt). EKU — constraining: for which applications it is allowed (server auth, client auth, email, code signing).
RSA: KU=digitalSignature,keyEncipherment + EKU=serverAuth. ECDSA: KU=digitalSignature + EKU=serverAuth.
Yes. In OpenSSL config: <code>keyUsage=digitalSignature,keyEncipherment</code> + <code>extendedKeyUsage=serverAuth</code>.
Firefox historically stricter on KU validation. Chrome also checks but sometimes warns less loudly.