ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

The Dangers of SSL Warnings and How to Resolve Them as a Website Admin

Updated on January 9, 2018
tamarawilhite profile image

Tamara Wilhite is a technical writer, an industrial engineer, a mother of two, and a published sci-fi and horror author.

An Overview of SSL Warnings

Common SSL errors include warnings of a security certification mismatch, security certificates aren’t issued by a trusted certificate authority and notices that the site may be a phishing scam. Warnings in web browsers like these are intended to inform users of the potential risks of using the website, while website administrators who fail to resolve these warnings create a serious risk for their business.

These warnings are taken to a new level by Google Chrome 56 and Mozilla Firefox 51. These browser versions put insecure login page warnings prominently on the top of the address bar. The SSL warnings in web browsers will only become more severe, since Google plans to eventually show a not secure warning for every page served over HTTP to force sites to migrate to HTTPS. Right now, the warnings will be prominent for every login page that isn’t already HTTPS.

Browsers will be amping up the warnings until it is almost impossible for someone to go to an unsecure site or any site that appears to be unsafe.

Unsecure sites and those misconfigured and seen as unsecure are increasingly hard for users to access.
Unsecure sites and those misconfigured and seen as unsecure are increasingly hard for users to access. | Source

The Danger of SSL Warnings to Users

Users are warned away from sites with SSL warnings because their browser outright states the site may be a phishing site intended to steal your information. Other SSL warnings state that the site may intercept any data you send to the legitimate server, essentially letting you access the legitimate site but steal your credentials or financial information in the process.

Warnings in web browsers are stop signs for most users. A majority of browsers will abandon your website at the sight of these warnings, killing your site’s search engine optimization as surely as a failure to load due to a slow connection. Those few that click through will now be ambivalent to doing business with the site due to security concerns. That negative perception will only grow as the red alerts given by browsers for sites without SSL and HTTPS will become not only unavoidable but require deliberate circumvention.

Browsers are building in warnings to sites that don't have the right SSL certificates that warn your customers away.
Browsers are building in warnings to sites that don't have the right SSL certificates that warn your customers away. | Source

The Danger of SSL Warnings to Website Administrators

SSL protects the privacy and security of your website. A large percentage of web users will refuse to buy anything from a website that isn’t secure; even websites that are protected by high level antivirus software and stringent information security guidelines will lose out on a fifth percent of potential purchases because customers prefer to buy from sites they know are safe. The ideal solution is installing SSL certificates from a reputable Certificate Authority and putting security icons near the total amount owed in the shopping cart. These security icons are separate from giving customers a variety of payment options that let them protect their financial information like Paypal or Bitcoin or letting them checkout as guest so they don’t have to register with your site.

As Google pushes everyone to a secure web by warning users about sites that are not already on HTTPS or using active SSL certificates, there is the possibility that websites will be pushed to the back pages of search results when they don’t meet security requirements just as mobile-unfriendly sites are being penalized in search engine results pages now.

How to Solve SSL Warnings on a Website

If the certificate is valid but listed as expired or not yet valid, the simplest thing to check is the server’s date and time. If this is wrong, it could cause security errors on an otherwise secure site. You should also check the certificate’s expiration date, and if it is actually expired, renew it. If necessary, generate a new SSL certificate. If the group that issued the certificate is no longer in business, buy a new one from a good SSL certifying authority.

Web browsers use a list of certificate authorities to determine which SSL certificates they will accept. Many self-signed certificates issued by the server itself will generate certificate is not trusted errors, an invalid security certificate notice or warning that the SSL certificate was not issued by a trusted provider. Website administrators can solve this problem by getting a certificate from a widely trusted certificate provider. If you have an SSL certificate from a Certificate Authority on the server, the errors could be caused by a second, self-signed certificate still on the server that needs to be removed.

These two issues are rare, but they are the simplest to solve, which is why they were mentioned first. The most common reason why websites generate a certificate not trusted error is that the certificate wasn’t installed correctly. You may need to reinstall the certificate or an intermediate certificate in the broken chain. Don’t forget to check the installation with an SSL certificate tester to verify that the chain that verifies that your SSL is secure is now complete.

Mismatch errors like “the security certificate presented by this site was issued for a different address” or “this certificate is only valid for” occur when the web address for the SSL certificate doesn’t exactly match the domain name in the URL bar. SSL certificate mismatch errors could generate warnings that you reached the wrong site (listing the site name versus the certificate’s site). Some browsers identify the mismatch error as a potential misconfiguration error, while most simply flag it as a threat to the user.

Self-signed certificates can cause this error, as well. In rare cases, the error is due to the domain name being misspelled in the certificate. Administrators can solve this problem by installing multi-domain certificates that work across multiple domain names or IP addresses. This is one way to prevent mobile ready websites and redirects from other domains from being killed by incorrect SSL warnings. If you set up brand new domains, the best solution to prevent errors is to buy an SSL certificate for that site.


This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

Show Details
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)