This article describes the procedures and requirements of .dm domain names.
Click on the subject below to open the dropdown for more information.
Successful domain registration via RCP or API requires:
- two or more nameservers or a nameserver group
- It is recommended that .DM Policies be reviewed at .DM policies prior to submitting an offer for registration to ensure compliance with current .DM Policies
NB:
All domain name offers for registration are reviewed for consideration in compliance with DM Policies during the course of a business day.
under review
Authorization code required | yes |
Method of confirmation | authcode |
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 .dm domains is available. |
Owner change (trade)
- under review
Other update
- under review
Delete
Explicit delete
- Requested via RCP or API
Expiration
In case the domain expires (not renewed in time);
- will be deleted at the registry
Restore / reactivate
- Restore is only possible after domain has expired, not after the explicit deletion of the domain.
- quarantine periods can be found under
Detailed extension information > Technical information > Quarantine period
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.