.music

This article describes the procedures and requirements of .music domain names.
Click on the subject below to open the dropdown for more information.
Registration
Successful domain registration via RCP or XML API or REST API requires:
two or more nameservers or a nameserver group
After a .MUSIC domain name is registered at a Registrar, registrants must complete an identity verification through the Registry Operator’s Identity Verification Solution Provider (IVSP) at the URL - https://id.music. Registrants have upto 1 year to do this. Upon registration success, .MUSIC domains are immediately active for use.
At the point of registration, registrants will simply confirm their Music Nexus by clicking an attestation checkbox to qualify. 
To ensure the protection of the .MUSIC namespace, completion of the former “hard” Nexus will be required through the registry’s Music Nexus AI Audit Program. 
Registered users should expect a Nexus audit email sometime during their first year of registration. After following the audit email instructions, failure to successfully complete the Nexus audit may result in the suspension of their domain name until the Nexus verification can be established.
List of "Reserved" and "Premium" .music domains is available here.
Please note that "Reserved" domain names cannot be registered.
Transfer
Successful domain transfer via RCP or XML API or REST API requires:
authorisation code
two or more nameservers or a nameserver group
Domain transfers are not real time, and might take a few days to complete.
Authorization code required
yes
Method of confirmation
authcode
Registration period after transfer
extends
Average transfer time
Advanced and simple transfers available
Contact our Sales department to check if easy transfer of 100 or more .music domains is available.
Update
Owner change (trade)
Requested via RCP or XML API or REST API
Other update
Requested via RCP or XML API or REST API
Processed realtime
Deletion / Restore
Delete
Explicit delete
Requested via RCP or XML API or REST API
processed realtime
Expiration
In case the domain expires (not renewed in time);
will not be deleted directly at the registry
will lead to soft quarantine, followed by regular quarantine
Restore / reactivate
Restore / reactivation supported via RCP or XML API or REST API 
Quarantine periods can be found under
Detailed extension information > Technical information > Quarantine period
Detailed extension information
Registry
Registry: DotMusic Limited
Registry whois: whois.nic.music
Registry web based whois: https://whois.nic.music/
Registry zonefile updates: Realtime
Domain lifecycle
[External embedded content: https://www.openprovider.com/domain-lifecycle/domains.php?ext=music]
Technical information
DNSSEC support: yes
Minimum length: 2 characters
Maximum length: 63 characters
Allowed characters: a-z, 0-9, -
IDN characters: No
Registration period: 1 - 10 years
Renewal date offset: 0 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: 40 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? no
Local activity required? no
Correct nameserver configuration required? no
The Domain(s) can be registered without further limitations.
Policies
TOS: https://nic.music/terms-of-use/
Privacy Policy: https://nic.music/privacy-policy/
Premium names: Yes
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.