• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Red Sift Blog

Red Sift Blog
  • redsift.com
  • Featured
  • Who are we?
  • Get in touch
You are here: Home / Cybersecurity / How HTTPS made HTTP a thing of the past

How HTTPS made HTTP a thing of the past

by Deepak Prabhakara
July 26, 2018August 16, 2022Filed under:
  • Cybersecurity
Photo by Paweł Czerwiński on Unsplash

On Tuesday 24th of July 2018, Google took a big step towards making the internet more secure with their release of Chrome 68. It will now flag a warning to users when they visit a website that uses unencrypted HTTP instead of HTTPS. This has been in discussion for a long time and we at Red Sift think that this is a great initiative as it will encourage website owners who use the HTTP to upgrade to the more secure and encrypted HTTPS or risk visitors fleeing when they see the words “Not Secure” appear in the browser bar.

What are HTTP and HTTPS?

HTTP stands for Hypertext Transfer Protocol and is one of the key elements that underpin the internet. This protocol is what allows you to fetch and load pages that are hosted on different servers. The modern HTTPS protocol solves the main problem of HTTP, the fact that it is inherently insecure and does not use encryption to protect users against malicious content and systems.

HTTPS isn’t new, so why now?

HTTPS, or Hypertext Transfer Protocol Secure, has been around for about 10 years, but people have only been using it for certain parts of their websites. You’d usually only find HTTPS used on pages where you filled in passwords or other sensitive information. If you think back to IT class in school, you’ll remember that one of the key things you were told was to never enter passwords or sensitive information into a website unless we saw the padlock symbol in the address bar.

The reason HTTPS wasn’t used more widely sooner was that not so long ago, it would have caused a significant strain on servers and network speed, not to mention you’d actually have to pay for your HTTPS certification. But happily, with modern technology, HTTPS doesn’t cause any server strain or impact speed meaning that in most cases, you won’t experience any loss in performance. Furthermore, initiatives such as “Let’s Encrypt” have brought together forces such as Google, Facebook, Github, and Cisco to offer free HTTPS certification.

So why does Red Sift love this development?

From now on, Google’s newest version of Chrome will warn users when they land on HTTP page with a note in the browser bar – compare this to what you see when you visit a site secured with HTTPS. Additionally, users may also see a popup that explains why the site is not secure.

Unsecured vs Secured websites

As a cybersecurity company with a mission to democratize it for all, we’re really happy to see initiatives like this being rolled out. They proactively encourage website owners to update their security or risk being labeled as an untrusted site. Although approaches like this may seem harsh to some there is no arguing that this approach will have a greater impact and contribute to a more secure online environment for all of us.

So how do you get your hands on Chrome 68?

You can update your Chrome version to 68 by:

  1. On your computer, open Chrome
  2. At the top right, click More
  3. Click Update Google Chrome. If you don’t see this button, you’re on the latest version.
  4. Click Relaunch

Simple! Now, the next time you unknowingly visit an HTTP website you’ll see the warning and can decide for yourself if you still want to carry on browsing.

Find out more about Red Sift

Keen to find out more about Red Sift, what we do, and how our products help businesses keep their email infrastructure and domains secure? Get in touch with us below!

Get in touch

Share this:

  • Click to share on Twitter (Opens in new window)
  • Click to share on LinkedIn (Opens in new window)

Related

Tagged:
  • Cybersecurity
  • Google
  • Tools

Post navigation

Previous Post The 5 biggest GDPR fails of 2018
Next Post How to be more meerkat about your email security

Primary Sidebar

Subscribe to our blog and be the first to get updates!

Categories

  • AI
  • BEC
  • BIMI
  • Brand Protection
  • Coronavirus
  • Cybersecurity
  • Deliverability
  • DMARC
  • DORA
  • Email
  • Finance
  • Labs
  • News
  • OnINBOX
  • Partner Program
  • Red Sift Tools
  • Work at Red Sift
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • October 2016

Copyright © 2023 · Red Sift