.慈善.xn--30rr7y

Internationalised top-level domain

Register: —first year
Renew: —a year
Transfer: —to move it
Registrars: —quoting it
Lookup: RDAP + WHOISanswers 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.

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 xn--30rr7y

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 both, so RDAP answers and WHOIS is the fallback if it does not.

RDAP: https://rdap.zdnsgtld.com/xn--30rr7yFrom IANA's bootstrap, refreshed when this page was built. The lookup is https://rdap.zdnsgtld.com/xn--30rr7y/domain/mybrand.xn--30rr7y — a 404 means the name is free.
WHOIS: whois.gtld.zdns.cnQueried on port 43, from the bundled whois.json. The name is called free when the reply contains the queried object does not exist — text matching, which is why RDAP is preferred where it exists.

ds mybrand --tld xn--30rr7y --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 generic TLD.

Run by: Excellent First LimitedBased in Cayman Islands. Delegated 2015-03-12, record last updated 2026-05-22.
Registry site: www.cishan.wangWhere 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.zdnsgtld.com · whois.gtld.zdns.cnWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers: a.zdnscloud.cnb.zdnscloud.cnc.zdnscloud.comd.zdnscloud.comf.zdnscloud.cng.zdnscloud.comi.zdnscloud.cnj.zdnscloud.comThe 8 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.

generic IANA Root Zone Database types it "generic"
idn the label is punycode — an internationalised TLD; unicode is how it reads
new-gtld ICANN delegated it on or after 2013-10-23, when the 2013 round opened — see delegated

What it is for

Our reading, not a fact — nothing in the root zone says what a TLD means. Hand-maintained in tld-categories.json.

People & Community Family, friends, charity, and the groups people belong to.

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: a.zdnscloud.cn203.99.24.1
b.zdnscloud.cn203.99.25.1
c.zdnscloud.com203.99.26.1
d.zdnscloud.com203.99.27.1
f.zdnscloud.cn116.169.54.111
g.zdnscloud.com223.72.199.37
i.zdnscloud.cn2401:8d00:1::1
j.zdnscloud.com2401:8d00:2::1
The 8 name servers the root hands out for .慈善, 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: Signed — 1 DS record in the root
key 44210RSA/SHA-256 · SHA-256CA8C1B37378E7EBA858C4FE9BAD7BD6748E70DA47639C3A0E31DB1F71F66F467
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--30rr7y. NS and dig +norec @a.root-servers.net xn--30rr7y. DS.