Revision as of 08:28, 10 September 2012 (view source) WikiAdmin (Talk | contribs) (→‎Restore Domain) ← Older edit		Latest revision as of 19:15, 6 November 2023 (view source) Timo (Talk | contribs) (→‎TLD specific)
(8 intermediate revisions by 2 users not shown)
Line 1:		Line 1:
−	{{#repositoryinfo: CO-LIVE-1API | co }}	+	{{Infobox ccTLD
−	{{#var:ABOUTTLD}}	+	| name = .CO
		+	| image    =[[File:CO.png|150px]]
		+	| introduced = 1991
		+	| country = Columbia
		+	| registry = CO Internet S.A.S.
		+	| idn capable = Yes
		+	| webpage = [https://www.hexonet.net/domain-name/co Register .CO]
		+	}}
		+	{{#repositoryinfo: ARI-LIVE-1API | co  }}
	{{Sidebar}}		{{Sidebar}}
		+	<div style="font-size: 250%;">'''.CO'''</div><br/>
		+	.CO is the official country code Top-Level-Domain of Colombia. .CO offers individuals and organizations exciting new options in branding their online presence. Research has shown that .CO is immediately recognizable by registrants around the world to mean "company", "corporation" and/or other types of commercial ventures.
−	<br>	+	__TOC__
−		+
	= Registry =		= Registry =
	{{Summarybox		{{Summarybox
	| TLD={{#IfEmpty: {{#var:TLD}} | {{#var:TLD}} | - }}		| TLD={{#IfEmpty: {{#var:TLD}} | {{#var:TLD}} | - }}
		+	| Allowed TLDs={{#IfEmpty: {{#var:ADDTLD}} | {{#var:ADDTLD}} | - }}
	| 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 127:		Line 137:
	=== Whois Reseller Branding ===		=== Whois Reseller Branding ===
−	The .CO registry allows registrars to insert information about its resellers into the .CO WHOIS records, on a per domain basis. For this purpose, they have introduced two new fields within the whois output, the reseller name and homepage url, e.g.:	+	The .CO registry allows registrars to insert information about their resellers into the .CO WHOIS records, on a per domain basis. For this purpose, they have introduced two new fields within the whois output, the reseller name and homepage URL, e.g.:
−	Domain Name:                     SOMEDOMAIN.CO	+	Domain Name:             SOMEDOMAIN.CO
−	Domain ID:                             D12345-CO	+	Domain ID:               D12345-CO
	Registrar-Reseller Name:  Reseller LLC		Registrar-Reseller Name:  Reseller LLC
−	Registrar-Reseller URL:     http://www.resellerhomepage.com	+	Registrar-Reseller URL:   http://www.resellerhomepage.com
	...		...
		+
		+	The reseller's name and URL may be supplied as X-WHOIS-RSP and X-WHOIS-URL parameters within the API commands AddDomain and ModifyDomain. Please beware that you should supply the reseller's name with X-WHOIS-RSP if you want to set the reseller's URL with X-WHOIS-URL.
		+
		+	=== ServerTransferProhibited ===
		+
		+	Recently registered domains will have a transfer lock applied by the registry. It will be automatically removed after 60 days.
	= Addons =		= Addons =
Line 144:		Line 160:
	{{#var:CATEGORY}}		{{#var:CATEGORY}}
−
−
−	<headertabs/>

---

Latest revision as of 19:15, 6 November 2023

.CO is the official country code Top-Level-Domain of Colombia. .CO offers individuals and organizations exciting new options in branding their online presence. Research has shown that .CO is immediately recognizable by registrants around the world to mean "company", "corporation" and/or other types of commercial ventures.

Introduced	1991
Country	Columbia
Registry	CO Internet S.A.S.
IDN Capable	Yes
Webpage	Register .CO

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 Domain renewal 4.2 Whois Reseller Branding 4.3 ServerTransferProhibited 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	-
Allowed TLDs	-
Registry	.CO Internet S.A.S.
Dispute Policy	Rules
Registrar	1api GmbH
WHOIS-Server	whois.nic.co
WHOIS-Update	15 minutes
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 13
Registry Nameservercheck	No
Host IP-Addresses Type	IPv4 / IPv6
Hosts managed as	Object
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	Update

[edit] Periods

{{{Possible Extensions}}}
Registration Periods	1-5 years
Add Grace Period	0 days
Accounting Period	-1 week
Finalization Period	0 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-4 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.

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.

Please note that you cannot transfer a .CO domain name in these cases:

• within the first 60 days after a domain registration
• within the first 60 days after the transfer of a domain name

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] Domain renewal

Although a .CO domain stays in your account for 44 days after a failed renewal before it gets deleted, the registry deactivates the DNS resolving for the domain during this period.

[edit] Whois Reseller Branding

The .CO registry allows registrars to insert information about their resellers into the .CO WHOIS records, on a per domain basis. For this purpose, they have introduced two new fields within the whois output, the reseller name and homepage URL, e.g.:

  Domain Name:              SOMEDOMAIN.CO
  Domain ID:                D12345-CO
  Registrar-Reseller Name:  Reseller LLC
  Registrar-Reseller URL:   http://www.resellerhomepage.com
  ...

The reseller's name and URL may be supplied as X-WHOIS-RSP and X-WHOIS-URL parameters within the API commands AddDomain and ModifyDomain. Please beware that you should supply the reseller's name with X-WHOIS-RSP if you want to set the reseller's URL with X-WHOIS-URL.

[edit] ServerTransferProhibited

Recently registered domains will have a transfer lock applied by the registry. It will be automatically removed after 60 days.

[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 (SHIELDWHOIS_ARI_NAMEISP)	X-PROXY = 0 | SHIELDWHOIS	1 month	All Contacts
Proxy (WHOISTRUSTEELITE_ARI)	X-ACCEPT-WHOISTRUSTEELITE-TAC = 0 | 1	1 month	All Contacts
Proxy (WHOISTRUSTEE_ARI)	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.