.cruise

Generic top-level domain

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.cruise

Check a name

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

Name

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 cruise

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 .cruise, 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 .cruise, 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. .cruise has both, so RDAP answers and WHOIS is the fallback if it does not.

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

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

The registry

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

Run by: Viking River Cruises (Bermuda) Ltd.Based in United States of America. Delegated 2016-10-21, record last updated 2023-08-11.
Registry site: www.vikingrivercruises.comWhere the registry documents .cruise — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services: rdap.identitydigital.services · whois.nic.cruiseWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers: a0.nic.cruisea2.nic.cruiseb0.nic.cruisec0.nic.cruiseThe 4 authoritative servers for the .cruise 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 .cruise was delegated to; this is what the root actually answers with when a resolver asks it where .cruise lives.

Delegated to: a0.nic.cruise65.22.192.252a01:8840:ba::25
a2.nic.cruise65.22.195.252a01:8840:bd::25
b0.nic.cruise65.22.193.252a01:8840:bb::25
c0.nic.cruise65.22.194.252a01:8840:bc::25
The 4 name servers the root hands out for .cruise, 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 33220RSA/SHA-256 · SHA-256254D748F9E700BD632010EEFFE96CC5A1DFEF5B4A85A18A1AB4962EA81F9937F
Each one is a fingerprint of .cruise'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 .cruise 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 cruise. NS and dig +norec @a.root-servers.net cruise. DS.