7 ms·

Does anyone actually believe that google isn’t hoovering up personal data with its DNS service?

• charleslmunger 9y ago
  https://developers.google.com/speed/public-dns/privacy https://developers.google.com/speed/public-dns/privacy
  • kakarot 9y ago
    we don't keep personally identifiable information We all know what that means. "Anonymous" user IDs that can trivially be traced when combined with another database.
    • hahainternet 9y ago
      Except that if you click the link, that's not what this means.
      • kakarot 9y ago
        I read the policy before quoting it... How can I verify that's not what it means? It's all about subtlety in language. It's just a fact that centralized DNS servers are a bad idea and cannot be trusted, regardless of what it very carefully says on a policy page or whatever speed gains you could get. It's a broken system and I have no reason to trust Google with even more data.
• jeremy7600 9y ago
  All this tasty data: Request domain name, e.g. www.google.com Request type, e.g. A (which stands for IPv4 record), AAAA (IPv6 record), NS, MX, TXT, etc. Transport protocol on which the request arrived, i.e. TCP, UDP, or HTTPS Client's AS (autonomous system or ISP), e.g. AS15169 User's geolocation information: i.e. geocode, region ID, city ID, and metro code Response code sent, e.g. SUCCESS, SERVFAIL, NXDOMAIN, etc. Whether the request hit our frontend cache Whether the request hit a cache elsewhere in the system (but not in the frontend) Absolute arrival time in seconds Total time taken to process the request end-to-end, in seconds Name of the Google machine that processed this request, e.g. machine101 Google target IP to which this request was addressed, e.g. one of our anycast IP addresses (no relation to the user's IP)
  • monochromatic 9y ago
    And my IP address, linking my browsing to my google account and my identity.