"Your connection is not private": every error code explained
Chrome, Firefox and Safari show the same "your connection is not private" warning for very different faults. Here is what each browser certificate error code means, what curl and openssl call it, and which ones an outside check can see."Your connection is not private" means the browser could not confirm it is talking to the real site, and the error code under the warning tells you why: an expired certificate, a certificate for a different name, an issuer the browser does not trust, a broken chain, or a TLS version the browser refuses. The same fault gets a different name in Chrome, Firefox, Safari and the command-line tools you would use to debug it, and some of the causes live on the visitor's device, not on your server.
This post maps those names to each other and to the cause. Every server-side case below was tested against badssl.com, a public set of deliberately broken test hosts, with curl, openssl, Safari and Chrome on macOS. The Firefox names come from its source code.
The codes side by side
One row per fault. Chrome shows the code under the warning (click "Advanced" if it is hidden); Firefox shows it under "Advanced" as well; Safari shows no code at all, more on that below.
| Fault (badssl test host) | Chrome | Firefox | openssl verify code | curl (macOS) |
|---|---|---|---|---|
Expired certificate (expired) |
NET::ERR_CERT_DATE_INVALID (the badssl host showed NET::ERR_CERT_AUTHORITY_INVALID, since its chain ends at the AddTrust root that expired in 2020) |
SEC_ERROR_EXPIRED_CERTIFICATE |
10, certificate has expired | exit 60, "certificate has expired" |
Certificate for another name (wrong.host) |
NET::ERR_CERT_COMMON_NAME_INVALID |
SSL_ERROR_BAD_CERT_DOMAIN |
0 unless you pass -verify_hostname, then 62 |
exit 60, "no alternative certificate subject name matches" |
Self-signed (self-signed) |
NET::ERR_CERT_AUTHORITY_INVALID |
MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT |
18, self signed certificate | exit 60, "self signed certificate" |
Unknown root CA (untrusted-root) |
NET::ERR_CERT_AUTHORITY_INVALID |
SEC_ERROR_UNKNOWN_ISSUER |
19, self signed certificate in certificate chain | exit 60, same text |
Missing intermediate (incomplete-chain) |
NET::ERR_CERT_AUTHORITY_INVALID if it cannot fill the gap (it filled it and loaded the badssl page) |
SEC_ERROR_UNKNOWN_ISSUER if it cannot fill the gap |
21, unable to verify the first certificate | loaded the page (200) |
Revoked (revoked) |
NET::ERR_CERT_REVOKED when it knows (it loaded the badssl page) |
SEC_ERROR_REVOKED_CERTIFICATE when it knows |
0, openssl does not check revocation by default | loaded the page (200) |
TLS 1.0 only (tls-v1-0, port 1010) |
ERR_SSL_VERSION_OR_CIPHER_MISMATCH |
a protocol-version error | macOS openssl (LibreSSL) connected over TLS 1.0 | loaded the page (200) |
Two rows in that table stand out. The first is that three different faults share one Chrome code, ERR_CERT_AUTHORITY_INVALID. Firefox's own help text for SEC_ERROR_UNKNOWN_ISSUER says the same thing in plain words: the issuer is unknown, the certificate is self-signed, or the server is not sending the correct intermediate certificates. The code tells you the family of the problem, not the fix.
The second is the last three rows: the command-line tools you would reach for to check a site loaded three broken sites without complaint.
What each Chrome code means
Chromium keeps its error list in net_error_list.h, with a comment under each code listing the causes its engineers expect. Paraphrased:
- [object Object]: the certificate has expired or is not valid yet, by the visitor's clock. Chromium lists "our clock is wrong" as one of the causes.
- [object Object]: the certificate does not cover the name in the address bar. Causes in the source: the server sends the wrong certificate, an attacker redirected the traffic, or a Wi-Fi login page intercepted the request.
- [object Object]: Chrome cannot build a chain to a root it trusts: self-signed, private CA, missing intermediate, or someone in the middle presenting their own certificate.
- [object Object]: the CA has revoked the certificate and Chrome knows about it.
- [object Object]: no TLS version or cipher both sides accept. The source notes that TLS 1.0 and 1.1 now land here.
- [object Object]: a catch-all. Its whole comment in the source is "An SSL protocol error occurred."
Some guides still list NET::ERR_CERT_SYMANTEC_LEGACY or ERR_SSL_OBSOLETE_VERSION. Chromium's own list marks both as removed; an old TLS version now shows as ERR_SSL_VERSION_OR_CIPHER_MISMATCH.
Safari gives no code at all
In Safari the expired, wrong-name, self-signed and unknown-root hosts all produced the same page, word for word apart from the hostname:
This Connection Is Not Private
This website may be impersonating "expired.badssl.com" to steal your
personal or financial information. You should close this page.There is no code and no reason on the page. The only way to see what is wrong is the "view the certificate" link at the bottom, which opens the certificate itself. So when a visitor on a Mac or iPhone reports the error, ask for the URL and test it yourself rather than asking for the error code: they do not have one to give you.
The TLS 1.0 host produced a different page, "Safari Can't Open the Page", saying Safari cannot establish a secure connection to the server. Unlike the certificate warning, it offers no link to continue anyway.
Three broken sites that loaded anyway
A revoked certificate
Safari, Chrome and curl all opened revoked.badssl.com without any warning. The certificate was issued by Let's Encrypt, which stopped running OCSP in 2025, so there is no live revocation check to fail. Browsers now learn about revocations from lists they download in the background, and a revoked certificate only triggers the warning once it is on the list the browser has. Do not count on a revocation to lock visitors out of a compromised certificate; replace it and remove it from your servers.
A missing intermediate certificate
Safari, Chrome and macOS curl all loaded the incomplete-chain host. openssl, run against the same host, refused:
echo | openssl s_client -connect incomplete-chain.badssl.com:443 \
-servername incomplete-chain.badssl.com 2>&1 | grep -E 'verify error|Verify return'
# verify error:num=20:unable to get local issuer certificate
# verify error:num=21:unable to verify the first certificateSome clients fill the gap themselves, from a cache or by downloading the missing certificate, and many do not: most Linux tools, language runtimes and API clients fail. That is how a site works in your browser while its webhooks, mobile app or a partner's integration break. Checking the chain itself, rather than whether a browser loads the page, is the only way to see it.
TLS 1.0
macOS curl connected to the TLS 1.0-only host and got a normal page, while Safari refused it. If you test a server with an old or permissive client, it can pass a check that every current browser fails.
When the problem is on the visitor's side
Some certificate errors have nothing to do with your server. Google measured this in "Where the Wild Warnings Are", a 2017 study of over 300 million Chrome certificate errors, and found that more than half were caused by the client or the network, not by a misconfigured server. In that data, a wrong system clock alone caused 33.5% of the errors on Windows. The numbers are from 2016-2017 and Chrome has changed its warnings since, but the causes are the same:
- Wrong clock: a device set to the wrong date sees a valid certificate as expired or not yet valid. Chrome now shows a dedicated "Your clock is behind" or "Your clock is ahead" page for this; Firefox has "Your Computer Clock is Wrong".
- Antivirus or a company proxy: software that inspects HTTPS traffic presents its own certificate. If its root is not trusted by the browser, the result is an authority error. Firefox checks against its own CA store rather than the operating system's, so a root installed only in the operating system still fails there.
- Wi-Fi login pages: a hotel or airport network intercepts the request before you log in, so the certificate does not match the site.
Google's method for telling these apart works for you too. For every report, it checked whether its own crawler had seen the same certificate problem on that site. If the crawler saw a valid certificate, the fault was on the visitor's side. An outside check does exactly this for you: if a check from outside your network sees a good certificate while one visitor sees an error, look at that visitor's device and network first.
Which ones a monitor can catch
An external SSL check sees what any visitor's client would see from a clean network, so it catches the server-side faults and none of the device-side ones:
| Fault | Seen from outside? |
|---|---|
| Expired or soon-to-expire certificate | Yes |
| Certificate for the wrong name | Yes |
| Self-signed or untrusted root | Yes |
| Missing intermediate | Yes, if the check validates the chain itself instead of filling the gap |
| TLS 1.0 / 1.1 only | Yes, if the check requires a modern TLS version |
| Revoked certificate | Not reliably, as the badssl test shows |
| Wrong clock, antivirus, proxy, Wi-Fi login page | No, these exist only on the visitor's device or network |
WebPixie's SSL monitoring runs this check daily: it validates the certificate against trusted roots, checks the hostname, verifies the full chain from leaf to root, requires TLS 1.2 or higher, and warns 15 days before expiry. That covers the first five rows above. It does not decide revocation for you, and nothing outside the visitor's device can see the last row.
A quick triage order
- Test the URL yourself from a different network. If it works, the cause is likely the visitor's clock, security software or network.
- If it fails for you too, read the code (or, in Safari, open "view the certificate") and find its row in the table above.
- For any ERR_CERT_AUTHORITY_INVALID or SEC_ERROR_UNKNOWN_ISSUER, run the openssl command above to tell a missing intermediate (21) from an untrusted root (19) or a self-signed certificate (18).
- For ERR_SSL_VERSION_OR_CIPHER_MISMATCH, check which TLS versions the server offers; anything below TLS 1.2 is refused by current browsers.