[260830] Firefox, the Privacy Protector, Called an "Internet Villain"?

Mozilla's 2019 decision to enable DNS over HTTPS (DoH) by default in Firefox led the UK Internet Service Providers Association (ISPA) to name it 'Internet Villain' of the year, highlighting how security upgrades like DoH, cloud computing, and AI agents redefine trust boundaries rather than eliminate risk. DoH encrypts DNS queries, shifting trust from ISPs to specialized DNS providers such as Cloudflare, Google, and Quad9, which still see the domain names to resolve them.

Firefox, the Privacy Protector, Called an "Internet Villain"? TLDR DoH encrypts DNS queries to shield browsing logs from ISPs, showing that security upgrades redefine trust boundaries rather than eliminate risk—a pattern also seen in cloud computing, open source, and AI Agents. In 2019, Mozilla was named "Internet Villain" of the year by the UK Internet Service Providers Association ISPA . The reason was simple: it intended to enable DNS over HTTPS DoH by default in Firefox. It sounds counterintuitive. Mozilla aimed to prevent ISPs from seeing what users visit, but ISPs argued this stripped away their DNS control and disrupted network management and filtering capabilities. A technology meant to protect privacy faced fierce pushback from service providers. DNS has never been just a technical protocol; it determines who sees user browsing history and who controls internet data. Resolving Problems and Shifting Trust DNS is foundational to the internet. Visiting a site like github.com requires querying DNS to resolve the domain to an IP address. The traditional query flow: User ↓ ISP DNS ↓ Website Standard DNS queries are unencrypted, exposing requested domains to ISPs. While HTTPS secures web content, unencrypted DNS leaks the destination. DoH encapsulates DNS queries inside HTTPS connections: User ↓ HTTPS Encrypted DNS Provider ↓ Website Intermediate network nodes can no longer inspect DNS queries. Chrome, Edge, and Safari eventually adopted DoH, and Firefox enabled it by default in multiple regions. What sparked controversy in 2019 became standard web infrastructure. Redefining Visibility over Absolute Anonymity DoH encrypts DNS traffic, but it does not make queries invisible to everyone. Resolvers like Cloudflare 1.1.1.1 , Google 8.8.8.8 , or Quad9 9.9.9.9 still need to view the domain name to return the correct IP address. DoH shifts trust rather than eliminating it. Instead of relying on ISPs for DNS resolution, queries are routed to specialized DNS providers. This addresses a real issue: ISPs should not inherently possess all user DNS records. Security upgrades reallocate trust rather than remove the need for it. Industry-Wide Pattern Cloud computing follows a similar pattern. Companies transitioned from on-premise servers to cloud infrastructure, trading local hardware control for elasticity and placing operational trust in cloud providers. Open-source software works the same way. Development teams speed up delivery by relying on third-party libraries, shifting trust to upstream maintainers, code repositories, and release pipelines. Password managers behave identically. They reduce weak password risks, but users must trust a single centralized vault. Security upgrades consistently redefine trust boundaries rather than eliminating risk. Trust in the AI Agent Era Past security models focused on human interaction with software. AI Agents shift this dynamic by acting on behalf of users. An Agent invokes APIs, accesses files and databases, executes business logic, and completes multi-step workflows autonomously. Underlying trust models directly shape Agent actions. DNS, authentication, API permissions, and third-party tools serve as steps in an Agent's execution chain. Evaluating Agents requires examining connected systems, allocated permissions, automated actions, and required human approvals alongside model intelligence. Redefining Trust Boundaries The 2019 debate questioned whether ISPs should access user DNS queries. The current consensus is that single network gateways should not monitor overall browsing activity by default. As trust shifts from ISPs to DNS providers and automated systems, permission scopes and data concentration limits must be continuously evaluated. From DoH to cloud computing and AI Agents, technological evolution continuously redefines trust boundaries. Please indicate the source and link of this article when reprinting. Help us make these docs great All X-CMD docs are generated from command help and multiple data sources. See something that's wrong or unclear? Feel free to let us know through any of these ways~