Personal tools

From HEXONET Wiki

Jump to: navigation, search
 
(4 intermediate revisions by one user not shown)
Line 4: Line 4:
 
| introduced = 2015
 
| introduced = 2015
 
| category = Business & Finance
 
| category = Business & Finance
| registry operator = Verisign
+
| registry = DONUTS
 
| idn capable = Yes
 
| idn capable = Yes
 
| webpage = [https://www.hexonet.net/preregistrations/forex Register .FOREX]
 
| webpage = [https://www.hexonet.net/preregistrations/forex Register .FOREX]
 
| legal = TBA
 
| legal = TBA
 
}}
 
}}
{{#repositoryinfo:  VNDS-LIVE-1API | forex }}  
+
{{#repositoryinfo:  DONUTS-LIVE-1API | forex }}  
 
{{Sidebar}}
 
{{Sidebar}}
 
<div style="font-size: 250%;">'''.FOREX'''</div><br/>
 
<div style="font-size: 250%;">'''.FOREX'''</div><br/>
Line 92: Line 92:
 
nameserver0 = (NAMESERVER)
 
nameserver0 = (NAMESERVER)
 
nameserver1 = (NAMESERVER)
 
nameserver1 = (NAMESERVER)
x-markets-accept-highly-regulated-tac = 1
+
x-forex-accept-highly-regulated-tac = 1
x-regulatory-body-authorization = REGISTRANT-LICENSE-VALID | LICENSE-NOT-REQUIRED
+
 
</pre>
 
</pre>
  
Line 109: Line 108:
 
<pre>
 
<pre>
 
auth = (TEXT)
 
auth = (TEXT)
x-forex-accept-highly-regulated-tac = 1
 
x-regulatory-body-authorization = REGISTRANT-LICENSE-VALID | LICENSE-NOT-REQUIRED
 
 
</pre>
 
</pre>
  
Line 140: Line 137:
 
ownercontact0 = (CONTACT)
 
ownercontact0 = (CONTACT)
 
x-forex-accept-highly-regulated-tac = 1
 
x-forex-accept-highly-regulated-tac = 1
x-regulatory-body-authorization = REGISTRANT-LICENSE-VALID | LICENSE-NOT-REQUIRED
 
 
</pre>
 
</pre>
  
Line 148: Line 144:
  
 
X-FOREX-ACCEPT-HIGHLY-REGULATED-TAC=1: The confirmation that the registrant has read and agrees and is willing to be compliant with the additional terms and conditions for .FOREX.
 
X-FOREX-ACCEPT-HIGHLY-REGULATED-TAC=1: The confirmation that the registrant has read and agrees and is willing to be compliant with the additional terms and conditions for .FOREX.
 
=== X-REGULATORY-BODY-AUTHORIZATION ===
 
 
X-REGULATORY-BODY-AUTHORIZATION=REGISTRANT-LICENSE-VALID: The registrant has a valid license or authorization to participate in the respective industry or sector.
 
 
X-REGULATORY-BODY-AUTHORIZATION=LICENSE-NOT-REQUIRED: The registrant participates in an industry or sector, that does not require a valid license or authorization.
 
  
 
=== Authorization code ===
 
=== Authorization code ===

Latest revision as of 15:30, 31 March 2021

.FOREX

.FOREX
Logo forex.png
Overview
Introduced 2015
Category Business & Finance
Registry DONUTS
IDN Capable Yes
Dispute Policy ICANN Rules
Webpage Register .FOREX
Legal Information
Legal TBA

Contents


[edit] Registrant Registration Requirement for the FOREX TLD

  1. Authorization, Charters, Licenses, Credentials. During registration you must confirm and represent that you possesses all necessary authorisations, accreditations, charters, licenses and/or related credentials for their participation in the regulated sector associate with the TLD and you agree to verification of same post registration.
  2. Applicable Laws, Rules, Policies, Regulations. You must comply with all applicable laws, rules, policies and/or regulations, including updates and renwals of any and all necessary authorisations, accreditations, charters, licenses and/or related credentials necessary for the continued participation in the regulated sectors and/or activities indicated.
  3. Report of Changes of Authorization, Charters, Licenses, Credentials. While during an active registration, you must report any material changes to the validity of your authorizations, accreditations, charters, licenses and/or other related credentials provided at the time of registration and/or which affect such Registrant's continued participation in the regulated sector and/or activities indicated and associated with the FOREX TLD.
  4. False Claims. You will not claim or infer to have authorisations, accreditations, charters, licences and/or other related credentials, that you do not possess;
  5. Accurate Administrative Contact Information. You will provide and keep up-to-date an administrative contact, to be used by the Registry and/or the Registrar for the notification of complaints or reports of registration abuse;
  6. Up-to-Date Accurate Administrative Contact Information. You will keep up-to-date information on the name and contact details of the regulatory, or industry self-regulatory entity or entities with control or jurisdiction over its main place of business, such information to be presented promptly upon request in cases where verification is necessary.

[edit] Registry

TLD

-

Registry

Donuts Inc.

Dispute Policy

Rules

Registrar

1api GmbH

WHOIS-Server

whois.donuts.co

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: 1

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

SEC DNS Interface

DS data interface

Transferclass

Pull

Transfer Periods

1Y

Transfer Authcode required

Yes

Transfer Real-Time

No

Transfer Pending Period

5 days

Transfer Expire Action

ACK

Transfer ACK by

Registrar

Transfer NACK by

Registrar

Transfer Lock

Yes

Owner Change by

ICANN-TRADE


[edit] Periods

{{{Possible Extensions}}}

Registration Periods

1-10 years

Add Grace Period

0 days

Accounting Period

-5 days

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)
x-forex-accept-highly-regulated-tac = 1

OPTIONAL

auth = (TEXT) | (NULL)
period = (PERIOD)
transferlock = 0 | 1 | (NULL)

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

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>

REQUIRED

ownercontact0 = (CONTACT)
x-forex-accept-highly-regulated-tac = 1

[edit] TLD specific

[edit] X-FOREX-ACCEPT-HIGHLY-REGULATED-TAC

X-FOREX-ACCEPT-HIGHLY-REGULATED-TAC=1: The confirmation that the registrant has read and agrees and is willing to be compliant with the additional terms and conditions for .FOREX.

[edit] Authorization code

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

REQUIRED

generaterandomauth = 1

[edit] Addons

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