Personal tools

From HEXONET Wiki

Jump to: navigation, search
(14 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{#repositoryinfo:  NAME-LIVE-1API | name }}  
+
{{Infobox gTLD
 +
| name = .NAME
 +
| image    =[[File:Name.png|250px]]
 +
| introduced = 2001
 +
| tld type = Generic
 +
| category = Lifestyle & Identity
 +
| registry = DotName
 +
| idn capable = Yes
 +
| webpage = [https://www.hexonet.net/domain-name/name-popular-TLD Register .NAME]
 +
}}
 +
{{#repositoryinfo:  VNDS-LIVE-1API | name }}  
 
{{Sidebar}}
 
{{Sidebar}}
 +
<div style="font-size: 250%;">'''.NAME'''</div><br/>
 +
.NAME is considered a global Top-Level Domain (gTLD). A .NAME domain is mostly used by individuals, who would like to create an internet presence beneath their last name.
  
{{#var:ABOUTTLD}}
+
__TOC__
 
+
<br><br>
+
 
+
  
 
= Registry =
 
= Registry =
 
{{Summarybox
 
{{Summarybox
 +
| TLD={{#IfEmpty: {{#var:TLD}} | {{#var:TLD}} | - }}
 
| 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 97: Line 107:
 
auth = <TEXT> | <NULL>
 
auth = <TEXT> | <NULL>
 
action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER
 
action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER
domainauth = <TEXT>
+
auth = <TEXT>
 
</pre>
 
</pre>
  
 
<span class="label label-info">OPTIONAL</span>
 
<span class="label label-info">OPTIONAL</span>
 
<pre>
 
<pre>
order = CREATE | REPLACE | UPDATE
 
orderid = <INT>
 
 
 
emaillanguage = <TEXT>
 
emaillanguage = <TEXT>
 
emailurl = <TEXT>
 
emailurl = <TEXT>
Line 113: Line 120:
 
emailsubject = <TEXT> | <NULL>
 
emailsubject = <TEXT> | <NULL>
  
preconfirmed = <TEXT>
 
transferconfirmationemailoverride = <EMAIL> | <NULL>
 
nameserver# = <TEXT> | <NULL>
 
host# = <TEXT> | <NULL>
 
 
subuser = <TEXT> | <NULL>
 
subuser = <TEXT> | <NULL>
 
period = <PERIOD>
 
period = <PERIOD>
x-idn-language = <TEXT> | <NULL>
 
ownercontact0 = <CONTACT> | <NULL>
 
admincontact0 = <CONTACT> | <NULL>
 
techcontact0 = <CONTACT> | <NULL>
 
billingcontact0 = <CONTACT> | <NULL>
 
  
 
transferlock = 0 | 1 | <NULL>
 
transferlock = 0 | 1 | <NULL>
 
repository = <NULL> | <TEXT>
 
 
</pre>
 
</pre>
  
Line 155: Line 151:
 
<span class="label label-info">OPTIONAL</span>
 
<span class="label label-info">OPTIONAL</span>
 
<pre>
 
<pre>
force = 0 | 1 | <NULL>
 
 
renewalmode = <NULL> | <TEXT>
 
renewalmode = <NULL> | <TEXT>
 
subuser = <TEXT>
 
subuser = <TEXT>
 
</pre>
 
</pre>
 
  
 
=== Ownerchange ===
 
=== Ownerchange ===
Line 165: Line 159:
  
 
= TLD specific =
 
= TLD specific =
 
+
=== Domain Limitations and Requirements ===
=== .NAME Email Forwardings ===
+
== .NAME Email Forwardings ==
  
 
You have the choice to register second-level domain names, third-level domains and Email Forwarding (e.g. [email protected]).  Email Forwarding is similar to second-level domain names, where they can be registered, modified and transferred.
 
You have the choice to register second-level domain names, third-level domains and Email Forwarding (e.g. [email protected]).  Email Forwarding is similar to second-level domain names, where they can be registered, modified and transferred.
  
=== .NAME email forwarding-Transfer ===
+
== .NAME email forwarding-Transfer ==
  
 
It is also possible to transfer a .NAME email forwarding, which is handled like a regular domain transfer:
 
It is also possible to transfer a .NAME email forwarding, which is handled like a regular domain transfer:
Line 180: Line 174:
 
This command would initiate a transfer of the email forwarding [email protected].  
 
This command would initiate a transfer of the email forwarding [email protected].  
  
=== .NAME Email Forwarding-Email-Registration ===
+
== .NAME Email Forwarding-Email-Registration ==
  
 
The following example shows you how to register a .NAME email forwarding while configuring it to forward to a private email address:
 
The following example shows you how to register a .NAME email forwarding while configuring it to forward to a private email address:
Line 207: Line 201:
  
 
{{#var:CATEGORY}}
 
{{#var:CATEGORY}}
 
 
<headertabs/>
 

Revision as of 09:42, 27 March 2018

.NAME

.NAME is considered a global Top-Level Domain (gTLD). A .NAME domain is mostly used by individuals, who would like to create an internet presence beneath their last name.

Name.png
Introduced 2001
TLD Type Generic
Category Lifestyle & Identity
Registry DotName
IDN Capable Yes
Webpage Register .NAME

Contents


Registry

TLD

.name

Registry

DotName

Dispute Policy

Rules

Registrar

1api GmbH

WHOIS-Server

whois.nic.name

WHOIS-Update

Real-Time

Min. Characters

3

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

Root Nameserver Update

Real-Time

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


Periods

{{{Possible Extensions}}}

Registration Periods

1 year

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


API

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

secdns-ds# = <LONGTEXT> | <NULL>
secdns-key# = <LONGTEXT> | <NULL>
secdns-maxsiglife = <INT>

auth = <TEXT> | <NULL>
host# = <TEXT> | <NULL>
transferlock = 0 | 1 | <NULL>
subuser = <TEXT> | <NULL>

nameserverset = <TEXT> | <NULL>

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> | <NULL>
action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER
auth = <TEXT>

OPTIONAL

emaillanguage = <TEXT>
emailurl = <TEXT>
emaillanguage = <TEXT>
emailtac = <TEXT>
requestentity = <TEXT>
emailsender = <TEXT> | <NULL>
emailsubject = <TEXT> | <NULL>

subuser = <TEXT> | <NULL>
period = <PERIOD>

transferlock = 0 | 1 | <NULL>

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)

REQUIRED

n/a

OPTIONAL

domainalerttriggercode = <TEXT> | <NULL>
repository = <TEXT> | <NULL>


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)

REQUIRED

n/a

OPTIONAL

renewalmode = <NULL> | <TEXT>
subuser = <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>

TLD specific

Domain Limitations and Requirements

.NAME Email Forwardings

You have the choice to register second-level domain names, third-level domains and Email Forwarding (e.g. [email protected]). Email Forwarding is similar to second-level domain names, where they can be registered, modified and transferred.

.NAME email forwarding-Transfer

It is also possible to transfer a .NAME email forwarding, which is handled like a regular domain transfer:

command = TransferDomain
domain = [email protected]
auth = <text> 

This command would initiate a transfer of the email forwarding [email protected].

.NAME Email Forwarding-Email-Registration

The following example shows you how to register a .NAME email forwarding while configuring it to forward to a private email address:

command = AddDomain
domain = [email protected]
period = 1
ownercontact0 = <HANDLE>
admincontact0 = <HANDLE>
techcontact0 = <HANDLE>
billingcontact0 = <HANDLE>
x-name-emailforward = [email protected]

IMPORTANT: Please note that the above command ONLY registers [email protected] and does NOT register the domain name doe.name. However, once [email protected] is successfully registered, the second-level domain name, doe.name, or the third-level domain, john.doe.name will no longer be available to the public. Email forwarding is billed annually similar to a second-level domain name. However, please refer to the pricing list as the cost of the registration is different from a second-level .NAME registration If a .NAME domain already exists for more than 7 days, you need to contact the support team to register the respective email address manually.



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 (WHOISTRUSTEELITE_VNDS) X-ACCEPT-WHOISTRUSTEELITE-TAC = 0 | 1 1 month All Contacts
Proxy (WHOISTRUSTEE_VNDS) X-ACCEPT-WHOISTRUSTEE-TAC = 0 | 1 1 month All Contacts






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



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.