The need for an SSL certificate on your website has always been debated. And for those of us that are unsure of what this is, an SSL certificate simply makes transferring data over the internet secure. Which is good for ecommerce websites that collect user card details. But for things like blogs for example, the average marketer doesn’t see the need.
If you have a website, there’s a 30% chance your developer mentioned this to you. There’s also a good chance you said “Nah, I don’t think I’d need it”. Heck I told a student at one of my trainings she didn’t need it. Looks like all of that is about to change.
Chrome’s drive for a more secure web
According to the Google Chrome blog
Studies show that users do not perceive the lack of a “secure” icon as a warning, but also that users become blind to warnings that occur too frequently.
And the plan to counter this is to clearly label non secure pages as such. Like in the image below
This will start by first marking all pages that request for passwords or credit card details of HTTP as non-secure pages. Starting from January 2017, which is in a few months time. Here’s how there pages will look
Still think this doesn’t affect you? After all you don’t collect card details right?
But do you run a tech startup that requires users to log into their account? Or a WordPress blog that allows user registration/login? If yes, you’re still busted. But maybe users wouldn’t notice the little attention seeking circle in their browsers for now. In a few years time though, a huge red triangle will start to make your website look like a phishing site.
It is also important to note though, that this update will only be effected from Chrome 53 upwards. Which is the most recent version of Chrome in circulation as at the time of this writing.
I guess this means you’d need to start selling SSL to your clients as a developer, or consider using it as an SME or startup. At least you’d need to soon enough. What do you think of this update? Let me know
- Was this article helpful?