.ms

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

You can register a .ms domain through our API or control panel. This registration is real time and requires the following information:
  • the domain's contact handles (owner, administrative, etc.)
  • two or more nameservers or a nameserver group


After registration the registry will send two emails to the owner of the domainname. One of these mails has a link in it where the owner has to approve the registration and accept the terms and conditions. If this approval is not given the domainname will be cancelled.
To transfer a .ms 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 owner will receive an email to approve of the transfer. If this approval is not given within two weeks, the transfer will be cancelled.

IMPORTANT: The domain will **NOT** be renewed during the transfer process! The registration period will **NOT** be extended!

Additional notes on a .ms transfer

-
Authorization code required optional
Method of confirmation authcode,email
Registration period after transfer unchanged
Average transfer time Max 14 days
Advanced and simple transfers available Contact our Sales department to check if easy transfer of 100 or more .ms domains is available.

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.

Delete

A delete is realtime. After a delete the domain will be in quarantine status for 21 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 21 days after expiring.
Registry
Technical information
  • DNSSEC support: no
  • Min: 3
  • Max: 63
  • Alphanumeric and a hyphen except in the first or last position
  • IDN: No
  • Registration period: 1 year
  • 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
  • The Domain(s) can be registered without further limitations.
Policies
  • .MS Policies: http://nic.ms/ms-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.

Was this article helpful?
Additional questions? Submit a request