.io for Builders: The No-Nonsense Guide to Your Next Domain (Chagos Question Included)

You named the repo. You wrote the README. The landing page is half done. Now you need a domain, and the obvious .com is gone.

Enter .io. Two letters that developers read as "input/output." The default ending for a generation of dev tools, APIs and SaaS dashboards.

But there is a question every careful builder asks in 2026: what about the Chagos deal? We will answer it straight, with the facts, then give you a checklist to decide in five minutes.

Let us ship.

TL;DR

• .io is the ccTLD of the British Indian Ocean Territory, delegated in 1997.
• Anyone, anywhere can register. No trustee. No local presence.
• DNSSEC: yes. IDN: no.
• Minimum term at SoxDomains: 1 year, up to 10.
• SoxDomains price: $88.00 to register, $99.00 per year to renew, $99.00 to transfer. WHOIS privacy free for the first year.
• Chagos: a UK and Mauritius treaty was signed in May 2025 but is not in force. .io is active and unchanged in the root today. If the territory's code ever disappears from the ISO list, ICANN policy gives a transition of at least five years.

The 60 second decision checklist

Answer honestly. Mostly yes? .io is a great fit.

• [ ] Is my audience technical: developers, engineers, product teams, startups?
• [ ] Is the product software: an API, a CLI, a SaaS app, an open source project?
• [ ] Is the .com taken, or priced out of reach?
• [ ] Do I want a short name that is easy to type in a terminal and say on a call?
• [ ] Am I fine with a renewal of $99.00 per year?
• [ ] Will I keep an eye on long term policy news, and hold a backup domain for critical services?

If your audience is mainly non technical consumers, or you are building a brand for decades with zero appetite for policy news, read the "When not to pick .io" section below first.

What .io actually is

Every country and territory in the ISO 3166 list gets a two letter ccTLD. New to the concept? Start with What are ccTLDs?.

IO is the code for the British Indian Ocean Territory, a group of atolls in the middle of the Indian Ocean that includes Diego Garcia. The IANA root zone database lists:

• Registration date: 16 September 1997.
• ccTLD manager: Internet Computer Bureau Limited (ICB), with a contact address c/o Sure (Diego Garcia) Limited, Diego Garcia.
• Technical contact: ICB in Orpington, Kent, United Kingdom.
• Registry site: nic.io, with WHOIS at whois.nic.io.

ICB describes itself on nic.io as the country code top level domain manager and registry operator for .io, .ac and .sh. Its registration agreement is governed by English law.

The registry itself leans into the tech identity. On nic.io it explains that early adopters in the technology industry started using .io as an abbreviation of "input/output," and that you are not required to live in the British Indian Ocean Territory to register.

How builders use .io today

• Developer tools: CLIs, SDKs, testing and CI services.
• APIs and infrastructure: status pages, docs portals, edge and hosting products.
• SaaS apps: dashboards, analytics, collaboration tools.
• Open source projects: a clean home for docs and downloads.
• Games and side projects: short, punchy, memorable.
• Startups that want a technical signal and a name that fits in a tweet.

Building your first site fast? Our guide to registering a domain without costly mistakes covers the basics in ten minutes.

Spec sheet

A few details worth knowing:

Eligibility. The .io rules say it plainly: "An applicant may reside in any legal jurisdiction." For second level names (yourname.io) you need at least two working name servers, and there is no requirement for them to be physically located in the territory. Third level names under the registry's own second level zones follow stricter rules, including residency in the territory, but that does not affect a normal yourname.io registration.

Restrictions. .io names may not be used for sexual or pornographic purposes or for anything against the statutory laws of any nation. The registry also reserves the right to act against domains used for spam. Contact details must be accurate and verifiable.

DNSSEC. The DNS root zone contains a DS record for .io, so the zone is signed and chained to the root trust anchor. Turn on DNSSEC for your name from your SoxDomains control panel and you get signed answers end to end. Refresher: How DNSSEC works.

IDN. .io names use letters a to z, digits and hyphens. There is no .io table in IANA's IDN practices repository, and at SoxDomains .io is offered for standard ASCII names.

Name servers. IANA lists four .io name servers, each with IPv4 and IPv6 addresses. Want to understand what sits between your registrar and your visitors? Read Nameservers, glue records and DNS propagation.

Specs look good? Grab your .io name at SoxDomains before someone else pushes to production first.

The Chagos question, clear-eyed

Here is the part many guides skip. We will not.

What happened. On 3 October 2024, the UK and Mauritius issued a joint statement announcing a political agreement on sovereignty over the Chagos Archipelago, including Diego Garcia. Under the planned treaty, the UK would agree that Mauritius is sovereign over the archipelago, while the UK would be authorized to exercise Mauritius's sovereign rights over Diego Garcia for an initial period of 99 years to keep the military base operating.

On 22 May 2025, the two governments signed the treaty. The UK government's published text carries the note "The Agreement is not in force." In the UK, the implementing legislation, the Diego Garcia Military Base and British Indian Ocean Territory Bill of the 2024 to 2026 session, stopped short of Royal Assent according to the UK Parliament's bill record. The treaty text itself says nothing about internet domains.

What it means for .io right now. Nothing has changed operationally. IANA's root zone database still lists .io as the ccTLD of the British Indian Ocean Territory, managed by ICB. The zone is signed, resolving and open for registrations. Your .io site works exactly as it did yesterday.

What could matter later. A ccTLD exists because its code is on the ISO 3166 list. If the IO code were ever removed from that list, ICANN's Policy for the Retirement of ccTLDs, adopted by the ICANN Board on 22 September 2022, would kick in. IANA explains the process:

• IANA notifies the ccTLD manager with a Notice of Removal.
• By default, the ccTLD is removed five years after that notice.
• The manager may apply for an extension of up to five more years, so the maximum retirement period is 10 years.
• The ccTLD is publicly advertised as under retirement, with the target removal date.

So even in the most dramatic scenario, there is no sudden switch off. There is a long, public, documented runway. And retirement is not the only possible path: the code could remain, or other arrangements could emerge. The honest summary is that the future depends on decisions by governments and standards bodies, and every step would be visible years in advance.

Our practical advice for builders:

1. Relax about today. .io is fully operational. Build.
2. Hold a backup. For critical services, register a matching .com or another extension and keep it pointed at a simple page. It costs little and makes any future migration boring.
3. Avoid hard coding your domain. Keep base URLs in config, use relative links, and make email and OAuth callbacks easy to change.
4. Watch the right signals. A change to the ISO 3166 list or a Notice of Removal on IANA's site would be the real trigger. Headlines alone are not.
5. Let us watch too. At SoxDomains we follow registry and IANA updates, and we will keep our customers informed.

For more context on who does what at the top of the DNS, read ICANN and IANA: the Internet's address book.

Pricing at SoxDomains

These are the prices on our .io page today:

And the classics, for comparison:

Quick math: year one of .io is $88.00. After that, $99.00 per year is about $8.25 per month. Our .com renewal is $15.89 per year, so .io costs roughly six times as much to keep.

Moving an existing .io to us? Start on our domain transfer page. If a transfer refuses to budge, it is usually a lock: Registrar lock explained.

Premium and short names

Short .io names are prime real estate. The .io rules note that certain single letter, two letter and number domains are made available "in a controlled and equitable manner," which is registry language for: special names follow special processes and pricing.

Our tips:

• Premium means premium renewals too. Always confirm what year two will cost.
• A slightly longer name is often smarter. "getacme.io" you can afford forever beats "ac.io" that eats your runway.
• Ask us. If a premium .io pops up in your search, our team will walk you through the details before you commit.

Renewal policy: do not let it lapse

• Renew at $99.00 per year at SoxDomains, before expiration.
• The .io terms say each new registration and each renewal fee covers a period of one year, and the registry may vary its terms at renewal. At SoxDomains you can renew for multiple years at once to reduce admin.
• Enable auto renew. Keep your card current.
• Know the timeline after expiration: grace, redemption and deletion. Our guide What happens when a domain expires? breaks it down.

A lapsed .io that hosts your API docs or login page is a production incident. Treat renewal like certificate renewal: automate it.

Why pay more than .com or .net?

Straight talk. You are paying about six times the .com renewal. Here is why builders do it anyway:

Signal. A .io name tells developers "this is a tool for you" before they click. It fits the culture of docs, APIs and dashboards.

Availability. The good .com names are gone or listed for thousands. A clean .io name at the standard price is often the fastest route to a name you actually like.

Brevity. Two letters after the dot. Shorter URLs, shorter email addresses, fewer typos in terminals and configs.

Cost in context. About $8.25 a month after year one. Less than most of the SaaS subscriptions in your stack.

Proven infrastructure. Signed zone, IPv6 name servers, instant registration, open eligibility.

When not to pick .io

• Your audience is mostly non technical consumers who expect .com.
• You are building a heritage brand meant to last generations, with zero tolerance for policy watching. In that case, make the .com your primary and hold the .io as a redirect.
• You need a name with accents or non Latin script. .io does not support IDNs.

Plenty of our customers run the product on .io and keep the .com as a shield. That combo covers you both ways.