Personal tools

From HEXONET Wiki

Jump to: navigation, search
 
Line 16: Line 16:
 
= Landrush Registration Eligibility =
 
= Landrush Registration Eligibility =
  
* Anyone can apply for a registration during the College Landrush Period, but only eligible applicants will receive their names during the College Landrush Period.  
+
* Anyone can apply for a registration during the College Landrush Period, but only eligible applicants will receive their names during the College Landrush Period.  
* An eligible applicant is any registrant of a domain name in the .edu or .ac.uk namespaces.  
+
* An eligible applicant is any registrant of a domain name in the .edu or .ac.uk namespaces.  
* Each application during the College Landrush Period will be on hold until the Registry is able to verify whether the applicant is an eligible applicant. The Registry will reach out to the applicant if it requires any further information in order to validate that the applicant is the true registrant of a .edu or .ac.uk domain  name. If the Registry determines that the applicant is an eligible applicant, the Registry will immediately allocate the eligible applicant the domain name. If the Registry determines that the applicant is not an eligible applicant, the applicant will be deemed a non-eligible applicant. (
+
* Each application during the College Landrush Period will be on hold until the Registry is able to verify whether the applicant is an eligible applicant. The Registry will reach out to the applicant if it requires any further information in order to validate that the applicant is the true registrant of a .edu or .ac.uk domain  name. If the Registry determines that the applicant is an eligible applicant, the Registry will immediately allocate the eligible applicant the domain name. If the Registry determines that the applicant is not an eligible applicant, the applicant will be deemed a non-eligible applicant. (
* If during the College Landrush a non-eligible applicant applies for a .College domain name before an eligible applicant, the eligible applicant takes priority over the non-eligible applicant and the eligible applicant will be allocated the domain name as soon as the Registry determines the eligible status of the eligible applicant.
+
* If during the College Landrush a non-eligible applicant applies for a .College domain name before an eligible applicant, the eligible applicant takes priority over the non-eligible applicant and the eligible applicant will be allocated the domain name as soon as the Registry determines the eligible status of the eligible applicant.
* The .College Registry Operator reserves the right to deem applicants that are not registrants of a .edu or .ac.uk domain name eligible applicants at its own discretion in order to further the goals of the College Launch Period.  
+
* The .College Registry Operator reserves the right to deem applicants that are not registrants of a .edu or .ac.uk domain name eligible applicants at its own discretion in order to further the goals of the College Launch Period.  
  
 
= Registry =
 
= Registry =

Latest revision as of 22:45, 20 April 2015

.COLLEGE

.COLLEGE
College logo.png
Overview
Introduced 2015
Category Education
Registry CentralNic
IDN Capable Yes
Dispute Policy ICANN Rules
Webpage Register .COLLEGE
Legal Information
Legal TBA

Contents


[edit] Landrush Registration Eligibility

  • Anyone can apply for a registration during the College Landrush Period, but only eligible applicants will receive their names during the College Landrush Period.
  • An eligible applicant is any registrant of a domain name in the .edu or .ac.uk namespaces.
  • Each application during the College Landrush Period will be on hold until the Registry is able to verify whether the applicant is an eligible applicant. The Registry will reach out to the applicant if it requires any further information in order to validate that the applicant is the true registrant of a .edu or .ac.uk domain name. If the Registry determines that the applicant is an eligible applicant, the Registry will immediately allocate the eligible applicant the domain name. If the Registry determines that the applicant is not an eligible applicant, the applicant will be deemed a non-eligible applicant. (
  • If during the College Landrush a non-eligible applicant applies for a .College domain name before an eligible applicant, the eligible applicant takes priority over the non-eligible applicant and the eligible applicant will be allocated the domain name as soon as the Registry determines the eligible status of the eligible applicant.
  • The .College Registry Operator reserves the right to deem applicants that are not registrants of a .edu or .ac.uk domain name eligible applicants at its own discretion in order to further the goals of the College Launch Period.

[edit] Registry

TLD

-

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

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

35 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)
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>
command = ModifyDomain
domain = (DOMAIN)

REQUIRED

ownercontact0 = (CONTACT)

[edit] TLD specific

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

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

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.