.jp – Openprovider

This article describes the procedures and requirements of .jp domain names.
Click on the subject below to open the dropdown for more information.

Registration

Successful domain registration via RCP or API requires:

The domain's contact handles (owner, administrative, etc.)
Local presence required - local presence service available (not for .co.jp requests)
Two or more nameservers or a nameserver group
First and last name required

This registration is real time
If you provide a Japanese address for one of the contacts, the "state/province" field is mandatory and must contain the 2-digit prefecture code.
A list of prefecture codes is available here; be sure not to include the "JP-" prefix, just the number.

co.jp: In case of a co.jp, additional documents are required (business license or ID card + registration form). You will receive an email with instructions after the registration.

Transfer

Successful domain transfer via RCP or API requires:

authorisation code
the domain's contact handles (owner, administrative, etc.)
Local presence required - local presence service available (not for .co.jp requests)
two or more nameservers or a nameserver group
The current owner contact information is required, a change of registrant is NOT possible during the transfer

Additional notes on a .jp transfer

Transfers are NOT possible, if the domain is expiring within the next 30 days.

Authorization code required	yes
Method of confirmation	authcode
Registration period after transfer	unchanged
Average transfer time	Max 7 days
Advanced and simple transfers available	Contact our Sales department to check if easy transfer of 100 or more .jp domains is available.

Outgoing transfer

Once a transfer has been initiated from the gaining registrar, please contact Openprovider Support
to approve the transfer manually.

If the owner contact does not have a Japanese address, you need to set a new owner contact with a Japanese address or otherwise it is not possible to transfer away. This is required due to the usage of a proxy address for non Japanese registrants, which has to be updated with an own one prior to the transfer out.

Update

Owner change (trade)

requested as a normal domain update via RCP or API
processed realtime

Other update

requested via RCP or API
processed realtime

Deletion / Restore

Delete

A delete is realtime. After a delete the domain will be in quarantine status for 14days. During this period the domain can be reactivated.

Restore / reactivate

A domain name can be restored for 14 days after the domain name has been deleted or expired.

Detailed extension information

Registry	Registry: Japan Registry Services Registry whois: whois.jprs.jp Registry web based whois: Registry zonefile updates: Unknown
Technical information	DNSSEC support: yes Minimum length: 3 characters Maximum length: 63 characters Allowed characters: a-z 0-9 - IDN characters: yes Registration period: 1 – 2 years Renewal date offset: 17 days The number of days before the registry's expiration date, that Openprovider requires the domain to be renewed or expired. More info. Note that the dates as shown in your Openprovider account are always leading, even if they do not match the renewal date offset mentioned here. Soft quarantine period: n/a days During this period, following after an expiration, the domain can be restored for free. This period does not apply if the domain is deleted explicitly. More info. Quarantine period: 28 days During this period, an expired or deleted domain name can be reactivated at an additional fee.
Restrictions	Local presence required? yes Does Openprovider provide local presence services? yes Local activity required? yes Correct nameserver configuration required? no Local address of the domain administrator is required. Trustee services are possible and are provided free of charge if the owner has no Japanese address No trustee service possible for co.jp Note: for .co.jp a limitation exists for no more than 1 domain per registrant!
Policies
Registration agreement	The registry requires that a registration agreement is in place between the provider and the domain holder. The text of this registration agreement and any required supplements is the following: General registration agreement

Due to the regular changes in registry rules and configuration or missing information from registry side, and despite our effort to keep our knowledge base up-to-date, information in the knowledge base may be outdated or incorrect. If you encounter some issue, please report it through the "HotJar" feedback collector on the bottom right, or (if it is blocked by your browser) by clicking the "Submit a request" link below. No rights can be derived from the information in this knowledge base. If there is discrepancy between the knowledge base and the process in Openprovider, the process in Openprovider is leading.