.crs

Generic top-level domain

RDAP + WHOIS

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

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 crs

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 .crs, 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 .crs, 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. .crs 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.crs — a 404 means the name is free.
WHOIS: whois.nic.crsQueried 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 crs --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .crs today. See Accuracy notes.

The registry

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

Run by: Federated Co-operatives LimitedBased in Canada. Delegated 2014-08-28, record last updated 2023-08-11.
Published services: rdap.identitydigital.services · whois.nic.crsWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers: a0.nic.crsa2.nic.crsb0.nic.crsc0.nic.crsThe 4 authoritative servers for the .crs 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

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 .crs was delegated to; this is what the root actually answers with when a resolver asks it where .crs lives.

Delegated to: a0.nic.crs65.22.112.252a01:8840:6e::25
a2.nic.crs65.22.115.252a01:8840:71::25
b0.nic.crs65.22.113.252a01:8840:6f::25
c0.nic.crs65.22.114.252a01:8840:70::25
The 4 name servers the root hands out for .crs, 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 63622RSA/SHA-256 · SHA-256D1647F1F8B7A8508B81F1D822C27581B628F7351EE8D99B8DC32A2BD802E0C37
Each one is a fingerprint of .crs'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 .crs 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 crs. NS and dig +norec @a.root-servers.net crs. DS.