Is .io Dying? The Chagos Transfer Explained

How We Got Here: The Chagos Story

The .io extension is, technically, the country-code top-level domain (ccTLD) of the British Indian Ocean Territory (BIOT) — a cluster of 58 remote islands in the Indian Ocean, collectively known as the Chagos Archipelago. The territory has almost no civilian population. The only significant inhabitants are military personnel stationed at the US-UK joint base on Diego Garcia.

The UK acquired the islands from Mauritius in 1965 during the decolonization process, splitting them off to host the Diego Garcia base. In the process, the entire Chagossian population was forcibly expelled between 1967 and 1973. That expulsion has been the subject of decades of human rights litigation.

In 2019, the International Court of Justice ruled the UK had an obligation to return the islands. In October 2024, the UK announced it would do so. The formal agreement was signed on May 22, 2025, with Mauritius assuming sovereignty while the UK retains a 99-year lease on Diego Garcia for the military base.

The Timeline So Far

Why the .io Question Is Complicated

ICANN's rules for ccTLDs are clear on the principle but fuzzy in practice: ccTLDs are assigned to countries or territories listed in the ISO 3166-1 standard. If a country/territory is removed from that standard, ICANN's retirement policy kicks in.

The catch: whether "IO" will actually be removed from ISO 3166-1 is not yet decided. The ISO 3166 Maintenance Agency is a separate body from ICANN, and they make their own call on country codes based on UN standards and member state notifications.

There are three plausible outcomes:

1. "IO" stays in ISO 3166-1 under a new name. Just as .uk remained when "United Kingdom" was still used despite various sovereignty tweaks, the "IO" code could be retained and simply reassigned to represent a different entity — possibly to Mauritius or a hybrid arrangement. This is the softest outcome and what many in the industry quietly expect.
2. "IO" is transitionally reserved. This is ISO's halfway-house — the code isn't officially retired but is flagged as deprecated. That could create commercial uncertainty without triggering immediate retirement.
3. "IO" is removed entirely. This triggers ICANN's community-developed retirement policy: a minimum five-year phaseout during which existing .io domains continue to work, but the TLD is wound down. This is the worst-case scenario for .io holders — but it's not the fastest-moving one.

ICANN's own statement

An ICANN spokesperson confirmed to The Register in late 2024 that "ICANN relies on the ISO 3166-1 standard to make determinations on what is an eligible country-code top-level domain." The spokesperson added: "Should 'IO' no longer be retained as a coding for this territory, it would trigger a 5-year retirement process... during which time registrants may need to migrate to a successor code or an alternate location."

What About the Registry Operator?

The .io registry is technically run by a private UK company called Internet Computer Bureau Ltd (ICB), which has operated the domain since 1997. In recent years, ICB has become essentially a shell company owned by US-based Identity Digital (the company behind dozens of new gTLDs including .info, .pro, .live, and others) through a series of corporate chains.

Identity Digital has a clear commercial interest in keeping .io alive. The registry generates substantial annual revenue, and disruption would hurt their business. The UK government has stated it has no formal relationship with the registry, meaning a change of sovereignty doesn't automatically mean a change of operator.

Historical Precedent: What Happens When Country Codes Die

.su (Soviet Union) — 34 years and counting

The USSR dissolved in 1991. The .su domain is still active in 2026. ICANN has "considered" phasing it out multiple times but hasn't acted. Over the years it's become a haven for cybercrime, but the key takeaway is: ICANN's retirement process, when it happens at all, is measured in decades, not months.

.yu (Yugoslavia) — phased out over ~7 years

Yugoslavia dissolved in the early 1990s. The .yu domain remained active while .rs (Serbia) and .hr (Croatia) came online. .yu was finally retired in 2010 — roughly 17 years after Yugoslavia ceased to exist. The transition caused real operational difficulties for existing registrants, but they had more than a decade of warning.

.tp (East Timor) — retired gracefully

When East Timor became Timor-Leste and was assigned .tl, the .tp domain was retired on a long schedule. No chaos.

.an (Netherlands Antilles) — full retirement

When the Netherlands Antilles dissolved in 2010, the .an TLD was retired over several years. Users migrated to country-specific codes (.cw for Curaçao, .sx for Sint Maarten).

The pattern: retirement happens, but slowly, and with transition support. A total overnight shutdown has never occurred.

What This Means for .io Domain Values

The uncertainty has had a measurable — if modest — effect on the aftermarket. Sedo and other brokers have noted a causal relationship between the .ai surge and the relative cooling of .io premium sales. Buyers who previously might have paid $50,000 for a short brandable .io are now either choosing .ai or waiting to see how the Chagos situation resolves.

But "cooling" is not "collapsing." Six-figure .io sales still happened throughout 2025, and the extension continues to attract serious end-user buyers in tech, crypto, and developer tooling. The market is discounting the risk — not writing the extension off.

What .io Owners Should Actually Do

If your .io is your company's primary domain

• Secure the .com if it's available. Even if you don't migrate yet, owning the .com blocks future trademark issues and gives you a migration path. Many .io startups eventually graduate to .com anyway as they scale.
• Set up passive monitoring. Follow ICANN announcements and ISO 3166 Maintenance Agency updates. If the code status changes, you'll have years to react.
• Don't panic-migrate. A rushed migration has real costs: broken backlinks, SEO hits, email disruption, brand confusion. Migrating on a 5-year horizon is very different from migrating tomorrow.

If you're a .io domain investor

• Premium short .io names still have value — the market has priced in some risk but not existential risk.
• Accept lower asking prices than you would have in 2022. The uncertainty discount is real.
• Consider dual-TLD positioning. If you own Word.io, grabbing Word.ai or Word.com (if available or affordable) gives you optionality.

If you're starting a new project

• A .com is still the safest choice and commands the strongest brand premium.
• A .ai is the momentum play but comes with its own premium pricing ($68–$200/year vs. $9 for .com).
• A .io is viable but carries the geopolitical risk premium. Think hard about your 10-year plan before building on it.

The Bottom Line

.io is not dying tomorrow. It might, eventually, be retired — but the most likely outcomes are either a quiet continuation under slightly revised management, or a very slow multi-year phaseout with plenty of warning.

The biggest mistake .io owners could make right now is either panicking and migrating too fast (destroying SEO equity and confusing customers for a risk that may never materialize), or ignoring the situation entirely (getting caught flat-footed if the ISO decision goes the wrong way).

The right move is somewhere in the middle: secure a .com backup, monitor ICANN and ISO announcements, don't let your .io become mission-critical without a contingency plan, and adjust your investment portfolio's TLD mix to reflect the new risk profile.

And if you're worried about a specific .io in your portfolio — run it through the estimator. Knowing its market value in today's environment is the first step to deciding what to do with it.