ds

.hotels

Generic top-level domain

RDAP + WHOISTravel & Hospitality

Register
—first year
Renew
—a year
Transfer
—to move it
Registrars
—quoting it
Lookup
RDAP + WHOISanswers for it
DNSSEC
Signed1 DS record in the root
Level
Secondmybrand.hotels

Check a name

One command, straight against the registry — no account, no page to load.

Fills the command and the registrar links below in with your own name. The page is static — nothing is looked up here, and nothing you type leaves the browser.

ds mybrand --tld hotels

Add --where for the registrars and the registry's rules, --registry for the server that answered, or --all-info for everything at once.

What it costs

No registrar in the price table bundled with ds quotes .hotels, so the CLI prints no figure beside it — one of 927 such TLDs. That is a gap in the table as often as it is a TLD nobody sells. See Prices for supplying your own table with --pricing-file.

Who can register

No eligibility rule is on file for .hotels, which is not the same as a promise that it is open: the list is hand-maintained and covers the restricted TLDs a registrar is likely to offer you. Check the registry's own page before counting on a name. 81 TLDs do carry a rule — see Who can register.

How ds answers for it

RDAP first, WHOIS second — the same order for every TLD. .hotels has both, so RDAP answers and WHOIS is the fallback if it does not.

RDAP
https://rdap.nic.hotelsFrom IANA's bootstrap, refreshed when this page was built. The lookup is https://rdap.nic.hotels/domain/mybrand.hotels — a 404 means the name is free.
WHOIS
whois.nic.hotelsQueried on port 43, from the bundled whois.json. The name is called free when the reply contains no data found — text matching, which is why RDAP is preferred where it exists.

ds mybrand --tld hotels --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .hotels today. See Accuracy notes.

The registry

From IANA's delegation record for .hotels. .hotels is a generic TLD.

Run by
Booking.com B.V.Based in Netherlands. Delegated 2016-09-16, record last updated 2024-05-11.
Registry site
www.booking.comWhere the registry documents .hotels — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services
rdap.nic.hotels · whois.nic.hotelsWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers
a.nic.hotelsb.nic.hotelsc.nic.hotelsns1.dns.nic.hotelsns2.dns.nic.hotelsns3.dns.nic.hotelsThe 6 authoritative servers for the .hotels zone — what the root delegates to. Nothing ds queries directly; they are what makes a registered name resolve.

What it is

Derived from the root zone and ICANN's registry list — each one is a fact with a source.

  • generic IANA Root Zone Database types it "generic"
  • new-gtld ICANN delegated it on or after 2013-10-23, when the 2013 round opened — see delegated

What it is for

Our reading, not a fact — nothing in the root zone says what a TLD means. Hand-maintained in tld-categories.json.

  • Travel & Hospitality Getting there, and staying there.

In the root zone

The delegation itself, read out of the root zone — serial 2026090900, on 2026-09-09. The registry section above is IANA's record of what .hotels was delegated to; this is what the root actually answers with when a resolver asks it where .hotels lives.

Delegated to
  • a.nic.hotels37.209.192.102001:dcd:1::10
  • b.nic.hotels37.209.194.102001:dcd:2::10
  • c.nic.hotels37.209.196.102001:dcd:3::10
  • ns1.dns.nic.hotels156.154.169.32610:a1:1071::1:3
  • ns2.dns.nic.hotels156.154.170.32610:a1:1072::1:3
  • ns3.dns.nic.hotels156.154.171.32610:a1:1073::1:3
The 6 name servers the root hands out for .hotels, with the glue addresses that come with them — every one of them answers over IPv6. None of this is what ds queries: these servers know which names exist, not who registered them.
DNSSEC
Signed — 1 DS record in the root
  • key 51700RSA/SHA-256 · SHA-256844A568CAAB77E76130C1551AC820B3A41A3C39F6419BA2411F9E3D3A581765E
Each one is a fingerprint of .hotels's own signing key, published by the root and signed with the root's key — which is how a resolver that trusts only one key can prove an answer under .hotels came from its registry and was not tampered with in transit. It says nothing about who owns a name or whether one is free.

Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net hotels. NS and dig +norec @a.root-servers.net hotels. DS.