# .mx This article describes the procedures and requirements of .mx domain names. Click on the subject below to open the dropdown for more information.
Registration Successful domain registration via [RCP](https://rcp.openprovider.eu/web/action/index#/domain/register) or [API](https://doc.openprovider.eu/API_Module_Domain_createDomainRequest) requires: - Two or more nameservers or a nameserver group - The "State/Province" field value must  be a 100% match.  - .mx registry explicitly checks "State/Province" field value if the registrant is from Mexico or United States. If value doesn't 100% match the registry's list, the registration will be interrupted. Refer to following links to look up the appropriate state/province name and copy/paste it to prevent errors during the domain registration. [States of Mexico](https://en.wikipedia.org/wiki/States_of_Mexico#ISO_3166_codes) (Use the **Official Name** column) [States of the United States](https://en.wikipedia.org/wiki/List_of_states_and_territories_of_the_United_States)  Any other countries will not have the "state/province" checked. - The street address may only contain up to 50 characters. ***NB:*** Extensions .net.mx, .edu.mx and .gob.mx cannot be ordered through the automated system of Openprovider. Please contact our support team and send us the required documentation, together with the domain name, handles and nameservers to use. **Information for .NET.MX** Based on the rules for registering a .NET.MX domain, please note the following: .NET.MX domains are reserved exclusively for the following types of organizations/companies: - Internet Service Providers (ISP) - Value-Added Service Providers - Wireless Network Service Providers - Data Transmission Service Providers - Special Telecommunications Service Providers ⚠️ Any other type of organization not included in the list above cannot register a domain under this category. Requirements (applicable for companies based in Mexico): - A copy of the registration before the Instituto Federal de Telecomunicaciones (formerly Comisión Federal de Telecomunicaciones) as a provider of the above-mentioned services. - A letter on company letterhead requesting the domain name. The letter must include details of the services you provide and must be signed by the company’s legal representative or attorney-in-fact. - A copy of an official identification document of the person signing the letter. Important note: The requested domain name must be related, in the opinion of the .MX Registry, to the name of the organization (as registered before the Instituto Federal de Telecomunicaciones).
Transfer Successful domain transfer via [RCP](https://rcp.openprovider.eu/web/action/index#/domain/transfer) or [API](https://doc.openprovider.eu/API_Module_Domain_transferDomainRequest) requires: - authorisation code - two or more nameservers or a nameserver group - "State/Province" field value must be a 100% match
**Authorization code required**yes
**Method of confirmation**authcode
**Registration period after transfer**[extends](https://openprovider.help/books/domains/page/expiration-date-after-successful-domain-transfer)
**Average transfer time**Max 10 days
**Advanced and simple transfers available**Contact our [Sales department](mailto:sales@openprovider.com) to check if easy transfer of 100 or more .mx domains is available.
Update ### Owner change (trade) - requested as a normal domain update via RCP or [API](https://doc.openprovider.eu/API_Module_Domain_modifyDomainRequest) - processed realtime ### Other update - requested via RCP or [API](https://doc.openprovider.eu/API_Module_Domain_modifyDomainRequest) - processed within ~2h
Deletion / Restore ### Delete - Requested via RCP or [API](https://doc.openprovider.eu/API_Module_Domain_deleteDomainRequest) - processed realtime ### Restore / reactivate - restore / reactivation supported via [RCP](https://rcp.openprovider.eu/domain/queue-restore.php) or [API](https://doc.openprovider.eu/API_Module_Domain_restoreDomainRequest) - restore comes with a subsequent renew and billed accordingly - quarantine periods can be found under  **Detailed extension information > Technical information > Quarantine period** **NOTE:** After a successful restore, we advise you to do a domain [sync](https://openprovider.help/books/domains/page/how-to-update-or-synchronize-domain-details) to make sure that the domain will resolve again.
Detailed extension information
**Registry** - Registry: [NIC México](http://www.registry.mx/?lng=en) - Registry whois: whois.mx - Registry web based whois: [https://whois.mx/results.jsf](https://whois.mx/results.jsf) - Registry zonefile updates: Every 15 minutes
**Technical information** - Available second level domains: .org.mx - DNSSEC support: yes - Minimum length: 3 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](https://openprovider.help/books/quick-start/page/renewal-policies-in-openprovider). 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: 44 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](https://openprovider.help/books/domains/page/soft-quarantine).* - Quarantine period: 10 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? **yes** - The Domain(s) can be registered without further limitations. - Nameservers must be configured and return an authoritative answer before the domain is requested.
**Policies** - [Domain Name General Policies](https://www.registry.mx/jsf/static_content/domain/policies_first_new.jsf)
**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](https://doc.openprovider.eu/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.