If a website's SSL certificate is invalid or not available, users may see an error message when they attempt to load it.
After reading this article you will be able to:
Copy article link
Users may occasionally find themselves blocked from reaching a website by a "Your connection is not private" message. This error means that the connection between the client (the user's device, such as a laptop or tablet) and the server (the website host) is not encrypted, even though the client device expected it to be encrypted.
As a result, attackers will be able to see what the user does on the website – messages between the client and the server are sent in plaintext, instead of being scrambled via encryption. In addition, the client is unable to verify that it is connected to the correct server.
This is why the browser will say "Your connection is not private" or "Your connection is not secure": it can't verify the web server, and it can't encrypt messages to stop attackers from reading them.
This error is caused by an issue with the website's SSL certificate – it's missing, or it's expired, or it wasn't issued by a legitimate certificate authority, or the client can't access it for some other reason. SSL certificates are necessary for serving websites over secure HTTPS connections.
An invalid or missing SSL certificate is almost the cryptographic equivalent of a cashier at a corner store asking a man for identification in order to prove he's old enough to purchase alcohol, and instead of producing a government-issued ID card, he pulls out a piece of paper on which someone has written, "This man is named Jeff, and he is 22 years old." This, of course, is not legitimate identification. The man may not in fact be 22 years old, and for that matter the man might not even be named Jeff. The cashier is right to respond with suspicion and terminate the transaction altogether.
Much like Jeff, a website without an SSL certificate cannot prove its identity. On top of that, a website without an SSL certificate can't encrypt communications – imagine if Jeff's lack of an ID card meant that anyone around the world could suddenly hear the conversation between Jeff and the cashier.
Often users can still continue on to the page in spite of this message, although this is not recommended. Without HTTPS, a variety of cyber attacks are possible.
An SSL certificate verifies ownership of a website and makes opening a secure, encrypted connection possible. It's a text file installed on a web server with information like:
If data is encrypted with TLS/SSL, when someone intercepts the data going back and forth between client and server, it just looks like random nonsense to them. If data is not encrypted, someone can intercept the data and easily read it. Encryption is like an envelope protecting the contents of a personal letter as it goes through the mail.
A number of issues with the SSL certificate can cause the "Your connection is not private" error:
The website's SSL certificate isn't valid or is missing. This could be the case for a number of reasons. It can mean that the SSL certificate presented lists the wrong website, that the SSL certificate has expired, or that there's no SSL certificate at all when one was expected – for instance, if a user types https://www.example.com into a browser, but example.com doesn't have HTTPS.
The SSL certificate doesn't list variations on the domain name. For example, the SSL certificate may list www.example.com, but not example.com (without the "www"). This happens when the Subject Alternative Name (SAN) section of an SSL certificate is not filled out properly. As a result, the website has a working SSL certificate, but there's a mismatch between the URL the user typed in and what's listed on the certificate. The browser therefore considers the certificate invalid.
The web server presented an SSL certificate for the wrong website. This can happen when multiple websites are hosted at one IP address. If each of those websites has its own SSL certificate, the server may not know which SSL certificate to show when a client device tries to securely connect to one of the websites – much like when a package is mailed to an apartment complex but the apartment number is not included in the address. An extension to the TLS protocol called SNI helps prevent this error.
Other possible causes include:
Refresh the page: Network connections involve a lot of back-and-forth communication between client and server that mostly goes unnoticed by the user. Any number of these communications may not go correctly. For this reason, a variety of errors can be solved by trying again and reloading the page.
Clear browser cache: A browser stores some information and content from websites users have visited before in a temporary storage location known as a "cache." Clearing the browser cache and trying to load the page again can have a similar effect to refreshing the page: the website has a clean slate from the browser's perspective, and the browser can try to make the proper connections again. Alternatively, users can also open the page in Incognito mode (Chrome), Private mode (Firefox and Safari), or InPrivate mode (Edge); in these modes the browser does not access the cache.
Reset the clock: Users can also try resetting their computer's clock, which may be inaccurate, causing the device to incorrectly reject an SSL certificate as expired or invalid.
Add 'www': To circumvent SAN errors, users can try retyping the domain name so that it includes "www" (or whatever the domain prefix is).
Use a different browser, or update the browser: Old versions of browsers may not support necessary features for TLS encryption (such as SNI). Make sure to use the latest versions of browsers.
Obtain a new SSL certificate: If the certificate is expired, outmoded, or self-signed, a website will need to obtain a new one from a certificate authority. (Cloudflare offers free SSL certificates, along with customized certificates for enterprise customers).
Make sure SAN is filled out, and subdomains are included: If the SSL certificate is otherwise valid, be sure all legitimate variations on the domain are listed. Also, subdomains – blog.example.com in addition to www.example.com – should be listed.
If a website doesn't have HTTPS, make sure all backlinks are HTTP only: If a user inadvertently tries to load a URL over HTTPS when the website only uses HTTP, they may get this error, because the browser has tried to obtain the website's SSL certificate when there isn't one. In addition to fixing backlinks, a website should set up redirects to HTTP in the event someone tries to load it over HTTPS. Also, it is highly recommended that such websites obtain SSL certificates.
In Chrome, this message appears when clicking on the "Not Secure" in the browser bar when on an HTTP site. It means that the website does not have an SSL certificate and does not use SSL/TLS for encrypting traffic to and from the site. Browsers won't typically block websites that don't have HTTPS, but users should avoid entering personal data, like login credentials, credit card data, or government-issued ID numbers, on non-HTTPS websites.
Cloudflare offers free SSL/TLS encryption for any website. Websites with Cloudflare TLS encryption should not encounter most of these errors, although improperly configured client devices could still cause them to pop up from time to time. Learn more about free SSL certificates from Cloudflare. Test for potential SSL/TLS errors at the Cloudflare Diagnostic Center.
Learning Center Navigation