Summary

  • JPRS's authority over .jp rests on a dated chain of instruments: the 1986 original delegation to Jun Murai, the 8 February 2002 IANA redelegation report, the 27 February 2002 ICANN ccTLD Sponsorship Agreement and the 9 November 2001 JPRS–JPNIC Memorandum.
  • Each instrument embeds a remedy: ICANN policy conformance and reassignment under the Sponsorship Agreement; JPNIC/Governmental-Authority breach consultation and re-transfer under the Memorandum; registrant-level dispute resolution under the JP-DRP.
  • The control surface is actively moving: rule revisions effective 2 June 2025 and 7 January 2026 changed provisional-registration economics and AC.JP eligibility, and a 24 February 2026 notice revised the JP-DRP Rules of Procedure themselves.
  • The currency of the control surface at publication time is the open question: the substance of the February 2026 dispute-procedure revision was not recoverable from public excerpts, leaving the remedy chain's newest change unverified.

The current record: who IANA recognizes

The IANA root database entry for .jp is the authoritative current record of the delegation. It lists Japan Registry Services Co., Ltd. of Chiyoda, Tokyo, as the ccTLD manager, with registration services at jprs.jp and WHOIS at whois.jprs.jp https://www.iana.org/domains/root/db/jp.html. That single line is the endpoint of a longer institutional history; everything else in this article is about the documents underneath it.

How the authority was granted, 1986–2002

The chain begins before ICANN existed. Per IANA's 8 February 2002 redelegation report, .jp was originally delegated by Dr. Jon Postel to Dr. Jun Murai on 5 August 1986 as a country/region test case https://www.iana.org/reports/2002/jp-report-08feb02.html. The same report records IANA's operative conclusion: in light of the Japanese Government's endorsement of JPRS as the appropriate private-sector manager, IANA found JPRS the appropriate delegee of the .jp ccTLD, provided JPRS's commitment to its responsibilities was effectively ensured https://www.iana.org/reports/2002/jp-report-08feb02.html.

Procedural completion followed. IANA's second report, dated 1 April 2002, records that on 12 February 2002 the ICANN Board authorized the President to sign the .jp ccTLD Sponsorship Agreement, that the agreement was signed on 27 February 2002 and became effective 1 April 2002, and that the framework of accountability consistent with clause 10 of the GAC Principles had been achieved https://www.iana.org/reports/2002/jp-report-01apr02.html. The Sponsorship Agreement itself is the contractual instrument: clause 3.1 states that ICANN "hereby recognizes the Sponsoring Organization as the manager of the Delegated ccTLD during the Term of this Agreement" https://www.icann.org/cctlds/jp/sponsorship-agmt-27feb02.htm.

Domestically, the 9 November 2001 JPRS–JPNIC Memorandum is the instrument that conditions the Japanese transfer on the international one: its Article 2 makes execution of the ccTLD Sponsorship Agreement a precondition of the transfer https://xn--cckje5di3nmg7ebb.jp/doc/redelegation/mou_e.html. JPNIC's contemporaneous announcement fills in the domestic dates: the JP Domain Name Management and Administration Transfer Agreement was signed on 31 January 2002, and management and administration transferred on 1 April 2002, with JPNIC and the Government of Japan assuming responsibility for overseeing that .jp is administered in the public interest while JPNIC retains responsibility for developing the JP-DRP https://www.nic.ad.jp/en/topics/2002/20020228-01.html.

What the instruments actually bind JPRS to do

Read together, the instruments convert a recognition into an operating constraint set. The Sponsorship Agreement obliges the manager to provide nameservice (4.1), maintain registry-data escrow with an agent approved by JPNIC, the Governmental Authority and the manager (4.3), conform to applicable ICANN policies (4.5) and contribute financially to ICANN (4.6); it also gives the manager prior notice, a comment opportunity and a written statement in ICANN policy development (5.1), and clause 6.3 provides for reassignment to a successor coordinated with the Governmental Authority and JPNIC, with transfer of registry data https://www.icann.org/cctlds/jp/sponsorship-agmt-27feb02.htm.

The Memorandum is sharper on the public-interest side. Article 6 requires JPRS to recognize the public-interest character of .jp registration services, establish a JP Domain Name Advisory Committee, comply with JPNIC and Governmental Authority procedures, and adopt and implement the JP Domain Name Dispute Resolution Policy established by JPNIC (6.4) https://xn--cckje5di3nmg7ebb.jp/doc/redelegation/mou_e.html. It also bars JPRS from claiming property rights in .jp itself (6.5), forbids assignment of delegee status (6.7), requires registry-data escrow (6.10) and continued operations until re-transfer (6.11) https://xn--cckje5di3nmg7ebb.jp/doc/redelegation/mou_e.html. Article 7 creates the oversight machinery: reporting to JPNIC, breach consultation between JPNIC and the Governmental Authority, a written re-transfer notice and successor selection.

The remedy chain for registrants

Below the institutional layer sits the registrant-level remedy. The JP-DRP is made an integral part of JPRS's registration rules by reference, so registrants submit to dispute-resolution procedures run by accredited dispute-resolution service providers and must comply with panel decisions https://www.nic.ad.jp/ja/drp/JP-DRPguide.pdf https://www.nic.ad.jp/ja/drp/jpdrp-provider.html. This is the mechanism by which a domain holder can be dispossessed without a court — and the mechanism whose own procedural rules JPRS revised in February 2026.

What has changed on the control surface, 2025–2026

The chain is not static, and the recent revisions show JPRS actively amending both the eligibility rules and the remedy rules.

Effective 2 June 2025, JPRS revised the Registration Rules for attribute-type and regional JP domain names. A registration renewal fee is now charged when the provisional (仮登録) registration period reaches one year or more; a new Article 21 paragraph 3 provides an exception on the full-registration period when the provisional period is extended; the provisional applicant definition (Article 21 paragraph 1) and the attachment documents (Article 22 paragraph 2, Appendix 1-3) were amended, adding proof of planned establishment or name change when JPRS deems necessary https://jprs.jp/whatsnew/notice/2025/250602.html.

The commercial logic of that revision is visible in JPRS's own 1 April 2025 press release. Before the change, attribute-type provisional registration was capped at 6 months for all types (AC.JP, CO.JP, ED.JP, GO.JP, OR.JP); after 2 June 2025, AC.JP and ED.JP provisional periods can be extended to match the planned establishment or name-change date, conditional on a clear establishment plan, with strengthened review requiring plan-confirming documents — motivated by schools that cannot be established within six months https://jprs.co.jp/press/2025/250401.html.

Effective 7 January 2026, applied early from 30 October 2025, JPRS amended Appendix 1 of the same rules to add Japanese-language educational institutions accredited by the Minister of Education (MEXT) under the Act on Proper and Reliable Implementation of Japanese-Language Education — in force since 1 April 2024 — to the organizations eligible to register AC.JP domain names https://jprs.jp/whatsnew/notice/2026/260107.html. This is eligibility policy being updated to track a Japanese statute: the control surface adjusting to domestic law rather than to ICANN policy.

Finally, on 24 February 2026, JPRS published a notice revising the Rules of Procedure for the JP Domain Name Dispute Resolution Policy https://jprs.jp/whatsnew/notice/2026/260224.html — a change to the dispute-remedy mechanism itself. JPRS's registrar notice index also records further 2026 revisions dated 18 March 2026 (gTLD-related domain name rules) and 30 March 2026 (launch of a Whois/RDAP proxy-disclosure service) https://jprs.jp/registrar/info/notice/, showing the amendment cadence continuing through the year.

Currency of the control surface

For a governance audit, the decisive test is not whether instruments exist but whether the reader is looking at the current versions. The delegation chain documents are stable; the operating rules are not. The February 2026 dispute-procedure revision is the clearest gap: the notice exists and is dated, but the substance of the revision was not recoverable from the excerpts retained for this article, so the newest change to the registrant remedy chain remains unverified here. The 2002 Sponsorship Agreement's current validity and any later amendments were also not independently verified in this run.

Sources