From HEXONET Wiki
|Allowed number of NS||
0 to 13
|Host IP-Addresses Type||
IPv4 / IPv6
|Hosts managed as||
|Root Nameserver Update||
every 15 minutes
|SEC DNS Interface||
DS data interface
|Transfer Authcode required||
|Transfer Pending Period||
|Transfer Expire Action||
|Transfer ACK by||
|Transfer NACK by||
|Owner Change by||
|Add Grace Period||
|Deletion Restorable Period||
|Deletion Hold Period||
Domains can be registered in Real-Time with the API AddDomain command.
command = AddDomain domain = (DOMAIN)
ownercontact0 = (CONTACT) admincontact0 = (CONTACT) techcontact0 = (CONTACT) billingcontact0 = (CONTACT) nameserver0 = (NAMESERVER) nameserver1 = (NAMESERVER) x-travel-uin = <TRAVEL UIN> x-travel-industry = 1
auth = <TEXT> | <NULL> transferlock = 0 | 1 | <NULL> subuser = <TEXT> | <NULL>
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 Transfer 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 start the transfer 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 them to deny the pending transfer. If there is no response received within 5 days, the transfer will automatically be processed.
command = TransferDomain domain = (DOMAIN)
auth = <TEXT> | <NULL> action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER
order = CREATE | REPLACE | UPDATE subuser = <TEXT> | <NULL> period = <PERIOD> transferlock = 0 | 1 | <NULL>
command = DeleteDomain domain = (DOMAIN)
domainalerttriggercode = <TEXT> | <NULL> repository = <TEXT> | <NULL>
Restores can be processed in realtime. A restore is possible within 30 days upon deletion. Please use the command RestoreDomain.
command = RestoreDomain domain = (DOMAIN)
renewalmode = <NULL> | <TEXT> subuser = <TEXT>
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>
In order to register .TRAVEL domains, use the flag X-TRAVEL-INDUSTRY with the value 1, which means that the registrant acknowledges a relationship to the travel industry. By proceeding with their registration, the registrant acknowledges that they are engaged in or plan to engage in activities related to travel.
X-TRAVEL-INDUSTRY = 1
Please note that UINs will be deprecated in September 2018. You are encouraged to begin using the X-TRAVEL-INDUSTRY flag instead.
Domain Limitations and Requirements
.TRAVEL domain names are available to everyone who provides or plans to provide services, products, or content related to travel. New travel startups are welcome, and that includes every new travel content provider.
The following list, which is non-exhaustive and provided solely for illustrative purposes, contains example areas where a .TRAVEL domain would help you stand out:
- Attractions/Theme Parks
- Bed & Breakfast Houses
- Bus/Taxi/Limousine Operators
- Camp Facility Operators
- Vehicle Rental Companies/Airport Specialty Car Park Companies
- Computer Reservation/Travel Technology Provider
- Convention & Visitor's Bureaus
- Cruise Lines
- National Tourism Offices
- Passenger Rail Lines
- Tour Operators
- Travel Agents
- Travel Bloggers
- Travel Media
- Travel-Consumer and Market Research Organizations
- Travel related Insurance
- Travel Associations and their members
- Travel search sites and applications, including any such site or application for use with the Internet or as an “app” for any mobile telephone or other communication device
- Travel technology providers
- Travel media providers
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 ProcessTo 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.