.mu – Openprovider

This article describes the procedures and requirements of .mu domain names.
Click on the subject below to open the dropdown for more information.

Registration

A .mu domain name registration is realtime and requires no specific additional data outside of the regular contact details for the owner, administrative and technical contact.

Transfer

To transfer a .mu domain name please make sure to first get the authorisation code from the current registrar. Using this code you can request the transfer through our website.
The transfer will complete instantly and the domain name will be available in your account immediately.

You can also transfer without a transfercode. If this option is chosen the current registrar can either approve or decline the transfer within 7 days.

IMPORTANT
Please, be aware that there is a transfer fee for this TLD and at the same time a transfer does NOT renew the domain. So
if you transfer it shortly before the domain's expiration date, you will pay for the transfer and a few days later for the renewal as well.

Authorization code required	optional
Method of confirmation	authcode
Registration period after transfer	unchanged
Average transfer time	Realtime when using
Advanced and simple transfers available	Contact our Sales department to check if easy transfer of 100 or more .mu domains is available.

Update

Owner change (trade)

An owner change can be performed by updating the owner handle of the domain. This change is processed realtime.
The whois will take 24 hours to update.

Other update

An contact update can be performed by updating the handle of the domain. This change is processed realtime.
The whois will take 24 hours to update.

Deletion / Restore

Delete

A delete is realtime. After a delete the domain will be in quarantine status for 28 days. During this period the domain can be reactivated.

Restore / reactivate

A domain can be restored using a restore domain command. The domain can be renewed for 28 days after expiring.

Detailed extension information

Registry	Registry: NIC MU Registry whois: whois.nic.mu Registry web based whois: http://nic.mu/index.php?option=com_wrapper&view=wrapper&Itemid=3 Registry zonefile updates: Hourly
Technical information	Available second level domains: .ac.mu, .co.mu, .com.mu, .net.mu, .org.mu DNSSEC support: no Minimum length: 3 characters Maximum length: 63 characters Allowed characters: a-z 0-9 - IDN characters: no Registration period: 1 - 5 years Renewal date offset: 3 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.
Restrictions	Local presence required? no Does Openprovider provide local presence services? n/a Local activity required? no Correct nameserver configuration required? no
Policies	Acceptable Use Policy: http://nic.mu/index.php/munic-polices.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: General registration agreement

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.