.co

This article describes the procedures and requirements of .co domain names.
Click on the subject below to open the dropdown for more information.

Successful domain registration via RCP or XML API or REST API requires:

  • two or more nameservers or a nameserver group


    Following the recent migration, Registry has implemented new compliance measures that restrict domain registrations and updates for certain countries and regions. These restrictions are based on international sanctions and regulatory requirements.

    Affected TLDs: The following top-level domains are impacted by these restrictions: (co, com.co, net.co, nom.co)

    Blocked Countries and Regions:- Domain contact creation or modification will be blocked if any of the following countries or regions are specified:
    CU Cuba
    IR Iran
    KP North Korea
    SD Sudan
    SY Syria

    Region Blocked: Crimea (Region of Ukraine) and regions under sanctioned countries.

    Impact: Any contact creation or modification involving these regions will be automatically blocked by the registry.

Successful domain transfer via RCP or XML API or REST API requires:

  • authorisation code
  • two or more nameservers or a nameserver group

 

During the transfer period which can take 6 days, the current provider or the owner can reject to the transfer.

The registration period after a successful transfer will extend with 1 year, unless the transfer is ordered within the domain's auto-renew grace period at the previous registrar. 

Authorization code required yes
Method of confirmation authcode
Registration period after transfer extends
Average transfer time 6 days
Advanced and simple transfers available Contact our Sales department to check if easy transfer of 100 or more .co domains is available.

Owner change (trade)

  • requested as a normal domain update via RCP or XML API or REST API
  • processed realtime

Other update

  • requested via RCP or XML API or REST API
  • processed realtime


    Following the recent migration, Registry has implemented new compliance measures that restrict domain registrations and updates for certain countries and regions. These restrictions are based on international sanctions and regulatory requirements.

    Affected TLDs: The following top-level domains are impacted by these restrictions: (co, com.co, net.co, nom.co)

    Blocked Countries and Regions:- Domain contact creation or modification will be blocked if any of the following countries or regions are specified:
    CU Cuba
    IR Iran
    KP North Korea
    SD Sudan
    SY Syria

    Region Blocked: Crimea (Region of Ukraine) and regions under sanctioned countries.

    Impact: Any contact creation or modification involving these regions will be automatically blocked by the registry.

Delete

PendingDelete Period - 5 days

Restore / reactivate

  • restore / reactivation supported via RCP or XML API or REST API 
  • quarantine periods can be found under 
    Detailed extension information > Technical information > Quarantine period

NOTE:
After a successful restore, we advise you to do a domain sync to make sure that the domain will resolve again.

 

Registry
Technical information
  • Available second level domains: .com.co, .net.co, .nom.co
  • DNSSEC support: yes
  • Minimum length: 2 characters
  • Maximum length: 63 characters
  • Allowed characters: a-z 0-9 -
  • IDN characters: yes
  • Registration period: 1-5 years
  • Renewal date offset: 0 days
    The number of days before the registry's expiration date, that Openprovider requires the domain to be renewed or expired. More info.
    Note that the dates as shown in your Openprovider account are always leading, even if they do not match the renewal date offset mentioned here.
  • Soft quarantine period: 43 days
    During this period, following after an expiration, the domain can be restored for free. This period does not apply if the domain is deleted explicitly. More info.
  • Quarantine period: 13 days
    During this period, an expired or deleted domain name can be reactivated at an additional fee.
Restrictions
  • Local presence required? no
  • Does Openprovider provide local presence services? no
  • Local activity required? no
  • Correct nameserver configuration required? no
  • The Domain(s) can be registered without further limitations.
Policies
  • Policies and procedures : https://www.cointernet.com.co/politicas
Registration agreement The registry requires that a registration agreement is in place between the provider and the domain holder. The text of this registration agreement and any required supplements is the following:


Due to the regular changes in registry rules and configuration or missing information from registry side, and despite our effort to keep our knowledge base up-to-date, information in the knowledge base may be outdated or incorrect. If you encounter some issue, please report it through the "HotJar" feedback collector on the bottom right, or (if it is blocked by your browser) by clicking the "Submit a request" link below. No rights can be derived from the information in this knowledge base. If there is discrepancy between the knowledge base and the process in Openprovider, the process in Openprovider is leading.

Was this article helpful?
Additional questions? Submit a request