ds

.சிங்கப்பூர்.xn--clchc0ea0b2g2a9gcd

Internationalised 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.சிங்கப்பூர்

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.

ds mybrand --tld xn--clchc0ea0b2g2a9gcd

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 .சிங்கப்பூர், 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 .சிங்கப்பூர், 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. .சிங்கப்பூர் has an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.

RDAP
https://rdap.ta.sgnic.sg/rdapFrom IANA's bootstrap, refreshed when this page was built. The lookup is https://rdap.ta.sgnic.sg/rdap/domain/mybrand.xn--clchc0ea0b2g2a9gcd — a 404 means the name is free.

ds mybrand --tld xn--clchc0ea0b2g2a9gcd --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .சிங்கப்பூர் today. See Accuracy notes.

The registry

From IANA's delegation record for .சிங்கப்பூர். .சிங்கப்பூர் is a country-code TLD.

Run by
Singapore Network Information Centre (SGNIC) Pte LtdBased in Singapore. Delegated 2011-02-05, record last updated 2026-02-11.
Registry site
www.sgnic.sgWhere the registry documents .சிங்கப்பூர் — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services
rdap.ta.sgnic.sg · whois.ta.sgnic.sgWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers
dsany2.sgnic.sgdsany3.sgnic.sgdsany4.sgnic.sgns4.apnic.netpch.sgzones.sgThe 5 authoritative servers for the .சிங்கப்பூர் 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"
  • idn the label is punycode — an internationalised TLD; unicode is how it reads

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 .சிங்கப்பூர் was delegated to; this is what the root actually answers with when a resolver asks it where .சிங்கப்பூர் lives.

Delegated to
  • ns4.apnic.net202.12.31.532001:dd8:12::53
  • pch.sgzones.sg204.61.216.572001:500:14:6057:ad::1
  • dsany2.sgnic.sg185.159.197.1702620:10a:80aa::170
  • dsany3.sgnic.sg185.159.198.1702620:10a:80ab::170
  • dsany4.sgnic.sg45.142.220.652a0e:dbc0:1::65
The 5 name servers the root hands out for .சிங்கப்பூர், 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 47752RSA/SHA-256 · SHA-256F76B1D7F3857A37138B77BEED55B38160EE01FC53DAE8DEDB41B91B4C443BE71
Each one is a fingerprint of .சிங்கப்பூர்'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 .சிங்கப்பூர் 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 xn--clchc0ea0b2g2a9gcd. NS and dig +norec @a.root-servers.net xn--clchc0ea0b2g2a9gcd. DS.