ds

.cw

Country-code top-level domain for Curaçao

neithersold by 1 registrar

Register
$249.99first year
Renew
$299.99a year
Transfer
$289.99to move it
Registrars
1quoting it
Lookup
neitherno public service
DNSSEC
Unsignedno DS in the root
Level
Secondmybrand.cw

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 cw

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

Every published quote in the bundled table, cheapest registration first. The figure ds prints beside .cw is the mean of the registration column — $249.99, which undercuts 7% of the 881 priced TLDs.

RegistrarRegisterRenewTransfer
101domain.com$249.99$299.99$289.99
Mean — what ds prints$249.99$299.99$289.99

List prices in US dollars, bundled with the binary and last regenerated 2026-09-09. Promotions, ICANN fees, taxes and premium names all move the real number, and a registry may decline to sell you the name at all. See Prices.

Where to register

One registrar in the bundled table publishes a registration price for .cw, which is evidence it sells it — nobody prices what they cannot sell. Cheapest first, exactly as ds mybrand --tld cw --where prints them.

Put a name in the box above and each link becomes that registrar's search for mybrand.cw, where it publishes one. This list is what the price table knows, not the whole market — see Where to register.

Who can register

No eligibility rule is on file for .cw, 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

Neither an RDAP endpoint nor a WHOIS server is on file for .cw: IANA's bootstrap does not list it and the bundled whois.json has no entry. It is left out of --tld all for that reason, and asking for it by name works only if IANA can name a server for it at the time. Anything ds cannot answer comes back UNKNOWN with the reason attached, never guessed as available.

The registry

From IANA's delegation record for .cw. .cw is a country-code TLD.

Run by
University of CuracaoBased in Curaçao. Delegated 2010-12-20, record last updated 2025-07-07.
Registry site
www.uoc.cwWhere the registry documents .cw — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Name servers
cw.cctld.authdns.ripe.netkadushi.curinfo.cwns0.ja.netns01-server.curinfo.cwns1.bna.cwns1.dns.cwns2.bna.cwThe 7 authoritative servers for the .cw 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.

  • country-code IANA Root Zone Database types it "country-code"

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

Delegated to
  • cw.cctld.authdns.ripe.net193.0.9.862a13:27c0:30::86
  • ns0.ja.net128.86.1.20193.63.94.202001:630:0:8::142001:630:0:9::14
  • ns1.bna.cw216.122.189.85
  • ns1.dns.cw194.0.28.62001:678:2c:0:194:0:28:6
  • ns2.bna.cw216.122.189.86
The 5 name servers the root hands out for .cw, with the glue addresses that come with them — 3 of them answer over IPv6. None of this is what ds queries: these servers know which names exist, not who registered them.
DNSSEC
UnsignedThe root publishes no DS record for .cw, so the chain of signatures stops at the root and a resolver has no way to prove an answer under .cw is genuine — it takes it on trust, as all of the DNS did before DNSSEC. 88 of the 1,438 TLDs in the root are in the same position. Names here still work; they are just not verifiable.

The record and the zone disagree. IANA's delegation record still lists kadushi.curinfo.cw, ns01-server.curinfo.cw, which the root zone does not carry. The zone is what resolvers use, so it is the one that counts; the record is maintained by hand and lags a change of servers.

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

Priced near it