.ryukyu
Generic top-level domain
- Register
- $24.99first year
- Renew
- $31.49a year
- Transfer
- $31.99to move it
- Registrars
- 2quoting it
- Lookup
- RDAPanswers for it
- DNSSEC
- Signed1 DS record in the root
- Level
- Secondmybrand.ryukyu
Check a name
One command, straight against the registry — no account, no page to load.
ds mybrand --tld ryukyuAdd --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
Every published quote in the bundled table, cheapest registration first. The figure ds prints beside .ryukyu is the mean of the registration column — $24.99, which undercuts 69% of the 881 priced TLDs.
| Registrar | Register | Renew | Transfer |
|---|---|---|---|
| namecheap.comcheapest | $17.98 | $22.98 | — |
| 101domain.com | $31.99 | $39.99 | $31.99 |
Mean — what ds prints | $24.99 | $31.49 | $31.99 |
List prices in US dollars, bundled with the binary and last regenerated 2026-09-09. Promotions, ICANN fees, taxes and premium names all move the real number, and a registry may decline to sell you the name at all. See Prices.
Where to register
2 registrars in the bundled table publish a registration price for .ryukyu, which is evidence they sell it — nobody prices what they cannot sell. Cheapest first, exactly as ds mybrand --tld ryukyu --where prints them.
Put a name in the box above and each link becomes that registrar's search for mybrand.ryukyu, where it publishes one. This list is what the price table knows, not the whole market — see Where to register.
Who can register
No eligibility rule is on file for .ryukyu, 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. .ryukyu has an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.
- RDAP
https://rdap.gmoregistry.net/rdapFrom IANA's bootstrap, refreshed when this page was built. The lookup ishttps://rdap.gmoregistry.net/rdap/domain/mybrand.ryukyu— a 404 means the name is free.
ds mybrand --tld ryukyu --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .ryukyu today. See Accuracy notes.
The registry
From IANA's delegation record for .ryukyu. .ryukyu is a generic TLD.
- Run by
- BRregistry, Inc.Based in Japan. Delegated 2014-03-13, record last updated 2019-08-20.
- Registry site
- www.gmo-registry.comWhere the registry documents .ryukyu — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
- Published services
rdap.gmoregistry.net · whois.nic.ryukyuWhat the registry itself tells IANA it runs. They agree with whatdsasks.- Name servers
a.gmoregistry.netb.gmoregistry.netk.gmoregistry.netl.gmoregistry.netThe 4 authoritative servers for the .ryukyu 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
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.
- Places Cities, regions, and parts of the world.
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 .ryukyu was delegated to; this is what the root actually answers with when a resolver asks it where .ryukyu lives.
- Delegated to
a.gmoregistry.net37.209.192.42001:dcd:1::4b.gmoregistry.net37.209.194.42001:dcd:2::4k.gmoregistry.net37.209.196.4l.gmoregistry.net37.209.198.42001:dcd:4::4
dsqueries: these servers know which names exist, not who registered them.- DNSSEC
- Signed — 1 DS record in the root
- key 52505RSA/SHA-256 · SHA-256
A19F9645F1832C3A1550F695DBA8F68E26DAA32BE47967F71B29A4A865D834B8
- key 52505RSA/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 ryukyu. NS and dig +norec @a.root-servers.net ryukyu. DS.