• booly
    link
    fedilink
    arrow-up
    14
    ·
    edit-2
    8 months ago

    The typical default configuration has the ISP providing DNS services (and even if you use an external DNS provider, the default configuration there is that the DNS traffic itself isn’t encrypted from the ISP’s ability to analyze).

    So even if you visit a site that is hosted on some big service, where the IP address might not reveal what you’re looking at (like visiting a site hosted or cached by Cloudflare or AWS), the DNS lookup might at least reveal the domain you’re visiting.

    Still, the domain itself doesn’t reveal the URL that follows the domain.

    So if you do a Google search for “weird sexual fetishes,” that might cause you to visit the URL:

    https://www.google.com/search?q=weird+sexual+fetishes
    

    Your ISP can see that you visited the www.google.com domain, but can’t see what search you actually performed.

    There are different tricks and tips for keeping certain things private from certain observers, so splitting up the actual ISP from the DNS resolver from the website itself might be helpful and scattering pieces of information, but some of those pieces of information will inevitably have to be shared with someone.