What do resellers know when using HTTPS?

Question

Computer networks

It is clear that it is known that a person from one IP connects to a site on another IP. But I go to this site on a certain page. The HTML I get is encrypted, right? Do you know the path to this page? That is, can I understand only that I went to Google, or can I determine the search query along the path to the page? And is the subdomain known?

Answer 1

It depends (Depending on :) )
In standard mode (you are at home, go to a regular site without proxy, provider without quirks, state without "protection from inappropriate content") you can see only IP from where, IP to and initial path. Everything that happens after the connection is established is not visible to a third party.
But then the subtleties begin.
In corporate networks, there is often a corporate certificate and a proxy with bumping, which allows the proxy itself to see everything that passes through the connection - quite a classic such MitM.
The provider on behalf of the state, or the state itself on its own behalf, can easily demand a certain "state certificate" in order to have the same opportunity. Yes, I have not heard about this in the Russian Federation yet, but in the Republic of Kazakhstan the system has already been tested (then turned off). That is, there is a technical possibility.

Answer 2

The fact of going somewhere in Google can be determined, the content of the request is not .

Answer 3

It is not for nothing that the HTTPS protocol has the ending S - Secured, i.e. encrypted. Because the POST method transmits data in headers, and the headers are encrypted, then the provider does not see anything inside the HTTPS request, except for the domain, page name and a bunch of encrypted data.

Answer 4

The domain may be known, but the path is no longer.

Answer 5

HTTPS only encrypts the content of the request, i.e. protects against weak MITM attacks. Everything else is not protected.
Ps
To initiate a criminal case, it is enough just to establish the fact of accessing the resource, i.e. HTTPS won't help.