{{{Possible Extensions}}}
Registration Periods	1-10 years
Add Grace Period	0 days
Accounting Period	-1 week
Finalization Period	-1 day
Failure Period	-1 day
Payment Period	-61 days
Deletion Restorable Period	30 days
Deletion Hold Period	0 days
Explicit Renewals	Yes
Renewal Periods	1-9 years

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)

X-RE-ACCEPT-TRUSTEE-TAC = 1
X-RE-REGISTRANT-BIRTH-DATE = (YYYY-MM-DD)
X-RE-REGISTRANT-BIRTH-PLACE = (TEXT)
X-RE-REGISTRANT-LEGAL-ID = (TEXT)
X-RE-REGISTRANT-TRADEMARK-NUMBER = (TEXT)
X-RE-REGISTRANT-DUNS-NUMBER = (TEXT)
X-RE-REGISTRANT-LOCAL-ID = (TEXT)
X-RE-REGISTRANT-JO-DATE-DECLARATION = (YYYY-MM-DD)
X-RE-REGISTRANT-JO-NUMBER = (NULL)
X-RE-REGISTRANT-JO-PAGE = (NULL)
X-RE-REGISTRANT-JO-DATE-PUBLICATION = (YYYY-MM-DD)

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 Customer or denied ("NACK") by Registry.

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)

REQUIRED

auth = (TEXT)
admincontact0 = (CONTACT)
techcontact0 = (CONTACT)

OPTIONAL

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

Delete Domain

Domains can be deleted with the API DeleteDomain command.
There is a Deletion Restorable Period of 30 days.

command = DeleteDomain
domain = (DOMAIN)

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)

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>

A Change of Registrar with the simultaneous change in the Registrant is possible. The trade request also includes a transfer request if the domain is currently managed by another registrar.

Registration

Depending on the type of registrant, different extensions must be provided. If a certain requirement can't be fulfilled, please use HEXONET´s Trustee service to register .RE domains.

1. Individual:
If you are an individual, you have to state the following parameters:

  French registrants have to provide the place of birth in the form <ZIP code>,<City>
         (e.g. "78181, Saint Quentin en Yvelines Cedex").
  Non-French registrants simply have to provide the <TWO-LETTER COUNTRY CODE> of their country of birth (e.g. "DE").

2. Company: Companies having their head office in the territory of the European Union: The VAT must be provided through an extension:

3. Companies with a European trademark: For companies with a European trademark can additionally add their trademark number using this extension:

4. Companies with a DUNS number: The DUNS number is a nine-digit number, issued by Dun & Bradstreet. DUNS is the abbreviation of Data Universal Numbering System. Companies with a valid DUNS number are still obliged having their head office in the territory of the European Union. The DUNS number can be provided using this extension:

5. Companies with a local identifier specific to a country of the European Economic Area can provide their local identifier using this extension:

6. French associations listed with the Journal Officiel de la République Française - The official gazette of the French Republic: The Journal Official Associations publishes notices of creations, breakup or substantial changes with nonprofit associations in France. Using the website http://www.societe.com and the database they provide, query for the respective data below to register a .FR domain name.

Nameserver requirements

Zone configuration:

• the zone is installed on all the name servers (at least two servers)
• the zone contact (RNAME) is legal;
• the serial number of the zone is the same on each of the servers;
• the values in the different fields of the SOA must comply with the following constraints
  • FIELD - Minimum Value - Maximum Value
  • Expires - 1 week - 100 weeks
  • Minimum - 3 minutes - 1 week
  • Refresh - 1 hour - 2 days
  • Retry - 15 minutes - 1 day
• the value of the retry field is lower than that of the refresh field, and
• the value of the expire field is far higher (at least seven times) than that of the refresh field;
• the "TLL" duration in the SOA specifies the TLL for negative responses (NXDOMAIN) and must not be greater than one day;
• the "TLL" duration must be at least one hour for SOA and NS registrations;
• the list of name servers for the zone returned by the server, corresponds with the list of servers stated in the Request;
• the hostmaster address for the zone is valid and can be contacted

Configuration of name servers:

• the server has international IP connectivity;
• the server can be contacted seven days a week, 24 hours a day;
• it must be possible to access the DNS service on port 53 in UDP and TCP for packets sent from any machine over the Internet;
• the server is authoritative for the zone requested;
• for the ".in-addr.arpa" and "." .re zones, the server must obtain a correct list of the corresponding name servers and is not authoritative if it does not
• appear in this list. The server addresses specified must be correct;
• the server obtains the correct address for each of the other servers in the zone;
• the server carries out checksums on the UDP packets and generates IP packets with a TLL of at least 64;
• the server does not forward requests to one of the AFNIC servers, it must be possible to obtain the names of the servers from their IP addresses.
• AFNIC performs a zone pre-check. You may perform this pre-check by yourself to check if the nameservers are correct: http://www.zonecheck.fr</a>

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)
Trustee	X-RE-ACCEPT-TRUSTEE-TAC = 0 | 1	1 month	OWNERCONTACT,ADMINCONTACT

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.