This article describes the procedures and requirements of .ml 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

Premium domains have a higher registration and renewal price.
Reseller will be notified about the exact domain price after requesting.

Not real-time - normal registration take 1 day, premium registrations can take up to 10 days.

Successful domain transfer via RCP or API requires:

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

Additional notes on a .ml transfer

The .ml registry has two platforms: a manual platform and an EPP platform. Transfers of domains that are registered on the EPP platform are handled realtime; transfers of domans that are registered on the manual platform can take up to a few weeks to be processed, due to slow uptake by the registry. If a domain is not transferred instantly, consider it a manual transfer with corresponding delays. Unfortunately it is not possible to see this before you start the transfer.

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

The transfercode for outgoing transfers can be requested via the support department --> support@openprovider.com

After the code has been manually requested by the support department, it can take 1 / 2 business day before the code is received and can be added to the detailpage of the domain name in your control panel.

Owner change (trade)

  • requested via RCP or API

Other update

  • Requested via RCP or API
  • Nameservers update is non-realtime.
  • In some cases update can take up to a few days.


Explicit delete

  • Requested via RCP or API
  • processed realtime


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

  • will not be deleted directly at the registry

Restore / reactivate

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


Technical information
  • DNSSEC support: no
  • Minimum length: 3 characters
  • Maximum length: 63 characters
  • Allowed characters: a-z 0-9 -
  • IDN characters: no
  • Registration period: 1
  • Renewal date offset: 35 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: 28 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.
  • Local presence required? no
  • Does Openprovider provide local presence services? no
  • Local activity required? no
  • Correct nameserver configuration required? no
  • This extension doesn't have any residency requirements.
  • http://www.point.ml/en/policies.html
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