CAll Us: +256 777 844 758 Live Chat   Login
Chrome to name and shame insecure HTTP websites

Chrome to name and shame insecure HTTP websites

Do you own a website??? or do you run any business accessed via the web?
Does your site run http protocal or https.
Just to emphasize visit your site and see if it starts with https:// with green.
If your site url doesnot start with https just know that by the end of this month(July) your site will ONLY be visible to certain percentage of visitors according to Google.
The problem is that HTTP data is not encrypted, so can be intercepted by third parties to gather data passed between the two systems. This can be addressed by using a secure version called HTTPS, where the S stands for Secure. It involves the use of an SSL (Secure Sockets Layer) certificate, which creates a secure encrypted connection between the web server and the web browser.

The good news is that our hosting Plans and web development packages now includes FREE SSL . Thus you are sure that your site is fully secure and will be accessed by all visitors all over the world .

Contact us + 256 777 844 758 Email: hosting@nugsoft.com
Website: www.nugsoft.com
If your HOST cannot give you SSL(https) For us we shall give you!

——-DETAILS OF ANNOUNCEMENT ARE HERE———
From July, Chrome will name and shame insecure HTTP websites
Shame! Shame! says carrot-dangling Google
By Thomas Claburn in San Francisco 8 Feb 2018 at 18:00 73 Reg comments SHARE ▼

Three years ago, Google’s search engine began favoring in its results websites that use encrypted HTTPS connections.

Sites that secure their content get a boost over websites that used plain-old boring insecure HTTP. In a “carrot and stick” model, that’s the carrot: rewarding security with greater search visibility.

Later this year comes the stick. This summer, Google will mark non-HTTPS websites as insecure in its Chrome browser, fulfilling a plan rolled out in September 2016.

Starting with Chrome 68, due to hit the stable distribution channel on July 2018, visiting a website using an HTTP connection will prompt the message “Not secure” in the browser’s omnibox – the display and input field that accepts both URLs and search queries.

“Chrome’s new interface will help users understand that all HTTP sites are not secure, and continue to move the web toward a secure HTTPS web by default,” Google explained in a draft blog post due to be published today and provided in advance to The Register.

About the Author

Leave a Reply

Enjoy this blog? Please spread the word :)