.mx

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

Successful domain registration via RCP or API requires:

  • two or more nameservers or a nameserver group
  • "State/Province" field value must  be a 100% match. 
    • .mx registry explicitly checks "State/Province" field value. If value doesn't 100% match the registry's list, the registration will be interrupted. Refer to this Wikipedia article to look up the appropriate state/province name and copy/paste it to prevent errors during the domain registration. Use the column "State".

 

NB:

Extensions .net.mx, .edu.mx and .gob.mx cannot be ordered through the automated system of Openprovider. If you want to apply for a domain under one of those extensions, please check Annex A of the .MX Domain Name General Policies to see if the intended domain holder is eligible for the domain name.

If so, contact our support team and send us the required documentation, together with the domain name, handles and nameservers to use.

Successful domain transfer via RCP or API 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
Average transfer time Max 10 days
Advanced and simple transfers available Contact our Sales department to check if easy transfer of 100 or more .mx domains is available.

Owner change (trade)

  • requested as a normal domain update via RCP or API
  • processed realtime

Other update

  • requested via RCP or API
  • processed within ~2h

Delete

  • Requested via RCP or API
  • processed realtime

Restore / reactivate

  • restore / reactivation supported via RCP or API
  • quarantine periods can be found under 
    Detailed extension information > Technical information > Quarantine period
Registry
Technical information
  • Available second level domains: .com.mx, .net.mx, .org.mx, .edu.mx, .gob.mx
  • DNSSEC support: no
  • Minimum length: 3 characters
  • Maximum length: 63 characters
  • Allowed characters: a-z 0-9 -
  • IDN characters: no
  • Registration period: 1 - 3 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: 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: 30 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:
Was this article helpful?
0 out of 0 found this helpful