Step-by-step: transfer a .mx domain after a successful complaint
A brand owner in Mexico City discovers its registered trademark is live as a .mx domain controlled by a stranger. The site redirects to a competitor's landing page. The demand that follows – pay a five-figure sum or lose the name – arrives by email within days. The question is not whether this is abuse. The question is which procedure converts a favorable ruling into actual control of the domain.
To transfer a .mx domain after a successful complaint, the complainant must complete the implementation stage that follows any favorable panel decision under the .mx dispute procedure – the LDRP (Lineamientos para la solución de disputas relativas a nombres de dominio .mx). The governing body is NIC.mx, and the transfer is executed by the registrar once NIC.mx confirms the decision. The entire process from filing to registry implementation typically runs a matter of weeks beyond the panel's ruling itself; no court order is required at this stage.
This guide walks every step in sequence – from confirming eligibility through the LDRP filing, the evidence package, the panel decision, and the registry transfer mechanics – and flags the procedural trap hidden inside each one.
What governs .mx domain disputes, and how does the LDRP differ from the UDRP?
The LDRP is the binding dispute-resolution procedure for all .mx second-level domain names, administered through NIC.mx, Mexico's national registry. It is modeled closely on the UDRP but contains several provisions that differ materially from the UDRP – and missing those differences is the most common source of failed complaints.
Like the UDRP, the LDRP requires a complainant to satisfy a three-element test: (1) the disputed domain is identical or confusingly similar to a name or mark in which the complainant has rights; (2) the registrant has no rights or legitimate interests in the domain; and (3) the domain was registered and is being used in bad faith. The cumulative requirement – registered and used in bad faith – tracks the UDRP standard exactly. That matters: a domain that was registered defensively but is currently pointing somewhere harmful does not automatically satisfy the third element if the original registration was in good faith.
The structural difference that catches complainants is eligibility. The UDRP imposes no nationality or nexus requirement on the complainant. The LDRP does impose constraints on who may hold a .mx registration – and those eligibility rules feed back into the transfer remedy. If the complainant cannot demonstrate that it qualifies to hold a .mx domain (for example, as a Mexican legal or natural person, or through an authorized presence), the transfer remedy may be replaced by cancellation rather than transfer to the complainant. The distinction matters enormously: a cancellation frees the name back into the pool, where anyone – including the original bad-faith registrant – can re-register it.
In our practice advising brand owners across Latin American ccTLDs, we consistently find that complainants who prepared their eligibility documentation in advance of filing avoided the cancellation-only outcome. That preparation step is not optional; it is structural.
For an assessment of whether your trademark and entity status support a transfer remedy in .mx, contact info@cognomenlaw.com.
Step 1 – Confirm trademark rights and confusing similarity before you file
The first element of the LDRP is satisfied when the complainant holds a recognized right in a name or mark and can show the disputed domain is identical or confusingly similar to it. Confirming this before filing prevents a dismissal on the opening element.
What counts as a recognized right? A registered trademark is the cleanest basis. A Mexican trademark registration – ideally one predating the domain's creation date – is the strongest anchor. Rights in a foreign registration are arguable under the LDRP, particularly where the mark has clear reputation in Mexico or the registrant's conduct shows awareness of the mark. Unregistered marks are harder to rely on; they require persuasive evidence of secondary meaning or widespread recognition in Mexico.
The confusing similarity analysis turns on a visual and phonetic comparison of the mark against the domain name (stripping the ccTLD, per standard practice). Typosquats – one-letter variations, transpositions, hyphen insertions – clear this bar easily. Generic additions such as "buy," "get," or "mx" appended to the exact mark also clear it. The trap at this step is assuming a partial match is obvious to a panel. Document the comparison explicitly: print the mark, print the domain string, and explain the similarity in plain language that a non-specialist panelist can follow.
A second trap is the creation date. Before filing, pull a current WHOIS/RDDS record for the domain and confirm the registration date. If the domain predates your trademark's registration or its first commercial use, you will face a causation problem on the third element (bad faith at the time of registration). The complaint is not automatically defeated – a panelist may find bad faith in use rather than registration in certain circumstances – but this factual gap must be addressed squarely, not left unanswered.
Step 2 – Establish that the registrant has no legitimate interest
The second element shifts the burden, in practice, once the complainant establishes a prima facie case: the registrant must come forward with evidence of a legitimate interest, and the panel assesses the strength of that evidence.
The LDRP, like the UDRP, recognizes three standard safe harbors for the registrant: (a) genuine use of the domain in connection with a bona fide offering of goods or services before notice of the dispute; (b) the registrant being commonly known by the domain name; (c) legitimate noncommercial or fair use without misleading diversion or tarnishment. A complainant does not need to disprove all three in detail upfront – but the complaint should address why none of the three obviously applies on the available facts.
The evidence that does the work here is the domain's current content. Screenshots of the parking page, the redirected site, or the demand email all go to the absence of legitimate use. If the domain is pointed at a blank page or a pay-per-click aggregator, that is not a bona fide offering. Capture those screenshots with a timestamp, a URL bar visible, and – where possible – a third-party archival record (such as a publicly available web archive). Panels expect a snapshot that cannot plausibly be fabricated after the fact.
The trap in step 2 is under-documenting what the site is not doing. Complainants often submit one screenshot and move on. A stronger evidential package includes: the parking page screenshot, a search result showing the registrant is not known by that name, a WHOIS/RDDS record showing no disclosed business identity, and any communications from the registrant (the demand email, if one exists) that cut against a claim of innocent use.
Step 3 – Build the bad-faith record
Bad faith under the LDRP is assessed at two points: the moment of registration and the ongoing use. Both must be shown. A complainant who proves bad-faith use without addressing bad-faith registration – or vice versa – gives the panel a gap it may decline to paper over.
The Paragraph 4(b) bad-faith circumstances from the UDRP carry through to the LDRP substantially intact. The most frequently invoked are: registration primarily to sell the domain to the mark owner or a competitor at an inflated price; registration to disrupt a competitor's business; attracting users for commercial gain by creating confusion with the complainant's mark; and a demonstrable pattern of abusive registrations. Any of these, clearly evidenced, satisfies the third element.
In practice, the demand email is the single most powerful bad-faith document. A written demand asking for a sum that bears no relationship to the registrant's out-of-pocket costs – a "five-figure buy-back demand," for instance – is textbook Paragraph 4(b)(i) evidence. Preserve it, authenticate it, and attach it as an exhibit. If no demand was made, the complainant must demonstrate bad faith through the totality of circumstances: the timing of registration (shortly after a trademark event or media announcement), the absence of any plausible legitimate use, and the registrant's known background in similar domains.
We have defended registrants in .mx matters where the complainant's bad-faith case rested entirely on proximity of the domain's creation date to a product launch. That argument is not self-executing. Panel outcomes in those matters turned on whether the registrant could document prior awareness of the name before the complainant's launch – and the ones who could, prevailed. The lesson for complainants is the same in reverse: if you have evidence of the registrant's awareness of your mark, put it in the record.
To weigh your bad-faith evidence and identify the gaps before filing, email info@cognomenlaw.com.
Step 4 – File the LDRP complaint and manage the response window
Filing under the LDRP is submitted to the designated dispute-resolution service provider authorized by NIC.mx. At the time of writing, WIPO administers a .mx procedure and acts as a provider in this zone – confirm the current authorized provider with counsel before filing, as procedural rules and fee schedules are subject to change by the registry.
The complaint must be substantially complete at filing: the complainant's identity and contact details, the disputed domain name, the grounds for the complaint across all three elements, the remedies sought (transfer or cancellation), and the exhibit package assembled in Steps 1 through 3. An incomplete complaint risks rejection at the administrative compliance stage, which adds delay without resetting the substantive clock.
Once the complaint is formally commenced, the registrant has a defined response window – confirm the exact period against the current LDRP rules, as this is a registry-controlled parameter. A respondent who files no response does not lose automatically; the panel decides on the record before it and may still dismiss if the complaint falls short. Do not assume default equals transfer. The complaint itself must be sufficient to satisfy all three elements.
The trap at step 4 is the scope rule. A single LDRP complaint may cover multiple domains only when the domains are held by the same registrant. If the bad-faith registrant distributed the domains across multiple registrant names – a known evasion tactic – you will need separate complaints, each independently sufficient. Identify all relevant domains and their listed registrants in your pre-filing WHOIS review.
Step 5 – Navigate the panel decision and understand the remedy options
A favorable panel decision under the LDRP orders either transfer or cancellation. Transfer is the preferred remedy for a complainant who is eligible to hold a .mx domain. Cancellation is the fallback where eligibility is not established or the panel elects not to order transfer on the facts.
Following the decision, there is an implementation pause – a short window during which the losing party may seek to stay implementation by filing proceedings in a court of competent jurisdiction in Mexico. If no stay application is filed and confirmed within that window, NIC.mx proceeds to direct the registrar to implement the panel's order. The registrar then executes the transfer.
What does the registrar actually do? The registrar changes the listed registrant of record from the losing party to the complainant (in a transfer order) or deletes the registration (in a cancellation). From the complainant's perspective, the domain will appear in its account under the registrar it nominates – and the registrar must be one accredited to handle .mx registrations. The complainant should have an accredited .mx registrar identified and ready before the decision issues, so that transfer processing is not delayed by a routine account-setup formality.
In a recent matter involving a .mx cybersquatting complaint (autumn 2025), we managed the post-decision implementation for a brand owner and confirmed that the practical bottleneck was not the panel ruling itself but the registrar coordination step – specifically, the complainant's failure to pre-identify an authorized .mx registrar. That delay was measured in days, not weeks, but it was entirely avoidable.
Step 6 – Handle the post-transfer technical and legal steps
Transfer of the registration record is not the end of the process. Several technical and legal steps follow, and each carries its own risk of delay or oversight.
First, DNS propagation. After the registrar updates the registration record, the domain's DNS settings – unless the complainant specified new nameservers as part of the transfer request – will point wherever the previous registrant directed them. A domain pointing at a park page or a competitor's site does not correct itself. Update the DNS configuration promptly and confirm propagation through a standard lookup tool.
Second, registration renewal. The complainant inherits the domain's current expiry date. If that date is within weeks of the transfer, a renewal must be filed immediately through the new registrar. A domain that transfers and then lapses for non-renewal is not protected by the LDRP outcome; it simply re-enters the registration pool. Check the expiry date before the panel decision issues and build a renewal reminder into the file management.
Third, related zones. A successful .mx complaint does not extend to .com.mx, .org.mx, or the plain .com version of the same name. If the registrant holds the name across multiple zones, each requires its own separate action – the UDRP for gTLD versions, the LDRP for other .mx second-level strings, and potentially court action where the zones fall outside any existing arbitration procedure. Mapping the full domain portfolio of the bad-faith registrant before you file is worth the investment.
We regularly advise brand owners who recover a .mx name only to discover the registrant pivots to a .com.mx or a new-gTLD variant within days. Anticipating that move and filing in parallel across zones – where the facts support it – eliminates the pivot opportunity.
When does court action in Mexico become necessary?
The LDRP is not the only path, and it is not always the right one. Several scenarios push a dispute toward the Mexican courts rather than – or in addition to – the administrative procedure.
The clearest case is where the complainant also seeks monetary damages. The LDRP, like the UDRP, offers no monetary remedy. Transfer or cancellation is the ceiling. A brand owner who lost revenue to a fraudulent site operating under its .mx domain – phishing customers, redirecting orders – may have a claim for damages that only a court can award. That litigation requires local litigation counsel in Mexico, and the LDRP and court action can run in parallel on separate tracks.
A second scenario is where the .mx bad-faith registrant also holds equivalent names in zones that lack an administered arbitration procedure. A DENIC-style approach – blocking the domain from transfer while litigation proceeds – may be available through a Mexican court injunction, depending on the circumstances and the relief the court is willing to grant. Confirm the current procedural options with local litigation counsel before relying on that route.
A third scenario is where the LDRP complaint is defeated but the underlying trademark infringement or unfair competition claim survives. An unsuccessful LDRP outcome is not res judicata for a court action. The panel's findings are persuasive, not binding, on a court. A complainant who was denied transfer under the LDRP for a technical gap in the bad-faith record may cure that gap with additional evidence in a court proceeding – but that is a substantially more expensive route.
The decision matrix for .mx, in short: if you want the name back with minimum cost and delay, and your eligibility is clear, the LDRP is the right instrument. If you want damages, or if the registrant has spread the abuse across multiple zones with different governing procedures, the LDRP is necessary but not sufficient.
Related at COGNOMEN
Frequently asked questions
How do I start to transfer a .mx domain after a successful complaint?
Once the panel issues a transfer order under the LDRP, the procedure moves automatically to the implementation stage managed by NIC.mx and the registrar. You do not need to file a separate application. The practical actions on your side are: (a) confirm that you hold an accredited .mx registrar account ready to receive the domain; (b) monitor the implementation-pause window during which the losing party may seek a court stay; and (c) as soon as the domain appears in your account, update DNS settings and check the expiry date. Delays at this stage are almost always administrative, not legal.
What are the realistic outcomes when you transfer a .mx domain after a successful complaint?
A favorable LDRP decision orders either transfer or cancellation. Transfer places the domain in the complainant's name and is the preferred result. Cancellation deletes the registration, returning the name to the open pool – a weaker outcome because the original bad-faith registrant can, in principle, re-register it. Panels choose cancellation over transfer when the complainant has not established eligibility to hold a .mx domain, or where the facts make transfer inequitable. Establishing eligibility in advance is therefore essential to securing a transfer rather than a cancellation.
How do fees split if the case escalates?
At the LDRP administrative stage, official filing fees are set by the authorized provider (such as WIPO) and are paid by the complainant. If the respondent requests a three-member panel, the parties generally share the incremental cost of the larger panel under the standard UDRP-derived fee structure – confirm current .mx provider fees before filing. If the dispute escalates to Mexican court proceedings – whether for a stay of implementation or for a damages claim – court costs and local litigation counsel fees apply separately and are substantially higher than arbitration fees. The two tracks are financially independent; a court escalation does not affect the administrative fee already paid.
Author: Gabriel Tennison — ccTLD and European procedures (.uk, .eu, .de). Meet the team.
Speak with Cognomen Law
For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter
This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.