Name Collision Blocks .home and .corp Dreams Deferred

When ICANN launched its ambitious new gTLD program in 2012, the internet industry braced itself for a revolution. Hundreds of new domain extensions were to be introduced, ranging from city names and brand-specific TLDs to broad generic terms that could reshape how people and businesses thought about their online identities. Amid the flood of applications, some of the most hotly contested and seemingly promising strings were short, universal words with deep resonance in both personal and corporate contexts: .home and .corp. These names sparked considerable excitement because they seemed destined for widespread adoption. .home evoked the most basic and universal concept of personal presence, perfectly suited for everything from family websites to smart-home services. .corp, meanwhile, was the natural shorthand for corporations, a sleek, professional marker that could have rivaled .biz or even .com in the business space. Yet despite their potential, neither .home nor .corp ever made it to public availability. Instead, they became victims of a phenomenon known as “name collision,” a technical issue that derailed their launches and turned them into two of the most high-profile disappointments in the history of the domain name system.

The term “name collision” refers to a conflict between domain names intended for use in the public global DNS and domain names that are already being used in private, internal networks. For decades, administrators of corporate intranets, home networks, and software systems had taken the liberty of using unregistered top-level strings for internal purposes. It was common, for example, for companies to configure internal servers with hostnames ending in .corp or for router manufacturers to use .home for local network services. These choices were convenient because they did not require registration and seemed safely disconnected from the public internet. But once ICANN’s new gTLD program sought to bring these strings into global use, the potential for chaos became apparent. If .home or .corp were delegated publicly, queries meant for private networks might suddenly resolve to external servers, leading to security breaches, data leakage, or widespread service disruptions.

When ICANN conducted studies on the potential risks, the results were sobering. Queries for .home and .corp were already among the most common unresolved lookups in the DNS root. This meant that countless devices, networks, and applications were regularly attempting to resolve addresses ending in these strings, assuming they were internal. Delegating them publicly would instantly redirect those queries into the global namespace, creating unpredictable and potentially dangerous consequences. The scale of the issue was far larger than anyone had anticipated. Unlike more obscure or invented TLDs, .home and .corp had been deeply ingrained in the operational fabric of private systems worldwide.

The decision was clear, though painful: ICANN concluded that .home and .corp posed unacceptable levels of risk and therefore could not be delegated. In effect, the dreams of applicants who had spent significant resources vying for these valuable extensions were dashed overnight. Multiple companies had applied for both strings, anticipating that they would become popular and lucrative additions to the domain name system. For .home, potential applications ranged from personal identity sites to real estate platforms, smart-home technology brands, and ISPs seeking user-friendly addresses for customer portals. For .corp, the possibilities were even more expansive. Global enterprises could have used .corp to standardize their digital presence, internal business tools might have migrated to it, and small companies could have adopted it as a mark of professionalism. The marketability of these strings was unquestionable. Yet the technical risks made them untouchable.

The fallout from this decision went beyond the disappointed applicants. It exposed a fundamental tension between the evolution of the internet’s namespace and the messy reality of how networks had grown over the preceding decades. The global DNS had always been intended as the authoritative, public namespace of the internet, but in practice, organizations had treated it as just one layer of a more complex system, appropriating unused TLDs for convenience. This informal practice, never officially sanctioned but rarely discouraged, created a legacy problem that came back to haunt the new gTLD program. .home and .corp were not the only strings affected—others like .mail also faced restrictions—but they were the most prominent examples, both because of their desirability and because of the sheer scale of their usage in private systems.

For ICANN, the controversy highlighted the difficulty of balancing innovation with stability. The new gTLD program had been pitched as a way to unleash creativity, competition, and choice, but the name collision issue showed that not every string could be safely brought into the fold. Critics accused ICANN of failing to anticipate the problem earlier, arguing that the industry had long known about the informal use of strings like .home and .corp in private networks. Others pointed out that the studies conducted after the program’s launch were thorough and responsible, demonstrating that ICANN was unwilling to compromise the stability of the internet for commercial gain. In either case, the result was that two of the most marketable extensions became permanent casualties of technical reality.

The disappointment was especially acute because .home and .corp had seemed like natural fits in a world increasingly conscious of digital identity and brand presence. At the consumer level, .home could have been marketed as the personal domain for families, individuals, or households, offering an accessible alternative to the corporate-heavy .com. In the emerging smart-home ecosystem, where devices from thermostats to voice assistants were becoming networked, .home could have served as a trusted namespace for connected living. For businesses, .corp might have offered a cleaner, more modern alternative to .biz, which had struggled with reputation issues since its own launch. Startups, global corporations, and everything in between might have found appeal in a domain that clearly signaled corporate identity. Instead, those dreams never left the drawing board.

In the years since, the blocked status of .home and .corp has become a reference point in discussions about the limits of namespace expansion. While hundreds of other gTLDs went forward—some successful, many struggling—.home and .corp remained permanently reserved, their potential frozen by the name collision problem. Some within the industry have speculated whether technological solutions could eventually make their delegation possible, perhaps by finding ways to mitigate the risks or gradually wean networks off their reliance on these strings. But the scale of the problem and the depth of their entrenchment make such scenarios unlikely in the near term. For all practical purposes, .home and .corp are lost to the public DNS, their futures indefinitely deferred.

The story of .home and .corp underscores the complexity of internet governance and the often invisible technical dependencies that shape what is possible. To outsiders, the idea that two such obvious and desirable extensions could not be launched seems puzzling. But for those who understand the fragile balance of the domain name system, the decision reflects the hard truth that not every idea, no matter how marketable, can be safely implemented. The disappointment lies not only in the commercial opportunities lost but also in the reminder that the internet’s history is full of informal practices and legacy shortcuts that cast long shadows over its future.

Ultimately, .home and .corp remain cautionary tales within the domain name industry. They illustrate how even the most promising visions can be thwarted by unseen technical realities, and how the interplay between private network practices and public infrastructure can derail innovation. The dreams of a digital “home” for every individual and a streamlined “corp” identity for businesses were compelling, but they collided—literally—with the legacy of how the internet evolved. Instead of becoming shining examples of the new gTLD era, they became symbols of its limits, reminders that some doors remain closed no matter how enticing the opportunities behind them.

When ICANN launched its ambitious new gTLD program in 2012, the internet industry braced itself for a revolution. Hundreds of new domain extensions were to be introduced, ranging from city names and brand-specific TLDs to broad generic terms that could reshape how people and businesses thought about their online identities. Amid the flood of applications,…