ds

.yun

Generic top-level domain

RDAPInternet & Technology

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.yun

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 yun

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 .yun, 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 .yun, 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. .yun 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 is https://rdap.teleinfo.cn/domain/mybrand.yun — a 404 means the name is free.

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

The registry

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

Run by
Beijing Qihu Keji Co., Ltd.Based in China. Delegated 2016-03-18, record last updated 2025-10-24.
Registry site
www.teleinfo.cnWhere the registry documents .yun — 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 what ds asks.
Name servers
ns1.teleinfo.cnns2.teleinfoo.comns3.teleinfo.cnns4.teleinfoo.comThe 4 authoritative servers for the .yun 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

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.

  • Internet & Technology Software, hosting, data, devices, and the web itself.

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

Delegated to
  • ns1.teleinfo.cn103.61.60.12402:7d80::1
  • ns2.teleinfoo.com103.61.61.12402:7d80:8888::1
  • ns3.teleinfo.cn103.61.62.1
  • ns4.teleinfoo.com103.61.63.1
The 4 name servers the root hands out for .yun, 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 — 2 DS records in the root
  • key 27565RSA/SHA-256 · SHA-256D8B3C3D5EE497216F3920A87706F270101F63803903DE581669754AC772BAA85
  • key 33427RSA/SHA-256 · SHA-256E3EEC0D837B6CA47052A5DCB693726C6EC3D2138624ED7B6E81A7A557BF7DE60
Each one is a fingerprint of .yun'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 .yun 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 yun. NS and dig +norec @a.root-servers.net yun. DS.

Also answered by rdap.teleinfo.cn