.opensource
Is .opensource a real TLD? Who’s applying to run it?
Nobody has applied for .opensource in its own right, as of 7 October 2026. Radix named .opensource as the replacement string of its .podcast application.
A clear label for open-source projects, but most already live happily on .org, .dev or .io, so demand stays modest.
open-source project maintainers, foundations and developer-tool companies who want their address to signal openness; secondarily community hubs and OSS-focused consultancies
No applications recorded for this TLD yet.
The 2012 applications making the most similar bet. Chosen by AI from every string in that round, without being told what happened to any of them.
Same bet: a movement's own self-identifying word turned into a namespace, where the registrants are ideologically-motivated projects and institutions rather than a commercial category, and the value depends entirely on the movement treating the string as a credential it polices rather than a place it rents.
Also a values/standards word that an identity-driven community claims as its primary label, with the same dependency: it only means something if who may use it is gated, otherwise it degrades to a generic adjective anyone can buy.
Same buyer pool and the same job of being the industry's neutral home address, but it is a plain category noun that any vendor can wear, where the target is a philosophy word only one slice of that industry would put its identity on.
What a .opensource domain is
.opensource is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. Nobody has applied for .opensource in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .opensource domain extension real yet?
.opensource is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. Nobody has applied for it on the public record; the ICANN 2026 new gTLD round is the process that would decide whether it becomes one.
When can you buy a .opensource domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .opensource name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .opensource was .eco, delegated on 28 August 2016.
Is .opensource a real TLD?
Not yet. .opensource is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .opensource as part of an application for another string. Every entry on this page links to its source.
- Radix · first recordedICANN
“RTIS2674T-T83171 · Radix Technologies Inc SEZC · replacement string of .podcast”ICANN
“LFGL2683T-T90578 · Link Freedom Group Ltd · primary · contention set 2026-213 PTL2645T-T73740 · Pirin Tablet, LLC · primary · contention set 2026-213 RTIS2674T-T99763 · Radix Technologies Inc SEZC · replacement string of .robotics · Deactivated VIL2659T-T55269 · Verse International Limited · replacement string of .did · Deactivated”ICANN
“Radix has applied for these TLDs; we do not own or operate them today.”Radix
- Band chosen: 30-49 (usable but limited). The string names a large, real community with a strong identity habit, and some projects, foundations and tooling vendors would plausibly register a descriptive address on it, which is why it sits above the 10-29 vanity band. It does not reach 50-69 because open-source projects already have entrenched defaults (.org for foundations and projects, .dev and .io for developer-facing tools, plus hosted code pages), so choosing .opensource as a primary identity needs explaining and the string is long to type and say. By analogy (flagged as analogy): descriptive software-sector gTLDs such as .software, .codes and .systems have found steady but thin use rather than becoming category defaults, while .dev gained traction partly on brevity and a well-known operator; .opensource looks closer to the former group. The application on record is a replacement string from Radix, a portfolio registry, which suggests a standard open-registration launch and pricing-driven adoption rather than a community-restricted namespace; that neither helps nor hurts the string's inherent appeal beyond making general availability likely. Aftermarket value would be thin: generic one-word names on the TLD might see occasional resale, but the brand signal is descriptive, not prestigious. Main market uncertainty: whether a meaningful share of OSS projects and foundations would treat 'open source' as part of their identity worth encoding in the domain, versus seeing it as redundant with their existing .org/.dev presence.