.git
Is .git a real TLD? Who’s applying to run it?
Nobody has applied for .git in its own right, as of 7 October 2026. Open Culture Foundation named .git as the replacement string of its .ops application.
A developer-vocabulary string with a real but narrow audience; useful for code-tool projects, unlikely to become a mainstream identity.
developer-tool makers, code-hosting and open-source projects, and individual developers wanting a short vanity address tied to version-control culture
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 in structure — a short, named software technology whose word is the identity badge of a developer ecosystem rather than a product category — but Java's name sat with one corporate steward, while a .git applicant would be claiming a term the community holds in common.
The same buyer and the same job: an occupational/infrastructure word that developers already type daily, bet on as the neutral home for tooling and project namespaces, differing only in that it names the audience rather than the specific tool they work through.
Shares the odd structural wrinkle of a vendor-born file-format/tool word that practitioners use as a plain common noun, so the string's value depends on an installed workflow habit rather than on marketing — but it is a proprietary format with an owner, not a community-governed open-source project name.
What a .git domain is
.git 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 .git in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .git domain extension real yet?
.git 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 .git domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .git name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .git was .java, delegated on 3 March 2015.
Is .git a real TLD?
Not yet. .git is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .git as part of an application for another string. Every entry on this page links to its source.
- Open Culture Foundation · first recordedICANN
“OCF2539-T20706 · Open Culture Foundation · replacement string of .ops”ICANN
- Band chosen: 30-49 (usable but limited). The string is everyday vocabulary for software developers because it names a widely used version-control tool, so there is a plausible buyer group of code-hosting services, developer tooling, and open-source projects that would understand the address instantly; by analogy (flagged as analogy), developer-targeted strings such as .dev and .sh have attracted genuine primary-identity use among technical projects, which is why .git is not in the 10-29 vanity band. It is not in the 50-69 band because the string names a specific tool rather than a category of businesses, so demand is bounded to a subset of the tech niche; the suffix '.git' is also conventionally the ending of repository paths, which may make an address read as a repo reference rather than a brand, and the term's association with an existing project and community makes commercial adoption dynamics uncertain (trademark or community-policy status: unknown). Aftermarket is likely thin and event-driven rather than sustained. Applicant facts, stated neutrally from the record: one application by Open Culture Foundation, recorded with status 'replacement' and a primary string of .ops, with zero contention on the record; a replacement-string position suggests the string was not the applicant's first target, which modestly lowers the likelihood of an aggressive commercial launch, though a community-oriented operator could still draw open-source projects. Main market uncertainty: whether the developer ecosystem embraces '.git' addresses as identities (vanity repo-style names, tool homepages) or treats the string as a technical suffix to be avoided, which would push it toward the vanity band.