ds

.sakura

Generic top-level domain

RDAP + WHOIS

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

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 sakura

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

RDAP
https://rdap.nic.sakura/rdapFrom IANA's bootstrap, refreshed when this page was built. The lookup is https://rdap.nic.sakura/rdap/domain/mybrand.sakura — a 404 means the name is free.
WHOIS
whois.nic.sakuraQueried 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 sakura --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .sakura today. See Accuracy notes.

The registry

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

Run by
SAKURA internet Inc.Based in Japan. ICANN records the contracted registry operator as SAKURA Internet Inc. Delegated 2015-06-04, record last updated 2025-12-03.
Registry site
dot-sakura.sakura.ad.jpWhere the registry documents .sakura — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services
rdap.nic.sakura · whois.nic.sakuraWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers
tld1.nic.sakuratld2.nic.sakuratld3.nic.sakuratld5.nic.sakuraThe 4 authoritative servers for the .sakura 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

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

Delegated to
  • tld1.nic.sakura103.47.2.32001:dda::3
  • tld2.nic.sakura117.104.133.182001:218:3001::3
  • tld3.nic.sakura65.22.40.92a01:8840:1ba::9
  • tld5.nic.sakura65.22.40.1372a01:8840:1ba::137
The 4 name servers the root hands out for .sakura, 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 52330RSA/SHA-256 · SHA-2561EC9C8BB9DEC28F30DE9520FAC9478B2DC3BE4B6E12BC7C5469AC3E0E3FD63CB
Each one is a fingerprint of .sakura'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 .sakura 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 sakura. NS and dig +norec @a.root-servers.net sakura. DS.