.co.tz
Country-code top-level domain for Tanzania — names are registered at the third level, under .tz
- 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.co.tz
Check a name
One command, straight against the registry — no account, no page to load.
ds mybrand --tld co.tzAdd --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 .co.tz, 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 .co.tz, 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. .co.tz has no RDAP service, so the answer comes from WHOIS text on port 43.
- WHOIS
whois.tznic.or.tzQueried on port 43, from the bundled whois.json. The name is called free when the reply containsNo entries found— text matching, which is why RDAP is preferred where it exists.
ds mybrand --tld co.tz --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .co.tz today. See Accuracy notes.
The registry
From IANA's delegation record for .tz — .co.tz is a zone under it, so the registry, the servers and the dates below are .tz's. .co.tz is a country-code TLD.
- Run by
- Tanzania Communications Regulatory AuthorityBased in Tanzania, the United Republic of. Delegated 1995-07-14, record last updated 2026-06-08.
- Registry site
- karibu.tzWhere the registry documents .tz — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
- Published services
rdap.tznic.or.tz · whois.tznic.or.tzWhat the registry itself tells IANA it runs. They agree with whatdsasks.- Name servers
fork.sth.dnsnode.netns.anycast.co.tzns2.tznic.or.tzrip.psg.comtz-e.ns.nic.czThe 5 authoritative servers for the .tz zone — what the root delegates to. Nothingdsqueries 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-codeIANA 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 .tz was delegated to; this is what the root actually answers with when a resolver asks it where .tz lives. .co.tz is not in the root zone — nothing below the top level is. It resolves because .tz does, on .tz's servers.
- Delegated to
ns.anycast.co.tz204.61.216.152001:500:14:6015:ad::1ns2.tznic.or.tz196.216.162.672001:43f8:e0:1::67rip.psg.com147.28.0.392001:418:1::39fork.sth.dnsnode.net77.72.229.2542a01:3f0:0:306::53tz-e.ns.nic.cz185.43.134.112001:148f:fffd::11
dsqueries: these servers know which names exist, not who registered them.- DNSSEC
- Signed — 1 DS record in the root
- key 30234ECDSA P-256/SHA-256 · SHA-256
3D83825B9F7D66F9B28B5566BA5371798E8D3B88EF079BB88F52617811C1B9A0
- key 30234ECDSA P-256/SHA-256 · SHA-256
Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net tz. NS and dig +norec @a.root-servers.net tz. DS.