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.
188.8.131.52). When using DoT / DoH, any third party (e. g. my ISP) does not know that I want to access
Now my browser will do the TCP handshake and TLS handshake with
184.108.40.206 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
220.127.116.11? 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?