This article describes the procedures and requirements of .museum domain names.
Click on the subject below to open the dropdown for more information.
Successful domain registration via RCP or XML API or REST API requires:
- two or more nameservers or a nameserver group
The registrant must be:
- An entity that is a Museum, or
- A professional association of Museums, or
- An individual with an interest or a link with Museum profession and/or activity, or
- A Museum enthusiast.
Successful domain transfer via RCP or XML API or REST API requires:
- authorization code
- two or more nameservers or a nameserver group
Authorization code required | yes |
Method of confirmation | |
Registration period after transfer | extends |
Average transfer time | 60 day(s) |
Advanced and simple transfers available | Contact our Sales department to check if easy transfer of 100 or more .museum domains is available. |
- External authorization code request - via RCP (Reseller Control Panel) or XML API or REST API
Delete
Restore / reactivate
Registry |
|
Domain lifecycle | |
Technical information |
|
Restrictions |
|
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.