.src
Is .src a real TLD? Who’s applying to run it?
.src is not contested. One application for it is on ICANN’s Reveal Day list, as of 18 November 2026. It is Stichting NLnet.
Who is applying, and what they run today
Stichting NLnet filed a community application, a type ICANN evaluates with community priority.
Will names sell?
Developers will get the 'source' pun instantly, but most serious projects will still choose .dev, .io or .org as their main address.
Last round the AI scored the 2012 strings blind to their fate. Strings it scored 60 or more hold a median 27,168 names today; those under 30, a median of 30. .src’s closest 2012 strings hold .prod 2, .dev 713K and .docs 3.
The nearest 2012 strings, and how many names each holds today
The closest 2012 string, .prod, held 2 names, June 2026. .dev held 712,600; .docs held 3. Chosen by AI from every string in the 2012 round, without being told what happened to any of them.
Same bet as .src: a four-letter piece of engineering-environment shorthand (src/, prod/) that is invisible jargon to the general public, so its value rests entirely on developers and tooling vendors agreeing to put infrastructure identity on a namespace only they can read.
The sibling term from the identical vocabulary — an abbreviation whose buyer is the engineer or the platform courting engineers, working only if a technical audience adopts a TLD as a professional habitat rather than a marketing word.
Another short repository-folder noun that sits next to src/ in every project and would be registered by the same code-hosting and developer-platform buyers, but it is a plain English word with mainstream meaning, so it carries far less of .src's insider-token risk.
open-source maintainers and developer-tool teams who want a short address that says "the source code lives here", plus individual developers using it for project and portfolio pages
What a .src domain is
.src is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our AI & tech category. One application for it is on ICANN’s Reveal Day list.
Is the .src domain extension real yet?
.src is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. It is a string applicants have put forward in the ICANN 2026 new gTLD round, the process that decides whether it becomes one.
When can you buy a .src domain?
You can’t yet. A .src name can only be registered once the string is delegated (added to the DNS root) and its registry opens. Last round's closest parallel to .src was .prod, delegated on 29 August 2014.
Is .src a real TLD?
Not yet. .src is not in the DNS root, so nothing resolves under it. It’s here because .src is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
“CA2682T-T18182 · CORE Association · primary · Withdrawn SN2610T-T87824 · Stichting NLnet · primary”ICANN
“CA2682T-T18182 · CORE Association · primary · contention set 2026-220 SN2610T-T87824 · Stichting NLnet · primary · contention set 2026-220”ICANN
- Band chosen: usable but limited (30-49), at the upper end. The string is short, typeable and carries an unambiguous meaning for one audience: 'src' is the conventional name for a source-code directory, so a developer reads project.src as 'this project's source' with no explanation needed. The verified record shows two confirmed applicants in a contention set, one of them a community application from Stichting NLnet, an organisation associated with funding open-source and internet-commons work; a community designation suggests the namespace could be positioned around open-source projects, which would sharpen the brand signal but also narrow volume (inference from the application type, not from a published policy). Why not the band above (strong niche, 50-69): by analogy, developer-oriented TLDs that reached genuine primary-identity use (.dev, .io) did so with either a major platform operator behind them or years of startup-culture momentum, and open-source projects already have strong defaults in .org and .dev; a new project choosing .src as its main identity over those would be the exception in the next 5 years, and the aftermarket would be thin because the meaning is tied to a single use (hosting source) rather than a company identity. Why not the band below (vanity/narrow, 10-29): unlike joke or event-driven strings, .src has a daily-use semantic hook for a large, global, technically literate buyer group, so demand should be sustained rather than spiky, and some projects would plausibly use it for canonical repository or download pages. Analogous outcomes flagged as analogy: .codes, .software and .engineer, which also spoke to developers but without platform backing, settled into low-volume, price-driven registration with little aftermarket; .src's shorter string and stronger semantic fit should place it above those but below .dev. Main market uncertainty: whether developers perceive .src as a primary identity for a project or merely as a redirect-style companion to an existing .org/.dev address, which decides whether it earns category-standard behaviour or stays a secondary registration.