{"id":510,"date":"2018-02-13T10:42:52","date_gmt":"2018-02-13T08:42:52","guid":{"rendered":"https:\/\/subsign.co\/stories\/?p=510"},"modified":"2018-02-20T10:54:44","modified_gmt":"2018-02-20T08:54:44","slug":"non-https-websites-not-secure","status":"publish","type":"post","link":"https:\/\/subsign.co\/stories\/non-https-websites-not-secure\/","title":{"rendered":"Google Chrome will mark all non-HTTPS websites as “Not secure”."},"content":{"rendered":"

How will this affect your browsing experience?<\/b><\/h2>\n

Short answer; it won\u2019t. You\u2019ll still be able to browse non-HTTPS websites as earlier. The idea behind the initiative is to let users know that their personal information is at a higher risk of getting into the wrong <\/span>hands while browsing non-HTTPS sites.<\/span><\/p>\n

\u201cFor the past several years, we\u2019ve moved toward a more secure web by strongly advocating for HTTPS encryption, and helped users to understand that HTTP sites are not secure. Developers transitioning their sites to HTTPS have made the web safer for everyone.\u201d –\u00a0Google said in a blog<\/a> post.<\/p><\/blockquote>\n

Will this affect websites that do not employ HTTPS?<\/b><\/h2>\n

Yes, websites that do not use HTTPS might witness a potential dip in traffic, as a yellow triangle with \u201cnot secure\u201d plastered next to it has the potential to scare away some of the more paranoid users. But, it is a good thing in the long run as it will incentivize more developers to use HTTPS on their websites.<\/span><\/p>\n

Honestly, there\u2019s no reason developers shouldn\u2019t adopt it. It\u2019s cheaper and easier than ever before. Undertakings such as Let\u2019s Encrypt and Google\u2019s SSL for Google App Engine makes it a lot easier for HTTPS to be implemented. There are also tools like Lighthouse, which identifies website resources that are ready to be upgraded to HTTPS.<\/span><\/p>\n

What Should I Be Doing to Secure My Pages?<\/b><\/h2>\n

If you believe as I do that HTTPS is going to be the new standard, then I bet you\u2019re thinking about what you actually need to do to ensure your corporate web pages and landing pages are secured. The three steps below are meant to get you started on the right path.<\/span><\/p>\n

STEP 1: Check if your Corporate Domain is Secure<\/b><\/h2>\n

While the title of this step sounds like you need to have mad technical skills\u2014you really don\u2019t. All you need to do is to type your corporate website URL into any browser. For me, it\u2019s opening up Chrome and typing, <\/span>www.subsign.co<\/span><\/a> . You\u2019re looking to see if the address bar says HTTP: or HTTPS: and\/or if using Chrome, you\u2019re looking for the green lock and word \u201csecure\u201d when your page loads. If you see HTTPS, your corporate site is secure. It\u2019s that easy.<\/span><\/p>\n

If your corporate site is not secured, you may want to do a quick audit of your pages. You\u2019ll want to note the address of any page that has a form or collects information. With the recent update to Chrome 62, it\u2019s those HTTP pages that collect data that will display the \u201cnot secure\u201d warning in the address bar. This list will also give you a starting point for the discussion you\u2019ll need to have with your IT and web teams in the next step.<\/span><\/p>\n

<\/p>\n

STEP 2: Meet with an experienced Web Team<\/b><\/h2>\n

It\u2019s now time to enlist your experts. Schedule a time to meet with whoever is responsible for your corporate website or others you trust and have a proven track record. You\u2019ll want to be sure they know of the changes to Chrome browser, and you\u2019ll want to know of any plans that may already be in place to secure your corporate pages.<\/span><\/p>\n

Google also shared the following statistics regarding web traffic.<\/span><\/p>\n

    \n
  • Over 68 percent of Chrome traffic on both Android and Windows is now protected;<\/li>\n
  • Over 78 percent of Chrome traffic on both Chrome OS and Mac is now protected;<\/li>\n
  • 81 of the top 100 sites on the web use HTTPS by default.<\/li>\n<\/ul>\n

    That being said, even HTTPS isn\u2019t one hundred percent waterproof, however, it is a step in the right direction to ensure a more secure browsing experience for everyone.<\/span><\/p>\n

    Feel free to get in touch with us at hello@subsign.co if any questions appear or even if you need help with securing your website.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

    How will this affect your browsing experience? Short answer; it won\u2019t. You\u2019ll still be able to browse non-HTTPS websites as earlier. The idea behind the initiative is to let users know that their personal information is at a higher risk of getting into the wrong hands while browsing non-HTTPS sites. \u201cFor the past several years, […]<\/p>\n","protected":false},"author":1,"featured_media":519,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3],"tags":[],"class_list":["post-510","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-development"],"acf":[],"_links":{"self":[{"href":"https:\/\/subsign.co\/stories\/wp-json\/wp\/v2\/posts\/510","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/subsign.co\/stories\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/subsign.co\/stories\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/subsign.co\/stories\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/subsign.co\/stories\/wp-json\/wp\/v2\/comments?post=510"}],"version-history":[{"count":7,"href":"https:\/\/subsign.co\/stories\/wp-json\/wp\/v2\/posts\/510\/revisions"}],"predecessor-version":[{"id":522,"href":"https:\/\/subsign.co\/stories\/wp-json\/wp\/v2\/posts\/510\/revisions\/522"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/subsign.co\/stories\/wp-json\/wp\/v2\/media\/519"}],"wp:attachment":[{"href":"https:\/\/subsign.co\/stories\/wp-json\/wp\/v2\/media?parent=510"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/subsign.co\/stories\/wp-json\/wp\/v2\/categories?post=510"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/subsign.co\/stories\/wp-json\/wp\/v2\/tags?post=510"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}