From HEXONET Wiki
|Dispute Policy||ICANN Rules|
- TMCH Sunrise: Starting Sept 1 - Oct 1, 2015, .SEX will be made available for a thirty day (30) period to trademark holders who are registered in the Trademark Clearinghouse (TMCH), as required under ICANN’s Rights Protection Mechanism.
- Sunrise B: Oct 5 - Oct 30, 2015, This priority registration period is for those 2011 XXX Sunrise B applicants.
- Domain Matching: Oct 5 - Oct 30, 2015, registered owners of any .XXX domain (EXAMPLE.XXX) will be given priority to register its counterpart in .SEX (EXAMPLE.XXX for EXAMPLE.SEX). The Domain Matching Program will be available to all .XXX registrants who have a .XXX registration as of October 1, 2015.
- General Availability: Nov 4, 2015, anyone can register a .SEX domain during this time, even individuals / entities outside the adult entertainment industry
Sunrise B and Matching Eligibility
Sunrise B Eligibility Requirements - Sunrise B Registration Requests in an ICM gTLD may only be submitted by the same Applicant that submitted a successful .XXX Sunrise B Reservation Request. The Applicant must use the same Accredited Registrar of Record that sponsored the Applicant in its underlying, directly matching .XXX Sunrise B Reservation Request; if such Registrar of Record is unwilling or unable to participate in the ICM gTLD Sunrise B Program, then the Applicant may use an alternate Accredited Registrar(s) designated by ICM. In the event there was more than one successful .XXX Sunrise B Reservation Request for the same second level domain name in the .XXX TLD, then, more than one Applicant may submit a Sunrise B Registration Request during the ICM gTLD Sunrise B Program for the directly matching second level domain name in an ICM gTLD. The Registry will allocate the matching second level domain name in the ICM gTLD on a first-come, first-served basis.
Domain Matching Eligibility Requirements - Only the Registrant of the directly matching .XXX TLD Registration is eligible to submit a Domain Matching Registration Request for the directly matching second level domain name in an ICM gTLD. The Applicant must use the same Accredited Registrar of Record that sponsored the Applicant in its underlying, directly matching .XXX Registration; if such Registrar of Record is unwilling or unable to participate in the ICM gTLD Domain Matching Program, then the Applicant may use an alternate Accredited Registrar(s) designated by ICM. The underlying, directly matching .XXX second level domain name must be registered by such Applicant as of October 1, 2015.
|Allowed number of NS||
0 to 13
|Host IP-Addresses Type||
IPv4 / IPv6
|Hosts managed as||
|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)
auth = (TEXT) | (NULL) period = (PERIOD) transferlock = 0 | 1 | (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)
period = (PERIOD) transferlock = 0 | 1 | (NULL) action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER
command = DeleteDomain domain = (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)
subuser = (TEXT) renewalmode = (NULL) | (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>
command = ModifyDomain domain = (DOMAIN)
ownercontact0 = (CONTACT)
There are special requirements regarding the format of the authorization code. Please consider the following restrictions, if you want to assign a new authorization code to a .COM domain:
- Minimum 8 characters
- having at least one (1) numeric,
- one (1) alphabetic, and
- one (1) special character
You may generate a valid random auth code by adding this parameter to the ModifyDomain command:
command = ModifyDomain domain = (DOMAIN)
generaterandomauth = 1