SEC_ERROR_UNKNOWN_CRITICAL_EXTENSION — cert carries an X.509 extension marked critical=TRUE, but Firefox does not recognise the OID. Per RFC 5280, a client MUST reject certs with unknown critical extensions. Fix: reissue cert without exotic extensions, or drop the critical flag.
Below: causes, fixes, FAQ.
critical = FALSEopenssl x509 -in cert.pem -text | grep -A1 "critical" — list critical onesSSL/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 freeRFC 5280: if the extension is critical, the client must process it. Otherwise reject the cert (for safety).
Chrome is more lenient with unknown extensions (if non-critical). Critical — reject too.
BasicConstraints, KeyUsage, NameConstraints. Custom Policy extensions are often non-critical.
https://crt.sh for public cert, or the dumpasn1 utility for binary parsing.