Ars Technica: Firefox, Chrome start calling HTTP connections insecure

Ars Technica: Firefox, Chrome start calling HTTP connections insecure. “The non-secure labelling will occur on pages delivered over HTTP that include forms. Specifically, pages that include password fields, and in Chrome, credit card fields, will put warnings in the address bar to explicitly indicate that the connection is not secure.”

Search Engine Land Has an Overview of SSL Certificates

Search Engine Land has an overview of SSL certificates. “A full range of SSL products are available on the market today that cater to various domain and security needs. Though many webmasters are exploring the possibilities, hoping a move to SSL will boost their search rankings, it can be overwhelming to try to compare these options, let alone fully understand what you’re paying for.”

WordPress Moving More Towards SSL

WordPress is moving more towards SSL. “We’re at a turning point: 2017 is going to be the year that we’re going to see features in WordPress which require hosts to have HTTPS available. Just as JavaScript is a near necessity for smoother user experiences and more modern PHP versions are critical for performance, SSL just makes sense as the next hurdle our users are going to face.”

Google Adds More Data to Transparency Report’s HTTPS Section

An update to Google’s Transparency Report shows the increased adoption of HTTPS. “Today, we’re adding a new section to the HTTPS Report Card in our Transparency Report that includes data about how HTTPS usage has been increasing over time. More than half of pages loaded and two-thirds of total time spent by Chrome desktop users occur via HTTPS, and we expect these metrics to continue their strong upward trajectory.”

National Center for Biotechnology Information is Shifting to HTTPS

The National Center for Biotechnology Information is shifting to https. “To improve security and privacy, and by Federal government mandate, NCBI is moving all of its Web sites and services, including Web APIs, to HTTPS only by September 30, 2016. If you use NCBI only through a Web browser (like Safari, Firefox, Chrome, Internet Explorer, Opera, etc.), this document is not of interest to you. …
If you maintain software that uses NCBI APIs or accesses NCBI servers through the Web, you should understand and act before the deadline to ensure uninterrupted service.”

Chrome Will Start Marking HTTP Site Connections as Insecure

Chrome will start marking http connections as unsecure. “To help users browse the web safely, Chrome indicates connection security with an icon in the address bar. Historically, Chrome has not explicitly labelled HTTP connections as non-secure. Beginning in January 2017 (Chrome 56), we’ll mark HTTP sites that transmit passwords or credit cards as non-secure, as part of a long-term plan to mark all HTTP sites as non-secure.”