A user receives this error message “Not Secure https://”. What is the cause?
- The user needs to change the URL to http:// from https://
- The domain is improperly configured at the registrar
- The SSL certificate is invalid or self-signed
- The web server doesn’t support HTTPS sites
- The user’s browser doesn’t support secure websites
Answer:- The correct option is 3. The SSL certificate is invalid or self-signed
This is caused by an invalid SSL certificate on the server. SSL (Secure Sockets Layer) certificates are tiny data files which allow encrypted communication of information between a web server and browser. They also confirm that the website is run by its domain owner. The certificate is signed by a trusted CA for the browser to trust it. The browser will show the warning “Not Secure” when certificate is self-signed by itself instead of a Certificate Authority, or it has expired or became corrupted. Although other problems such as an improper domain configuration or web server mismatch may keep HTTPS access from happening, an invalid SSL certificate is the most prevalent cause. To rectify the above, it is necessary that an appropriate SSL certificate from a trusted CA has been purchased and installed on this particular site. Once proper signing configuration of an operative certificates have occurred, access to the official website can be carried out over secure HTTPS connections without any pre October warnings occurring within browser warning mechanisms. This is one of the common security issues which can be easily avoided by renewing SSL certificates regularly.
Leave a Reply