.transit
Is .transit a real TLD? Who’s applying to run it?
Nobody has applied for .transit in its own right, as of 7 October 2026. NextGEN TLDs GmbH named .transit as the replacement string of its .text application.
A clear word for buses, trains and logistics, but its natural buyers mostly live on government and city domains already.
public transit agencies and transit-technology or logistics companies wanting a descriptive address for route, ticketing or freight-tracking services
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.
Both are plain generic nouns naming a mode of passenger movement, sold to the fragmented operators of that mode as a trade-wide namespace, so each depends on thousands of small incumbents choosing to re-badge an identity they already have.
Same bet as the target in form — a short, everyday transport-service noun offered to the operators of that service — but it is the colloquial register of an existing string rather than the sector's own umbrella term, so its buyer pool is narrower and more consumer-facing.
The nearest structural match for the target's abstract sector-umbrella shape: an infrastructure-industry noun whose natural registrants are agencies, utilities and sector bodies with entrenched institutional identities, not a consumer trade looking for a catchy address.
What a .transit domain is
.transit is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Infrastructure. Nobody has applied for .transit in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .transit domain extension real yet?
.transit 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 .transit domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .transit name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .transit was .taxi, delegated on 7 May 2015.
Is .transit a real TLD?
Not yet. .transit is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .transit as part of an application for another string. Every entry on this page links to its source.
- NextGEN TLDs GmbH · first recordedICANN
“NTG2671T-T27988 · NextGEN TLDs GmbH · replacement string of .text”ICANN
“GEL2647T-T15541 · Glass Emotion, LLC · primary · contention set 2026-116 NSL2674T-T66583 · NAME SPACE LLC · primary · contention set 2026-116 NTG2671T-T35907 · NextGEN TLDs GmbH · replacement string of .tkns · Deactivated XL2625T-T36661 · XYZ.COM LLC · replacement string of .dao · Deactivated”ICANN
- Band chosen: 10-29 (vanity/narrow), upper part. The string is a plain, well-understood English word with two real meanings (passenger transport; goods or data in transit), so it is not in the 1-9 band: a transit-tech startup, a freight forwarder or a city could plausibly register a descriptive name on it. It is not in the 30-49 band because the natural anchor buyers, public transit agencies, are overwhelmingly public-sector bodies that identify through government, city or country-code namespaces, and commercial transit-tech brands tend to pick mainstream TLDs rather than a sector word. By analogy (flagged as analogy), the 2012-round transport-flavoured strings such as .taxi, .cab, .limo and .delivery reached only modest registration bases with little primary-identity use and thin aftermarkets, and .transit is narrower than those because its dominant buyer group is less commercial. The record shows one application, by NextGEN TLDs GmbH, filed as a standard (not community or geographic) application and recorded as a replacement string of .text; no transit-industry sponsor or community backing is recorded, which gives no basis to expect agency-driven adoption. Main market uncertainty: whether any sizeable group of transit agencies or transit-data platforms would adopt a commercial gTLD as a primary identity rather than treating it as a redirect or defensive name.