Personal tools

From HEXONET Wiki

Jump to: navigation, search
(Domain Transfer)
 
(22 intermediate revisions by one user not shown)
Line 1: Line 1:
{{#repositoryinfo:  ASIA-LIVE-1API | asia }}  
+
{{Infobox ccTLD
{{#var:ABOUTTLD}}
+
| name = .ASIA
 +
| image    =[[File:asia.jpg|250px]]
 +
| introduced = 2006
 +
| country = All of Asia
 +
| registry = DotASIA
 +
| idn capable = No
 +
| webpage = [https://www.hexonet.net/domain-name/asia-popular-TLD Register .ASIA]
 +
}}
 +
{{#repositoryinfo: AFILIASSRS-LIVE-1API | asia }}  
 
{{Sidebar}}
 
{{Sidebar}}
 +
<div style="font-size: 250%;">'''.ASIA'''</div><br/>
 +
.ASIA is a sponsored TLD serving as a regional domain for companies, organizations, and individuals based in Asia, Australia, and the Pacific. DotAsia is the Sponsoring Organisation and Registry Operator for the .Asia. The updated Charter Eligibility Requirement Policies allows for "entities seeking relationship or presence in Asia" to register a .Asia domain without a pre-existing address or ID.
 +
<br/>
  
  
<br>
+
__TOC__
 
+
  
 
= Registry =
 
= Registry =
 
{{Summarybox
 
{{Summarybox
| TLD={{#IfEmpty: {{#var:TLD}} | {{#var:TLD}} | - }}
+
| TLD={{#IfEmpty: {{#var:TLD}} | {{#var:TLD}} | .asia }}
 
| Registry={{#IfEmpty: {{#var:REGISTRYURL}} | [{{#var:REGISTRYURL}} {{#var:REGISTRYURLNAME}}] | - }}
 
| Registry={{#IfEmpty: {{#var:REGISTRYURL}} | [{{#var:REGISTRYURL}} {{#var:REGISTRYURLNAME}}] | - }}
 
| Dispute Policy={{#IfEmpty: {{#var:REGISTRYDISPUTEPOLICY}} | [{{#var:REGISTRYDISPUTEPOLICY}} Rules] | - }}
 
| Dispute Policy={{#IfEmpty: {{#var:REGISTRYDISPUTEPOLICY}} | [{{#var:REGISTRYDISPUTEPOLICY}} Rules] | - }}
Line 26: Line 36:
 
| Transfer Period={{#var:ZONETRANSFERPERIODS}}
 
| Transfer Period={{#var:ZONETRANSFERPERIODS}}
 
| Transfer Authcode required={{#var:REGISTRYTRANSFERREQUIREAUTHCODE}} {{#var:REGISTRYTRANSFERREQUIREAUTHCODEADDITION}}
 
| Transfer Authcode required={{#var:REGISTRYTRANSFERREQUIREAUTHCODE}} {{#var:REGISTRYTRANSFERREQUIREAUTHCODEADDITION}}
| Transfer ACK by={{#var:REGISTRYTRANSFERACKBY}}
+
| Transfer ASIAK by={{#var:REGISTRYTRANSFERASIAKBY}}
| Transfer NACK by={{#var:REGISTRYTRANSFERNACKBY}}
+
| Transfer NASIAK by={{#var:REGISTRYTRANSFERNASIAKBY}}
 
| Transfer Real-Time={{#var:REGISTRYTRANSFERREALTIME}}
 
| Transfer Real-Time={{#var:REGISTRYTRANSFERREALTIME}}
 
| Transfer Lock={{#var:REGISTRYTRANSFERLOCK}}
 
| Transfer Lock={{#var:REGISTRYTRANSFERLOCK}}
 
| Transfer Pending Period={{#var:REGISTRYTRANSFERPENDINGPERIOD}}
 
| Transfer Pending Period={{#var:REGISTRYTRANSFERPENDINGPERIOD}}
| Transfer Expire Action={{#var:REGISTRYTRANSFEREXPIREACTION}}
+
| Transfer Expire Action={{#var:REGISTRYTRANSFEREXPIREASIATION}}
 
| Transfer Confirmation={{#var:ZONEPOLICYDOMAINTRANSFERCONFIRMATION}}
 
| Transfer Confirmation={{#var:ZONEPOLICYDOMAINTRANSFERCONFIRMATION}}
 
| Transfer included={{#var:REGISTRYTRADETRANSFERINCLUDED}}
 
| Transfer included={{#var:REGISTRYTRADETRANSFERINCLUDED}}
Line 38: Line 48:
 
| Trade Real-Time={{#var:REGISTRYTRADEREALTIME}}
 
| Trade Real-Time={{#var:REGISTRYTRADEREALTIME}}
 
| Trade Confirmation={{#var:ZONEPOLICYDOMAINTRADECONFIRMATION}}
 
| Trade Confirmation={{#var:ZONEPOLICYDOMAINTRADECONFIRMATION}}
| Trade ACK by={{#var:REGISTRYTRADEACKBY}}
+
| Trade ASIAK by={{#var:REGISTRYTRADEASIAKBY}}
| Trade NACK by={{#var:REGISTRYTRADENACKBY}}
+
| Trade NASIAK by={{#var:REGISTRYTRADENASIAKBY}}
 
| Nameservers={{#var:NAMESERVERMIN}} to {{#var:NAMESERVERMAX}}
 
| Nameservers={{#var:NAMESERVERMIN}} to {{#var:NAMESERVERMAX}}
 
| Nameserverchecks={{#var:REGISTRYNAMESERVERCHECKS}}
 
| Nameserverchecks={{#var:REGISTRYNAMESERVERCHECKS}}
Line 45: Line 55:
 
| Hosts managed as={{#var:HOSTMANAGEDAS}}
 
| Hosts managed as={{#var:HOSTMANAGEDAS}}
 
| Root DNS Update={{#var:REGISTRYNAMESERVERROOTUPDATE}}
 
| Root DNS Update={{#var:REGISTRYNAMESERVERROOTUPDATE}}
| SEC DNS Interface={{#var:ZONESECDNSINTERFACE}}
+
| SEC DNS Interface={{#var:ZONESECDNSINTERFASIAE}}
 
}}
 
}}
  
Line 51: Line 61:
 
{{Summarybox
 
{{Summarybox
 
| Registration Period={{#var:ZONEREGISTRATIONPERIODS}}
 
| Registration Period={{#var:ZONEREGISTRATIONPERIODS}}
| Add Grace Period={{#var:ZONEREGISTRATIONGRACEPERIOD}}
+
| Add Grace Period={{#var:ZONEREGISTRATIONGRASIAEPERIOD}}
 
| Finalization Period={{#var:ZONERENEWALFINALIZATIONPERIOD}}
 
| Finalization Period={{#var:ZONERENEWALFINALIZATIONPERIOD}}
 
| Failure Period={{#var:ZONERENEWALFAILUREPERIOD}}
 
| Failure Period={{#var:ZONERENEWALFAILUREPERIOD}}
| Accounting Period={{#var:ZONERENEWALACCOUNTINGPERIOD}}
+
| Accounting Period={{#var:ZONERENEWALASIACOUNTINGPERIOD}}
 
| Payment Period={{#var:ZONERENEWALPAYMENTPERIOD}}
 
| Payment Period={{#var:ZONERENEWALPAYMENTPERIOD}}
 
| Deletion Restorable Period={{#var:DELETIONRESTORABLEPERIOD}}
 
| Deletion Restorable Period={{#var:DELETIONRESTORABLEPERIOD}}
Line 82: Line 92:
 
period = (PERIOD)
 
period = (PERIOD)
 
transferlock = 0 | 1 | (NULL)
 
transferlock = 0 | 1 | (NULL)
X-ASIA-CED-ACCEPT-TRUSTEE-TAC = 0 | 1
 
X-ASIA-MAINTAINERURL = (TEXT) (max. 255 chars)
 
X-ASIA-CED-CONTACT = registrant | admin | tech | billing
 
X-ASIA-CED-CCLOCALITY = (COUNTRY)
 
X-ASIA-CED-LOCALITYSP = (TEXT) (max. 255 chars)
 
X-ASIA-CED-LOCALITYCITY = (TEXT) (max. 255 chars)
 
X-ASIA-CED-LEGALENTITYTYPE = naturalPerson | corporation | cooperative | partnership | government | politicalParty | society | institution | other Type of Entity.
 
X-ASIA-CED-IDENTFORM = passport | certificate | legislation | societyRegistry | politicalPartyRegistry | other
 
X-ASIA-CED-IDENTNUMBER = (TEXT) (max. 255 chars)
 
X-ASIA-CED-OTHERLETYPE = (TEXT) (max. 255 chars)
 
X-ASIA-CED-OTHERIDENTFORM = (TEXT) (max. 255 chars)
 
X-ASIA-MAINTAINERURL = (TEXT) (max. 255 chars)
 
X-ASIA-NOTF-CONTACT = (CONTACT)
 
 
</pre>
 
</pre>
 +
[https://wiki.hexonet.net/index.php/ASIA#tab=TLD_specific Further information can be found at TLD specific]
  
 
=== Domain Transfer ===
 
=== Domain Transfer ===
Line 132: Line 130:
 
ownercontact0 = (CONTACT)
 
ownercontact0 = (CONTACT)
 
</pre>
 
</pre>
 +
 +
[https://wiki.hexonet.net/index.php/ASIA#tab=TLD_specific Further information can be found at TLD specific]
  
 
= TLD specific =
 
= TLD specific =
{{Summarybox
 
  
}}
+
The updated Charter Eligibility Requirement Policies allows for "entities seeking relationship or presence in Asia" to register a .Asia domain without a pre-existing address or ID. This means that since July 15, 2017 the Asia Pacific locality checks during the .Asia domain registration process are no longer required.
=== Specification of extensions ===
+
'''X-ASIA-MAINTAINERURL = <TEXT> (max. 255 chars)'''
+
 
+
This field is optional. If you want to utilize this field, it can contain the URL and/or name of the party responsible for maintaining the domain. The maintainer is defined by ICANN as "a person that has been designated by the Registrar for the registration of the domain (for example a reseller, could also depend on the registrant)."
+
 
+
 
+
'''X-ASIA-NOTF-CONTACT = <CONTACT>'''
+
 
+
An Operations and Notifications Contact (OPN/NOTF Contact) is submitted to designate the point of contact to whom documentary evidence requests, auction invitations, and reminders are to be sent. If no OPN Contact is nominated by the registrant, the Sponsoring Registrar should be designated as the point of contact.
+
 
+
Notifications and communications regarding documentary evidence for an application will be sent to both the OPN Contact and the Sponsoring Registrar. Updates to the OPN Contact will not be permitted during the Sunrise period.
+
 
+
The Registry does not guarantee that any changes to OPN Contact will be effected in the notification system immediately. The sponsoring registrar is responsible to inform those applicants who updated their OPN Contact that they must continue to accept and expect notifications being sent to their previous OPN Contact for a reasonable period of time after the submission of the changes.
+
 
+
In order to be eligible for a .ASIA domain, at least one of the Domain Contacts associated with the Domain Name must be an existing and current legal entity in the DotAsia Community. The Charter Eligibility Declaration Policy can be viewed at [http://www.dot.asia/policies/DotAsia-Charter-Eligibility--COMPLETE-2007-08-15.pdf 1]
+
 
+
The DotAsia Community is defined based on the geographical boundaries described by the ICANN Asia / Australia / Pacific region: [http://archive.icann.org/en/meetings/montreal/georegions-topic.htm 2]
+
 
+
 
+
=== CED contact extensions ===
+
 
+
 
+
'''X-ASIA-CED-ACCEPT-TRUSTEE-TAC = 0 | 1'''
+
 
+
Enables our "trustee service".
+
 
+
 
+
'''X-ASIA-CED-CONTACT = registrant | admin | tech | billing'''
+
 
+
Indicates which contact should be used as CED.
+
 
+
 
+
'''X-ASIA-CED-CCLOCALITY = <COUNTRY>'''
+
 
+
Location or domicile of the Entity (based on the corresponding ISO3166 code).
+
 
+
 
+
'''X-ASIA-CED-LOCALITYSP = <TEXT> (max. 255 chars)'''
+
 
+
Province of establishment of the CED.
+
 
+
 
+
'''X-ASIA-CED-LOCALITYCITY = <TEXT> (max. 255 chars)'''
+
 
+
City of establishment of the CED.
+
 
+
 
+
'''X-ASIA-CED-LEGALENTITYTYPE = naturalPerson | corporation | cooperative | partnership | government | politicalParty | society | institution | other Type of Entity.'''
+
 
+
a. Corporations or Companies
+
 
+
b. Cooperatives
+
 
+
c. Partnerships or Collectives
+
 
+
d. Government Bodies, States, Sovereigns or Municipalities
+
 
+
e. Political parties or Trade Unions
+
 
+
f. Trusts, Estates, Associations or Societies
+
 
+
g. Institutions
+
 
+
h. Natural Persons
+
 
+
i. Other
+
 
+
 
+
'''X-ASIA-CED-IDENTFORM = passport | certificate | legislation | societyRegistry | politicalPartyRegistry | other'''
+
 
+
Form of Identification
+
 
+
a. Certificate of Incorporation or equivalent business registration certificate issued by the relevant government registry as confirmation of the due incorporation and valid existence of the company.
+
 
+
b. Act, decree or legislation chartering the formation of an entity
+
 
+
c. Societies Registry or equivalent registry for non-corporate entities
+
 
+
d. Political Parties Registry
+
 
+
e. Passport or Citizenship ID
+
 
+
f. Other
+
 
+
 
+
'''X-ASIA-CED-IDENTNUMBER = <TEXT> (max. 255 chars)'''
+
 
+
Identification Number / Code of Reference (e.g. Passport number, Business Certificate number, Act or Legislation number/code, etc.).
+
 
+
 
+
'''X-ASIA-CED-OTHERLETYPE = <TEXT> (max. 255 chars)'''
+
 
+
 
+
'''X-ASIA-CED-OTHERIDENTFORM = <TEXT> (max. 255 chars)'''
+
 
+
If the legal entity type or form of identification is "other", please enter the appropriate information to support the claim. Information submitted for the CED Contact, except where privacy considerations for personal data dictates (e.g. passport number), will be included in publicly accessible WHOIS databases to allow for public inspection of applicants' eligibility. Registered Domain holders who are found to have provided false or misleading information will have their domain registration cancelled.
+
  
 
= Addons =
 
= Addons =
Line 242: Line 145:
  
 
{{#var:CATEGORY}}
 
{{#var:CATEGORY}}
 
<headertabs/>
 
 
<headertabs/>
 

Latest revision as of 13:45, 27 July 2017

.ASIA

.ASIA is a sponsored TLD serving as a regional domain for companies, organizations, and individuals based in Asia, Australia, and the Pacific. DotAsia is the Sponsoring Organisation and Registry Operator for the .Asia. The updated Charter Eligibility Requirement Policies allows for "entities seeking relationship or presence in Asia" to register a .Asia domain without a pre-existing address or ID.


Asia.jpg
Introduced 2006
Country All of Asia
Registry DotASIA
IDN Capable No
Webpage Register .ASIA

Contents


[edit] Registry

TLD

.asia

Registry

DotASIA

Dispute Policy

Rules

Registrar

1api GmbH

WHOIS-Server

whois.nic.asia

WHOIS-Update

Real-Time

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: 1 / Maximum: 1
  • Billing Contacts: Required: 1 / Maximum: 2

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

Hosts managed as

Object

Root Nameserver Update

Real-Time

Transferclass

Pull

Transfer Periods

1Y

Transfer Authcode required

Yes

Transfer Real-Time

No

Transfer Pending Period

5 days

Transfer Lock

Yes

Owner Change by

ICANN-TRADE


[edit] Periods

{{{Possible Extensions}}}

Registration Periods

1-10 years

Finalization Period

1 day

Failure Period

44 days

Payment Period

-61 days

Deletion Restorable Period

30 days

Deletion Hold Period

5 days

Explicit Renewals

Yes

Renewal Periods

1-9 years


[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)

Further information can be found at TLD specific

[edit] 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.
As soon as a domain transfer has been initiated it can either be approved ("ACK") by Registrar or denied ("NACK") by Registrar. If the registry receives neither a denial ("NACK") nor an approval ("ACK") the transfer will be ACKed after 5 days.

Please note that HEXONET is acting in compliance with ICANN Transfers Guidelines. The respective policies can be viewed under http://www.icann.org/transfers/ :

As soon as you have submitted a transfer request, the HEXONET system will send an email to the domain registrant/administrative contact, asking for approval. As soon as this email has been confirmed, the transfer is initiated through the official registry and the losing registrar will receive the transfer request. The losing registrar will then send an email to the domain registrant/administrative contact, allowing him/her to cancel or deny the pending transfer. If there is no response received within 5 days, the transfer will automatically be processed.

If the email address in the WHOIS is invalid, then the transfer cannot be processed. If this is the case, then kindly contact your current registrar and ask them to update the WHOIS information accordingly. If you do not know the name of the registrar simply perform a WHOIS search at http://www.hexonet.net/


command = TransferDomain
domain = (DOMAIN)

REQUIRED

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.
There is a Deletion Restorable Period of 30 days and a following Deletion Hold Period of 5 days.

command = DeleteDomain
domain = (DOMAIN)

[edit] Restore Domain

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

command = RestoreDomain
domain = (DOMAIN)

OPTIONAL

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

[edit] Ownerchange

All contact information with the exception of registrant Name, Firstname and Organisation can be updated through the ModifyDomain command.
In order to change the owner you have to request a trade with the TradeDomain command. This can be done through our web interface or through our API:

command = TradeDomain
domain = <DOMAIN>
ownercontact0 = <CONTACT>
command = ModifyDomain
domain  = (DOMAIN)

REQUIRED

ownercontact0 = (CONTACT)

Further information can be found at TLD specific

[edit] TLD specific

The updated Charter Eligibility Requirement Policies allows for "entities seeking relationship or presence in Asia" to register a .Asia domain without a pre-existing address or ID. This means that since July 15, 2017 the Asia Pacific locality checks during the .Asia domain registration process are no longer required.

[edit] Addons

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 (WHOISTRUSTEE_AFILIASSRS) X-ACCEPT-WHOISTRUSTEE-TAC = 0 | 1 1 month All Contacts
Trustee X-ASIA-CED-ACCEPT-TRUSTEE-TAC = 0 | 1 1 year BILLINGCONTACT
Trustee X-ASIA-CED-ACCEPT-TRUSTEE-TAC = 0 | 1 1 year BILLINGCONTACT






*1) Parameter to (de)activate: When accessing our backend through the API, you can either activate the addon with X-ACCEPT-WHOISTRUSTEE-TAC=1 or deactivate it with
      X-ACCEPT-WHOISTRUSTEE-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

ICANN Whois Data Reminder Policy (WDRP)

At least annually, a registrar must present to the registrant the current Whois information, and remind the registrant that provision of false Whois information can be grounds for cancellation of his domain name registration. Registrants must review their Whois data, and make any corrections.

ICANN Registrar Data Escrow Program (RDE)

Under the data escrow provision of the Registrar Accreditation Agreement (RAA), all ICANN-accredited registrars must regularly deposit a backup copy of their gTLD registration data with ICANN through ICANN's arrangement with Iron Mountain or they may elect to use a Third Party Provider of RDE services that has been approved by ICANN.

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.