Personal tools

From HEXONET Wiki

Jump to: navigation, search
(→‎Domain Transfer)
Line 136: Line 136:
 
===Ownerchange ===
 
===Ownerchange ===
  
−
The request will be processed manually by the support team. After being processed the current registrant will receive an email by JPRS, which must be approved for the changes to take effect.
+
The registrant update can be done by a simple domain update without any special procedures.
−
 
+
−
{{Warnbox|Please note that a change of ownership for a .JP domain is not free of charge.
+
−
Therefore we also require an email confirmation where you state, that you are aware of and agree with the costs.}}
+
  
 
= Addons =
 
= Addons =

Revision as of 07:28, 6 March 2013




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


{{{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


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>
transferlock = 0 | 1 | <NULL>
subuser = <TEXT> | <NULL>

Domain Transfer

The transfer has to be initiated by the gaining registrar and can be requested with the API TransferDomain command.
A valid Authorization Code must be provided to initiate a transfer successfully. You may obtain the authorization code from the losing registrar.
Before a transfer gets initiated at the registry, a confirmation is required: An email confirmation (ICANN FOA email) will be sent to the registrant / administrative contact which has to be confirmed. Once confirmed then the transfer is initiated.

command = TransferDomain
domain = (DOMAIN)

REQUIRED 

ownercontact0 = <TEXT>
admincontact0 = <TEXT>
techcontact0 = <TEXT>
billingcontact0 = <TEXT>

action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER
auth = <TEXT>

OPTIONAL 

order = CREATE | REPLACE | UPDATE

subuser = <TEXT> | <NULL>
period = <PERIOD>
transferlock = 0 | 1 | <NULL>

Delete Domain

Domains can be deleted with the API DeleteDomain command. 

command = DeleteDomain
domain = (DOMAIN)

REQUIRED 

n/a


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)

REQUIRED 

n/a

OPTIONAL 

renewalmode = <NULL> | <TEXT>
subuser = <TEXT>


Ownerchange

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

Ownerchange

The registrant update can be done by a simple domain update without any special procedures.

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.
      



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.



Retrieved from "https://wiki.hexonet.net/index.php?title=JP&oldid=2050"