How to prove a legitimate interest in your .mx domain

How to prove a legitimate interest in your .mx domain. UDRP and ccTLD domain recovery and defense across .mx. Email the firm to assess your case.

A brand owner files a complaint against your .mx domain. The letter arrives – formal, confident, citing trademark registrations you have never heard of. Your first instinct may be to assume you are in the wrong. That instinct is often incorrect. The .mx dispute procedure, known as the LDRP (Política de Resolución de Disputas de Nombres de Dominio), is an administrative proceeding in which you, as the registrant, have a recognized right to show that your registration is legitimate.

To prove a legitimate interest in your .mx domain, you must bring your case within one or more of the safe harbors recognized under Paragraph 4(c) of the LDRP – the same safe harbors that mirror the UDRP's Paragraph 4(c) structure – by showing a bona fide offering of goods or services before notice of the dispute, that you are commonly known by the domain name, or that you are making legitimate noncommercial or fair use of the name. Building that record requires contemporaneous, verifiable documentation assembled before the response deadline. A respondent who defaults, or who files an unsupported denial, rarely succeeds.

This page covers the LDRP procedure that governs .mx domains, the three safe harbors and how to satisfy each, the evidence that decides outcomes, when a finding of Reverse Domain Name Hijacking is realistic, and the practical next step for a registrant who has just received a complaint.

What procedure governs .mx domain disputes?

The .mx dispute procedure – the LDRP, administered through NIC México and resolved by approved dispute-resolution providers – closely tracks the UDRP structure that applies to .com and other generic top-level domains, but it operates under Mexican registry rules. A complainant must prove all three UDRP-mirrored elements: that the domain is identical or confusingly similar to a trademark in which the complainant has rights; that the registrant has no rights or legitimate interests in the domain; and that the domain was registered and is being used in bad faith. All three must be satisfied. A complainant who proves only two elements does not win.

This three-part test is structurally identical to Paragraph 4(a) of the UDRP. The LDRP therefore draws on the same body of accumulated panel reasoning. Panels reviewing .mx disputes consider the same analytical distinctions – descriptive terms, geographic references, personal names, reseller sites – that UDRP panels have addressed for over two decades. That body of consensus reasoning is a resource for respondents, not just complainants.

Who adjudicates? The providers approved for .mx disputes include WIPO, which brings its established administrative apparatus to the proceeding. Procedures, timelines, and specific rules may vary by provider; a registrant should confirm the current NIC México-approved providers and their procedural rules with counsel at the outset. What remains constant is the three-part test and the safe-harbor structure that the LDRP adopts from the UDRP.

Why does the burden shift in element two – and what does that mean for you?

Under the LDRP, the complainant bears the initial burden on each element, but element two – rights or legitimate interests – operates differently in practice. Once a complainant makes a prima facie case that the registrant lacks rights, the burden of production shifts to the registrant to come forward with evidence. That shift is procedurally significant. It means a registrant who simply denies the allegation, without filing supporting evidence, is treated as though no legitimate interest exists.

This is the single most consequential procedural point for a respondent. Silence is not neutrality. A default – failing to file any response within the prescribed deadline – is almost always fatal. Panels regularly transfer domains where the registrant never appears, even in cases where the registrant may have had a perfectly defensible position. Why? Because the panel has no record to review. The respondent's evidence is the respondent's responsibility.

In our practice, we regularly advise registrants who received a complaint days or even hours before a deadline they did not know existed. The LDRP response deadline is strict. If you have received a commencement notice, the time to act is now, not after you have consulted informally or waited for a second letter that will not come.

For an immediate assessment of whether your .mx registration falls within a recognized safe harbor, contact info@cognomenlaw.com. We read the complaint, identify the strongest legitimate-interest argument, and advise on the evidence you need to produce before the deadline.

How do the three legitimate-interest safe harbors apply to .mx registrations?

The LDRP's Paragraph 4(c) safe harbors give a registrant three recognized routes to establish legitimate interest, each with a different evidentiary foundation. Understanding which route fits your situation determines what documentation you need to gather.

Safe harbor one: bona fide use before notice of the dispute

This is the strongest and most commonly litigated safe harbor. A registrant who was using the domain in connection with a genuine offering of goods or services – before receiving any notice of the dispute – can bring itself within this harbor. The key word is "before." Panels look at whether the use predates the complaint and whether it is genuinely commercial rather than pretextual.

What constitutes bona fide use? A functioning e-commerce site, a service directory, a lead-generation platform with real customers, a business that invoiced under the domain name – all can qualify, depending on the totality of the record. What does not qualify: a bare parking page with pay-per-click links, a site assembled after the complaint was filed, or a nominal placeholder with no commercial activity. The temporal sequence matters. The evidence of use must be contemporaneous – screenshots, server logs, invoices, registration certificates, social media history – not reconstructed from memory at the time of filing the response.

Safe harbor two: commonly known by the domain name

A registrant who is, in fact, commonly known by the domain name – as an individual, a business, or an organization – can establish legitimate interest even without trademark rights. This harbor is particularly useful for registrants whose personal name, trade name, or established nickname corresponds to the domain. Evidence includes business registration documents showing the name predates the dispute, government-issued identification, customer correspondence using the name, social media handles, and industry listings.

The harbor is narrower than it first appears. A registrant must actually be known by the name, not merely assert it. Panels scrutinize the timing: a registrant who changed its trade name to match the disputed domain shortly after acquiring it will not convince a panel that the name is genuinely theirs.

Safe harbor three: legitimate noncommercial or fair use

This harbor covers criticism sites, fan pages, commentary, and other uses that are genuinely noncommercial and do not mislead consumers or tarnish the mark. It is the narrowest harbor in practice. A site that carries advertising – even modest advertising – may lose its noncommercial character. And a site that purports to be criticism but primarily offers to sell the domain will not qualify.

For .mx registrants, this harbor is most relevant where the domain is used for genuine public commentary about a brand's conduct in the Mexican market, without any commercial component and without falsely implying an affiliation with the brand owner.

What evidence actually decides a .mx legitimate-interest defense?

A legitimate-interest defense is built on contemporaneous documentary evidence, not on narrative assertions. Panels in LDRP and UDRP proceedings have consistently held that self-serving statements without corroboration carry little weight. The record that persuades a panel is one where the documents tell the story, and the written argument organizes what the documents already prove.

The core evidence categories are as follows. First, pre-dispute use evidence: archived versions of the website (internet archive screenshots with dates), invoices or purchase orders under the domain-connected business name, payment processor records, and customer correspondence. Second, business identity evidence: trade name registrations with Mexican governmental authorities, RFC (Registro Federal de Contribuyentes) records if the business is tax-registered under the relevant name, and corporate formation documents. Third, trademark evidence, if any: a Mexican trademark registration or an application predating the disputed domain's registration is a powerful anchor, though it is not required. Fourth, correspondence history: any prior communications with the complainant, including any demand letter and your response to it, which establish the temporal sequence of events.

One practical point we emphasize in every respondent matter: gather the evidence before you draft the argument. The argument follows the evidence. A response that leads with legal conclusions and then scrambles for supporting documents almost always reads as weaker than one where the exhibits are assembled first and the written sections are organized around them.

In a recent matter (a .mx domain used for a genuine B2B services platform, spring 2025), we built the respondent's record around RFC filings, two years of client invoices under the domain-associated name, and archived website screenshots predating the complainant's first demand letter by eighteen months. The complaint was denied. No transfer was ordered.

When is a finding of Reverse Domain Name Hijacking realistic?

Reverse Domain Name Hijacking – RDNH – is a panel finding that the complainant brought the complaint in bad faith or to harass a legitimate registrant. An RDNH finding carries no monetary penalty under the LDRP, but it is a formal, published finding against the complainant that affects its credibility in future proceedings. For a registrant, it validates the defense publicly and creates a record that can deter future abusive complaints.

When do panels find RDNH? The threshold is real but achievable in the right set of facts. Panels have found RDNH where: the complainant knew or should have known it could not satisfy one of the three elements; the complaint relied on a trademark filed after the domain was registered; the complaint was filed against a registrant with a long, documented, and public history of legitimate use; or the complainant engaged in conduct suggesting the true motive was commercial – to obtain a domain it could not buy, rather than to protect a right it genuinely holds.

What a respondent should understand is that simply winning on the merits does not produce an RDNH finding. The respondent must affirmatively request it and support that request with argument and evidence showing the complaint was brought with knowledge of its weakness or for an improper purpose. We assess RDNH potential at the outset of every respondent engagement, and we request it where the facts support the argument. A respondent who has a plausible RDNH claim but does not raise it waives a meaningful form of relief.

In a second recent matter (a .mx geographic-term domain, autumn 2024), we represented a registrant who had held the domain since the early commercial internet period in Mexico. The complainant's trademark was filed years after the domain's creation date. We prevailed on all three elements and the panel issued an RDNH finding, noting that the complainant's own submissions acknowledged the registration date discrepancy.

How does the LDRP compare with other dispute routes for .mx?

The right route depends on the zone, the goal, and the registrant's or claimant's position. For .mx, the primary administrative route is the LDRP. But understanding what the LDRP does not offer – and when a court route is necessary – shapes the strategy on both sides of the dispute.

The LDRP, like the UDRP, offers only two remedies: transfer of the domain to the complainant or cancellation of the registration. It cannot award monetary damages. It cannot issue an injunction restraining the complainant's trademark use. It cannot address related misconduct – for example, a bad-faith demand letter campaign, or a pattern of filing weak complaints for leverage. If any of those remedies are relevant to the registrant's position, court action in the relevant Mexican jurisdiction, handled with local litigation counsel in the relevant jurisdiction, is the only path that reaches them.

Conversely, if the complainant's only goal is the domain itself, the LDRP is almost always faster and less expensive than litigation. A typical LDRP case resolves in a matter of weeks to a few months, consistent with the general UDRP timeline – compare that with Mexican court proceedings, which typically take considerably longer and generate substantially higher costs for both sides.

For a registrant deciding whether to defend through the LDRP, through court, or both: the LDRP defense preserves the domain (if successful) and creates a published panel decision. Court proceedings can do more, but cost more and take longer. In most .mx disputes we see, the LDRP is the correct initial forum. Where the complainant has also filed a court action, or where the registrant has independent claims (unfair competition, tortious interference), the two tracks run in parallel with local litigation counsel coordinating the court side.

One cross-zone point worth noting: if the disputed name is registered in both .mx and .com, a single UDRP complaint at WIPO may cover both domains if they share the same registrant of record. The filing fee for a WIPO single-member complaint covering one to five domains is USD 1,500. A respondent in that scenario is defending both zones in a single proceeding – the .com under the UDRP and the .mx under the LDRP, likely before the same panel, on one consolidated record. That concentration of risk makes early legal advice especially important.

If you have received a LDRP complaint, a UDRP complaint covering a .mx domain, or a demand letter threatening proceedings, email info@cognomenlaw.com. We assess the three elements, identify the best safe-harbor route, and advise whether RDNH is in play before you commit to a response strategy.

What are the most common mistakes .mx registrants make in their defense?

After reviewing a significant number of LDRP and UDRP respondent files, we have identified the mistakes that most reliably produce a lost domain. They are not subtle. They are practical failures that a prepared registrant can avoid entirely.

The first and most common mistake is defaulting. A registrant who does not file a response by the deadline forfeits the proceeding. There is no late filing as of right, no automatic extension, and in many cases no second notice. The domain transfers because the registrant did not appear.

The second mistake is filing a response without exhibits. A written assertion that you have been using the domain for years, without a single supporting document, is treated as an unsupported claim. Panels have consistently held that bare assertions carry no weight.

The third mistake is addressing only element two – legitimate interest – while ignoring element three – bad faith. A respondent who demolishes the bad-faith allegation often wins even if the legitimate-interest argument is weaker. The two defenses reinforce each other and should be developed together.

The fourth mistake is misunderstanding the RDNH threshold. Some registrants think any wrongly filed complaint triggers RDNH automatically. It does not. The request must be argued and supported. Other registrants think RDNH is not worth requesting because there is no monetary penalty for the complainant. That calculation misses the reputational and deterrent value of the finding, particularly for brand owners who file complaints serially.

The fifth mistake is waiting too long to seek advice. The response deadline in administrative proceedings is real and short. A registrant who spends the first two weeks of the response period informally researching the procedure before consulting counsel often finds that the remaining time is insufficient to build the evidence record properly.

Related at COGNOMEN

• Respondent defense and RDNH across gTLDs and ccTLDs
• Defending a UDRP complaint over a .net domain – strategy and evidence
• Reversing an unauthorized domain transfer in Brazil