What is .booking?
.booking entered the DNS root zone on July 23, 2016, 10 years ago. It came out of ICANN's New gTLD Program, the 2012 application round that grew the root from 22 generic TLDs to well over a thousand.
Booking.com B.V. also runs one other TLD, including .hotels.
On the technical side, .booking is served by 6 authoritative name servers, every one of them reachable over IPv6. It is also DNSSEC-signed: the root zone carries a DS record for .booking, which lets validating resolvers check its answers cryptographically. Registration data is published over RDAP.
Same registry, other endings
1 other TLD shares this operator.
.booking FAQ
What does .booking mean?
.booking is a generic top-level domain named for the word "booking", and it's aimed at travel & hospitality. It doesn't belong to any country.
What is .booking used for?
.booking is mostly used for travel & hospitality. Like most gTLDs, it's a label of intent rather than a guarantee — check the site, not just the ending.
What country is .booking?
None. .booking is a generic top-level domain, so it isn't tied to any country.
Who owns the .booking domain extension?
Booking.com B.V. operates .booking as its registry, under a registry agreement with ICANN.
When was .booking created?
.booking was delegated to the DNS root zone on July 23, 2016.
Is .booking a valid domain?
Yes. .booking is an active top-level domain in the DNS root zone, delegated in 2016, so .booking addresses work in every browser.
Can I buy a .booking domain?
.booking names are sold through ICANN-accredited registrars. Some gTLDs restrict who can register, so read Booking.com B.V.'s policy if you're unsure.
Is .booking DNSSEC-signed?
Yes, the root zone holds a DS record for .booking.
Sources
Data from IANA root zone version 2026102000. Last changed May 11, 2024. Spotted something wrong? Tell us.
