.reservation
Is .reservation a real TLD? Who’s applying to run it?
Nobody has applied for .reservation in its own right, as of 7 October 2026. Identity Digital named .reservation as the replacement string of its .biotech application.
A functional word for booking pages at hotels and restaurants; useful as a side address, rarely a business's main name.
hotels, restaurants, tour and event operators and booking platforms wanting a dedicated reservations address beside their main domain; secondarily, booking-software vendors
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 almost exactly: the English noun for the act of reserving, sold as the transaction verb of the whole travel/hospitality trade, where any operator taking bookings (or the platform that intermediates them) would want its primary identity.
Also a transaction-word generic rather than a business-category word — it names the commercial act, so its value depends on an entire inventory-and-availability industry adopting the deal-word as its address, which is the same wager .reservation makes.
A generic noun for the entitlement-to-attend half of the same booking flow, bet on being the obvious place any seller of time-slotted access puts its identity, though it labels the object sold rather than the act of holding it.
What a .reservation domain is
.reservation is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Commerce. Nobody has applied for .reservation in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .reservation domain extension real yet?
.reservation 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 .reservation domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .reservation name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .reservation was .booking, delegated on 23 July 2016.
Is .reservation a real TLD?
Not yet. .reservation is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .reservation as part of an application for another string. Every entry on this page links to its source.
- Identity Digital · first recordedICANN
“GEL2647T-T73865 · Glass Emotion, LLC · replacement string of .biotech”ICANN
“GEL2647T-T15541 · Glass Emotion, LLC · replacement string of .ify · Deactivated GEL2647T-T23460 · Glass Emotion, LLC · replacement string of .nutrition · Deactivated GEL2647T-T42189 · Glass Emotion, LLC · replacement string of .accounting · Deactivated GEL2647T-T58027 · Glass Emotion, LLC · replacement string of .advisors · Deactivated XL2625T-T30125 · XYZ.COM LLC · primary”ICANN
- Band chosen: 30-49 (usable but limited), at its lower edge. The string is a clear, single-meaning functional noun in hospitality and travel: a hotel, restaurant, spa or tour operator could plausibly route guests to name.reservation as a booking entry point. That is real utility, but it is utility as a secondary, action-oriented address next to an existing primary domain, not as a primary identity, and the string is long (eleven characters), which by analogy with other long dictionary-word TLDs such as .vacations, .holiday and .restaurant (analogy, no figures) tends to mean modest volumes, price-driven registrations and a thin aftermarket. It is not in the 50-69 band because there is no visible community that would adopt it as a primary identity and explaining the choice would still be necessary; it is not in the 10-29 band because the demand is functional and recurring (every hospitality business takes reservations) rather than vanity or event-driven, so a steady trickle of practical registrations over five years is likely. A second reading of the word (tribal reservations in North America) adds some ambiguity rather than a distinct buyer group. Applicant facts from the record, stated neutrally: the single application is by Identity Digital (Glass Emotion, LLC), recorded as a replacement string of .biotech, standard type, with zero contention recorded; a single uncontested standard application suggests an open, commercially run namespace rather than a restricted one, which is consistent with ordinary volume-and-price adoption. Registration counts, pricing and comparable sales for this or analogous strings are unknown to me under the rules here. Main market uncertainty: whether hospitality businesses actually adopt functional-verb TLDs as customer-facing booking addresses at any scale, or keep reservations inside their main domain and third-party booking widgets, leaving the TLD to defensive and speculative registrations.