.MX

.MX is the official country code Top-Level-Domain (ccTLD) of Mexico. A .MX or .COM.MX domain is normally used by companies which are located in or have business relationships with Mexico.

Introduced	1989
Country	Mexico
Registry	MX
IDN Capable	No
Webpage	Register .MX

Registry

TLD	.mx
Allowed TLDs	.mx, .com.mx
Registry	MX
Dispute Policy	Rules
Registrar	1api GmbH
WHOIS-Server	whois.nic.mx
WHOIS-Update	Real-Time
Min. Characters	2
Max. Characters	249
Character Set	Letters and numbers Hyphens ("-"), however not at the beginning or directly in front of the TLD IDN: not allowed
Limitations	Registrant Contacts: Required: 1 / Maximum: 1 Admin Contacts: Required: 1 / Maximum: 1 Tech Contacts: Required: 1 / Maximum: 1 Billing Contacts: Required: 1 / Maximum: 1
{{{Possible Extensions}}}
IDN capable	No
Restore capable	Real-Time
Handle Updates	Unsupported
Registration System	Real-Time
Allowed number of NS	0 to 5
Registry Nameservercheck	No
Host IP-Addresses Type	IPv4
Hosts managed as	Object
Root Nameserver Update	several times a day
SEC DNS Interface	DS data interface
Transferclass	Pull
Transfer Periods	1Y
Transfer Authcode required	Yes
Transfer Real-Time	No
Transfer ACK by	Customer
Transfer NACK by	Customer
Transfer Lock	Yes
Transfer Confirmation (Request / Approve)	- / E-Mail
Owner Change by	Update

Periods

{{{Possible Extensions}}}
Registration Periods	1-10 years
Add Grace Period	0 days
Accounting Period	0 days
Finalization Period	44 days
Failure Period	44 days
Payment Period	-61 days
Deletion Restorable Period	30 days
Deletion Hold Period	0 days
Explicit Renewals	Yes
Renewal Periods	1-9 years

API

Domain Registration

Domains can be registered in Real-Time with the API AddDomain command.

command = AddDomain
domain  = (DOMAIN)

REQUIRED

ownercontact0 = (CONTACT)
admincontact0 = (CONTACT)
techcontact0 = (CONTACT)
billingcontact0 = (CONTACT)
nameserver0 = (NAMESERVER)
nameserver1 = (NAMESERVER)

OPTIONAL

auth = <TEXT> | <NULL>
transferlock = 0 | 1 | <NULL>
subuser = <TEXT> | <NULL>

Domain Transfer

The transfer has to be initiated by the gaining registrar and can be requested with the API TransferDomain command.
A valid Authorization Code must be provided to initiate a transfer successfully. You may obtain the authorization code from the losing registrar.
As soon as a domain transfer has been initiated it can either be approved ("ACK") by Customer or denied ("NACK") by Customer.

command = TransferDomain
domain = (DOMAIN)

REQUIRED

action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER
auth = <TEXT>

OPTIONAL

order = CREATE | REPLACE | UPDATE

subuser = <TEXT> | <NULL>
period = <PERIOD>
transferlock = 0 | 1 | <NULL>

Delete Domain

Domains can be deleted with the API DeleteDomain command.
There is a Deletion Restorable Period of 30 days and a following Deletion Hold Period of 0 days.

command = DeleteDomain
domain = (DOMAIN)

REQUIRED

n/a

Restore Domain

Restores can be processed in realtime. A restore is possible within 30 days upon deletion. Please use the command RestoreDomain.

command = RestoreDomain
domain = (DOMAIN)

REQUIRED

n/a

OPTIONAL

renewalmode = <NULL> | <TEXT>
subuser = <TEXT>

Ownerchange

An Ownerchange is free of charge and can be done with the API ModifyDomain command.

PLEASE NOTE: The registry does not support contact handle updates directly. To update a domain's contact information, a new contact handle with the updated information must be created first. Then using this new contact handle and the ModifyDomain command, the domain's contact information can be changed.

TLD specific

Transfer Auto-approval

.MX domain transfers will auto-approve on the 11th day if the registrant does not decline a pending transfer.

RegistrarOC

Restore Process

To restore a domain as a RegistrarOC customer, you simply have to execute the RestoreDomain command. HEXONET directly forwards the restore request to the registry, which performs the restore in real-time. As soon as the restore is complete, the domain will get assigned to your account with the original domain data.

Please do not initiate a restore directly at the registry (e.g. using the registrar webinterface). All restore operations must be performed through our system.