Relationship between DoT / DoH and HTTPS



  • I'm trying to understand the different roles that DoT / DoH and HTTPS are playing when it comes to protecting sensitive data in the internet. I spend the day reading a lot of stuff about DoT, HTTPS, TCP and IP.

    But there is one thing that doesn't become clear to me: say I want to surf to https://www.myForbiddenSite.org and download an image from there. At first, my device has to retrieve the IP address for myForbiddenSite.org (e. g. 1.2.3.4). When using DoT / DoH, any third party (e. g. my ISP) does not know that I want to access myForbiddenSite.org.

    Now my browser will do the TCP handshake and TLS handshake with 1.2.3.4 and I can start communicating with the website via HTTPS. The image I want to download will be encrypted.

    But isn't my public IP address part of all IP packages that are send across the wire? So basically every node between my router and myForbiddenSite.org sees my public IP address and 1.2.3.4? If this is the case, are there any projects that address that issue? And if not, why? Is it related to the fact the resolving the IP address for a DNS name is easy, but not vice versa?



  • If you want to hide your browsing activity from your ISP (and every other router that your traffic passes through), then you might want to consider using a VPN. This will prevent your ISP from knowing which sites your are connecting to, as the ISP only sees that you are connecting to the VPN. However the VPN will know which sites your are connecting to. Some VPN's claim that they do not log this information, but this is difficult to verify.

    As another option, you might want to consider using TOR. With TOR, your traffic is routed through several nodes, so that no single node is privy to both your source address and your destination address. See https://2019.www.torproject.org/about/overview.html.en for more info on how TOR works.



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2