Certificates

Firefox "Warning: Potential Security Risk Ahead": fix your site

In short. Firefox shows "Warning: Potential Security Risk Ahead" when it cannot verify your website's security certificate, the proof of identity that makes the secure connection possible. Your visitors see a warning and may leave without entering your site. The error code under "Advanced" names the cause. It is up to you, or to your hosting provider or web provider, to fix the certificate, which usually takes a few minutes of configuration.

"Warning: Potential Security Risk Ahead" is the page Firefox shows when it cannot verify a site's certificate. The error code, shown under Advanced, gives the cause. On the site side, four codes come up: expired certificate (SEC_ERROR_EXPIRED_CERTIFICATE), certificate issued for another name (SSL_ERROR_BAD_CERT_DOMAIN), unknown issuer (SEC_ERROR_UNKNOWN_ISSUER) and self-signed certificate (MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT).

Last verified: November 18, 2026, in the Firefox source code.

What your visitors see

The page is titled "Warning: Potential Security Risk Ahead". A more recent version of this page, being rolled out in Firefox, is titled "Warning: Security Risk" and begins with "Be careful. Something doesn’t look right." In both cases, the detail says:

your-domain.com uses an invalid security certificate.

followed by the cause and the line "Error code: …".

The four codes, and the fix

Firefox codeFirefox text (excerpt)Cause on the site sideFix
SEC_ERROR_EXPIRED_CERTIFICATE"The certificate for your-domain.com expired on …"certificate not renewedRenew
SSL_ERROR_BAD_CERT_DOMAIN"… it uses a certificate that is not valid for your-domain.com."name missing from the certificate (www, subdomain)Add the name
SEC_ERROR_UNKNOWN_ISSUER"… its certificate issuer is unknown, the certificate is self-signed, or the server is not sending the correct intermediate certificates."incomplete chain, or unrecognized authorityInstall the chain
MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT"The certificate is not trusted because it is self-signed."temporary certificate, never replacedInstall a real certificate

Chrome flags the same problems with other codes: NET::ERR_CERT_DATE_INVALID, NET::ERR_CERT_COMMON_NAME_INVALID and NET::ERR_CERT_AUTHORITY_INVALID. The fixes are identical.

A Firefox particularity: the certificate chain

The SEC_ERROR_UNKNOWN_ISSUER text says it itself: the server may not be sending the right intermediate certificates. A site can therefore display without error in one browser and fail in Firefox. The fix is on the server: serve the full chain (with certbot, the fullchain.pem file).

Another particularity: Firefox verifies certificates against Mozilla's authority store, not the system's. An antivirus or a company network that inspects connections can therefore trigger the warning on a single machine: in that case, the site is not at fault.

Check from the Internet

Test the site from another device and another network. If the error appears everywhere, the cause is on the site.

Check your certificate for free. Our tool reads your certificate from the Internet, like a browser, and tells you whether it has expired, whether it covers your address and whether the chain is complete. Check my certificate

Frequently asked questions

The error only appears in Firefox. Why?

Most often, the chain is incomplete: other browsers find the missing intermediate, Firefox does not. Serve the full chain.

No. If Firefox says the site might not support TLS 1.2, the minimum version it accepts, the problem comes from the server configuration, not the certificate. You need to enable TLS 1.2 or 1.3 on the server.

Can a visitor add an exception?

Yes, but it is best avoided: they cannot tell your faulty certificate from an attacker's. Fix the certificate rather than counting on exceptions.

Sources

Accessed on 11/18/2026.