Skip to content

.tci

Generic top-level domain

RDAP

Register
—first year
Renew
—a year
Transfer
—to move it
Registrars
—quoting it
Lookup
RDAPanswers for it
DNSSEC
Signed1 DS record in the root
Level
Secondmybrand.tci

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.

Check a name under .tcids mybrand --tld tci

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 .tci, 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 .tci, 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. .tci has an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.

RDAP
https://rdap.nominet.uk/tciFrom IANA's bootstrap, refreshed when this page was built. The lookup is https://rdap.nominet.uk/tci/domain/mybrand.tci — a 404 means the name is free.

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

The registry

From IANA's delegation record for .tci. .tci is a generic TLD.

Run by
Emergency Back-End Registry Operator Program - ICANNBased in United States of America. Delegated 2015-11-25, record last updated 2025-01-30.
Registry site
icann.orgWhere the registry documents .tci — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services
rdap.nominet.ukWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers
dns1.emdns.ukdns2.emdns.ukdns3.emdns.ukdns4.emdns.ukdnsa.emdns.ukdnsb.emdns.ukdnsc.emdns.ukdnsd.emdns.ukThe 8 authoritative servers for the .tci 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.

  • generic IANA Root Zone Database types it "generic"
  • new-gtld ICANN delegated it on or after 2013-10-23, when the 2013 round opened — see delegated
  • contract-terminated ICANN records the registry contract as terminated

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

Delegated to
  • dns1.emdns.uk213.248.217.1532a01:618:401::153
  • dns2.emdns.uk103.49.81.1532401:fd80:401::153
  • dns3.emdns.uk213.248.221.1532a01:618:405::153
  • dns4.emdns.uk43.230.49.1532401:fd80:405::153
  • dnsa.emdns.uk156.154.100.32001:502:ad09::3
  • dnsb.emdns.uk156.154.101.32001:502:2eda::3
  • dnsc.emdns.uk156.154.102.32610:a1:1009::3
  • dnsd.emdns.uk156.154.103.32610:a1:1010::3
The 8 name servers the root hands out for .tci, with the glue addresses that come with them — every one of them answers 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 52844RSA/SHA-256 · SHA-2568C7871967D2F0D9C396AF5F498EDCCBB2BB4F9B29031AEAF3D103343C45C2EA7
Each one is a fingerprint of .tci'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 .tci 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 tci. NS and dig +norec @a.root-servers.net tci. DS.