Afric TLD That Never Got ICANN Approval

The story of the proposed .afric top-level domain is one of ambition, geopolitics, legal entanglements, and ultimately, failure to launch. Distinct from the now-delegated and functioning .africa domain, the .afric proposal represents a cautionary tale of how the domain name system’s expansion—while intended to be inclusive and empowering—can become mired in conflicts over governance, control, and legitimacy. Despite being envisioned as a digital namespace for pan-African identity and enterprise, .afric never achieved the backing of the Internet Corporation for Assigned Names and Numbers (ICANN). It exists now only as a footnote in the sprawling history of gTLD hopefuls, a reminder of the complex dynamics at play when naming rights intersect with continental aspirations.

The origins of .afric trace back to the early 2010s when ICANN opened the door to a massive expansion of the domain name space, inviting organizations to apply for new generic top-level domains. It was an era of optimism, innovation, and speculation. Amidst the flurry of proposals for everything from .app to .ninja, there was a special significance attached to geographic and cultural identifiers. The idea of a domain dedicated to Africa was met with widespread interest, and multiple groups stepped forward with competing visions for what that domain should be—and who should control it.

One application came from DotConnectAfrica Trust (DCA), a Kenya-based organization founded by Sophia Bekele. DCA applied for the .africa TLD, styling itself as a pan-African initiative representing the continent’s digital future. But ICANN’s evaluation process introduced friction early on. The African Union Commission (AUC), acting as the de facto political body for African governments, did not endorse DCA’s bid. Instead, it backed a competing application led by a South African-based non-profit, ZA Central Registry (ZACR). In the political calculus of ICANN’s Geographic Names Panel, the AUC’s support carried weight—particularly because geographic TLDs were expected to have local governmental backing.

Amid this dispute, DotConnectAfrica introduced a parallel idea: .afric. Slightly different in spelling, but unmistakably designed to evoke the same pan-African identity, .afric was not a mere fallback—it was a legal and symbolic maneuver. DCA’s argument was that .afric represented an alternate digital identity for Africa, one unbound by what they perceived as the political biases and procedural failings of the .africa approval process. It was a linguistic workaround, a protest, and a bid for legitimacy all at once.

However, ICANN rejected the .afric application outright. One of the central reasons was confusion with .africa, which had already been delegated to ZACR. ICANN’s string similarity review process is designed to prevent the creation of visually or phonetically confusing domains that might mislead users or dilute the value of existing TLDs. Despite the one-letter difference, .afric was judged to be too close to .africa, particularly given their nearly identical semantic scope. ICANN’s decision effectively killed the proposal before it could gain serious traction.

What followed was a long and bitter legal battle between DCA and ICANN over the .africa decision. DCA alleged procedural unfairness, conflicts of interest, and breaches of due process. It filed for Independent Review Process (IRP) arbitration, and in 2015, a panel ruled in DCA’s favor on certain procedural counts. This temporarily delayed the delegation of .africa to ZACR but did not ultimately reverse it. After further rounds of litigation and appeals, .africa was officially delegated in 2017, and ZACR began managing the domain.

By contrast, .afric never resurfaced with serious institutional support. It had no regional endorsements, no governmental backers, and no standing within the ICANN community post-rejection. There was no groundswell of demand or civil society push to revive the application. Its primary advocate, DCA, continued to dispute ICANN’s treatment in broader terms but did not appear to submit a renewed application for .afric in subsequent rounds. The term lingered in public records as a rejected string, a domain that might have been—if not for politics, timing, and the delicate balances ICANN must strike when adjudicating global interests.

In hindsight, the .afric saga reflects a recurring tension in global internet governance: who has the right to define and claim continental identity in the domain name system? Should it be private entrepreneurs, public commissions, or grassroots organizations? In the case of .afric, the answer was none of the above. It remained an unrealized idea—a name too close to another, with too much baggage to move forward. The dream of multiple African-themed gTLDs serving different constituencies remains technically possible, but practically remote. The digital identity of a continent, it turns out, cannot easily be separated by a single letter.

The legacy of .afric now sits in shadow. While .africa domains are slowly gaining adoption among African brands, NGOs, and regional initiatives, .afric remains a case study in failed digital nation-building. It’s a reminder that in the highly governed, quasi-political world of internet naming, even a well-intentioned domain can be derailed not by technology, but by trust, endorsement, and the politics of legitimacy.

The story of the proposed .afric top-level domain is one of ambition, geopolitics, legal entanglements, and ultimately, failure to launch. Distinct from the now-delegated and functioning .africa domain, the .afric proposal represents a cautionary tale of how the domain name system’s expansion—while intended to be inclusive and empowering—can become mired in conflicts over governance, control,…