This article describes the procedures and requirements of .cl domain names.
Click on the subject below to open the dropdown for more information.
Successful Incoming transfer via RCP or XML API or REST API requires:
- Authorization code (valid for 30 days).
- Two or more nameservers.
- Verified transfer email.
- Transfer can not be initiated in the last 5 days before the expiration. Expiration dates can be checked at .cl registry whois
Authorization code required | yes |
Method of confirmation | authcode |
Registration period after transfer | extends |
Average transfer time | 5 days |
Advanced and simple transfers available | Contact our Sales department to check if easy transfer of 100 or more .cl domains is available. |
Successful outgoing transfer requires:
- Authorization code request - via RCP (Reseller Control Panel) or XML API or REST API
- Authorization code reset - via RCP or API
Owner change (trade)
- requested via RCP or API
- processed realtime
Other update
Delete
Expiration
- Domain is put in quarantine for 28 days.
- Domain gets released at random time 15 days after the quarantine.
Explicit delete
- Requested via RCP or XML API or REST API
- Domain is put in quarantine for 28 days.
- Domain gets released at random time 15 days after the quarantine.
Restore / reactivate
Registry |
|
Technical information |
|
Restrictions |
|
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.