About .booking domain
.booking is a brand generic top-level domain (gTLD) operated by Booking.com B.V., a subsidiary of Priceline.com. It was delegated by ICANN on July 19, 2016, with technical support managed by GoDaddy Registry. The TLD is governed under a Registry Agreement with ICANN that defines it as a "single registrant TLD," meaning all registrations are for the exclusive use of the registry operator and its affiliates.
Who can register .booking domain
Registration of .booking domain names is strictly restricted. Only Booking.com B.V., the registry operator, and its corporate affiliates are eligible to register domains. No third parties, including the general public, other businesses, or trademark holders, can register a .booking domain. This is a contractual requirement of the TLD's operation with ICANN.
How to register .booking domain
The .booking TLD is not allocated through a commercial registrar sales process. Domain names are registered internally by the registry operator, Booking.com B.V., for its own exclusive use. The registry's technical provider, GoDaddy Registry, manages the backend infrastructure. No public application or purchase mechanism exists, as the registry agreement prohibits the sale or transfer of domains to any non-affiliated third party.
Typical uses of .booking domain
This TLD is used exclusively by the Booking.com brand for its online services. As a single-registrant TLD, its primary use is to secure and protect the brand's digital namespace, preventing cybersquatting. Domains are likely used for specific marketing campaigns, product launches, or internal services, reinforcing brand identity and trust in the online travel and accommodation booking sector.
Tips for registering .booking domain
- All domains are registered and maintained solely by the registry operator, with no sales or transfers to external parties permitted.
- There is no public market for premium .booking domains, as the registry controls all registrations.
- The TLD operates under the standard ICANN registry agreement, which includes obligations for WHOIS accuracy and adherence to UDRP for any potential disputes, though disputes are highly unlikely given the closed nature of the TLD.