is .io still safe for your startup? .io vs .com in 2026.

.com remains the safest default and nothing in the last few years has changed that. .io is a reasonable bet with two costs attached: you pay more every year, and you accept a category of risk that .com does not carry.

whether that trade is worth it depends almost entirely on how much the .com you actually want costs, and on whether anyone types your domain rather than clicking it.

what .io actually is

a country-code TLD assigned to the British Indian Ocean Territory. essentially nobody uses it for that. it became a de facto technical TLD because the letters mean input/output to anyone who writes software, because short names were available in it long after .com ran dry, and then because enough recognisable companies used it that it stopped needing justification.

the operational reality matters more than the label. .io is run as a commercial registry business rather than as a government service, sold through ordinary registrars worldwide, with no local presence requirement. day to day it behaves like a generic TLD. that is precisely why the sovereignty question surprises people — nothing about using it feels country-specific.

the sovereignty question

the UK has agreed to transfer sovereignty of the Chagos Archipelago to Mauritius. the British Indian Ocean Territory is the entity that .io's two-letter code represents, and ccTLD delegation follows the ISO 3166-1 country code list. if the code is eventually withdrawn from that list, the ccTLD becomes eligible for retirement.

that is the real mechanism, and it is worth being precise about what it does and does not imply.

what it does not mean. it does not mean .io stops resolving, and it does not mean a date has been set. ISO code changes are not automatic consequences of a treaty, IANA operates a published retirement process with a lengthy transition period rather than a switch, and retirement has historically been slow, negotiated and signposted years ahead. there are ccTLDs still operating long after the country they were named for ceased to exist, precisely because the process is deliberate and nobody involved wants to break millions of names.

what it does mean. it is a real, structural dependency that .com does not have. .io's continued existence rests on an ISO listing that depends on a political arrangement, and no registry, registrar or blog can promise you an outcome. anyone telling you .io is definitely fine is guessing, and so is anyone telling you it is doomed. the correct posture is that this is a low-probability, long-horizon, high-consequence risk that you can mitigate cheaply and should not lose sleep over.

the mitigation is unglamorous: own the .com equivalent of your name when you can afford it, even if you do not use it, and keep the domain out of places you cannot change — hard-coded values in shipped software, printed material, identifiers that are expensive to migrate.

the cost gap is the part that definitely affects you

the sovereignty story gets the attention and the renewal price is what actually shows up on your card. .io renews at a substantial multiple of .com, every year, permanently. we are not quoting figures here because they change and the price pages are generated from a live catalogue — compare .io against .com directly, or run either through price check.

two things make the gap larger than it first looks.

it compounds across variants. in practice nobody registers one domain. you take the .io, then the .com if it is free, then the .co, then a couple of typos and a hyphenated version. the multiplier applies to all the .io registrations in that set, every year, for as long as the company exists. the five-year view is where this stops being a rounding error, and total cost of ownership is the framing worth applying before you buy rather than after.

ccTLD registries set prices with more freedom than gTLD registries. generic TLD registries operate under ICANN contracts that constrain how and when prices can be raised, with notice requirements attached. country-code registries are not party to those agreements. a ccTLD registry can revise its wholesale pricing on its own terms, and .io's pricing has moved upward more than once. budget for the possibility that it moves again.

the same reasoning applies with more force to .ai, which is a smaller ccTLD with an even higher renewal and the same class of political dependency — currently fashionable, and fashion is not a pricing strategy you control.

what .io buys you

• availability. the honest reason most people choose it. the short, clean, obvious name is free in .io and gone in .com, and a good name in a lesser extension genuinely beats a bad name in a great one.
• context. in developer tooling, infrastructure and open source, .io reads as native rather than as a compromise. that is a real if modest signal to a specific audience.
• it is no longer a fundraising problem. enough well-known companies run on .io that no investor treats it as evidence of anything.

what .com still buys you

• the default. people type .com when they are half paying attention, say it aloud without ambiguity, and get it right when they hear your address over the phone. every other extension carries a small ongoing tax paid in spelling it out.
• trust, measurably. extension does affect how a link is perceived, particularly outside technical audiences. TLD trust rankings is our read on that.
• liquidity. .com is the only extension with a deep resale market. if the company does not work out, the .com is an asset and the .io is a cancelled subscription.
• no political dependency. .com's operator is contracted, regulated and about as boring as internet infrastructure gets. boring is the feature.

the unexcited answer

if the .com for your name is available at registration price, take it. this is not a close call and no argument for .io survives contact with a free .com.

if the .com is on the aftermarket at a price you can absorb, it is usually still worth it, because you are buying a permanent end to the entire discussion. weigh the asking price against several years of the .io renewal premium and the cost of migrating later if you change your mind.

if the .com is genuinely out of reach — held by a company, priced in six figures, or simply not for sale — .io is a defensible choice and you are in good company. do it with your eyes open: expect to pay materially more each year, buy the .com when you can, and avoid putting the domain anywhere you cannot change it later.

and if neither is available, check what else is. run the name through domain search to see availability across extensions with live renewal prices beside each one, because the right answer is quite often a third TLD nobody suggested.

one closing note whichever way you go. the failure mode is not the TLD — it is forgetting the renewal on a premium-priced name held at a registrar you no longer use. that is a mundane, solvable, extremely common way to lose a domain, and it happens to expensive extensions as easily as cheap ones.