This article describes the procedures and requirements of .com.de domain names.
Click on the subject below to open the dropdown for more information.
Successful domain registration via RCP or API requires:
- the domain's contact handles (owner, administrative, etc.)
- two or more nameservers or a nameserver group
The transfer is submitted to the registry and the losing registrar is automatically notified by them.
The losing registrar sends an email to the owner (and optionally admin) contact, informing about the transfer; this may include options to approve and/or deny the transfer. If neither explicitly approved nor denied, the transfer will be automatically finalized after 5 days.
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 .com.de domains is available. |
Owner change (trade)
- Trade - via RCP or API, by updating the owner handle
Other update
- Domain updates - via RCP or API.
Delete
- Delete - explicit delete is possible via RCP or API.
Restore / reactivate
- Restore - via RCP or API
Registry |
|
Domain lifecycle | |
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.