.io: a startup favorite with a geopolitical footnote
.io is the country-code domain of the British Indian Ocean Territory, yet most of its registrants are software companies. Its future depends on a territorial dispute.
A ccTLD that was adopted, not designed for tech
.io is a country-code TLD. Its two letters come from the ISO 3166 code for the British Indian Ocean Territory (BIOT), an archipelago with no permanent resident population. The code resembles "input/output", an abbreviation every programmer knows, and that coincidence made it a developer favourite from the late 1990s onwards. Today it is arguably the best-known example of a ccTLD used almost entirely as a generic one.
The IANA root zone database lists Internet Computer Bureau Limited as manager, with name servers under nic.io, a DNSSEC delegation and the WHOIS server at whois.nic.io. Reporting by the domain trade press and the company's own statements describe Identity Digital as the operator of the registry, and Internet Computer Bureau is generally described as part of that group. Since corporate lines can shift, check IANA's current entry if the exact legal entity matters to you.
The Chagos question
This is the most unusual risk attached to any popular TLD. In October 2024 the United Kingdom announced an agreement to transfer sovereignty over the Chagos Archipelago, which contains BIOT, to Mauritius. A country code exists in ISO 3166 because a territory exists; if the territory ceases to exist as a separate entry, the code can eventually be removed, and ICANN's practice for retired country codes is a multi-year phase-out rather than an overnight shutdown.
As of November 2026, from trade reporting rather than an official statement: DomainIncite reported on 13 April 2026 that the UK government had frozen its plans to ratify the transfer because it lacked US support, that the legislation had run out of parliamentary time and that the next King's Speech was not expected to carry a successor bill; UK ministers denied the deal was dead. Press coverage describes .io as safe for now while its long-term status stays unresolved. We found no ICANN or IANA notice about retiring or redelegating .io, and IANA's record (last updated 2026-11-03) still lists Internet Computer Bureau Limited as manager. Any plan for a transition, a new code or continued operation has not been decided.
This page does not predict an outcome. If you are building a brand on .io, the sensible response is a contingency, not panic: also register the matching .com or another name you can fall back to, and keep your canonical URLs configurable.
Who actually uses it
Developer tools, infrastructure products, open-source projects, early-stage SaaS and game studios. Real examples include redis.io and socket.io, both software projects. The suffix also appears in hosting of static pages (for instance github.io is used for project sites on GitHub's platform).
It signals "tech product" more than a location, which helps when the .com is occupied by an unrelated business. See .com vs .io vs .ai vs .app for the head-to-head view.
Registration rules and price pattern
There is no residency requirement; anyone can register. Pricing is in the premium range for a ccTLD: noticeably above ordinary gTLDs, with renewal at the same elevated level. Short dictionary words and one-word brands are priced as premium or are already taken, and an aftermarket exists. Do not assume a promotional first-year price continues. Budget for renewal and use expiry protection for names you rely on.
Is the zone in CZDS?
No, to the best of current knowledge. ICANN's CZDS covers gTLDs under ICANN registry agreements; most ccTLDs, including .io, publish no zone file there, and registries guard their zones. Any .io data at all on a site like TLDlive would therefore rely on other sources, and this page makes no claim that it is covered. Read about the service in zone files and CZDS.
SEO treatment
Google documents a short list of country-code domains it treats as generic, because they are widely used without a geographic meaning, and .io is on it. A .io site is not geotargeted to the British Indian Ocean Territory; international audiences see it like .com. You can still set a target country in Search Console. Ranking depends on the normal factors. Some users distrust unfamiliar extensions, but in technical niches .io is routine.
Pros and cons
Pros
- Strong recognition in developer and startup circles.
- Short names, and treated as generic by Google.
- Mature registry with DNSSEC and a long track record.
Cons
- Unresolved long-term sovereignty question.
- Expensive to hold compared with common gTLDs.
- No public zone data, which limits independent analysis.
- Confusing for non-technical consumers.
For the underlying distinction between types of TLD, see gTLD vs ccTLD vs new gTLD.
Building on .io without betting the company on it
A few habits reduce exposure without abandoning the extension. Keep the product name usable as a second brand on another TLD, so a future move would be a redirect project and not a rename. Store your canonical domain in configuration, not scattered through email templates, OAuth callbacks, webhook URLs and package metadata. Register the .com if it is for sale at a sane price, or at least a defensive alternative. Make sure DNS is hosted with a provider you control and that registrar lock and auto-renew are on, a basic precaution that applies to every name; DNS and nameserver providers explains the options.
What a TLD retirement would look like
If a country code is ever removed from the ISO 3166 list, ICANN policy gives the registry a defined wind-down, reported in the press as a period of several years that can be extended. That is a very different thing from a sudden switch-off. It would still force every active brand to migrate, which is why the risk is a planning issue and not a reason to avoid .io outright. Because the outcome is political, no current source can say whether or when it will happen.
Aftermarket note
Short and dictionary-word .io names trade on the aftermarket, and buyers price in some uncertainty. If you are evaluating a purchase, treat the registration fee as a recurring cost and read domain investing basics for how to separate brand value from speculation.
Sources
- IANA root zone database: .io (Internet Computer Bureau Limited as manager; last updated 2026-11-03)
- DomainIncite: .io safe for now as Trump puts Chagos deal on ice (April 2026)
Frequently asked questions
Which country owns .io?
It is the country code for the British Indian Ocean Territory. It is used worldwide and requires no local presence.
Will .io be shut down because of the Chagos treaty?
Not decided. Not decided. DomainIncite reported in April 2026 that the UK froze ratification of the Chagos treaty and called .io safe for now. We found no ICANN or IANA notice about retiring it, and no official long-term plan has been announced.
Who runs the .io registry?
IANA lists Internet Computer Bureau Limited as manager; reporting identifies Identity Digital as the operating company.
Does Google treat .io as a country domain?
No. Google lists it among ccTLDs treated as generic, so it is not tied to one country for ranking.
Are .io domains in ICANN zone files?
Not to the best of current knowledge; most ccTLDs do not publish zone files through CZDS.
Is .io expensive?
Pricing is typically well above ordinary gTLDs, and renewal follows the same level. Check renewal prices at checkout.