Personal tools

From HEXONET Wiki

Jump to: navigation, search
(Domain Transfer)
 
(23 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{Infobox ccTLD
 +
| name = .JP
 +
| image    =[[File:Japan-flag.gif|200px]]
 +
| introduced = 1986
 +
| country = Japan
 +
| registry = JPRS
 +
| idn capable = Yes
 +
| webpage = [https://www.hexonet.net/domain-name/jp Register .JP]
 +
}}
 
{{#repositoryinfo: JP-LIVE-WIXI | jp }}  
 
{{#repositoryinfo: JP-LIVE-WIXI | jp }}  
{{#var:ABOUTTLD}}
 
 
{{Sidebar}}
 
{{Sidebar}}
  
 +
<div style="font-size: 250%;">'''.JP'''</div><br/>
 +
.JP is the official country code Top-Level-Domain (ccTLD) of Japan. A .JP domain is normally used by companies or private entities who are located in Japan or who have business relationships with Japan.
  
<br>
 
  
 +
__TOC__
  
 
= Registry =
 
= Registry =
Line 91: Line 101:
 
techcontact0 = (CONTACT)
 
techcontact0 = (CONTACT)
 
billingcontact0 = (CONTACT)
 
billingcontact0 = (CONTACT)
 +
auth = (TEXT) | (NULL)
 
</pre>
 
</pre>
  
Line 113: Line 124:
 
renewalmode = (NULL) | (TEXT)
 
renewalmode = (NULL) | (TEXT)
 
</pre>
 
</pre>
 +
 +
Please see [[#Restore|TLD Specific]] for more information.
  
 
=== Ownerchange ===
 
=== Ownerchange ===
{{#var:TRADESENTENCE}}
 
 
{{#var:MODIFYDOMAINCOMMAND}}
 
{{#var:MODIFYDOMAINCOMMAND}}
 +
{{#var:TRADESENTENCE}}
 
<span class="label label-important">REQUIRED</span>
 
<span class="label label-important">REQUIRED</span>
 
<pre>
 
<pre>
Line 124: Line 137:
 
= TLD specific =
 
= TLD specific =
  
The registrant update can be done by a simple domain update without any special procedures.
+
===The strengthened checks on contact information for .JP domain===
 +
Please be aware of the strengthened checks on contact information for .JP domain. In the domain contact details ("City" field), you must enter the prefecture specified in the "State" field. Please note that an error will occur if this is not entered. Also, please keep in mind that if Japan is mentioned in the domain contacts, then the combination of postal code, street, and state must be correct.
 +
 
 +
 
 +
'''Example 1'''
 +
 
 +
City: Osaka-shi, Osaka
 +
 
 +
State: Osaka
 +
 
 +
'''Example 2:'''
 +
 
 +
City: Chiyoda-ku, Tokyo
 +
 
 +
State: Tokyo
 +
 
 +
 
 +
=== Registrant name in Japanese (.CO.JP only) ===
 +
Registrants can have their name shown with Japanese characters with the following parameter. It can be used when modifying or registering the .CO.JP domain.
 +
<pre>
 +
COMMAND = ModifyDomain
 +
DOMAIN = (DOMAIN)
 +
X-JP-KANA-ORGANIZATION = TEXT or NULL
 +
</pre>
 +
 
 +
=== Transfer ===
 +
The transfer has to be requested at the gaining registrar and FoA confirmation is required. An email confirmation will be sent to the whois domain contact. Once confirmed, the transfer is initiated at the registry.
 +
 
 +
After the transfer has been initiated, the transfer must be approved by the losing registrar within 10 days.
 +
 
 +
=== Restore ===
 +
 
 +
Often the domain is restorable for a longer period of time but the period can vary depending on the domain expiration date. Please contact support to see if a restore is still possible.
 +
 
 +
=== DNSSEC ===
 +
 
 +
The registry has announced they will not be supporting the following DNSSEC Algorithms and Digest Types.
 +
 
 +
Algorithms:
 +
 
 +
* 3(DSA)
 +
* 5(RSASHA1)
 +
* 6(DSA-NSEC3-SHA)
 +
* 7(RSASHA1-NSEC3-SHA1)
 +
* 10(RSASHA512)
 +
* 12(ECC-GOST)
 +
 
 +
Digest Types:
 +
 
 +
* 1(SHA-1)
 +
* 3(GOST R 34.11-94)
 +
 
 +
(Jan 2020)
  
 
= Addons =
 
= Addons =
 +
 +
Trustee Service is applied to all applications automatically.
  
 
{{#var:DOMAINADDONTABLE}}
 
{{#var:DOMAINADDONTABLE}}
Line 135: Line 202:
  
 
{{#var:CATEGORY}}
 
{{#var:CATEGORY}}
 
 
<headertabs/>
 

Latest revision as of 11:34, 2 October 2024

.JP

.JP is the official country code Top-Level-Domain (ccTLD) of Japan. A .JP domain is normally used by companies or private entities who are located in Japan or who have business relationships with Japan.


Japan-flag.gif
Introduced 1986
Country Japan
Registry JPRS
IDN Capable Yes
Webpage Register .JP

Contents


[edit] Registry

TLD

.jp

Registry

JPRS

Dispute Policy

Rules

Registrar

1api GmbH

WHOIS-Server

-

Min. Characters

1

Max. Characters

63

Character Set
  • Letters and numbers
  • Hyphens ("-"), however not at the beginning or directly in front of the TLD
  • IDN: allowed
Limitations
  • Registrant Contacts: Required: 1 / Maximum: 1
  • Admin Contacts: Required: 1 / Maximum: 1
  • Tech Contacts: Required: 0 / Maximum: 1
  • Billing Contacts: Required: 0 / Maximum: 1


The registrant must be located in Japan (JP).

{{{Possible Extensions}}}

IDN capable

Yes

Restore capable

Real-Time

Handle Updates

Supported

Registration System

Real-Time

Allowed number of NS

0 to 13

Registry Nameservercheck

No

Host IP-Addresses Type

IPv4

Hosts managed as

Object

SEC DNS Interface

DS data interface

Transferclass

Pull

Transfer Periods

0Y

Transfer Authcode required

Yes

Transfer Real-Time

-

Transfer Confirmation (Request / Approve)

FOA E-Mail / -

Owner Change by

Update


[edit] Periods

{{{Possible Extensions}}}

Registration Periods

1 year

Add Grace Period

0 days

Accounting Period

-12 days

Finalization Period

-6 days

Failure Period

2 days

Payment Period

-61 days

Deletion Restorable Period

0 days

Deletion Hold Period

0 days

Explicit Renewals

No

Renewal Periods

1 year


[edit] API

[edit] Domain Registration

Domains can be registered in Real-Time with the API AddDomain command.

command = AddDomain
domain  = (DOMAIN)

REQUIRED

ownercontact0 = (CONTACT)
admincontact0 = (CONTACT)
techcontact0 = (CONTACT)
billingcontact0 = (CONTACT)
nameserver0 = (NAMESERVER)
nameserver1 = (NAMESERVER)

OPTIONAL

auth = (TEXT) | (NULL)
period = (PERIOD)
transferlock = 0 | 1 | (NULL)

[edit] Domain Transfer

command = TransferDomain
domain = (DOMAIN)

REQUIRED

ownercontact0 = (CONTACT)
admincontact0 = (CONTACT)
techcontact0 = (CONTACT)
billingcontact0 = (CONTACT)
auth = (TEXT) | (NULL)

OPTIONAL

period = (PERIOD)
transferlock = 0 | 1 | (NULL)
action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER

[edit] Delete Domain

Domains can be deleted with the API DeleteDomain command.

command = DeleteDomain
domain = (DOMAIN)

[edit] Restore Domain

Restores can be processed in realtime. A restore is possible within 0 days upon deletion. Please use the command RestoreDomain.

command = RestoreDomain
domain = (DOMAIN)

OPTIONAL

subuser = (TEXT)
renewalmode = (NULL) | (TEXT)

Please see TLD Specific for more information.

[edit] Ownerchange

command = ModifyDomain
domain  = (DOMAIN)

An Ownerchange is free of charge and can be done with the API ModifyDomain command. REQUIRED

ownercontact0 = (CONTACT)

[edit] TLD specific

[edit] The strengthened checks on contact information for .JP domain

Please be aware of the strengthened checks on contact information for .JP domain. In the domain contact details ("City" field), you must enter the prefecture specified in the "State" field. Please note that an error will occur if this is not entered. Also, please keep in mind that if Japan is mentioned in the domain contacts, then the combination of postal code, street, and state must be correct.


Example 1

City: Osaka-shi, Osaka

State: Osaka

Example 2:

City: Chiyoda-ku, Tokyo

State: Tokyo


[edit] Registrant name in Japanese (.CO.JP only)

Registrants can have their name shown with Japanese characters with the following parameter. It can be used when modifying or registering the .CO.JP domain.

COMMAND = ModifyDomain
DOMAIN = (DOMAIN)
X-JP-KANA-ORGANIZATION = TEXT or NULL

[edit] Transfer

The transfer has to be requested at the gaining registrar and FoA confirmation is required. An email confirmation will be sent to the whois domain contact. Once confirmed, the transfer is initiated at the registry.

After the transfer has been initiated, the transfer must be approved by the losing registrar within 10 days.

[edit] Restore

Often the domain is restorable for a longer period of time but the period can vary depending on the domain expiration date. Please contact support to see if a restore is still possible.

[edit] DNSSEC

The registry has announced they will not be supporting the following DNSSEC Algorithms and Digest Types.

Algorithms:

  • 3(DSA)
  • 5(RSASHA1)
  • 6(DSA-NSEC3-SHA)
  • 7(RSASHA1-NSEC3-SHA1)
  • 10(RSASHA512)
  • 12(ECC-GOST)

Digest Types:

  • 1(SHA-1)
  • 3(GOST R 34.11-94)

(Jan 2020)

[edit] Addons

Trustee Service is applied to all applications automatically.

The following overview shows you all available Domain Addons which can be used for this special kind of TLD. It also shows the respective API parameters which are required to activate the Domain Addons:

Addon Class Parameter to (de)activate *1) Renewal term *2) Affected Parameters *3)
Proxy (WHOISTRUSTEELITE_JP) X-ACCEPT-WHOISTRUSTEELITE-TAC = 0 | 1 1 month All Contacts
Proxy (WHOISTRUSTEE_JP) X-ACCEPT-WHOISTRUSTEE-TAC = 0 | 1 1 month All Contacts
Proxy (WIXIPRIVACY_JP_WIXI) X-PROXY = 0 | WIXIPRIVACY 1 month All Contacts
Trustee X-JP-ACCEPT-TRUSTEE-TAC = 0 | 1 1 month OWNERCONTACT






*1) Parameter to (de)activate: When accessing our backend through the API, you can either activate the addon with X-ACCEPT-WHOISTRUSTEELITE-TAC=1 or deactivate it with
      X-ACCEPT-WHOISTRUSTEELITE-TAC=0
*2) Renewal Term: Is the minimum renewal term of the "Addon Class"
*3) If you are using a "Proxy" Domain Addon normally all contact handles are affected (registrant, admin, tech, and billing contact).
      
      
      If you are using a "Trustee" Domain Addon normally the original owner contact or the original admin contact or both are replaced by a contact provided by the trustee provider.
      



[edit] RegistrarOC

Restore Process

To restore a domain as a RegistrarOC customer, you simply have to execute the RestoreDomain command. HEXONET directly forwards the restore request to the registry, which performs the restore in real-time. As soon as the restore is complete, the domain will get assigned to your account with the original domain data.

Please do not initiate a restore directly at the registry (e.g. using the registrar webinterface). All restore operations must be performed through our system.