This article describes the procedures and requirements of .co.mz 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
  • ADMIN contact MUST be a verifiable human person

Registrations are real time.

Successful domain registration via RCP or API requires:

  • Two or more nameservers or a nameserver group
  • Authorization code
  • ADMIN contact MUST be a verifiable human person
Authorization code required no
Method of confirmation email
Registration period after transfer unchanged
Average transfer time Instant
Advanced and simple transfers available Contact our Sales department to check if easy transfer of 100 or more .co.mz domains is available.

Owner change (trade)

Not supported.

Other update

  • requested via RCP or API
  • processed real time


Explicit delete

  • Requested via RCP or API
  • Processed real time

Restore / reactivate

  • If you wish to restore a deleted or expired .co.mz domain, please contact our Support Team to check if your domain could be restored manually.
Domain lifecycle
Technical information
  • DNSSEC support: yes
  • Minimum domain length : 3
  • Premium supported : No
  • IDN support: No
  • Registration period: 1-10 years
  • 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: n/a 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
  • No documentation is required. ADMIN contact MUST be a verifiable human person.
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