.tj.cn

Country-code top-level domain for China — names are registered at the third level, under .cn

WHOIS

Register: —first year
Renew: —a year
Transfer: —to move it
Registrars: —quoting it
Lookup: WHOISanswers for it
DNSSEC: Signed1 DS record in the root
Level: Thirdmybrand.tj.cn

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 tj.cn

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 .tj.cn, 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 .tj.cn, 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. .tj.cn has no RDAP service, so the answer comes from WHOIS text on port 43.

WHOIS: whois.cnnic.net.cnQueried on port 43, from the bundled whois.json. The name is called free when the reply contains No matching record — text matching, which is why RDAP is preferred where it exists.

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

The registry

From IANA's delegation record for .cn — .tj.cn is a zone under it, so the registry, the servers and the dates below are .cn's. .tj.cn is a country-code TLD.

Run by: China Internet Network Information Center (CNNIC)Based in China. Delegated 1990-11-28, record last updated 2025-07-17.
Registry site: www.cnnic.cnWhere the registry documents .cn — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services: whois.cnnic.cnWhat the registry itself tells IANA it runs. Note: the bundled table asks whois.cnnic.net.cn instead — one of them is out of date, and ds falls back to asking IANA when a bundled host goes stale.
Name servers: a.dns.cnb.dns.cnc.dns.cnd.dns.cne.dns.cnns.cernet.netThe 6 authoritative servers for the .cn 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 .cn was delegated to; this is what the root actually answers with when a resolver asks it where .cn lives. .tj.cn is not in the root zone — nothing below the top level is. It resolves because .cn does, on .cn's servers.

Delegated to: a.dns.cn203.119.25.12001:dc7::1
b.dns.cn203.119.26.12001:dc7:1::1
c.dns.cn203.119.27.12001:dc7:2::1
d.dns.cn203.119.28.12001:dc7:1000::1
e.dns.cn203.119.29.12001:dc7:3::1
ns.cernet.net202.112.0.44
The 6 name servers the root hands out for .cn, with the glue addresses that come with them — 5 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 33094RSA/SHA-256 · SHA-256CCCF13ED73A83244F7D2936F0B6C3507D85C3EBC5E1BE4FB644064BC5B5FE3B2
Each one is a fingerprint of .cn'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 .tj.cn 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 cn. NS and dig +norec @a.root-servers.net cn. DS.