Ask HN: What happens to ".io" TLD after UK gives back the Chagos Islands?

Hacker News Discussion ↗

Uncertainty over the future of the popular .io domain is growing after the UK agreed to transfer sovereignty of the Chagos Islands to Mauritius, potentially ending the British Indian Ocean Territory that .io technically represents. Commenters examine ICANN’s ccTLD retirement rules, ISO country-code constraints, and precedents like .su and .yu, weighing whether .io will be phased out, reassigned to Mauritius, or granted some exceptional status. Many note the practical risk for businesses built on a politically fragile country-code domain, alongside ethical concerns about profiting from a namespace tied to a territory created through colonial displacement.

Background and Immediate Question

  • Thread examines what happens to the .io ccTLD if the UK hands sovereignty of the Chagos Islands (British Indian Ocean Territory, BIOT) to Mauritius.
  • Linked news focuses on Diego Garcia and sovereignty; .io is not addressed there.

How ccTLDs Are Supposed to Work

  • Two‑letter TLDs are reserved for country codes tied to ISO 3166‑1 alpha‑2.
  • ICANN has a written ccTLD retirement policy: when an ISO code is removed, the matching ccTLD is supposed to be wound down over 5 years, extendable to 10 with specific justification.
  • Trigger depends on what ISO does with IO: delete, keep, or “exceptionally reserve” it.

Precedents and Edge Cases

  • Some ccTLDs were retired after country changes: .yu, .zr, .cs, .an, .um.
  • .su (Soviet Union) persists as an exceptionally reserved code; ICANN backed off retirement after resistance.
  • Territories can have their own codes and ccTLDs even if not full states (.tv, .co, .me, .tf, .re, .cx, .cc, etc.).
  • BIOT was never a state, unlike the USSR, so analogy to .su is debated.

Possible Outcomes for .io

  • Continue as a ccTLD under Mauritius or a special Chagos/“Indian Ocean” territory, potentially with licensing revenue to Mauritius (comparison to .tv).
  • Be phased out per ICANN policy: new registrations frozen, existing domains given a long transition window before shutdown.
  • ISO could exceptionally reserve IO, giving ICANN cover to keep .io indefinitely.
  • Converting to a two‑letter gTLD is viewed as unlikely because two‑letter codes are reserved for country use.

Operators, Governance, and Corruption Concerns

  • .io was originally delegated to a private operator with loose/contested links to BIOT; now run by a commercial registry conglomerate (described as hedge‑fund‑owned).
  • Some argue ccTLD delegations are hard to claw back without current operator consent; others emphasize ICANN ultimately controls the root.
  • ICANN and related bodies are described as political and lobby‑susceptible, though they also publish formal policies.

Technical and Business Risk

  • Several comments treat .io as a risky “vanity” ccTLD: subject to geopolitical change, outages, and governance issues.
  • Past examples (.af after Taliban takeover, .tk upheavals) show ccTLD users can lose domains or face instability.
  • Some suggest .com/.net or one’s national ccTLD are safer, with fewer political surprises.

Ethics and Colonialism Debate

  • Strong thread on BIOT’s history: forced expulsion of Chagossians, ongoing military base, and the characterization of .io as “digital colonization.”
  • Some see using .io as morally problematic and have rebranded away from it; others dismiss this as ideological posturing and focus on practicality.

Practical Takeaways for .io Holders

  • No consensus that .io is doomed, but clear that it is not guaranteed permanent.
  • Common advice: have a migration/backup domain plan; avoid anchoring critical identity and email solely on .io; monitor ICANN/ISO decisions.