Say (an encrypted) hello to a more private internet. | The Mozilla Blog - eviltoast
  • venusenvy47@reddthat.com
    link
    fedilink
    arrow-up
    7
    ·
    1 year ago

    If I understand correctly, someone other than your ISP could see the name of the website, since it isn’t encrypted. I think it would bounce through several servers that could possibly read the data.

    • SquigglyEmpire@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      This makes it so that your ISP doesn’t see the actual name of the server/site you’re communicating with, only the IP address. Without Encrypted Hello they’re able to see both.

        • SquigglyEmpire@lemmy.world
          link
          fedilink
          arrow-up
          5
          ·
          edit-2
          1 year ago

          In many cases you can, but there’s never a guarantee that a given IP address will have reverse DNS records configured for resolve it into. On top of that, if it’s a major site it’s likely hosted behind a content delivery network that may a share a single IP address across thousands or even millions of completely unrelated servers. Cloudflare does some pretty interesting stuff with that approach: https://blog.cloudflare.com/cloudflare-servers-dont-own-ips-anymore/ edit: bad at typing

    • jet@hackertalks.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      Cloudflare fronts much of the internet, so all your ISP would see is that you connect to cloudflare, not which site you actually connect to.

      In fact this was a big reason cloudflare and Amazon were angry with the signal foundation, for using domain front running, using the same trick in fascist countries to still be able to talk to signal servers