.transport
Is .transport a real TLD? Who’s applying to run it?
.transport is contested: 2 applications for it are on ICANN’s Reveal Day list, as of 7 October 2026. They are XYZ Registry and Identity Digital.
A clear industry word that freight, transit and mobility firms could use, but sector TLDs like this rarely become a company's main address.
freight and logistics operators, transit agencies, mobility startups and transport consultancies wanting a descriptive secondary or campaign address
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 bare generic sector noun pitched at an entire infrastructure industry, where success depends on B2B operators and trade bodies agreeing to wear a sector label as their primary identity instead of .com.
Same bet: a long, unabbreviated industry noun whose buyers are commercial firms and associations inside one regulated trade, wagering that sector credibility outweighs the cost of a long string.
Same kind of open generic serving the movement-of-goods trade, but it names a service a company sells rather than the sector a company belongs to, so it pulls marketing pages rather than corporate identity.
What a .transport domain is
.transport is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Commerce category. 2 applications for it are on ICANN’s Reveal Day list.
Is the .transport domain extension real yet?
.transport 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 .transport domain?
You can’t yet. A .transport 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 .transport was .energy, delegated on 1 November 2014.
Is .transport a real TLD?
Not yet. .transport is not in the DNS root, so nothing resolves under it. It’s here because .transport is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
“MH2645T-T36407 · Mystic Hammer, LLC · primary · contention set 2026-234 XL2625T-T32770 · XYZ.COM LLC · primary · contention set 2026-234”ICANN
- Band chosen: 30-49 (usable but limited). The string is a plain, universally understood sector word covering freight, passenger transit, shipping and mobility, so it reads credibly and a real population of businesses and agencies could register descriptive names on it. It is not in the 50-69 band because, by analogy with the sector-vertical TLDs from the earlier new-gTLD round (taxi, limo, flights, cruises, the auto/car family — flagged as analogy), industry-word TLDs have tended to draw modest registration volumes, mostly defensive or secondary use, with established operators keeping their primary identity on legacy namespaces and little aftermarket beyond a handful of generic one-word names; nothing in the verified facts suggests a different trajectory here. It is not in the 10-29 band because the demand is not event-driven or novelty-based: transport is a large, durable industry with many small and mid-size firms, and a nine-letter string that says exactly what the business does is a plausible primary identity for a new logistics or mobility company, unlike a joke or vanity string. Both recorded applicants are portfolio registries (Identity Digital and XYZ, per the verified facts), which by analogy with their other strings suggests broad registrar distribution and promotional pricing, supporting volume rather than premium positioning. Main market uncertainty: whether transit authorities and freight operators — conservative buyers who favour established namespaces — would adopt a sector TLD at all, versus the registrations being almost entirely descriptive secondaries and speculative holds.