.repo
Is .repo a real TLD? Who’s applying to run it?
.repo is not contested. One application for it is on ICANN’s Reveal Day list, as of 18 November 2026. It is Internet Naming Company.
Who is applying, and what they run today
Will names sell?
A developer-flavored word that reads clearly but rarely becomes a project's main address; expect cheap registrations, little resale.
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. .repo’s closest 2012 strings hold .dev 713K, .docs 3 and .app 1.48M.
The nearest 2012 strings, and how many names each holds today
The closest 2012 string, .dev, held 712,600 names, June 2026. .docs held 3; .app held 1,478,674. Chosen by AI from every string in the 2012 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.
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
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. One application for it is on ICANN’s Reveal Day list.
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. 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 .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 .repo is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- 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.