.jp WHOIS Lookup

Yes, the holder's name is published. JPRS gives it on two lines: [登録者名] in Japanese and [Registrant] in English. In the jprs.jp record we measured on 4 October 2026, both carried the name of an organisation, once in Japanese script and once in Latin letters. No value in the reply was masked or replaced with REDACTED, so the name you read is the one held in the registry database. To find out who owns a .jp address, start with those two lines.

Through the Contact Information [公開連絡窓口] block, the public contact point JPRS includes in the reply. In our measurement it held a name, an email address, a postal code, an address in Japanese and English, a phone number and a fax number, and the name matched the holding organisation. When you write, give the exact domain name and the reason for your message. Bear in mind that the notice at the head of the reply restricts use of the data to network administration purposes, so check that your enquiry fits that use.

Read the [有効期限] line, which means expiry date. JPRS writes dates year/month/day: in the measured jprs.jp record it read 2027/02/28, that is 28 February 2027. The registration date sits on the [登録年月日] line (2001/02/02, 2 February 2001), and [最終更新] gives the last update with a time and the JST time zone. Because the year comes first, you cannot mix up the day and the month, whatever date convention you are used to.

JPRS answers in both languages by default: each label is in square brackets, some in Japanese and some in English, and names and addresses arrive in both scripts. The notice at the head of the reply describes the English-only option: add /e to the end of the query, as in whois -h whois.jprs.jp xxx/e, and the Japanese output is suppressed. That helps when your terminal or script cannot display Japanese characters.

They are the values of the [ロック状態] (lock status) lines, and the measured record carried both. Read literally, DomainTransferLocked says the domain cannot currently be transferred and AgentChangeLocked says a change of agent (Agent) is locked. These are JPRS's own values rather than EPP codes such as clientTransferProhibited, and they sit apart from the [状態] line, which read Active. If you are planning to move a .jp name, check these two lines first.

Only port 43. IANA's RDAP bootstrap registry defines no endpoint for .jp, which our measurement on 4 October 2026 confirmed. Registration data for .jp therefore comes as plain text from whois.jprs.jp, queried with the bare domain name. That text uses its own bracketed layout: during the measurement our automatic parser did not recognise it, and the fields were read from the raw reply by hand. If you write your own scripts, that format needs handling of its own.

Because the JPRS reply has no registrar line. The record we measured gave the domain, the holder, the name servers, the dates, the state, the locks and a public contact block, but not the company through which the name was registered, and no separate abuse contact either. With .com the picture is reversed: the registry record names the registrar, and the holder's details sit with that registrar. For a side-by-side view, see the .com WHOIS lookup.

Yes. The .jp zone has a DS record in the root, so the chain of trust starts there. The [Signing Key] line in the WHOIS reply concerns the individual domain: for jprs.jp it read 7240 8 2 followed by a digest of 64 hexadecimal characters. That is the layout of a DS record: key tag, algorithm number, digest type and then the digest itself. When the line appears in a reply, the registry holds DS data for the name you queried.