Have you ever encountered a situation where a website displays a "Certificate Valid" message, but at the same time, your browser shows it as "Not Secure"? This can be quite confusing, but don't worry, we've got you covered. In this article, we will explain what this means, why it happens, and what you can do about it.
First, let's start with the basics. A website's SSL certificate is what enables the HTTPS protocol, which encrypts the data that is transmitted between your browser and the website's server. This is important for protecting sensitive information, such as login credentials, credit card numbers, and personal data.
When you visit a website, your browser checks the website's SSL certificate to ensure that it is valid and that the website is who it claims to be. If the certificate is valid, the browser will display a padlock icon and the HTTPS protocol in the address bar. However, if the certificate is not valid, the browser will display a "Not Secure" message instead.
So, why would a website display a "Certificate Valid" message, but still show as "Not Secure" in some browsers? There are a few reasons why this might happen:
- Mixed Content: Mixed content occurs when a website uses both HTTPS and HTTP protocols. If a website has an SSL certificate but still serves some of its content over an unencrypted HTTP connection, it can cause the browser to display a "Not Secure" message. This is because the unencrypted content can be intercepted and modified by malicious actors.
- Outdated Browser: Some older browsers may not support the latest SSL/TLS protocols. If a website uses a newer protocol that is not supported by an older browser, it can cause the browser to display a "Not Secure" message.
- Expired Certificate: Although this is not a common scenario, if a website's SSL certificate has expired, it can cause the browser to display a "Not Secure" message. This is because an expired certificate is no longer valid and cannot be trusted.
Now that we know why this might happen, let's take a look at what you can do about it:
Check for Mixed Content
The first thing you should do is check if the website is serving any content over an unencrypted HTTP connection. You can do this by right-clicking anywhere on the website and selecting "Inspect" or "Inspect Element". This will open the developer console, which will display any mixed content warnings.
If you find any mixed content, you can contact the website's owner and let them know about the issue. They should be able to update the website to use HTTPS for all content.
Update Your Browser
If you are using an older browser, you may want to consider updating it to the latest version. This will ensure that you have the latest SSL/TLS protocols and that you are protected against known vulnerabilities.
Most modern browsers, such as Google Chrome, Mozilla Firefox, and Microsoft Edge, support the latest SSL/TLS protocols and will display a padlock icon and the HTTPS protocol in the address bar if a website's SSL certificate is valid.
Contact the Website Owner
If you have checked for mixed content and have updated your browser, but the website still displays a "Not Secure" message, you may want to contact the website's owner. They may be able to provide more information about the issue and can take steps to resolve it.
A website's SSL certificate is an important part of its security infrastructure. If a website displays a "Certificate Valid" message but still shows as "Not Secure" in some browsers, it can be caused by mixed content, an outdated browser, or an expired certificate. By checking for mixed content, updating your browser, and contacting the website owner, you can help ensure that your data is protected and that you are browsing safely.
References
| Title | Author | Date | URL |
|---|---|---|---|
| What Does It Mean When a Website Is Not Secure? | Google Chrome Team | 2021-02-16 |
https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/security/not_secure.md
|
| HTTPS Mixed Content | Mozilla Developer Network | 2021-02-16 |
https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content
|
| HTTPS and SSL/TLS | Microsoft Edge Developer Network | 2021-02-16 |
https://docs.microsoft.com/en-us/microsoft-edge/dev-guide/security/https
|