0

In the interest of security, is it safe to use HTTP (and not HTTPS) on a website where no sensitive information is being transmitted?

On a website that is purely informational, for example, and doesn’t even have the option to make an account.

So the only data being transmitted is publicly available to any attacker waiting to MITM.

The only concern I can think of is data tampering, which could be an issue, but even then I am still not too sure.

May I also add, my question also entails whether this is a responsible choice for the website owner, too, in this circumstance?

2
  • 2
    It might also impact usability, as some browsers enforce using TLS, and will throw up a warning if the website doesn't support it.
    – Dijkgraaf
    Commented Aug 29 at 23:17
  • @Dijkgraaf thanks, even though this doesn't actually affect the security of said site, this is a very good point that I hadn't considered. Commented Aug 29 at 23:41

1 Answer 1

5

No, this is not secure.

First off, which information counts as sensitive is highly subjective. For example, the news sites I'm visiting are entirely public, but that doesn't mean I'm fine with sharing the exact articles I'm reading, let alone allow somebody to observe my behavior on the site over a long period of time and create a profile of my interests. So even information which doesn't seem sensitive at all can at least lead to privacy issues.

Besides that, HTTP allows an attacker to inject arbitrary malicious or illegal content into the responses. There are lots of scenarios where this would cause serious harm:

  • If users trust the site (even when they shouldn't), an attacker could try to perform phishing, e.g., set up a fake paywall to get payment data, or collect passwords through a fake registration feature.
  • Attackers could spread malware by offering a download or even exploiting browser vulnerabilities that don't require any user interaction.
  • If illegal content is injected, this will be a huge problem both for the website owner and its users. The owner may have a hard time proving that this wasn't actually their content, and the user will have to explain how they've ended up accessing the content and possibly storing it in the browser cache.

So HTTPS really is a must for the security of all parties.

4
  • Thanks, this is what I had expected. I still think that it's funny that modern browsers even allow users to visit sites with unencrypted connections, seeing as most people don't know the risk. And not to mention that browsers only warn users about not to enter information such as credit card details, and don't even bother warning users about the several points you've listed above. Commented Aug 29 at 23:48
  • 3
    @security_paranoid: At least Firefox and Chrome now always use HTTPS by default, and if only HTTP is available, they put up an entire warning page that must be actively closed to proceed. With HSTS (preloading or not), it's not even possible to get past the warning. Browser vendors cannot do much more without breaking parts of the WWW.
    – Ja1024
    Commented Aug 30 at 0:02
  • Yeah, that’s true. In fact, on another level entirely, it may be that in the near future, HTTP without the S might be illegal… Commented Aug 30 at 0:49
  • Times change quickly with cybersec. Commented Aug 30 at 0:49

Not the answer you're looking for? Browse other questions tagged .