.cm

Country-code top-level domain for Cameroon

RDAP + WHOISsold by 2 registrars

Register: $128.23first year
Renew: $159.74a year
Transfer: $115.49to move it
Registrars: 2quoting it
Lookup: RDAP + WHOISanswers for it
DNSSEC: Signed1 DS record in the root
Level: Secondmybrand.cm

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 cm

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 .cm is the mean of the registration column — $128.23, which undercuts 12% of the 881 priced TLDs.

Registrar	Register	Renew	Transfer
101domain.comcheapest	$115.49	$146.49	$115.49
namecheap.com	$140.98	$172.98	—
Mean — what `ds` prints	$128.23	$159.74	$115.49

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

2 registrars in the bundled table publish a registration price for .cm, which is evidence they sell it — nobody prices what they cannot sell. Cheapest first, exactly as ds mybrand --tld cm --where prints them.

Put a name in the box above and each link becomes that registrar's search for mybrand.cm, 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 .cm, 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. .cm has both, so RDAP answers and WHOIS is the fallback if it does not.

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

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

The registry

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

Run by: Agence Nationale des Technologies de l'Information et de la Communication (ANTIC)Based in Cameroon. Delegated 1995-04-29, record last updated 2025-07-15.
Registry site: www.nic.cmWhere the registry documents .cm — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services: rdap.nic.cm · whois.nic.cmWhat the registry itself tells IANA it runs. Note: the bundled table asks whois.netcom.cm instead — one of them is out of date, and ds falls back to asking IANA when a bundled host goes stale.
Name servers: auth02.ns.uu.netns-cm.afrinic.netns-cm.nic.frns.itu.chns1.nic.cmns2.nic.cmphloem.uoregon.eduThe 7 authoritative servers for the .cm 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 .cm was delegated to; this is what the root actually answers with when a resolver asks it where .cm lives.

Delegated to: ns.itu.ch156.106.192.1212a00:7580:60:2141::10
ns1.nic.cm195.24.205.60
ns2.nic.cm195.24.205.61
ns-cm.nic.fr194.0.9.12001:678:c::1
ns-cm.afrinic.net196.216.168.672001:43f8:120::67
auth02.ns.uu.net198.6.1.82
phloem.uoregon.edu128.223.32.352001:468:d01:20::80df:2023
The 7 name servers the root hands out for .cm, with the glue addresses that come with them — 4 of them answer 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 45784ECDSA P-256/SHA-256 · SHA-256BC03884AE075280B78A03306EBCD816E29E014A74247C68887FF1B37D22F81F5
Each one is a fingerprint of .cm'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 .cm 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 cm. NS and dig +norec @a.root-servers.net cm. DS.