.tj

Country-code top-level domain for Tajikistan

WHOISsold by 1 registrar

Register: $57.99first year
Renew: $67.49a year
Transfer: $57.99to move it
Registrars: 1quoting it
Lookup: WHOISanswers for it
DNSSEC: Unsignedno DS in the root
Level: Secondmybrand.tj

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

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

Registrar	Register	Renew	Transfer
101domain.com	$57.99	$67.49	$57.99
Mean — what `ds` prints	$57.99	$67.49	$57.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 .tj, which is evidence it sells it — nobody prices what they cannot sell. Cheapest first, exactly as ds mybrand --tld tj --where prints them.

101domain.com$57.99

Put a name in the box above and each link becomes that registrar's search for mybrand.tj, 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 .tj, 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 has no RDAP service, so the answer comes from WHOIS text on port 43.

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

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

The registry

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

Run by: Information Technology CenterBased in Tajikistan. Delegated 1997-12-11, record last updated 2020-03-09.
Registry site: www.nic.tjWhere the registry documents .tj — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Name servers: ns1.nic.tjns2.tojikiston.comphloem.uoregon.edutj.cctld.authdns.ripe.netThe 4 authoritative servers for the .tj 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 .tj was delegated to; this is what the root actually answers with when a resolver asks it where .tj lives.

Delegated to: tj.cctld.authdns.ripe.net193.0.9.1172001:67c:e0::117
ns1.nic.tj91.218.160.197
ns2.tojikiston.com193.111.11.4
phloem.uoregon.edu128.223.32.352001:468:d01:20::80df:2023
The 4 name servers the root hands out for .tj, with the glue addresses that come with them — 2 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 .tj, so the chain of signatures stops at the root and a resolver has no way to prove an answer under .tj 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.

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