Step-by-step: prove a legitimate interest in your .es domain

Step-by-step: prove a legitimate interest in your .es domain. UDRP and ccTLD domain recovery and defense across .es. Email the firm to assess your case.

A complaint lands in your inbox. A Spanish brand owner – or an overseas company with a Spanish trademark – is demanding the transfer of your .es domain, and the clock is already running. The instinct is to search for the quickest exit. The smarter move is to understand whether you have a legitimate interest in the name, because if you do, that interest is a complete defense under the applicable rules.

To prove a legitimate interest in your .es domain you must demonstrate that your registration and use fall within one of the recognized safe harbors under the governing .es dispute procedure administered by Red.es: a bona fide commercial use before notice of the dispute, a genuine connection between you and the name, or a legitimate noncommercial or fair use. The standard closely tracks the Paragraph 4(c) safe harbors of the UDRP, which all three UDRP elements must be proven by the complainant to succeed. Build your record early; the evidence you do not document before the deadline is evidence you cannot introduce later.

This guide walks each step of the legitimate-interest defense for .es, flags the trap hidden inside every step, and explains when an RDNH finding – a declaration that the complaint itself was abusive – is a realistic objective.

What rules govern .es disputes, and how do they differ from UDRP?

The .es dispute procedure is administered by Red.es, the Spanish registry, under its own regulatory framework – not the UDRP, though the .es rules incorporate concepts that will be familiar to anyone who has handled a gTLD complaint. The core test asks whether the registrant has a legitimate right or interest in the domain and whether the registration was made in bad faith. That two-limb structure maps loosely onto Paragraph 4(a)(ii) and 4(a)(iii) of the UDRP, but the procedural rules, timelines, and available evidence standards are specific to Red.es.

Why does that distinction matter? Because importing a UDRP-based argument directly, without adjusting for the .es procedural context, is a common error. Panels applying the .es rules look at the same underlying conduct – use of the domain, the intent behind registration, the timing relative to the complainant's trademark – but they do so under a national regulatory instrument, not ICANN's Policy. A defense built around UDRP authorities alone may carry less weight than one grounded in the .es rules themselves. We regularly advise registrants who file a technically competent UDRP-style brief and then lose on a .es procedural point they never saw coming.

One procedural difference that catches respondents off guard: the .es system imposes strict response deadlines, and extensions are not freely available. The 20-day response window familiar from the UDRP is a useful reference point, but verify the current Red.es rules with counsel before assuming that figure applies verbatim to your case. Miss the filing date and you default; a default is treated as an admission that no legitimate interest exists.

Step 1 – Identify which safe harbor applies to your situation

The first decision in any legitimate-interest defense is which safe harbor you are actually trying to invoke, because each one demands different evidence and carries different traps. Three categories cover almost every defensible registration.

Bona fide commercial use before notice of the dispute. If you were using the domain in connection with a genuine offering of goods or services before you received any complaint or cease-and-desist, you have a potential foothold. The trap: the use must be genuine. Parking pages, pay-per-click links, and thin affiliate pages typically do not qualify as bona fide use – panels have consistently found that monetizing a domain through third-party advertising, with no substantive content of your own, is insufficient. Document the nature and timeline of your commercial activity carefully.

Commonly known by the name. If you, your business, or your organization is commonly known by the domain name – even without a registered trademark – that can establish a legitimate interest. This safe harbor is often underused by respondents who assume you need a trademark to defend a domain. You do not. What you need is evidence of association: business records, incorporation documents, invoices issued under the name, customer correspondence, social media history, or press references. The trap: "commonly known" is a factual question, not a legal declaration. The longer your history and the more varied the evidence, the stronger the case.

Legitimate noncommercial or fair use. Fan sites, criticism sites, commentary pages, and informational resources can qualify – provided they do not create a false impression of official endorsement and are not used to divert commercial traffic for gain. The trap: a criticism site that also carries affiliate links or sell-side advertising will be scrutinized hard. Keep the fair-use lane clean.

Which safe harbor fits your situation? That is the first question to answer, because it drives every evidence-gathering step that follows.

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

Step 2 – Build the legitimate-interest record before the response deadline

A legitimate-interest defense stands or falls on contemporaneous documentation. "Contemporaneous" means evidence created before or during the period in question, not assembled after the complaint arrives. This is the step where the most capable respondents lose: they wait until the complaint triggers the search for proof, and the proof they find is thin, recent, or ambiguous.

Start with a timeline. Map every material event in the domain's history: the date of registration, the first substantive use, any correspondence with the complainant or third parties, and any changes in the site's content or purpose. That timeline becomes the skeleton of your response, and any gap in it is a gap the complainant's counsel will exploit.

Assemble evidence in these categories, in rough order of persuasive weight:

• Business registration or incorporation documents showing use of the name before the domain complaint was filed.
• Invoices, contracts, purchase orders, or delivery confirmations that reference the name and predate the notice of dispute.
• Web archive captures (available through publicly accessible archiving services) showing the domain's content at different points in time. Date-verified screenshots differ from live screenshots; ensure your captures are timestamped and verifiable.
• Tax filings, advertising records, or marketing materials under the name.
• Third-party press references, directory listings, or reviews naming your business by the domain name.
• Customer-facing correspondence – emails, support tickets, order confirmations – using the domain name as your identity.

The trap at this step: respondents often produce a large volume of documents without a coherent narrative. Quantity is not persuasion. Each piece of evidence should be introduced with a brief factual statement tying it to the timeline. A panelist reading a 40-document exhibit with no index or introduction will give it less credit than a 10-document exhibit clearly organized around the key dates.

Step 3 – Address the timing of registration relative to the complainant's mark

One of the most consequential facts in any .es respondent case is whether the complainant's trademark rights existed at the time you registered the domain. If they did not – if your registration predates the mark – the bad-faith registration element cannot typically be established, and a well-constructed defense will say so clearly.

How do you verify the dates? Pull the public WHOIS or RDDS record for your domain and confirm the original registration date. Then obtain the complainant's trademark registration certificate and check the application date, the registration date, and the claimed first-use date. If your domain predates even the trademark application, say so explicitly, with the documents attached. Do not assume the panelist will do that comparison unaided; lay it out.

The trap here is more subtle: some complainants assert common-law or unregistered rights that predate your registration, arguing that the mark was well-known before it was registered. That argument is strongest for genuinely famous marks. For lesser-known brands, panels have regularly declined to extend the bad-faith analysis to cover registrations that preceded any recognizable public presence. Your response should address the common-law argument directly if the complaint raises it, with any evidence showing that the name was not distinctively associated with the complainant at the date of your registration.

In a recent matter (a .es domain registered by a small regional services company, spring 2025), we secured a rejection of the complaint after demonstrating that our client's registration predated the complainant's trademark application by more than four years. The complainant had not alleged common-law rights and could not cure that omission in a supplemental submission.

How does RDNH apply in .es, and when is it worth pursuing?

Reverse Domain Name Hijacking – a finding that the complainant brought the proceeding in bad faith, typically to deprive a legitimate registrant of a domain – is available under the UDRP and under ccTLD procedures that mirror the UDRP's abuse-prevention mechanism. Whether the .es dispute procedure provides a formal RDNH finding or an equivalent declaration of abusive complaint depends on the current Red.es rules; verify the precise remedy with counsel before treating this as a certainty.

What does RDNH require? In the UDRP context – which informs ccTLD analogs – panels have consistently held that an RDNH finding requires more than a failed complaint. The complainant must have filed knowing that it could not prevail, or with the primary purpose of interfering with a legitimate registrant rather than genuinely asserting trademark rights. The clearest RDNH cases share a pattern: the complainant knew the respondent's registration predated the mark; the complainant held only a weak or narrow mark and tried to use the dispute process to acquire a domain it could not otherwise obtain; or the complainant's trademark was geographically limited and the domain was registered entirely outside that scope.

Is RDNH worth pursuing in your case? Three conditions make it realistic. First, the complaint must be factually weak – not simply unsuccessful, but demonstrably ill-founded at the time of filing. Second, you need a clear record of the complainant's awareness of facts that undermine its own case (a prior negotiation, a public use history, a correspondence record). Third, the costs and reputational stakes must justify the additional briefing effort, because an RDNH claim that does not succeed risks being read as overreach rather than legitimate defense.

We have built the legitimate-interest record, documented good-faith registration, and sought RDNH findings in .es-adjacent cases where the complainant's conduct warranted it. The decision to pursue that finding is strategic, not automatic.

To weigh whether an RDNH finding is realistic in your .es dispute, email info@cognomenlaw.com.

Step 4 – Draft the response: structure, tone, and what to omit

A response to a .es domain complaint is a legal submission, not a customer-service letter. It should be structured around the elements the complainant must prove, not around your feelings about the fairness of the claim. That distinction sounds obvious. Respondents who draft their own responses routinely confuse the two, and the result is a document that is emotionally compelling and legally ineffective.

The structure to follow is element by element. Under each element, state the complainant's burden, then address whether it is met on the facts, then attach the evidence. For the legitimate-interest element specifically, identify the safe harbor, introduce the evidence chronologically, and explain what each document shows. Do not assume the panelist will draw the inference you intend; state the inference explicitly.

Tone matters. Accusations of bad faith against the complainant – without the documentary foundation to support them – reduce your credibility. If you have the evidence for an RDNH argument, make it; if you do not, do not hint at it. Panels distinguish between a respondent who is genuinely aggrieved and one who is simply hostile.

What to omit: lengthy recitals of general UDRP doctrine that do not connect to the .es rules; exhibits that are duplicative or unlabeled; arguments about the complainant's commercial motives that are not supported by evidence. A tight, well-organized 12-page response with 10 labeled exhibits will generally outperform a 35-page submission with 60 unnumbered attachments.

In a second matter we handled (a .es geographical term domain, late 2024), the original response drafted by the registrant personally ran to 28 pages of factual narrative with no legal structure. We reorganized it around the three operative elements, cut it to 14 pages, and added five key exhibits that had been omitted. The outcome was a rejection of the complaint on the legitimate-interest element alone.

Step 5 – Decide whether the .es dispute or a UDRP at another forum is your actual battlefield

This step catches many registrants off guard. A complainant with both a Spanish trademark and an international portfolio may file simultaneously – or sequentially – under the .es procedure for the domain you hold and under the UDRP for related gTLD domains. If that happens, you face concurrent proceedings under different rules, with different evidentiary standards and different timelines.

The decision matrix here is practical. If the dispute is confined to the .es domain and the complainant has no viable gTLD claim, the .es proceeding is the only battlefield and you can focus entirely there. If the complainant holds a .com or other gTLD counterpart that it is also targeting, your UDRP response strategy should be consistent with your .es defense – the same timeline of use, the same legitimate-interest narrative – even though the two proceedings run independently. Inconsistency between a UDRP response and a ccTLD response, when both become public record, is a vulnerability that experienced complainant's counsel will exploit.

If the complainant holds only a Spanish registered trademark with no international extension, its UDRP standing for a .com is limited. That matters for portfolio planning: a registrant who wins on the .es but loses a related .com because of an inconsistent record has achieved only a partial outcome. The right moment to think about the cross-zone picture is before the first response is filed, not after both decisions are issued.

The UDRP at WIPO handles the largest volume of these cases – WIPO administered approximately 6,282 domain-name cases in 2025, a record – and the Forum is the second most common venue. For a .es dispute alongside a .com filing, the two proceedings require coordinated strategy, not parallel but separate filings. We coordinate exactly that kind of cross-zone defense, identifying the governing national procedure, checking eligibility, and ensuring consistency across all active filings.

What evidence decides the outcome? A decision checklist

After years of handling respondent-side ccTLD cases, the evidence that most often decides close legitimate-interest disputes falls into a predictable short list. Use this as a pre-submission checklist.

• Registration date vs. trademark priority date: the single most important fact in most cases. If your registration predates the complainant's trademark rights by any margin, that margin must be prominently stated with documentary proof.
• Continuous and substantive use: panels distinguish between a domain that has been actively used in commerce and one that has been parked or lightly developed. Archived page captures across multiple years of genuine use are among the most persuasive exhibits.
• Business identity connection: a company name, trading name, or personal name that corresponds to the domain creates a strong legitimate-interest inference. Corporate registration predating the domain registration is ideal; longstanding use of the name in trade is the fallback.
• Absence of targeting: evidence showing that you did not know of the complainant's mark when you registered, and that the domain was not chosen because of that mark, is important even when you cannot prove it affirmatively. Absence of evidence of targeting is itself evidence.
• Communications record: any prior negotiation, offer, or demand between the parties before the complaint was filed is part of the record. Document it accurately and completely; do not cherry-pick.

The AUDIENCE_MYTH worth addressing here: many registrants believe that if they have not done anything wrong, the complaint will obviously fail. That is not how dispute panels work. The complainant bears the burden, but burden does not shift automatically in the respondent's favor because of inaction. An undocumented legitimate interest is legally the same as no legitimate interest at all. The record you build is the case you make.

Related at COGNOMEN

• Respondent defense and RDNH services – how COGNOMEN builds the legitimate-interest record and pursues abuse findings
• When to seek an RDNH finding in an app-domain dispute – analysis of the conditions that make the finding realistic
• Brand protection monitoring FAQ for .ca – how domain monitoring intersects with dispute preparedness