Opens in a new tab

NET::ERR_CERT_AUTHORITY_INVALID and SEC_ERROR_UNKNOWN_ISSUER

The browser could not trace the certificate back to an authority it trusts. There are three usual reasons: the certificate is self-signed, the server is not sending its intermediate certificate, or something on the visitor’s device or network — antivirus, a company proxy — is replacing certificates with its own.

Your connection is not private
NET::ERR_CERT_AUTHORITY_INVALID
How 3 other clients word the same error

Firefox

Error code: SEC_ERROR_UNKNOWN_ISSUER — “Firefox doesn’t trust this site because we can’t tell who issued the certificate, it’s self-signed, or the site isn’t sending intermediate certificates we trust.”

curl on Windows (Schannel)

curl: (60) schannel: SEC_E_UNTRUSTED_ROOT (0x80090325) - The certificate chain was issued by an authority that is not trusted.

Go

x509: certificate signed by unknown authority
ErrorNET::ERR_CERT_AUTHORITY_INVALID
Usually fixed byEither side
FirefoxSEC_ERROR_UNKNOWN_ISSUER
Can visitors click through?Yes, unless the site uses HSTS

Check the certificate a site serves

Enter the site’s domain: we connect the way a browser does and show the certificate, its chain and the TLS versions it offers.

What it means

A browser trusts a certificate when it can follow a chain from it, through one or more intermediate certificates, to a root it has built in. This error means that chain could not be completed — the root is unknown, or a link is missing.

Whose problem it is depends on where you see it. On one site only, the site is at fault: self-signed, or missing its intermediate. On every HTTPS site, something on your device or network is intercepting connections.

Why it happens

  • A self-signed certificate, or one from a private certificate authority — see self-signed certificate.
  • The server sends only its own certificate, without the intermediate — see missing intermediate certificate. Chrome often repairs this by downloading the intermediate; Firefox and most apps do not.
  • Antivirus “HTTPS scanning”, a company proxy or security software replacing certificates — see HTTPS interception.
  • A Wi-Fi sign-in page, a browser extension, or an outdated operating system missing newer roots.

How to fix it

  1. Run the check above. If it shows a self-signed or private certificate, replace it with one from a public authority such as Let’s Encrypt.
  2. If it shows a missing intermediate, configure the server to send the full chain (fullchain.pem, not cert.pem).
  3. If the site checks out fine here but your browser complains about every site, the cause is on your device or network.

If you are visiting the site

  • If the error appears on many sites, turn off HTTPS scanning in your antivirus or ask your IT team about the network’s proxy; try another network. Update the operating system and the browser.

Sources

Error text and meaning checked on 25 September 2026 against these official sources:

Hear about it before your visitors do

Add your domain and we check its certificate on every scan and email you before it expires, and when it changes or stops being valid — along with DNS, email and security headers. Free for your first domain.

Create a free account