How the next round handles closed generics dot cloud 2.0

As the next round of new gTLD applications draws closer, one of the most contentious and unresolved policy questions is the treatment of closed generics—top-level domains that represent generic terms but are proposed for exclusive use by a single entity. The term “closed generic” refers to strings like .book, .cloud, or .shop when registered not for open community or market use, but for internal branding or strategic purposes by a single applicant. This issue, left unsettled during the 2012 round, remains a flashpoint in policy discussions as ICANN prepares the framework for the next gTLD expansion. The treatment of closed generics will not only shape who can apply for what, but also affect the competitive, semantic, and philosophical structure of the DNS itself.

In the 2012 round, ICANN received numerous applications for generic terms by companies seeking to operate them as closed registries. Notable examples included Amazon’s application for .book and Google’s bids for .app and .search. These applications triggered widespread debate, as stakeholders from governments, civil society, and competing businesses argued that allowing exclusive control over widely used dictionary terms could have anti-competitive consequences and stifle innovation. Although some applications like .cloud ultimately proceeded in an open registration model under a commercial operator, others were withdrawn or delayed indefinitely due to pressure from the Governmental Advisory Committee (GAC) and public policy concerns.

In response to this controversy, ICANN imposed a de facto moratorium on closed generics, without formally codifying a permanent rule. The result has been a policy vacuum—closed generics were neither allowed nor explicitly banned in future rounds, leaving applicants and observers in a prolonged state of ambiguity. This vacuum was tolerable in the intervening years, but with a new application window targeted for 2026, a definitive policy is now required.

To address the issue, ICANN initiated a facilitated dialogue in 2023 between representatives of the GAC and the Generic Names Supporting Organization (GNSO), the two groups most invested in the outcome. This “closed generics dialogue” was intended to develop a mutually acceptable framework for how and whether closed generics could be allowed in the next round. The conversations were highly detailed, exploring models of limited public interest commitments, hybrid access models, and requirements for public benefit usage. Participants debated whether an applicant for a closed generic should be required to demonstrate how the TLD would serve the global public interest, particularly in domains that represent categories of commerce, education, or infrastructure.

One of the key proposals discussed was the creation of a Public Interest Application (PIA) model, where a prospective closed generic applicant would submit a detailed plan explaining the intended use of the TLD and how it would benefit end users. This model would involve a higher threshold of scrutiny during the application review, including potential public comment periods, independent evaluations, and mandatory commitments enforceable by ICANN compliance mechanisms. A closed .cloud, for example, would need to articulate how its restricted use—say by a single cloud services provider—would not harm the broader internet community’s access to semantic and economic opportunities around the “cloud” keyword.

The challenge lies in balancing legitimate business interests with broader public policy goals. For companies, the incentive to control a generic TLD is strong. It offers branding advantages, SEO potential, and market defensibility. A company that controls .search or .shop could consolidate digital operations in a way that enhances user trust and streamlines services. But from a policy standpoint, allowing exclusive control over language that has universal utility raises red flags. The potential for monopolistic behavior, exclusion of smaller players, and diminished namespace diversity is real. Critics argue that permitting closed generics could effectively privatize linguistic commons, undermining the open principles on which the DNS was founded.

The GAC, in particular, has expressed strong reservations about granting closed generics without robust safeguards. In previous communications, it has insisted that generic terms should be made broadly available or used in a way that serves a clear public benefit. This tension has placed ICANN in a difficult position—balancing governmental concerns, multistakeholder principles, and commercial innovation within a process that is supposed to be fair, neutral, and scalable. The organization has signaled that it may allow closed generics in a limited and controlled manner, provided the policy framework is robust enough to avoid abuse and protect the public interest.

As of early 2025, ICANN is expected to finalize its policy direction on closed generics ahead of the release of the Draft Applicant Guidebook. Any decision taken will have major implications for applicants, particularly those in industries where keyword ownership can yield significant strategic advantage. It is anticipated that a limited path to closed generics will be offered, likely restricted to scenarios where applicants commit to public benefit obligations, accept third-party audits, and make demonstrable contributions to the user community.

This means that .cloud 2.0—symbolic of the next generation of high-value, generic keyword TLDs—may not be closed in the pure sense of a single-tenant namespace, but could emerge under a model of conditional exclusivity or limited public access. Companies seeking closed generics will likely need to offer more than just business plans; they must provide transparency, stakeholder consultation, and built-in mechanisms for accountability. The path forward will be narrow, regulated, and policy-heavy, but not completely closed off.

The issue of closed generics, then, is more than a technical or commercial question—it is a litmus test for the values ICANN wishes to uphold in the next era of internet governance. How it resolves this issue will set the tone for the balance between innovation and equity in domain name expansion. Whether .cloud becomes a public highway, a private toll road, or something in between will depend not just on who applies, but on how deeply the application embeds openness, trust, and purpose in its design.

As the next round of new gTLD applications draws closer, one of the most contentious and unresolved policy questions is the treatment of closed generics—top-level domains that represent generic terms but are proposed for exclusive use by a single entity. The term “closed generic” refers to strings like .book, .cloud, or .shop when registered not…