.食品.xn--jvr189m

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--jvr189m

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.identitydigital.services/rdapFrom IANA's bootstrap, refreshed when this page was built. The lookup is https://rdap.identitydigital.services/rdap/domain/mybrand.xn--jvr189m — a 404 means the name is free.
WHOIS: whois.nic.xn--jvr189mQueried on port 43, from the bundled whois.json. The name is called free when the reply contains domain not found — text matching, which is why RDAP is preferred where it exists.

ds mybrand --tld xn--jvr189m --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: Amazon Registry Services, Inc.Based in United States of America. Delegated 2016-01-29, record last updated 2025-06-17.
Registry site: www.nic.xn--jvr189mWhere 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.identitydigital.services · whois.nic.xn--jvr189mWhat the registry itself tells IANA it runs. They agree with what ds asks.

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.

Food & Drink Eating, drinking, cooking, and growing.

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: v0n0.nic.xn--jvr189m65.22.76.102a01:8840:4a::10
v0n1.nic.xn--jvr189m65.22.77.102a01:8840:4b::10
v0n2.nic.xn--jvr189m65.22.78.102a01:8840:4c::10
v0n3.nic.xn--jvr189m161.232.38.102a01:8840:10c::10
v2n0.nic.xn--jvr189m65.22.79.102a01:8840:4d::10
v2n1.nic.xn--jvr189m161.232.39.102a01:8840:10d::10
The 6 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 2149RSA/SHA-256 · SHA-256508BDDCCB2B2B23586882A59E145310ACA85FFB453EB073565E900466F52A39F
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--jvr189m. NS and dig +norec @a.root-servers.net xn--jvr189m. DS.