SEC_ERROR_CA_CERT_INVALID — Firefox treats the intermediate/root CA cert as invalid. Causes: expired CA cert, malformed DER encoding, deprecated CA (Symantec 2018), root removed from NSS. Fix: replace chain with a fresh intermediate, or switch CA. Let's Encrypt ISRG Root X1 is 2026-valid with no issues.
Below: causes, fixes, FAQ.
Free online tool — SSL certificate checker: instant results, no signup.
ssl_certificate fullchain.pem; (fullchain, not cert alone)The SEC_ERROR_CA_CERT_INVALID error in Firefox indicates that the browser cannot verify the certificate authority (CA) for the website you are trying to access. To resolve this issue, check the website's SSL certificate, ensure your system time and date are correct, and potentially clear your browser cache or update Firefox. If the issue persists, consider updating the certificate authority list or checking for any expired certificates.
The SEC_ERROR_CA_CERT_INVALID error occurs when Firefox detects that the SSL certificate presented by a website is either self-signed, expired, or issued by an untrusted certificate authority. This error can prevent users from accessing secure websites, impacting both user experience and site credibility.
When encountering this error, it is essential to consider the following factors:
To diagnose the issue, users can check the certificate details by clicking on the padlock icon in the address bar, then selecting 'More Information' and 'View Certificate'. This will display the issuer, validity dates, and trust level of the certificate.
To effectively resolve the SEC_ERROR_CA_CERT_INVALID error, follow these practical steps:
dateOn Linux, use the date command to verify the current date and time.
After following these steps, restart Firefox and try accessing the website again. If the issue persists, consider checking the server-side configuration or contacting the website administrator for further assistance.
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 freeActive. 2021 → 2035. Cross-signed the old DST Root (expired 2024), but X1 self-trust in 99% of modern stacks.
Fullchain includes intermediate. nginx does not fetch intermediate automatically; it ships only the leaf cert → Firefox fails validation.
Firefox uses NSS (separate from OS), ~420 roots. Chrome uses OS trust (Windows/macOS) or the Chrome Root Store.
OpenSSL ca.cnf + valid extensions. Import .crt via about:preferences#privacy → View Certificates → Import.
Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.