Revisiting ICANN’s Role in Content Blocking Requests

As the central coordinator of the global Domain Name System, the Internet Corporation for Assigned Names and Numbers (ICANN) has long maintained a limited mandate focused on the stable and secure operation of internet unique identifiers—specifically domain names, IP addresses, and protocol parameters. ICANN’s technical coordination mission was deliberately scoped to exclude the regulation of content hosted on websites. However, in recent years, the global rise in disinformation, hate speech, copyright infringement, and illicit online activity has led to increasing pressure on DNS actors to engage in content regulation, often through domain-level interventions. These developments have renewed debate over ICANN’s role in content blocking requests and whether the current boundaries of its mission are tenable in an environment where the DNS is being used, increasingly, as a tool for content-based enforcement.

ICANN’s foundational documents, including its Bylaws and its Affirmation of Commitments with the U.S. government, explicitly emphasize that ICANN is not a content regulator. Its remit is to ensure that the internet’s naming and addressing systems function in a stable, secure, and resilient manner. Content governance—such as whether a website should or should not host particular material—is understood to lie outside ICANN’s jurisdiction and is typically left to national legal systems, hosting providers, or content delivery platforms. This delineation has enabled ICANN to maintain broad international support for its multistakeholder governance model, avoiding the risk of being perceived as a global censorship body or as an enforcer of politically or culturally specific content norms.

Despite this clarity, content blocking requests aimed at DNS intermediaries, including registries and registrars governed by ICANN contracts, have grown in number and complexity. Government agencies, private litigants, and advocacy organizations have at times approached ICANN with appeals to intervene in cases involving domains alleged to be associated with terrorist content, online piracy, child exploitation, or misinformation. While ICANN typically responds that it is not in a position to enforce such requests, critics argue that the organization cannot remain entirely neutral when its contracted parties are increasingly involved in domain-level takedowns that effectively suppress access to content. For example, when a domain name is suspended or deleted due to a complaint, it renders the associated content inaccessible, even though the underlying data may remain on a server somewhere.

The question, then, is not whether ICANN directly regulates content—it does not—but whether its policy framework and contractual relationships enable or limit third parties from using the DNS as a point of enforcement. This is most evident in the Registrar Accreditation Agreement (RAA) and the Registry Agreement (RA), which contain clauses related to the mitigation of abuse. These provisions typically refer to threats to the security and stability of the DNS, such as malware distribution, botnets, phishing, or spam. However, some interpretations have stretched the definition of abuse to include certain types of illegal content, creating ambiguity about whether content-related issues fall within the scope of DNS abuse or are separate matters.

This ambiguity has led to inconsistency in how registrars and registries respond to takedown requests. Some contracted parties choose to act preemptively on content complaints to avoid reputational or legal risk, even in jurisdictions where no court order has been issued. Others require formal legal documentation before acting. ICANN, while reiterating that such decisions are the responsibility of the contracted parties, has not provided detailed guidance on where the line lies between content regulation and DNS abuse mitigation. This has resulted in a fragmented enforcement landscape, where outcomes vary significantly depending on the registrar or registry involved.

The absence of a unified position also creates challenges for transparency and accountability. Many domain suspensions occur without public explanation, and registrants may have limited ability to appeal or seek redress. ICANN’s Contractual Compliance department rarely publishes detailed reports on content-related disputes, which makes it difficult for civil society and academic researchers to assess the extent to which DNS infrastructure is being leveraged for de facto content regulation. This opacity stands in contrast to ICANN’s otherwise strong emphasis on transparency and accountability within its policy-making processes.

International legal developments further complicate ICANN’s position. The European Union’s Digital Services Act, for example, and similar regulatory proposals in other jurisdictions, may require faster and more standardized responses to illegal online content, potentially drawing DNS intermediaries into a more formalized enforcement role. These frameworks often blur the line between content hosts and domain operators, raising questions about intermediary liability and due process. If domain registrars and registries become subject to such laws, ICANN may face pressure to align its contractual requirements accordingly, even if that would entail greater involvement in content governance.

At the same time, there are strong normative and operational arguments for ICANN to resist expanding its role. The DNS was never designed as a mechanism for policing content, and the technical community has repeatedly emphasized the importance of avoiding mission creep. Using the DNS for content takedowns introduces systemic risks, including overblocking, collateral damage, and undermining the universality of the internet. Moreover, it creates incentives for authoritarian governments to push for globalized censorship via DNS control, threatening the open nature of the internet. These risks must be weighed against legitimate efforts to combat harm online.

In response to this tension, some stakeholders have proposed that ICANN facilitate greater community discussion on the boundaries of DNS abuse, content moderation, and the role of contracted parties. This could include clearer definitions within ICANN’s contracts, better reporting requirements for domain takedowns, and the development of principles that registrars and registries can follow when handling content-based requests. Such initiatives would allow ICANN to maintain its neutrality while still promoting due process, consistency, and accountability across its ecosystem.

Ultimately, the question of ICANN’s role in content blocking requests is not about whether it should become a global internet censor. Rather, it is about how ICANN can uphold its core values—stability, openness, accountability, and multistakeholder governance—in a world where DNS intermediaries are increasingly pressured to act on matters of speech, legality, and societal harm. Navigating this challenge requires a delicate balance: resisting encroachment on ICANN’s limited technical mission while fostering a governance environment in which policy is shaped transparently, inclusively, and with an understanding of the broader implications for human rights and the global internet. As content blocking pressures continue to mount, ICANN’s response will be critical in determining whether the DNS remains a neutral infrastructure or becomes a contested front in the digital regulation landscape.

As the central coordinator of the global Domain Name System, the Internet Corporation for Assigned Names and Numbers (ICANN) has long maintained a limited mandate focused on the stable and secure operation of internet unique identifiers—specifically domain names, IP addresses, and protocol parameters. ICANN’s technical coordination mission was deliberately scoped to exclude the regulation of…