.repo
Is .repo a real TLD? Who’s applying to run it?
Nobody has applied for .repo in its own right, as of 7 October 2026. Internet Naming Company named .repo as the backup string of its .api application.
A developer-flavored word that reads clearly but rarely becomes a project's main address; expect cheap registrations, little resale.
developers and open-source maintainers who want a short address for a code repository or package mirror, plus a smaller set of finance firms working in repurchase markets
Nobody has applied for .repo in its own right.
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 clipped piece of developer jargon nobody outside software fully parses, sold as identity space to tooling vendors and code projects rather than to the general public, and worth something only if engineers accept a trade-term TLD as a real address.
Same bet in a different slot of the same workflow — a shortened artifact-container noun whose value comes from replacing a conventional subdomain (docs.x, repo.x) with a top-level label, bought by whoever hosts that artifact for others.
Same bet one layer up the stack: a clipped generic noun for the unit of software itself, where the buyer is any maker putting its primary product identity on a category word, but it is aimed at the whole market rather than at practitioners' internal vocabulary.
What a .repo domain is
.repo is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our AI & tech category. Nobody has applied for .repo in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .repo domain extension real yet?
.repo 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 .repo domain?
You can’t yet. A .repo 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 .repo was .dev, delegated on 18 December 2014.
Is .repo a real TLD?
Not yet. .repo is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .repo as part of an application for another string. Every entry on this page links to its source.
- Internet Naming Company · first recordedICANN
“INC2624T-T91582 · Internet Naming Company · replacement string of .api”ICANN
- Band chosen: 30-49 (usable but limited), at its lower edge. The string has one dominant meaning in a large professional community (a code repository) and secondary meanings in finance (repurchase agreements) and in collections (repossession), so the word is understood without explanation by its best-fit buyer. The catch is that repositories live as sub-paths under hosting platforms, so a project's primary identity is normally the project name on a general TLD or a developer-oriented TLD, with the repository a secondary pointer; .repo therefore reads as a redirect or mirror address, not a home address. It is not in the 50-69 band because genuine primary-identity use is hard to picture outside a handful of self-hosted or mirror projects, and no sustained aftermarket is plausible for a word tied to a sub-resource. It is not in the 10-29 band because the demand is not joke-driven or event-driven: by analogy with other short developer-vocabulary TLDs, a steady trickle of low-price registrations from developers and tooling vendors is likely, which the rubric treats as volume-on-price with a weak brand signal. By analogy (flagged as analogy), broad developer TLDs have reached category-standard status only when backed by a widely used ecosystem and a broad meaning ("developer" or "app"), whereas narrower developer-noun TLDs have stayed thin; .repo sits with the narrower group. The record lists one application, from Internet Naming Company, filed as a replacement string for a .api application and as a standard (not brand, community or geographic) application; this is read neutrally and only as an adoption signal, since a standard open registry means any developer can register. Main market uncertainty: whether any code-hosting, package-registry or mirror-network operator adopts name.repo as a resolution convention for repositories or package feeds; without such a convention the TLD stays a vanity-redirect namespace, with it the string could move toward the strong-niche band. Specific registration counts, prices and comparable-TLD volumes are unknown and are not asserted here.