Is the .io Domain Going Away? What the Chagos Handover Means for Buyers

No, the .io domain is not going away in 2026. The United Kingdom signed a treaty in May 2025 to transfer sovereignty of the Chagos Archipelago to Mauritius, and that sparked headlines predicting the end of .io, but nothing operational has changed. The IO code is still listed in the ISO 3166-1 standard, the registry is renewing and issuing names as normal, and even in the worst case ICANN's own rules would open a multi-year phase-out rather than shut anything off. Here is what the Chagos handover actually means for anyone who owns or is thinking about buying a .io domain.

Why do people think .io is going away?

Because the extension is a country code, and the country it represents is changing hands. The .io code was assigned to the British Indian Ocean Territory, a group of islands in the Indian Ocean. In October 2024 the UK announced it would hand sovereignty of the Chagos Archipelago to Mauritius, and the two governments signed a treaty in May 2025. Country code domains are tied to an entry in the ISO 3166-1 list of countries and territories, so commentators reasoned that if the territory dissolves, its code could be removed, and the domain with it. That chain of logic is real, but every link in it is slow, and none of it has happened yet.

What is actually happening with .io right now?

Operationally, nothing has changed. As of early 2026 the IO code is still assigned in ISO 3166-1, registrars still sell and renew .io names at normal prices, and existing sites keep resolving. ICANN, which oversees the domain name system, published a blog in November 2024 acknowledging the Chagos situation and confirming that no immediate action was required. The treaty still has to be fully implemented, and even then the ISO decision on the IO code is a separate step that the standards body would take on its own timeline. In practical terms, an .io you own today works exactly as it did before the news broke.

Could .io be retired in the future?

It is possible but far from certain, and it would not be sudden. Retirement would only start if the IO code were removed from ISO 3166-1. If that happened, ICANN's community-developed retirement process would apply, which opens a phase-out window of up to five years before a code is fully wound down. During that window the registry would keep operating while owners migrated. There is also a live discussion about creating an exception so that heavily used technical codes like IO are not retired just because the underlying territory changed, precisely because millions of unrelated businesses depend on them. So the realistic timeline for any disruption is measured in years, not months, and even the trigger has not been pulled.

Is it safe to buy a .io domain in 2026?

Yes, for most buyers it is safe, especially if you are registering or renewing rather than paying a large premium on the aftermarket. The extension is fully functional, ranks globally, and shows no sign of interruption. The honest caveat is that .io carries a small amount of long-term policy risk that .com does not, because its future ultimately depends on decisions outside any registry's control. If you are spending five or six figures on a single .io as a decade-long brand, that tail risk is worth weighing. For a normal registration or a mid-range purchase, the risk is minor next to the benefit of owning the exact name you want.

What should .io owners do to be safe?

Keep it simple and do not panic-migrate. Watch for one specific event: the formal removal of the IO code from ISO 3166-1. Until that happens, there is nothing to act on. If it ever does, you would have years of notice and a clear phase-out window to move. It is reasonable to register the matching .com as a defensive backup if it is available and affordable, so you have a fallback brand ready. If you ever do move to a new primary domain, the priority is to carry your search rankings over cleanly with proper redirects so the migration does not cost you traffic. Our guide on changing your domain name later walks through the full process.

Does the Chagos news affect .io SEO?

No. Google still classifies .io as a generic top-level domain, so it ranks worldwide with no country targeting, exactly as it did before the handover news. Search engines index the domain on its content and links, not on the geopolitics of the underlying territory. There is no ranking penalty, no warning, and no change to how an .io site performs in United States or global search. The only SEO consideration would arise years from now if you chose to migrate, and that is a standard redirect exercise, not an .io-specific problem.

The bottom line on .io in 2026

The .io domain is stable, popular, and safe to use today. The Chagos handover is a genuine long-term policy question, but it is a slow-moving one with multiple gates still unopened, and ICANN's own rules guarantee a gradual transition even in the worst case. For a tech startup, developer tool, or SaaS brand, .io remains a credible choice, and the availability of good names is still the main reason founders pick it. See how it stacks up against the default in our .io vs .com comparison, or review the latest .io domain statistics before you buy. Browse available .io domains on BoldDomains with escrow-backed transfer.

This article reflects the status of the .io extension and the Chagos Archipelago treaty as of early 2026, based on public ICANN guidance and reporting on the UK to Mauritius agreement.