Personal tools

From HEXONET Wiki

Jump to: navigation, search
(Created page with "{{#repositoryinfo: CENTRALNIC-LIVE-1API | de.com }} {{#var:ABOUTTLD}} {{Sidebar}} <br> = Registry = {{Summarybox | TLD={{#IfEmpty: {{#var:TLD}} | {{#var:TLD}} | - }} | R...")
 
 
(20 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{#repositoryinfo: CENTRALNIC-LIVE-1API | de.com  }}
+
{{Infobox gTLD
{{#var:ABOUTTLD}}
+
| name = CentralNic TLDs
 +
| image    =[[File:Centralnic.png|150px]]
 +
| introduced = Varies
 +
| tld type = Secondary domains
 +
| category = Country
 +
| registry = CentralNic
 +
| idn capable = Yes
 +
| webpage = [https://www.hexonet.net/domain-name/de.com Register a secondary domain]
 +
}}
 +
{{#repositoryinfo: CENTRALNIC-LIVE-1API | de.com  }}
 
{{Sidebar}}
 
{{Sidebar}}
 +
<div style="font-size: 250%;">'''CentralNic Secondary TLDs'''</div><br/>
 +
Beside the TLD .LA, the CentralNic registry offers the following second level domains:
  
 +
<p>'''''COM:'''.br.com, .cn.com, .eu.com, .gr.com,  .uk.com,  .us.com, .mex.com, .ru.com, .sa.com, .za.com, .de.com, com.de, .jpn.com,''</p>
 +
<p>'''''NET:''' .gb.net, in.net, .uk.net, .hu.net, .se.net, jp.net''</p>
 +
<p>'''''ORG:''' .ae.org,  .us.org''</p>
  
<br>
+
'''The following secondary TLDs have been sunsetted by the registry on April 30th, 2017. New registrations and renewals are no longer permitted:''''' .ar.com, .gb.com, .hu.com, .kr.com, .qc.com, .no.com, .se.com, .uy.com''
  
 +
__TOC__
  
 
= Registry =
 
= Registry =
Line 104: Line 119:
 
{{#var:DELETESENTENCE}}
 
{{#var:DELETESENTENCE}}
 
{{#var:DELETEDOMAINCOMMAND}}
 
{{#var:DELETEDOMAINCOMMAND}}
<span class="label label-important">REQUIRED</span>
 
<pre>
 
n/a
 
</pre>
 
 
  
 
=== Restore Domain ===
 
=== Restore Domain ===
 
{{#var:RESTOREPOLICYSENTENCE}}
 
{{#var:RESTOREPOLICYSENTENCE}}
 
{{#var:RESTOREDOMAINCOMMAND}}
 
{{#var:RESTOREDOMAINCOMMAND}}
<span class="label label-important">REQUIRED</span>
 
<pre>
 
n/a
 
</pre>
 
  
 
<span class="label label-info">OPTIONAL</span>
 
<span class="label label-info">OPTIONAL</span>
Line 123: Line 129:
 
subuser = <TEXT>
 
subuser = <TEXT>
 
</pre>
 
</pre>
 
  
 
=== Ownerchange ===
 
=== Ownerchange ===
Line 130: Line 135:
 
= TLD specific =
 
= TLD specific =
  
{{#var:NOSPECIFIC}}
+
=== Zone Info ===
 +
 
 +
Beside the TLD .LA, the CentralNic registry offers the following second level domains: .ar.com, .br.com, .cn.com, .eu.com, .gb.com, .gb.net, .gr.com, .uk.com, .uk.net, .us.com, .uy.com, .hu.com, .mex.com, .no.com, .qc.com, .ru.com, .sa.com .se.com, .se.net, .za.com, .de.com, .jpn.com, .ae.org, .kr.com, .us.org, com.de.
  
 
= Addons =
 
= Addons =
Line 141: Line 148:
  
 
{{#var:CATEGORY}}
 
{{#var:CATEGORY}}
 
 
<headertabs/>
 

Latest revision as of 17:11, 5 June 2017

CentralNic Secondary TLDs

Beside the TLD .LA, the CentralNic registry offers the following second level domains:

COM:.br.com, .cn.com, .eu.com, .gr.com, .uk.com, .us.com, .mex.com, .ru.com, .sa.com, .za.com, .de.com, com.de, .jpn.com,

NET: .gb.net, in.net, .uk.net, .hu.net, .se.net, jp.net

ORG: .ae.org, .us.org

The following secondary TLDs have been sunsetted by the registry on April 30th, 2017. New registrations and renewals are no longer permitted: .ar.com, .gb.com, .hu.com, .kr.com, .qc.com, .no.com, .se.com, .uy.com

150px
Introduced Varies
TLD Type Secondary domains
Category Country
Registry CentralNic
IDN Capable Yes
Webpage Register a secondary domain

Contents


[edit] Registry

TLD

Centralnic TLDs

Registry

CentralNic

Dispute Policy

Rules

Registrar

1api GmbH

WHOIS-Server

whois.centralnic.net

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 10

Registry Nameservercheck

No

Host IP-Addresses Type

IPv4 / IPv6

Hosts managed as

Object

Root Nameserver Update

every 15min

SEC DNS Interface

DS data interface

Transferclass

Pull

Transfer Periods

0Y,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

Update


[edit] Periods

{{{Possible Extensions}}}

Registration Periods

1-10 years

Add Grace Period

0 days

Accounting Period

0 days

Finalization Period

44 days

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)

OPTIONAL

auth = <TEXT> | <NULL>
transferlock = 0 | 1 | <NULL>
subuser = <TEXT> | <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.

command = TransferDomain
domain = (DOMAIN)

REQUIRED

action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER
auth = <TEXT>

OPTIONAL

order = CREATE | REPLACE | UPDATE

subuser = <TEXT> | <NULL>
period = <PERIOD>
transferlock = 0 | 1 | <NULL>

[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

renewalmode = <NULL> | <TEXT>
subuser = <TEXT>

[edit] Ownerchange

An Ownerchange is free of charge and can be done with the API ModifyDomain command.

[edit] TLD specific

[edit] Zone Info

Beside the TLD .LA, the CentralNic registry offers the following second level domains: .ar.com, .br.com, .cn.com, .eu.com, .gb.com, .gb.net, .gr.com, .uk.com, .uk.net, .us.com, .uy.com, .hu.com, .mex.com, .no.com, .qc.com, .ru.com, .sa.com .se.com, .se.net, .za.com, .de.com, .jpn.com, .ae.org, .kr.com, .us.org, com.de.

[edit] 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_CENTRALNIC) X-ACCEPT-WHOISTRUSTEELITE-TAC = 0 | 1 1 month All Contacts
Proxy (WHOISTRUSTEE_CENTRALNIC) 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).
      
      



[edit] RegistrarOC

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.