How HTTPS made HTTP a thing of the past

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

PUBLISHED BY

Deepak Prabhakara

26 Jul. 2018

SHARE ARTICLE:

Categories

Recent Posts

VIEW ALL
News

Microsoft announces new email requirements for bulk senders

Red Sift

Microsoft has officially announced new authentication requirements for bulk email senders, aligning with the policies rolled out in 2024 by Google and Yahoo. These changes aim to improve email security and deliverability for Outlook.com users, covering domains like outlook.com, hotmail.com, and live.com. The update marks a significant shift as Microsoft moves to require SPF,…

Read more
DMARC

From concept to market leader: Reflecting on the development of Red Sift…

Rahul Powar

Following Red Sift OnDMARC being featured in 18 reports in G2’s Spring 2025 Report, CEO Rahul Powar shares his thoughts on the innovation behind the product—and what’s driving its continued momentum in the fight against phishing and Business Email Compromise (BEC). When I founded Red Sift, my goal was to make proactive cybersecurity accessible…

Read more
DMARC

Keep your Microsoft Online Email Routing Address secure with Red Sift OnDMARC

Faisal Misle

Every Microsoft 365 tenant includes a default domain in the format tenantname.onmicrosoft.com. This is known as the Microsoft Online Email Routing Address (MOERA). What many don’t realize is that attackers have started using these domains to impersonate organizations in phishing attacks. If left unmonitored, MOERA domains can become a blind spot in your email…

Read more
News

Red Sift OnDMARC ranked #1 in EMEA and Europe for DMARC in…

Francesca Rünger-Field

G2’s Spring 2025 Report is here, and we’ve got some exciting news to share! Red Sift OnDMARC has been named the #1-rated DMARC solution in both EMEA and Europe, and that’s just the start. We also took the #1 spot in the Mid-Market Results Index and Mid-Market Usability Index, and were featured in 18…

Read more