Case study: defend a .mx domain against a UDRP complaint

Case study: defend a .mx domain against a UDRP complaint. UDRP and ccTLD domain recovery and defense across .mx. Email the firm to assess your case.

A registrant in Mexico City had held a short, descriptive .mx domain for several years. The name combined a common Spanish-language commercial word with a numeric suffix. Then a complainant filed a UDRP complaint, asserting trademark rights and demanding transfer. The registrant had no idea the Policy applied to a country-code domain – and was right to wonder whether it did.

Mexico's .mx registry has adopted a dispute procedure – the LDRP (Lineamientos para la Resolución de Disputas relativas a Nombres de Dominio) – that closely tracks the UDRP's three-element test. Where a complainant files under that procedure, the registrant has 20 days to respond before a default decision may issue. The key defenses mirror those of Paragraph 4(c) of the UDRP: a bona fide use before notice of the dispute, a legitimate noncommercial or fair use, or being commonly known by the name.

This case study covers the situation, the defense strategy, and the outcome – anonymized, with no case numbers or party names.

The Situation: A Descriptive Domain and a Late-Filed Complaint

The registrant had operated a small import business under the domain since well before the complainant's trademark application was filed. The domain matched the complainant's registered mark phonetically, but the registration date told a different story. Our client had first registered the name years earlier. The complainant was a foreign company with no established presence in Mexico at the time of that registration.

The complaint alleged bad faith under the standard four-factor list: registration to sell to the mark owner, disruption of a competitor, and attraction of users by confusion. Each allegation read plausible on its face. None held up once we assembled the evidence.

The Strategy: Building the Legitimate-Interest Record

Winning a respondent defense requires more than pointing out weaknesses in the complaint. The panel needs an affirmative record. We identified three parallel lines of evidence.

First, we documented the registration date relative to the complainant's trademark priority date. Chronology is often decisive. If the registrant could not have known about the mark at the time of registration, bad faith under the cumulative "registered and used" standard is very difficult to establish. The complainant's earliest trademark filing postdated our client's domain registration by a meaningful margin.

Second, we gathered business records – invoices, supplier agreements, a business-registration certificate, and archived web captures – showing continuous commercial use of the domain in connection with a genuine trade. These materials directly addressed the Paragraph 4(c) bona fide offering safe harbor. Evidence of this kind is not optional; it is the core of a legitimate-interest defense.

Third, we assessed whether the complaint met the threshold for a reverse domain name hijacking finding. RDNH is available where the complaint was brought in bad faith to deprive a legitimate registrant of a domain. The complainant here had filed without conducting basic due diligence: a simple RDDS search would have disclosed the registration date well before the trademark. That gap was worth pressing.

If you have received a UDRP or LDRP complaint and believe your registration predates the complainant's trademark rights, the response window is short. For a read on whether the three UDRP elements are met, reach us at info@cognomenlaw.com.

The Outcome: Transfer Denied, RDNH Finding Sought

In a matter of this type (a .mx descriptive-term domain, spring 2025), the panel denied transfer on all three grounds. The registrant's documentation of pre-dispute use was found sufficient to establish a legitimate interest. The complainant's trademark post-dated the registration, which the panel held fatal to bad-faith registration under the cumulative test. Because the complainant had access to the registration date before filing and chose to proceed regardless, the panel also made an RDNH finding.

An RDNH finding carries no financial penalty – that is a limitation of the procedure. Its practical value is reputational: it is a formal record that the complaint was abusive. In the domain industry, and in any follow-on litigation, that finding matters.

What decided the outcome was evidence, not argument. The registrant's business records, assembled before the response deadline, carried the case. Without them, the same chronological argument would have been considerably weaker.

If a prior complaint produced a bad result, or if you are facing a first filing and want to understand the realistic paths, email info@cognomenlaw.com.

Related at COGNOMEN

• Respondent defense and RDNH – full service overview across gTLDs and ccTLDs
• FAQ: what if you registered the domain before the trademark existed?
• Guide: recovering a hijacked domain when US court action is the route