Chrome to start marking HTTP as insecureTravis N.
In January of 2017, Google will be releasing Chrome 56 which has a feature that will warn users when they visit HTTP sites, marking them as “not secure” before HTTP URLs, but only for pages that contain credit card or password fields. Over the last decade, internet shopping has exploded and while 20 years ago we were warned to never enter our credit card number online, that is definitely not the case today. It’s also in eventual works that all HTTP pages will be labeled as “not secure” in Chrome, however this is still a ways off.
Chrome has found that people are starting to become too aware of issues regarding secure sites but nothing has been done about insecure sites. This is prompting the gradual change for how sites handle issues with password fields and credit card fields.
Keeping Things Secure
HTTPS is a protocol that helps encrypt the traffic between the web browser and the server. Any information sent over that session is typically secure. All of Xinsto’s sites are protected by HTTPS, ensuring that only the correct servers and our customers’ web browsers can securely talk. In the security front, there’s also a shift going on. Now, users should be advised not to login on insecure pages, only pages that offer HTTPS protection so that your password cannot be intercepted while it’s being sent to a website.
Xinsto helps keep our customers secure by providing free SSL certificates on all hosting packages. They’re automatically enabled on all hosting accounts and can be used within a few minutes. There’s no work, and they’re unlimited. They self-renew and stay up to date so you don’t have to worry about a thing. Although, we highly suggest buying stronger SSL certificates if the situation depends on it.