.com.mx – Openprovider

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

Registration

Successful domain registration via RCP or API requires:

1-5 Nameservers
The state/province value must be a 100% match.
.mx registry explicitly checks "State/Province" field value. If the value doesn't 100% match the registry's list, the registration will be interrupted. Refer tot this Wikipedia article to look up the appropriate State/Province name and copy/paste it to prevent errors during the domain registration. Use the Official Name column.
The street address may only contain up to 50 characters.
Nameservers must be configured and return an authoritative answer before the domain is requested.

Transfer

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
Nameservers must be configured and return an authoritative answer before the domain is requested.

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 .com.mx domains is available.

Update

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

Deletion / Restore

Delete

Requested via RCP or API
processed realtime

Restore / reactivate

restore / reactivation supported via RCP or API
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 to make sure that the domain will resolve again.

Detailed extension information

Registry	Registry: NIC México Registry whois: whois.mx Registry web based whois: https://whois.mx/results.jsf Registry zonefile updates: Every 15 minutes
Domain lifecycle	domain lifecycle
Technical information	DNSSEC support: yes Minimum length: 3 characters Maximum length: 63 characters Allowed characters: a-z 0-9 - IDN characters: no Registration period: 1 - 5 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: 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. 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: 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.