How to defend a .es domain against a UDRP complaint

How to defend a .es domain against a UDRP complaint. UDRP and ccTLD domain recovery and defense across .es. Email the firm to assess your case.

A complaint lands in your inbox. Someone has filed against your .es domain before WIPO or the Forum, claiming your name infringes their trademark. You have 20 days to respond once the case commences — and the clock does not pause while you consider your options.

To defend a .es domain against a UDRP complaint, you must answer all three elements of Paragraph 4(a) of the UDRP: challenge the complainant's trademark rights or confusing similarity, establish your own rights or legitimate interests under Paragraph 4(c), and rebut the bad-faith allegations. The UDRP applies to .es because Red.es — Spain's domain registry — has adopted the Policy for .es registrations. A default hands the panel an uncontested record; a timely, evidence-backed response is your only protection.

This page covers the procedural setting for .es disputes, the safe harbors that matter most, how to build a winning record, and when to seek a finding of Reverse Domain Name Hijacking.

Why the UDRP applies to .es and what that means for respondents

Red.es, the Spanish government body that administers the .es ccTLD, has adopted the UDRP as its mandatory dispute-resolution procedure for .es domains. That means the full framework of the Policy — the three-element test, the safe harbors, and the forum rules — applies to your .es registration in essentially the same way it applies to a .com. WIPO and the Forum both accept .es complaints. The governing rules and the evidentiary standards are those of the UDRP, not a distinct Spanish national procedure.

This matters for respondents in two ways. First, the institutional and procedural familiarity of the UDRP works in your favor if you know how to use it. Second, the complainant carries the burden on all three Paragraph 4(a) elements. Panels will not transfer a domain simply because a trademark exists and the names resemble each other. The complainant must also prove you lack any legitimate interest — a showing that depends heavily on facts you supply in your response.

There is also a critical cross-zone dimension worth noting at the outset. If you hold the .com, .net, or a second ccTLD variant alongside your .es, the complainant may file a consolidated complaint covering all registrations under a single holder. A consolidated defense — one response addressing every domain — is generally more efficient and ensures consistent positions across the record.

If you have just received a UDRP complaint against your .es domain, contact info@cognomenlaw.com for an assessment of the three elements and the response deadline in your specific case.

What does the UDRP three-element test require when defending a .es domain?

The complainant must prove all three elements of Paragraph 4(a) — each one independently — and the panel must find against you on all three before a transfer order issues. Challenge any element successfully and the complaint fails.

Element one: confusing similarity. This is the threshold test. Panels compare the domain to the trademark as registered. Generic or descriptive additions — a geographic suffix, a common noun, or a product category — rarely defeat confusing similarity. But where the domain predates the trademark, or where the mark is weak and the domain is a common word or phrase, there is genuine scope to contest this element on the merits.

Element two: rights or legitimate interests. The burden shifts here in practice. Once the complainant makes a prima facie case, you must produce evidence of your own legitimate interest. Paragraph 4(c) provides three safe harbors: (a) a bona fide offering of goods or services before you received notice of the dispute; (b) being commonly known by the domain name; or (c) legitimate noncommercial or fair use without intent to mislead for commercial gain. Panels assess the totality of the evidence. A domain that has pointed at an active, relevant website for years is a materially stronger position than one that has sat parked or redirected.

Element three: registered and used in bad faith. The UDRP uses a conjunctive standard — registered and used. Panels have consistently held that both conditions must be met at the same time, across the registration period. If you registered the domain before the complainant's trademark existed, that fact goes to both registration and use in bad faith simultaneously. A longstanding registration with legitimate active use is among the strongest defenses available.

Note an important distinction from some ccTLD procedures. The Nominet DRS for .uk, for example, reads "registered or used" abusively — a lower bar for complainants. The UDRP's cumulative standard is comparatively more protective for registrants, and you should not assume the .es procedure tracks the .uk model.

How do you build the legitimate-interest record for a .es domain defense?

Assembling a credible legitimate-interest record before the response deadline is the core task of a .es domain defense. What you include — and how you present it — often determines the outcome.

Start with the registration history. When was the domain registered? What was the stated reason? If the registration predates the complainant's mark — or predates the complainant's first use in Spain or the EU — that chronology is your most durable asset. Document it with the registrar's WHOIS history, archive screenshots, and any correspondence from the time of registration.

Next, document use. Evidence of an active website, a running business, a published blog, or even consistent email use tied to the domain all demonstrate a bona fide offering. Panels draw adverse inferences from a domain that has been persistently parked or redirected to a pay-per-click page. If your .es pointed at a legitimate site, pull the archived versions from web crawl records covering the full registration period.

Third, consider personal name or business name evidence. If your legal name, your company's registered name, or a well-known trading name corresponds to the domain, that falls squarely within the safe harbor for being "commonly known by the name." Spanish commercial registry records, tax filings, business licenses, and long-standing correspondence addressed to that name all serve as exhibits.

Finally, address the complainant's theory of bad faith directly. Paragraph 4(b) lists non-exhaustive bad-faith circumstances: registering to sell to the mark owner at a profit, disrupting a competitor, attracting users through confusion for commercial gain, and engaging in a pattern of abusive registrations. For each one the complainant raises, the response should either negate the factual predicate or affirmatively present contrary evidence. Silence on a bad-faith allegation is never safe — panels treat unanswered allegations as uncontested.

In a recent defense matter involving a .es domain (autumn 2024), we built a legitimate-interest record centered on a Spanish company's pre-trademark registration history and seven years of continuous active use. The panel found the complainant had failed on both elements two and three, and the domain remained with the registrant.

When is a Reverse Domain Name Hijacking finding realistic in a .es dispute?

Reverse Domain Name Hijacking — an RDNH finding — means the panel concludes the complainant brought the complaint in bad faith to deprive a legitimate registrant of a domain it was entitled to hold. The finding carries no monetary penalty, but it is a formal, published rebuke that damages the complainant's credibility and serves as a public record.

RDNH is realistic when one or more of the following conditions is present. First, the complainant filed knowing the domain predated its trademark. A complainant who can see from the registration date and trademark registration certificate that the domain was registered years before its rights existed — yet filed anyway — is in RDNH territory. Second, the complainant mounted a weak or pretextual case: the trademark is generic, the similarities are superficial, or the bad-faith theory depends on speculation rather than evidence. Third, the complaint appears to be a leveraged acquisition attempt — where the complainant already tried to buy the domain at a negotiated price and, upon refusal, filed a UDRP complaint.

Requesting an RDNH finding is not a defensive afterthought. It requires a dedicated section of the response, citing the specific conduct that makes the filing abusive. The request alone does not bind the panel, but panels have consistently declined to find RDNH where the respondent merely asserted it without argument. Build the record for it just as you build the record for your legitimate-interest defense.

One clarification: RDNH panels apply a high threshold. A complaint that simply loses on the merits does not automatically become RDNH. The panel looks for something more — typically, that the complainant knew or should have known the complaint could not succeed, yet filed regardless.

If you believe the complaint against your .es was filed without a genuine basis, email info@cognomenlaw.com. We regularly advise registrants on whether the specific facts support an RDNH request.

What evidence decides the outcome in a .es UDRP defense?

Panels decide .es UDRP cases on the written record alone. There is no hearing, no live testimony, and no cross-examination. Every fact you want the panel to consider must appear in your response, properly supported by documentary exhibits.

The exhibits that carry the most weight in a respondent defense are: (1) dated screenshots showing active use of the domain over time; (2) registrar records or archived WHOIS data establishing the registration date; (3) trademark registers confirming the complainant's mark date and scope; (4) commercial registry extracts, licenses, or invoices demonstrating the registrant's business under the name; and (5) correspondence or prior negotiation records if the complainant approached you before filing — that sequence is directly relevant to both legitimate interest and RDNH.

Format matters. Panels read dozens of cases; a well-organized response with numbered exhibits and concise headings is easier to follow and less likely to miss a critical point. The response narrative should address each of the three elements in turn, directly engage the complainant's arguments, and direct the panel to the specific exhibit that rebuts each allegation.

Do not rely on the response alone. If there is genuinely relevant supplemental material — a development that postdates the complaint — check the applicable forum's rules on supplemental filings. WIPO and the Forum each have their own standards. Supplemental filings are generally disfavored, but a narrow, relevant submission submitted promptly and with a credible procedural basis can be accepted.

How does the .es defense timeline and forum choice work?

Once a UDRP complaint against your .es is filed, the relevant forum — typically WIPO for .es matters — notifies you and commences the case. From that commencement date, you have 20 days to file your response. Extensions are available only in narrow circumstances; missing the deadline is not recoverable in the normal course.

A standard single-member UDRP case runs approximately two months from filing to decision. A three-member panel adds time for the appointment process but gives you greater procedural flexibility — you may request a three-member panel even if the complainant chose a single panelist, though doing so splits the higher three-member panel fee between the parties.

The WIPO filing fee for a single-member panel on a single .es domain is USD 1,500. If the respondent requests a three-member panel, the panel fee rises to USD 4,000, with the parties generally splitting the incremental cost. There is no filing fee payable by the respondent unless it requests the upgrade to a three-member panel. Legal fees for a respondent defense are separate from forum fees and vary with case complexity.

What drives the three-member panel decision? In high-value domains, where credibility determinations are central, or where RDNH is a serious objective, a three-member panel provides more process and, in our experience, more thorough engagement with a complex record. For a clear-cut registration-predates-trademark defense, a single-member panel is often sufficient.

A practical note on cross-zone strategy: if the same complainant holds proceedings against your .es and your .com simultaneously, the response timelines may not align. We have managed coordinated defenses across both zones — the .com under the UDRP and a ccTLD under its own procedure — ensuring consistent positions and no gap in the record that a panel in one forum could use against a position taken in the other.

Decision matrix: which response strategy fits your .es domain?

The right strategy depends on the specific facts, not a template. Here is how the main scenarios map to a response approach.

If your .es was registered before the complainant's trademark came into existence, the core defense is a registration-predates-trademark argument. Build the chronological record — registration date, first use evidence, trademark filing date — and address bad faith directly. That combination, handled well, defeats element three and often element two as well. RDNH is a realistic companion request if the complainant's filing date and trademark date are obviously incompatible.

If you operate a legitimate business under the domain name and the complainant is a later entrant in a different market, the element-two safe harbor under Paragraph 4(c)(i) — a bona fide offering before notice of the dispute — is your primary line. Document the business thoroughly: commercial registry, invoices, correspondence, the active website. The complainant may have rights in its mark, but that does not extinguish yours.

If the domain is a common word or a geographic term in Spanish, element one may be contestable on confusing similarity itself. Generic or descriptive terms in the .es zone are frequently registered by local businesses with legitimate purposes, and a trademark in a single category does not monopolize the word. That argument, combined with a strong element-two record, is a two-front defense that many complainants have not adequately prepared for.

If the domain has been dormant or parked — pointing at pay-per-click ads — the defense is harder but not impossible. A credible development plan, supported by business registration or investment documentation, can demonstrate legitimate interest even where the domain is not yet actively used. Panels have held that a registrant need not have launched a site; the intent to develop must be genuine and supported. That distinction is fact-intensive, and the response must be precise.

In all scenarios, a .es defense that reaches the right conclusion on strategy — contest all three elements, support every assertion with exhibits, request RDNH where warranted — is materially more likely to succeed than a generic denial. We have defended registrants across all four scenarios above, including a .es generic-term defense (spring 2025) where we secured a denial and a published RDNH finding after the complainant filed a speculative complaint against a domain the registrant had held for more than a decade.

Related at COGNOMEN

• UDRP respondent defense and RDNH – the full service overview
• Domain registered before a trademark: how to build the defense record
• URS vs. UDRP: choosing the right procedure for a tech-sector domain

About COGNOMEN

COGNOMEN is an independent boutique focused exclusively on domain-name disputes. We recover, defend, and transact internet domains across generic and country-code zones, before WIPO, the Forum, CAC, ADNDRC, and national procedures, and in court where arbitration cannot reach. We act for brand owners, domain investors, and registrants — including respondent-side defense and reverse domain name hijacking. Our practice is solely domain disputes: every matter we handle involves a domain name at its center. We have defended registrants across .es, .com, .eu, and a range of other zones, including in consolidated multi-domain proceedings. To discuss a domain, contact info@cognomenlaw.com.

By Anton Grant — Respondent defense and RDNH practice, focusing on contested UDRP cases where registrants face speculative or abusive complaints across gTLD and ccTLD zones.

Disclaimer: This article is general information about domain-name dispute procedures and does not constitute legal advice. Outcomes depend on the specific facts, the zone, and panel or court discretion. For advice on your domain, contact info@cognomenlaw.com.

Speak with Cognomen Law

For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter

Related

• Respondent Rdnh
• Registered Before Trademark Nl
• Case Urs Vs Udrp Tech

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.