{"id":1030,"date":"2016-12-02T13:09:16","date_gmt":"2016-12-02T13:09:16","guid":{"rendered":"http:\/\/ntsplhosting.com\/blog\/\/?p=1030"},"modified":"2024-09-18T06:58:18","modified_gmt":"2024-09-18T06:58:18","slug":"theres-less-than-two-months-before-browsers-start-penalizing-sites-without-ssl","status":"publish","type":"post","link":"https:\/\/www.ntsplhosting.com\/blog\/theres-less-than-two-months-before-browsers-start-penalizing-sites-without-ssl\/","title":{"rendered":"There&#8217;s Less Than Two Months Before Browsers Start Penalizing Sites Without SSL."},"content":{"rendered":"<p style=\"text-align: justify;\">We&#8217;ve said it before, and we&#8217;ll say it again: <a href=\"https:\/\/www.ntsplhosting.com\/security\/ssl-certificate\/\" target=\"_blank\" rel=\"noopener noreferrer\">SSL<\/a> is no longer optional. It&#8217;s mandatory. Regardless of what kind of site your customers are running, soon they&#8217;ll be penalized by the browser community for not having encryption.<\/p>\n<p style=\"text-align: justify;\">Already, the browsers are rewarding encrypted sites with SEO ranking boosts and the use of advanced features. But soon, non-encrypted sites will be given negative security indicators and actively labeled &#8220;not secure&#8221; in the address bar.<\/p>\n<p style=\"text-align: justify;\">From January 2017, Google Chrome (version 56 and onwards) will begin marking HTTP sites that transmit passwords or request credit card details as \u201cnot secure\u201d.<\/p>\n<p style=\"text-align: justify;\">The move comes as part of a longer term strategy to eventually label all non-HTTPS sites as insecure within Google\u2019s browser, helping users to browse the web more safely.<\/p>\n<p style=\"text-align: justify;\">The current neutral indicator that\u2019s displayed for HTTP connections in Google Chrome doesn\u2019t point out their lack of security. It is possible for someone else on the same network to look at or interfere with a website using an HTTP connection before it reaches you.<\/p>\n<p style=\"text-align: justify;\">Sites that do make use of an HTTPS connection will continue to be labelled with a green padlock icon, marking them as secure. The lack of a secure icon however, is not enough for users to recognize a site as insecure. The new label for HTTP sites will help highlight their insecure nature to users.<\/p>\n<p style=\"text-align: justify;\"><a href=\"http:\/\/ntsplhosting.com\/blog\/\/wp-content\/uploads\/2016\/12\/non-https-examples.png\"><img loading=\"lazy\" class=\"aligncenter wp-image-1031 size-full\" src=\"https:\/\/ntsplhosting.com\/blog\/\/wp-content\/uploads\/2016\/12\/non-https-examples.png\" alt=\"SSL Certificate\" width=\"850\" height=\"270\" srcset=\"https:\/\/www.ntsplhosting.com\/blog\/wp-content\/uploads\/2016\/12\/non-https-examples.png 850w, https:\/\/www.ntsplhosting.com\/blog\/wp-content\/uploads\/2016\/12\/non-https-examples-300x95.png 300w, https:\/\/www.ntsplhosting.com\/blog\/wp-content\/uploads\/2016\/12\/non-https-examples-768x244.png 768w\" sizes=\"(max-width: 850px) 100vw, 850px\" \/><\/a><\/p>\n<p style=\"text-align: justify;\"><strong>The Gradual Plan<\/strong><\/p>\n<p style=\"text-align: justify;\"><strong>Google\u2019s plan to label HTTP sites will include the introduction of indicators gradually:<\/strong><\/p>\n<ul style=\"text-align: justify;\">\n<li>Firstly, starting in January 2017 on Chrome 56 \u2013 the aforementioned \u201cnot secure\u201d label for HTTP sites with password or credit card form fields.<\/li>\n<li>Subsequent releases \u2013 further warnings, for instance, HTTP sites being labelled as \u201cnot secure\u201d when users are in Incognito mode, with higher privacy expectations.<\/li>\n<li>Eventually \u2013 all HTTP sites to be labelled as \u201cnot secure\u201d, displayed with a red triangle like the current broken HTTPS indicator.<\/li>\n<\/ul>\n<p style=\"text-align: justify;\" align=\"center\"><a href=\"http:\/\/ntsplhosting.com\/blog\/\/wp-content\/uploads\/2016\/12\/not-secure-example.png\"><img loading=\"lazy\" class=\"aligncenter wp-image-1032 size-full\" src=\"https:\/\/ntsplhosting.com\/blog\/\/wp-content\/uploads\/2016\/12\/not-secure-example.png\" alt=\"not-secure-example\" width=\"850\" height=\"155\" srcset=\"https:\/\/www.ntsplhosting.com\/blog\/wp-content\/uploads\/2016\/12\/not-secure-example.png 850w, https:\/\/www.ntsplhosting.com\/blog\/wp-content\/uploads\/2016\/12\/not-secure-example-300x55.png 300w, https:\/\/www.ntsplhosting.com\/blog\/wp-content\/uploads\/2016\/12\/not-secure-example-768x140.png 768w\" sizes=\"(max-width: 850px) 100vw, 850px\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">This announcement by Google should act as a warning call to website owners. If you haven\u2019t already, it is now more important than ever to consider switching your site to HTTPS to avoid being flagged as \u201cnot secure\u201d in Chrome.<\/p>\n<p style=\"text-align: justify;\">This label could put off potential customers from trusting your site\u2019s content and security, leading them to turn elsewhere for their desired products or services. Along with the fact that a small search engine ranking boost is given to sites that make use of HTTPS, this should provide sufficient reason to make the switch.<\/p>\n<p style=\"text-align: justify;\"><a href=\"https:\/\/ntsplhosting.com\" target=\"_blank\" rel=\"noopener noreferrer\">NTSPL Hosting<\/a> can help you switch your site over to a secure HTTPS connection, and avoid being labelled as &#8220;not secure&#8221; in Google Chrome. To find out more, please don&#8217;t hesitate to <a href=\"https:\/\/www.ntsplhosting.com\/company\/contact-us\">contact us<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>We&#8217;ve said it before, and we&#8217;ll say it again: SSL is no longer optional. It&#8217;s mandatory. Regardless of what kind of site your customers are running, soon they&#8217;ll be penalized by the browser community for not having encryption. Already, the browsers are rewarding encrypted sites with SEO ranking boosts and the use of advanced features. [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":1451,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[22],"tags":[98,145,305,335,347,361],"_links":{"self":[{"href":"https:\/\/www.ntsplhosting.com\/blog\/wp-json\/wp\/v2\/posts\/1030"}],"collection":[{"href":"https:\/\/www.ntsplhosting.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ntsplhosting.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ntsplhosting.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ntsplhosting.com\/blog\/wp-json\/wp\/v2\/comments?post=1030"}],"version-history":[{"count":6,"href":"https:\/\/www.ntsplhosting.com\/blog\/wp-json\/wp\/v2\/posts\/1030\/revisions"}],"predecessor-version":[{"id":37882,"href":"https:\/\/www.ntsplhosting.com\/blog\/wp-json\/wp\/v2\/posts\/1030\/revisions\/37882"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ntsplhosting.com\/blog\/wp-json\/wp\/v2\/media\/1451"}],"wp:attachment":[{"href":"https:\/\/www.ntsplhosting.com\/blog\/wp-json\/wp\/v2\/media?parent=1030"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ntsplhosting.com\/blog\/wp-json\/wp\/v2\/categories?post=1030"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ntsplhosting.com\/blog\/wp-json\/wp\/v2\/tags?post=1030"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}