Case Study Preview Why dotWeb Has Taken So Long and What That Means for Future Strings
- by Staff
The saga of .web stands as perhaps the most emblematic case of the complexities, delays, and contentious politics that can surround the launch of a new generic top-level domain (gTLD). Despite being one of the most anticipated strings during the 2012 application round—offering the promise of a strong, generic namespace with wide appeal—.web has yet to be delegated over a decade later. This delay is not just a bureaucratic anomaly; it is a revealing case study in the intersection of policy ambiguity, legal maneuvering, and institutional inertia. Understanding the specific factors that have stalled .web offers invaluable insights into how similar issues may arise in future application rounds, and what changes may be necessary to prevent such stagnation from recurring.
The root of the .web delay lies in a combination of contention, objections, and post-auction complications. In 2012, seven different entities applied for .web, making it one of the most heavily contested strings. Among these applicants was Nu Dot Co, a relatively unknown player backed financially by Verisign, the registry operator for .com. While at first glance this kind of financial backing was not prohibited by ICANN rules, it quickly became controversial. Competing applicants raised concerns that Verisign’s funding of Nu Dot Co violated the spirit—if not the letter—of ICANN’s new gTLD program, particularly the rules around maintaining a fair and open competition. The situation escalated when Nu Dot Co declined to engage in a private auction, pushing the contention set into an ICANN-managed public auction. When the public auction took place in 2016, Nu Dot Co won with a staggering bid of $135 million, the highest ever for a gTLD.
Rather than resolving the issue, this outcome only intensified scrutiny. Rival applicants filed complaints and initiated accountability mechanisms, questioning whether Verisign’s involvement was properly disclosed and whether ICANN had fulfilled its obligation to assess the fairness of the process. These complaints triggered a series of Independent Review Processes (IRPs), accountability investigations, and even litigation. The result was an effective freeze on the delegation of .web, with ICANN forced into a position of administrative limbo, unable to move forward due to ongoing legal and procedural uncertainties. This stasis persisted even as technical evaluations were completed and the applicant of record, Nu Dot Co, continued to insist on its right to operate the string.
The .web dispute has underscored the fragility of ICANN’s conflict resolution architecture. Although mechanisms like the IRP and reconsideration requests were meant to safeguard transparency and fairness, in practice they have proven vulnerable to exploitation. The protracted legal wrangling over .web shows how well-resourced parties can use these mechanisms not just to seek redress but to stall the process indefinitely. This raises serious questions about whether the existing checks and balances are fit for purpose, particularly when multiple applicants with conflicting commercial interests converge on high-value strings. For ICANN, the challenge lies in balancing procedural fairness with operational efficiency—something that has yet to be adequately resolved.
The .web case also highlights the ambiguous nature of third-party backing and vertical integration in the gTLD space. While financial partnerships and registry affiliations are inevitable, the .web experience revealed the discomfort many stakeholders feel when dominant incumbents seek to expand their control through indirect means. Verisign’s funding of Nu Dot Co was technically permissible, yet it sparked concerns about market consolidation and the circumvention of policy intent. ICANN’s decision not to intervene more forcefully in this situation has led to a broader erosion of trust, particularly among smaller applicants and civil society groups who view the outcome as evidence that financial power can undermine procedural integrity. This perception could dampen enthusiasm for future application rounds unless clearer guidelines and stronger enforcement mechanisms are established.
The implications for future gTLD applicants are sobering. The .web stalemate illustrates that even a technically sound application, backed by substantial resources and a winning bid, can languish indefinitely if the surrounding process lacks clarity and decisiveness. Future applicants, especially those targeting high-profile or contested strings, must now contend with the possibility that their efforts could be derailed by years of procedural uncertainty. This could lead to a chilling effect, where only the most risk-tolerant and well-capitalized entities pursue competitive strings, further entrenching inequality in the domain name ecosystem.
ICANN’s handling of .web will likely influence several key changes in the next round of gTLDs. Among these are anticipated revisions to the auction process, including greater transparency about funding sources, tighter controls around affiliation disclosures, and perhaps the establishment of pre-qualification audits to screen applicants for conflicts of interest before contention resolution begins. Additionally, there is growing support for rethinking the role of public auctions themselves, with some stakeholders advocating for capped bids or non-monetary evaluation metrics that favor community impact and innovation over sheer financial strength. Without such reforms, the .web precedent could repeat itself, potentially multiplying the number of unresolved gTLDs and further complicating ICANN’s governance model.
Ultimately, the .web story is not just about a single domain—it is a warning about systemic weaknesses that can paralyze even the most promising initiatives. As ICANN prepares for future rounds, it must reckon with the lessons of this unresolved case: that fairness is not guaranteed by rules alone, that transparency must be backed by enforcement, and that process integrity requires both clarity and courage. Until these lessons are internalized, .web will remain more than a missing domain—it will remain a symbol of how far the new gTLD program still has to go.
The saga of .web stands as perhaps the most emblematic case of the complexities, delays, and contentious politics that can surround the launch of a new generic top-level domain (gTLD). Despite being one of the most anticipated strings during the 2012 application round—offering the promise of a strong, generic namespace with wide appeal—.web has yet…