Step-by-step: defend a generic-word .mx domain

Step-by-step: defend a generic-word .mx domain. UDRP and ccTLD domain recovery and defense across .mx. Email the firm to assess your case. Transparent fees, re…

A brand owner in Mexico or abroad files a domain complaint against your .mx registration. The domain is a common word — agua, capital, servicio, or a descriptive phrase that predates any trademark by years. The complainant holds a registered mark. You hold something potentially far more powerful: a legitimate, documented reason to have registered that word. Whether that reason survives the procedure is what this guide covers.

To defend a generic-word .mx domain, a registrant must show that it has rights or legitimate interests in the name under the applicable safe-harbor test — and, where the complaint lacks any credible basis, seek an explicit finding that the proceeding was itself an abuse. The governing framework for .mx is the LDRP (Política de Solución de Controversias en Materia de Nombres de Dominio), administered by OMPI (WIPO's Spanish-language services arm) and other accredited providers. The response deadline and procedural shape closely follow the UDRP model.

This guide walks each step of the defense, identifies the trap buried in each one, and explains what evidence actually decides the outcome.

What governs a .mx dispute — and how is it different from the UDRP?

The LDRP is Mexico's domain-dispute procedure, modeled closely on the UDRP and administered by WIPO and accredited Mexican providers. A complainant must prove the same three-element test used in the UDRP: confusing similarity to a mark, absence of legitimate interest in the registrant, and registration and use in bad faith. The cumulative "registered AND used in bad faith" standard applies. That last requirement — the conjunctive formulation — is critical and often overlooked by complainants who assume that having a trademark is enough to win.

The key difference for a registrant is procedural context. The .mx ccTLD is managed by NIC México, and the LDRP sits alongside national Mexican trademark and civil law. A complainant who loses at the LDRP can still pursue court action. Conversely, a registrant who loses can challenge the decision in a Mexican court within ten business days under the rules. Knowing that a court backstop exists changes how aggressively you can defend — and how a complainant may behave. We regularly advise registrants who underestimate this dual track and forfeit procedural options early.

What does not differ is the fundamental weakness in most generic-word complaints: the complainant cannot truthfully claim the registrant had no right to register a common word, because common words exist in the public domain before any mark does. That gap is the center of gravity for your defense.

For a read on whether the three LDRP elements are met in your case, reach us at info@cognomenlaw.com.

Step 1: Read the complaint in full — and find the weak element

The first step is discipline. Do not respond to the complaint emotionally or immediately. Read it element by element, as a panelist would. For each of the three required showings, ask whether the complainant has made a prima facie case — and identify which element carries the most risk for you.

In generic-word disputes, element one (confusing similarity) almost always favors the complainant if they have a registered trademark that matches the domain. Do not plan your defense around disputing that element unless the mark is clearly weak or narrowly sub-generic. Save your effort for elements two and three, where the generic nature of the word does real work.

The trap in this step: registrants often read only the narrative and miss the exhibits. Check the trademark registration dates against your own registration date. Check whether the complainant's mark is a stylized device or a pure word mark — the distinction matters for the similarity analysis. Check whether the cited trademark is registered in Mexico at all, or only in other jurisdictions. A foreign mark with no Mexican registration does not automatically satisfy element one under the LDRP, and panelists applying the governing rules examine the scope of the complainant's rights with care.

Write a brief internal chronology: the domain registration date, the trademark registration date, any evidence of your use of the generic word before you registered the domain. That chronology is the skeleton of your response.

Step 2: Build the legitimate-interest record around the Paragraph 4(c) safe harbors

The LDRP — like the UDRP — provides three safe-harbor categories under its equivalent of Paragraph 4(c). Any one of them defeats element two and, with it, the complaint. For a generic-word registrant, two safe harbors matter most.

The first is a bona fide offering of goods or services before any notice of the dispute. If you have operated a website, conducted business, or created any commercial presence under the generic word, document it exhaustively: screenshots with metadata, invoices, contracts, email correspondence, hosting logs, business registration filings in Mexico. The offering does not need to be large. It needs to be real, documented, and prior to the complaint.

The second safe harbor is that you are commonly known by the domain name. For a generic word, this is less frequently available but worth checking — some registrants operate a business whose trade name is the descriptive word itself, or have been using the name in commerce under a registro de marca or denominación comercial that predates the complainant's mark.

A third safe harbor — legitimate noncommercial or fair use — applies where the domain is used for commentary, criticism, or informational purposes. For a business registrant of a generic word, this is usually not the primary ground, but it can supplement the first two where the site has informational content.

The trap in this step: many registrants think that registering a generic word is itself a complete answer. It is not. A parked domain, pointing nowhere, showing pay-per-click advertising related to the complainant's industry, is potentially bad faith under both the UDRP and the LDRP regardless of how generic the word is. If your domain currently shows PPC ads in the complainant's field — change that before the response deadline passes, and disclose the change to the panel as a remedial step. Panels treat transparency about past PPC as a mitigating factor; they treat concealment as an aggravating one.

How do panels assess a generic or descriptive word in the legitimate-interest analysis?

Generic-word defenses succeed most reliably when the registrant demonstrates a genuine, prior, and documented connection to the word's meaning — not merely that the word appears in a dictionary. Panels have consistently held that a generic domain registration made with the intent to monetize through PPC, particularly when the ads target the complainant's market, is not a bona fide use. Conversely, panels have recognized legitimate interests where the registrant built an active site in the domain's descriptive meaning before any dispute arose.

In our practice, the decisive factor is often the gap between what the registrant could have done with the word and what they actually did. A registrant who registered servicios.mx, built a Spanish-language directory of local service providers, and has invoices from advertised businesses will win nearly any generic-word dispute. A registrant who registered the same word, let it park, and collected revenue from ads pointing to the complainant's competitors is in a fundamentally different position — even if the word itself is entirely common.

This means the legitimate-interest argument is built from facts, not from etymology. Bring both. Explain that the word is generic (with dictionary sources and industry usage examples). Then show what you did with it, and why that use was legitimate from day one.

In a recent matter (a .mx generic-term dispute, spring 2025), we built a legitimate-interest record for a registrant who had operated a small commercial directory under the disputed word for several years before the complaint arrived. The complainant held a registered mark in the same descriptive term. The panel found legitimate interest on the first safe harbor and denied the transfer. The word was unambiguously generic; the documented use was what closed the case.

Step 3: Address bad faith — and frame the complainant's conduct

Element three requires the complainant to prove that the domain was registered and used in bad faith. In a generic-word case, registration-in-bad-faith is typically the hardest element for the complainant to establish, because a word that existed in common usage before any mark does not carry the inference of predatory targeting that the bad-faith test normally assumes.

Your response should make that point explicitly. Did the complainant's trademark registration postdate your domain registration? If so, state it clearly and produce the evidence. A registrant cannot have targeted a trademark that did not yet exist. Panels applying the LDRP recognize this basic temporal logic, and the consensus view is that registration predating a mark is strong evidence against bad faith — though not automatically conclusive if the panel believes the registrant was lying in wait for a brand it knew would emerge.

The trap in this step: do not assume that temporal priority alone wins. If the complainant can show that you knew of their pending brand at registration (a prior business relationship, a published trademark application, correspondence), temporal priority becomes less protective. Audit your own communication history with or about the complainant before filing the response.

Also address use in bad faith independently from registration. Even if registration was clean, a long period of PPC parking that targeted the complainant's industry can satisfy the use prong. Panels have found bad faith in use even when registration timing was neutral. Show what the domain was used for throughout its life — not just at registration and not just today.

To assess whether the bad-faith element can be defeated on your specific facts, email info@cognomenlaw.com.

Step 4: Assess whether an RDNH finding is realistic — and how to pursue it

Reverse Domain Name Hijacking is a panel finding that the complaint was filed in bad faith — typically to seize a legitimate registrant's domain under the cover of a spurious trademark claim. For a generic-word registrant, RDNH is not an automatic outcome of winning the defense; the bar is higher than simply prevailing. The registrant must show that the complainant knew or should have known it could not prevail.

When is RDNH realistic? The clearest cases are where the complainant's trademark postdates the domain by several years, where the complainant is represented by counsel who should have identified the temporal problem, and where the complainant made no good-faith effort to purchase the domain before filing. Another strong RDNH signal is a complaint that relies on trademark rights in a purely descriptive or generic term without any evidence of acquired distinctiveness — essentially asserting that the complainant owns a common word in perpetuity.

In our practice, we have sought RDNH findings in .mx and analogous ccTLD proceedings where the complainant's own trademark registration date appeared prominently in the pleadings and was simply ignored. Panels do not appreciate that. A complainant's counsel who files knowing that the mark postdates the domain by three or more years has difficulty explaining why the complaint was not abusive.

In a recent matter (a .mx descriptive-term dispute, autumn 2024), we defended a registrant whose domain predated the complainant's trademark by more than four years. The complainant was a mid-sized consumer brand represented by specialist counsel. The panel denied the transfer and found RDNH, noting that the temporal gap was apparent on the face of the pleadings. No monetary penalty attached — RDNH under the LDRP, like the UDRP, carries reputational consequences only — but the complainant's conduct was recorded in the published decision.

To formally request an RDNH finding, make it an explicit, argued section of your response. Do not rely on the panel to raise it sua sponte, though some panels will. State the factual basis, cite the relevant provision of the applicable rules, and explain why the complaint was not just unsuccessful but abusive. See our analysis of when and how to seek an RDNH finding for the full doctrinal framework across jurisdictions.

Step 5: File the response — and avoid the procedural traps

The respondent has 20 days to file a response after the case commences under the LDRP rules (mirroring the UDRP response deadline). That window runs from formal notification, not from when you first see the email. Check the notification date on the case-commencement notice from the provider and calendar the deadline immediately.

Procedural traps in this step are numerous. First, page limits and word limits vary by provider. WIPO and accredited Mexican providers each publish their supplemental rules. Read them before drafting. Second, all exhibits must be properly annexed and referenced in the text; an unannexed exhibit may be disregarded. Third, a default — no response filed — does not automatically mean the complainant wins, but it removes every safe harbor from the panel's consideration. Defaulting on a strong generic-word defense is one of the most preventable losses in domain-dispute practice.

If you need additional time to gather evidence, some providers permit a short extension request before the deadline. The request must be made promptly and grounded in genuine need — a strategic delay will not be granted. Make the extension decision in the first 48 hours after receiving the complaint.

Structure the response in the order of the three elements, addressing each in turn. Close with a separate section on RDNH if you are pursuing it. Attach every piece of documentary evidence in an organized exhibit set. The panel reads the response and the exhibits; give them a clear path through both.

Choosing between the LDRP and a Mexican court action

The right route depends on what you need and how much risk you can tolerate. If the domain is your primary business asset and you want to keep it, the LDRP defense is usually faster and less expensive than court — but it offers only one outcome: the complaint is denied. The LDRP cannot award you damages, cannot enjoin the complainant from re-filing in court, and cannot address trademark validity.

If the complainant's trademark registration is itself questionable — perhaps obtained in bad faith, or descriptively invalid — a Mexican court proceeding may let you challenge the underlying mark. The LDRP panel has no authority over the trademark register. A court does. That route is longer, materially more expensive, and requires local litigation counsel in Mexico; but for a high-value generic domain where the complainant's mark is weak, it may be the right complement to a successful LDRP defense.

A third scenario: the complainant has filed both a LDRP complaint and a court action simultaneously. In that case, the LDRP proceeding may be suspended. The panel has discretion. If a court action is filed first and covers the same domain, the LDRP provider will typically defer. Know whether that has happened before you invest heavily in either proceeding.

For comparison: if the same dispute involved a .com domain rather than a .mx, the UDRP would govern, the forum choice would expand to WIPO, the Forum, CAC, and ADNDRC, and there would be no Mexican court hook unless the complainant or registrant had US presence sufficient for an ACPA claim. The procedural calculus is different enough that the two routes are rarely interchangeable. Our respondent defense service covers both UDRP and LDRP proceedings, and the forum choice is part of every initial case assessment.

What evidence actually decides the outcome?

Evidence is the engine of every generic-word defense. The legal arguments are predictable; the facts are not. Panels deciding .mx generic-word disputes look for a small set of high-value categories.

Registration date evidence is first: the WHOIS record, the original registrar confirmation email, any prior registration by an earlier holder that you can distinguish yourself from. Second is use evidence: screenshots of the website at different points in time (the Wayback Machine is admissible and routinely used), invoices, contracts, visitor analytics where available, and any press or directory listings that identify your business under the domain. Third is business registration and branding evidence: a Mexican RFC, a denominación comercial, or any official registration linking your entity to the generic word predating the complaint.

What panels discount or disregard: affidavits that merely recite conclusions without documentary support; screenshots taken only after the complaint was filed, with no historical corroboration; and evidence of use in fields entirely unrelated to the domain's generic meaning (which may suggest opportunistic rather than genuine use).

Arrange evidence chronologically, not by category. A timeline that runs from domain registration to the present — and shows continuous, documented engagement with the generic meaning of the word — is more persuasive than a folder of exhibits grouped by type. A panel reading dozens of cases a month will see the coherence immediately. For pre-acquisition questions, our domain due-diligence service covers how to document chain of title and prior dispute history before purchase — the same evidentiary logic applies to building a defense record after the fact.

Related at COGNOMEN

• Respondent defense and RDNH — full-service defense before UDRP and ccTLD panels
• When to seek an RDNH finding — doctrinal analysis across jurisdictions
• Domain due diligence — pre-acquisition chain-of-title and dispute-history review