Reserved String Conflicts in Subsequent gTLD Application Rounds

As the domain name industry prepares for the second round of new gTLD applications, one of the most complex and often controversial policy challenges to re-emerge is the issue of reserved string conflicts. Reserved strings are domain name labels that are restricted from delegation or registration due to policy decisions, technical concerns, or geopolitical sensitivities. During the 2012 round, ICANN established a range of reserved strings including country and territory names, intergovernmental organization identifiers, and terms deemed problematic for stability, security, or public policy reasons. However, as the second round approaches with new players, evolved branding strategies, and a broader global digital footprint, the collision between previously reserved strings and future applicants’ naming ambitions is shaping up to be a central point of contention.

The tension arises when prospective applicants seek to apply for strings that were previously placed on ICANN’s reserved or blocked list—either at the top level (TLD) or in second-level domain reservations maintained by registry operators. These strings may now have significant commercial, cultural, or technological relevance, leading applicants to argue for their release or reclassification. For example, terms like “mail,” “home,” “appstore,” or “healthcare” may have been previously withheld for reasons of confusion, brand protection, or policy ambiguity, yet today they hold immense potential in the modern digital economy and have gained support from stakeholder communities or corporate sponsors who are ready to build responsible, global-use platforms.

One of the most prominent categories of reserved string conflict involves geographic and geopolitical names. ICANN’s Applicant Guidebook for the 2012 round imposed strict limitations on applications for names matching country or territory names listed in ISO 3166-1, as well as certain combinations involving capital cities and sub-national regions. These limitations were introduced in part due to advice from the Governmental Advisory Committee (GAC), which expressed concern about sovereignty, cultural integrity, and the potential for misuse. However, some geographic terms that were previously caught in the net of overcautious reservation—such as region names that double as generic commercial terms (e.g., “amazon,” “patagonia,” “tuscany”)—are now being reconsidered in light of evolving market demand and precedent-setting legal outcomes.

Another flashpoint concerns generic strings that are perceived to have industry-wide applicability but were reserved due to perceived confusion with existing registry services or potential anti-competitive behavior. In 2012, several generic terms like “search,” “cloud,” “book,” and “music” were the subject of contention, with some being delayed, contested, or withdrawn entirely due to objections from other stakeholders or ICANN’s own review mechanisms. As the second round unfolds, there is growing debate over whether these strings should remain reserved, be re-opened to competition, or be assigned under new governance models that reflect public interest commitments.

Complicating matters further is the treatment of closed generics—a model where a single entity applies for a string representing a broad category but intends to operate it in a closed fashion, limiting access to affiliated or controlled parties. This approach was temporarily curtailed in the first round following a wave of community concern and policy indecision. Many strings that might have been operated as closed generics were effectively reserved as a result. With a new policy framework under discussion by the Generic Names Supporting Organization (GNSO), questions have re-surfaced: should previously reserved or disputed closed generics like “bank,” “news,” or “store” be reopened to applications? If so, under what conditions or contractual safeguards should they be delegated to ensure fairness and competition?

Technical reservations are also part of the conflict landscape. Certain strings have been held back due to potential root zone stability risks, name collision concerns, or conflicts with established protocols. Terms like “home,” “corp,” and “mail” were flagged in the Name Collision Analysis Project (NCAP) and subsequently deferred. However, advances in DNS risk mitigation, coupled with refined testing methodologies, have led some stakeholders to argue that the original reservations may now be overly conservative. Registry service providers and applicants eager to utilize these terms contend that technical conflicts can be mitigated through well-defined safeguards, opening the door for previously blocked strings to enter the namespace under controlled deployment models.

An additional layer of complexity comes from registry-reserved second-level domains. Many operators of existing gTLDs reserved high-value terms at launch, either for future monetization or to avoid legal conflict. These names—often involving single-character labels, brandable generics, or common industry terms—are not accessible through traditional registration channels. As new applicants propose similar or overlapping strings in the next round, registries may challenge these applications on the grounds of confusion, competition, or existing contractual rights. This is especially likely when new TLD applicants propose strings that replicate a valuable keyword already controlled as a reserved second-level name in a popular extension like .app, .cloud, or .store.

Resolution mechanisms for these conflicts remain a hotly debated topic. Some stakeholders advocate for a centralized arbitration process overseen by ICANN, allowing for transparent evaluation of contested string claims based on a matrix of policy, technical, and market factors. Others call for expanded use of objection processes—such as the Legal Rights Objection or Community Objection models—allowing affected parties to raise challenges on specific grounds. A third approach proposes a shift toward cooperative delegation models, where competing applicants for a contested or formerly reserved string are encouraged to enter into joint ventures, public benefit arrangements, or shared governance structures that allow multiple stakeholders to participate in the operation of the TLD.

As ICANN’s SubPro (Subsequent Procedures) PDP team finalizes its recommendations and the organization prepares for the next round of applications, clear guidance on how to handle legacy reserved strings will be essential. Without updated frameworks, the second round risks being bogged down by litigation, objection overload, and policymaking paralysis. Conversely, thoughtful re-evaluation and modernized criteria could unlock a wealth of meaningful, high-value domains that were previously locked away—not due to actual risk or harm, but due to incomplete frameworks and risk-averse defaults.

Ultimately, the resolution of reserved string conflicts in subsequent gTLD rounds will be a litmus test for the domain industry’s ability to evolve. It will test the balance between rights protection and innovation, stability and openness, exclusivity and public good. The goal should not simply be to protect prior decisions but to refine them in light of new data, improved systems, and the growing maturity of a multi-stakeholder ecosystem. If done correctly, resolving these conflicts will lead not to fragmentation, but to a more vibrant, inclusive, and semantically rich internet namespace.

As the domain name industry prepares for the second round of new gTLD applications, one of the most complex and often controversial policy challenges to re-emerge is the issue of reserved string conflicts. Reserved strings are domain name labels that are restricted from delegation or registration due to policy decisions, technical concerns, or geopolitical sensitivities.…