Skip to content

.jprs

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

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.

Check a name under .jprsds mybrand --tld jprs

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

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

The registry

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

Run by
Japan Registry Services Co., Ltd.Based in Japan. Delegated 2014-12-18, record last updated 2025-09-30.
Registry site
nic.jprsWhere the registry documents .jprs — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services
rdap.nic.jprs · whois.nic.jprsWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers
tld1.nic.jprstld2.nic.jprstld3.nic.jprstld4.nic.jprstld5.nic.jprsThe 5 authoritative servers for the .jprs 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 .jprs was delegated to; this is what the root actually answers with when a resolver asks it where .jprs lives.

Delegated to
  • tld1.nic.jprs103.47.2.12001:dda::1
  • tld2.nic.jprs117.104.133.162001:218:3001::1
  • tld3.nic.jprs65.22.40.12a01:8840:1ba::1
  • tld4.nic.jprs103.198.210.12403:2880::1
  • tld5.nic.jprs65.22.40.1292a01:8840:1ba::129
The 5 name servers the root hands out for .jprs, 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 1915RSA/SHA-256 · SHA-256D2D8B07B59B3127E2890A593A1424CBA519989A20D39A1809B860314A6BEC199
Each one is a fingerprint of .jprs'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 .jprs 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 jprs. NS and dig +norec @a.root-servers.net jprs. DS.