Personal tools

From HEXONET Wiki

Jump to: navigation, search
.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

6 hours

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 ACK by

Registrar

Transfer NACK by

Registrar

Transfer Lock

Yes

Transfer Confirmation (Request / Approve)

FOA E-Mail / -

Owner Change by

ICANN-TRADE


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


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.
Before a transfer gets initiated at the registry, a confirmation is required: An email confirmation (ICANN FOA email) will be sent to the registrant / administrative contact which has to be confirmed. Once confirmed then the transfer is initiated.
As soon as a domain transfer has been initiated it can either be approved ("ACK") by Registrar or denied ("NACK") by Registrar.

Please note that HEXONET is acting in compliance with ICANN Transfers 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 will send an email to the domain registrant/administrative contact, asking for approval. As soon as this email has been confirmed, the transfer is initiated 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 him/her to cancel or deny the pending transfer. If there is no response received within 5 days, the transfer will automatically be processed.

If the email address in the WHOIS is invalid, then the transfer cannot be processed. If this is the case, then kindly contact your current registrar and ask them to update the WHOIS information accordingly. If you do not know the name of the registrar simply perform a WHOIS search at http://www.hexonet.net/


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. firstname@lastname.name). 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 = john@doe.name
auth = <text> 

This command would initiate a transfer of the email forwarding john@doe.name.

.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 = john@doe.name
period = 1
ownercontact0 = <HANDLE>
admincontact0 = <HANDLE>
techcontact0 = <HANDLE>
billingcontact0 = <HANDLE>
x-name-emailforward = yourprivateaddress@mailprovider.info

IMPORTANT: Please note that the above command ONLY registers john@doe.name and does NOT register the domain name doe.name. However, once john@doe.name 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_NAME) X-ACCEPT-WHOISTRUSTEELITE-TAC = 0 | 1 1 month All Contacts
Proxy (WHOISTRUSTEE_NAME) 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.