cross-posted from: https://lemmy.ml/post/14100831

"No, seriously. All those things Google couldn’t find anymore? Top of the search pile. Queries that generated pages of spam in Google results? Fucking pristine on Kagi – the right answers, over and ov

  • Bogasse@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    7 months ago

    And it’s not only about user data, it would also expose the website to content spoofing in public wifi, which would for example allow the attacker to inject fishing content in the website.

    SSL encrypts the data you’re sending but it also ensures that you’re communicating only with who you think you are. Without SSL you can’t be confident about any of that.

    • pixxelkick@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      7 months ago

      If a website has literally no login system, there’s nothing to phish.

      There is honestly no reason to use SSL on a static website that has no login system and just displays some content.

      IE a static blog or etc, where the only content on the website is just “look at this stuff, okay thank you!”