.io TLD audit hub
Originally the British Indian Ocean Territory ccTLD; co-opted by the dev community as 'input/output'.
Although .io was delegated in 1997 as the country-code TLD for the British Indian Ocean Territory, almost none of its registrations belong to that jurisdiction. Developer communities seized on the I/O abbreviation in the early 2010s and Internet Computer Bureau (since acquired by Identity Digital) priced it accordingly — a .io domain costs roughly four to five times a .com renewal. The TLD became the de facto signal for B2B SaaS, infrastructure, dev-tools and crypto launches, partly because of the geek-friendly name and partly because short brand-name combinations were still available long after the dot-com gold rush ended. Politically the namespace has had moments of uncertainty — the 2024 announcement that the UK would cede sovereignty over the Chagos Archipelago to Mauritius prompted a wave of speculation about whether IANA might retire the code. ICANN's published guidance has been that retention is technically possible and that registrants would not be summarily evicted, but it is a real consideration for any dependency you cannot easily migrate. Operationally, modern .io registrars hand out DNSSEC, registry-lock and WHOIS privacy on parity with .com. The historical reliability concern from the early 2010s — periodic root server outages — has been resolved since the 2020 infrastructure upgrade. We see slightly more aggressive expiry and transfer-lock behaviour on .io than on the legacy gTLDs.