.xihuan
Generic top-level domain
- Register
- —first year
- Renew
- —a year
- Transfer
- —to move it
- Registrars
- —quoting it
- Lookup
- RDAPanswers for it
- DNSSEC
- Signed2 DS records in the root
- Level
- Secondmybrand.xihuan
Check a name
One command, straight against the registry — no account, no page to load.
ds mybrand --tld xihuanAdd --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 .xihuan, 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 .xihuan, 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. .xihuan has an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.
- RDAP
https://rdap.teleinfo.cnFrom IANA's bootstrap, refreshed when this page was built. The lookup ishttps://rdap.teleinfo.cn/domain/mybrand.xihuan— a 404 means the name is free.
ds mybrand --tld xihuan --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .xihuan today. See Accuracy notes.
The registry
From IANA's delegation record for .xihuan. .xihuan is a generic TLD.
- Run by
- Beijing Qihu Keji Co., Ltd.Based in China. Delegated 2016-03-18, record last updated 2026-08-11.
- Registry site
- www.teleinfo.cnWhere the registry documents .xihuan — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
- Published services
rdap.teleinfo.cn · whois.teleinfo.cnWhat the registry itself tells IANA it runs. They agree with whatdsasks.- Name servers
ns1.teleinfo.cnns2.teleinfoo.comns3.teleinfo.cnns4.teleinfoo.comThe 4 authoritative servers for the .xihuan 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.
genericIANA Root Zone Database types it "generic"new-gtldICANN delegated it on or after 2013-10-23, when the 2013 round opened — seedelegated
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 .xihuan was delegated to; this is what the root actually answers with when a resolver asks it where .xihuan lives.
- Delegated to
ns1.teleinfo.cn103.61.60.12402:7d80::1ns2.teleinfoo.com103.61.61.12402:7d80:8888::1ns3.teleinfo.cn103.61.62.1ns4.teleinfoo.com103.61.63.1
dsqueries: these servers know which names exist, not who registered them.- DNSSEC
- Signed — 2 DS records in the root
- key 27565RSA/SHA-256 · SHA-256
B77F15373B8AF8E7BA2D8641701AE833416F8D439BBDAEE71D18CE55EFDE7903 - key 33427RSA/SHA-256 · SHA-256
1061B1AACADA68D55B091340A0765746A4FA68530D47FAA10EDFCD3237E3748C
- key 27565RSA/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 xihuan. NS and dig +norec @a.root-servers.net xihuan. DS.