Revision as of 20:20, 10 February 2017 (view source) WikiAdmin (Talk | contribs) (Created page with "{{Infobox IDN | name = ОНЛАЙН | image =200px | puny code = XN--80ASEHDB | introduced = 2014 | definition = ''"Online"'' | language = Cyrillic | category ...")		Latest revision as of 20:51, 8 March 2017 (view source) WikiAdmin (Talk | contribs)
(3 intermediate revisions by one user not shown)
Line 1:		Line 1:
	{{Infobox IDN		{{Infobox IDN
	| name = ОНЛАЙН		| name = ОНЛАЙН
−	| image    =[[File:TBA|200px]]	+	| image    =[[File:online-idn.png|200px]]
	| puny code = XN--80ASEHDB		| puny code = XN--80ASEHDB
	| introduced = 2014		| introduced = 2014
	| definition = ''"Online"''		| definition = ''"Online"''
	| language = Cyrillic		| language = Cyrillic
−	| category = TBA	+	| category = IDN
	| registry = CORE Association		| registry = CORE Association
	| idn capable = Yes		| idn capable = Yes
−	| webpage = [TBA Register .ОНЛАЙН]	+	| webpage = [https://www.hexonet.net/domain-name/ОНЛАЙН Register .ОНЛАЙН]
	| legal = [http://cyrillicregistry.com/online-pravila-ru/ Registry Policies]		| legal = [http://cyrillicregistry.com/online-pravila-ru/ Registry Policies]
	}}		}}
−	{{#repositoryinfo:  TBA | XN--80ASEHDB }}	+	{{#repositoryinfo:  XN--80ASEHDB-LIVE-1API | XN--80ASEHDB }}
	{{Sidebar}}		{{Sidebar}}
	<div style="font-size: 250%;">'''.ОНЛАЙН (.ONLINE in Cyrillic)'''</div><br/>		<div style="font-size: 250%;">'''.ОНЛАЙН (.ONLINE in Cyrillic)'''</div><br/>
		+
		+	The word “онлaйн” means “online” in the sense of available on the Internet. This IDN in Cyrillic will be more PERSONAL - for private homepages and blogs, youth organizations, current events websites. The big potential of having a domain name using the new generic Cyrillic TLD .ОНЛАЙН is its recognizability -- it is readable and memorable to its audience.
		+
		+	The .ОНЛАЙН TLD will facilitate the creation of local content that is better accepted and easier to read and understand for Cyrillic-alphabet Internet users across the globe. Please note registrations may only be made in the Cyrillic alphabet.
		+
		+	Register your .ОНЛАЙН today to showcase your online content and to be on the internet IN YOUR OWN LANGUAGE.
		+
	__TOC__		__TOC__
	= Registry =		= Registry =

---

Latest revision as of 20:51, 8 March 2017

The word “онлaйн” means “online” in the sense of available on the Internet. This IDN in Cyrillic will be more PERSONAL - for private homepages and blogs, youth organizations, current events websites. The big potential of having a domain name using the new generic Cyrillic TLD .ОНЛАЙН is its recognizability -- it is readable and memorable to its audience.

The .ОНЛАЙН TLD will facilitate the creation of local content that is better accepted and easier to read and understand for Cyrillic-alphabet Internet users across the globe. Please note registrations may only be made in the Cyrillic alphabet.

Register your .ОНЛАЙН today to showcase your online content and to be on the internet IN YOUR OWN LANGUAGE.

ОНЛАЙН
Overview
Name	ОНЛАЙН
Puny Code	XN--80ASEHDB
Introduced	2014
Definition	"Online"
Language	Cyrillic
Category	IDN
Registry	CORE Association
IDN Capable	Yes
Dispute Policy	ICANN Rules
Webpage	Register .ОНЛАЙН
Legal Information
Legal	Registry Policies

Contents 1 Registry 2 Periods 3 API 3.1 Domain Registration 3.2 Domain Transfer 3.3 Delete Domain 3.4 Restore Domain 3.5 Ownerchange 4 TLD specific 4.1 Landrush Application 4.2 Authorization code 5 Addons 6 RegistrarOC 6.1 ICANN Whois Data Reminder Policy (WDRP) 6.2 ICANN Registrar Data Escrow Program (RDE) 6.3 Restore Process

[edit] Registry

TLD	-
Registry	Dot XN--80ASEHDB
Dispute Policy	Rules
Registrar	1api GmbH
WHOIS-Server	whois.nic.xn--80asehdb
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 12
Registry Nameservercheck	No
Host IP-Addresses Type	IPv4 / IPv6
Hosts managed as	Object
SEC DNS Interface	KEY 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)

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] Landrush Application

... is now opening for Landrush registration!

Start: 15-01-2014
End: 14-02-2014

REQUIRED

command = AddDomainApplication
domain = (DOMAIN)
class = LANDRUSH
ownercontact0 = (CONTACT)
admincontact0 = (CONTACT)
techcontact0 = (CONTACT)
billingcontact0 = (CONTACT)
nameserver0 = (NAMESERVER)
nameserver1 = (NAMESERVER)
nameserver2 = (NAMESERVER)

OPTIONAL

EOI = <YOUR-EOI-APPLICATION-ID>

[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

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_XN--80ASEHDB)	X-ACCEPT-WHOISTRUSTEELITE-TAC = 0 | 1	1 month	All Contacts
Proxy (WHOISTRUSTEE_XN--80ASEHDB)	X-ACCEPT-WHOISTRUSTEE-TAC = 0 | 1	1 month	All Contacts

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