1. Openprovider
  2. Domains
  3. Documentation per TLD

.eco

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

Registration

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

  • two or more nameservers or a nameserver group.
  • registrant e-mail address verification applies.
  • For the US and Canada, state and province codes should conform to ISO 3166-2 (the two character codes). For other countries, the field must be from two (2) to two-hundred and fifty-five (255) characters in length.

A new registration is processed in realtime, however, the domain is not immediately active. The registry places each new domain registration on serverHold status and sends an e-mail to the domain holder. This e-mail comes from activate@profiles.eco with subject "Activate {domain}.eco". It contains a link to create an "ECO profile" on the registry's website. When the profile is created, the registry will activate the domain name. The domain will then resolve. For more information about the ECO profile, please refer to the section "Policies" below.

Transfer

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


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.

Problems transferring your domain?
Please take a look at this extended article for possible solutions.

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

Owner change (trade)

  • requested as a normal domain update via RCP or XML API or REST API
  • processed realtime
  • both previous and new registrant will receive an e-mail. This is a notification only, no action is required.
  • registrant e-mail address verification applies

Other update

 

If as part of the update the domain owner’s e-mail address changes, we’re obliged to start a contact verification process if this new e-mail address was not verified before.

Deletion / Restore

Delete

Explicit delete

  • Requested via RCP or XML API or REST API
  • processed realtime
  • will directly result in quarantine (redemption period)  (no soft quarantine applies)


Expiration
In case the domain expires (not renewed in time);

  • will not be deleted directly at the registry
  • will lead to soft quarantine, followed by regular quarantine

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
  • After quarantine, 5 days PendingDelete period (restore not possible)
Detailed extension information
Registry
Domain lifecycle
Technical information
  • DNSSEC support: yes
  • Minimum length: 1 character
  • Maximum length: 63 characters
  • Allowed characters: a-z, 0-9, -
  • IDN characters: no
  • Registration period: 1-10 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: 40 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: 0 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? n/a
  • Local activity required? no
  • Correct nameserver configuration required? no
  • Registrant must either be member of the .eco organization or belong to one of the following eligibility categories: [1] Not-for-profit mission-based organizations, both small and large, that work for the good of the planet; [2] businesses of all sizes committed to providing products and services that encourage positive environmental change; [3] government bodies that support sustainability through programs, infrastructure and funding amongst other policies and actions; [4] people who participate in and support environmental change through membership, financial support or donating their time, as well environmental professionals who contribute to positive environmental change through their work; [5] farms and other producers of agricultural products that achieve EU organic production and labelling standards.
Policies
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