.robotaxi
Is .robotaxi a real TLD? Who’s applying to run it?
.robotaxi is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Uber.
A buzzy but narrow word for driverless cabs: memorable, yet few businesses would make it their main web address.
autonomous ride-hailing fleet operators, their city and airport launch pages, and vehicle makers wanting a product-line address alongside their main brand domain
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 almost exactly: a plain service-category noun that ride operators and dispatch businesses put their primary identity on, winning only if the everyday word for the ride itself is worth owning as a namespace.
The identical category-noun-for-a-ride bet, aimed at the same registrant class of fleet and booking operators, differing only in which synonym the market says.
A coined compound naming a brand-new technology-defined product class rather than an established trade, so the plausible registrant pool is the few firms racing to own the category and the bet is that the category label itself sticks.
What a .robotaxi domain is
.robotaxi is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. One application for it is on ICANN’s Reveal Day list.
Is the .robotaxi domain extension real yet?
.robotaxi 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 .robotaxi domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .robotaxi name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .robotaxi was .taxi, delegated on 7 May 2015.
Is .robotaxi a real TLD?
Not yet. .robotaxi is not in the DNS root, so nothing resolves under it. It’s here because .robotaxi is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Uber · first recordedICANN
- Band chosen: 10-29 (vanity/narrow). The string names a single product category that is operated by a small number of large companies, each of which already carries a strong brand it would use as its primary identity; the plausible use is a secondary marketing or city-launch address (by analogy, the way vehicle-category and vertical TLDs such as .taxi, .car and .auto have been used, which is an inference from analogy, not a verified count). It is not in the 30-49 band because there is no realistic volume of registrants: ordinary taxi firms, dispatchers and drivers do not run robotaxis, so neither price-driven volume nor a thin aftermarket is likely to form in five years. It is not in the 1-9 band because the term's cultural salience is rising, it is short and self-explanatory, and the record shows one confirmed standard (not brand) application from Uber (RENNPFERD, LLC), which is a neutral indication that a company in the mobility space sees use for the namespace; a standard application leaves general availability open, which is assumed here. Main market uncertainty: whether the word 'robotaxi' remains the public's label for the category over five years or is displaced by brand names and other generic terms, which would decide whether even the secondary-address use materialises.