Is the .io top level domain headed for extinction?

Message to all organizations that use.io domain names, of which there are currently an estimated 1.6 million: A move announced last week by the new Labour government in the UK could mean you may have to eventually replace that ccTLD (Country Code Top Level Domain).

As reported by the BBC, the UK is “giving up sovereignty of a remote but strategically important cluster of  islands in the Indian Ocean.” Under the terms of the deal, it will “hand over the Chagos Islands to Mauritius in a historic move.”

While the move certainly has political implications in that a US-UK military base located on Diego Garcia, the largest island in the region, will remain in operation, it may also result in the elimination of the.io domain for one simple reason — the region it represents will no longer exist.

The domain name regulatory environment works as follows:  the ISO 3166 standard is used to define a nation or region’s ccTLD and the Internet Corporation for Assigned Names and Numbers (ICANN) maintains that standard. Also involved is the Internet Assigned Numbers Authority or IANA, a standards organization that oversees global IP addresses and is an operating unit of ICANN.

In the case of the.io domain, digital strategist Gareth Edwards wrote in a social media post,  “IANA bases TLDs off ISO 3166 country codes. If a code stops existing, in theory, they follow suit and kill the TLD. Officially this was British Indian Ocean Territory. That is the.io domain everyone loves so much.”

According to Edwards, “once this treaty is signed, the British Indian Ocean Territory will cease to exist. Various international bodies will update their records. In particular, the International Standard for Organization (ISO) will remove country code ‘IO’ from its specification.”

While an email from Computerworld to the ISO 3166 Maintenance Agency asking for comment is so far unanswered, Kim Davies, vice president of IANA Services and president of Public Technical Identifiers (PTI) at ICANN, said ICANN relies on “the ISO 3166-1 standard to make determinations on what is an eligible country-code top-level domain.”

Currently, he said, “the standard lists the British Indian Ocean Territory as IO. Assuming the standard changes to reflect this recent development, there are multiple potential outcomes depending on the nature of the change.”

According to Davies, one such change “may involve ensuring there is an operational nexus with Mauritius to meet certain policy requirements. Should.io no longer be retained as a coding for this territory, it would trigger a five-year retirement process, during which time registrants may need to migrate to a successor code or an alternate location.”

He added, “We cannot comment on what the ISO 3166 Maintenance Agency may or may not do in response to this development. It is worth noting that the ISO 3166-1 standard is not just used for domain names, but many other applications. The need to modify or retain the IO encoding may be informed by needs associated with those other purposes, such as for Customs, passports, and banking applications.”

Edwards’ advice to any organization that might be impacted is this: “There’s no need for anyone with an.io domain to panic. The IANA may decide to fudge their own rules and keep the domain going, perhaps assigned to Mauritius instead, or by turning it into a generic, non-country domain. Even if they decide to deprecate it, this will be managed over multiple years.”

However, he added, “If an organization has made.io part of their identity, though, then it may be time to at least think about a brand review.”