Step-by-step: respond to a UDRP complaint within the deadline for a .eu domain

A .eu domain dispute has its own rulebook. The complaint lands in your inbox, and the clock starts immediately. Before you can mount any defense, you need to understand which procedure actually governs – and the answer is not the UDRP as most brand owners or investors understand it from .com practice.

The .eu dispute procedure is administered through the Czech Arbitration Court's ADR.eu platform, not WIPO or the Forum. It operates under the EURid Dispute Resolution Rules, which draw on UDRP principles but carry distinct differences in eligible rights, available remedies, and EU eligibility requirements. The respondent's deadline to file a response is set by those rules; missing it typically results in a default decision on the complainant's written record. This guide walks every step, flags the trap each step contains, and identifies the evidence that decides the outcome.

The sections below move from receipt of the complaint through the final decision, covering how to build a legitimate-interest record under the .eu rules, when a finding of bad faith by the complainant is realistic, and how the .eu procedure compares with UDRP at WIPO or the Forum for a concurrent gTLD dispute.

Why the .eu dispute procedure is not the same as the UDRP you may already know

The EURid ADR procedure borrows the three-limb structure of the UDRP but re-states each limb in ways that matter at the response stage. Under the UDRP, bad faith requires proof that the domain was registered and used in bad faith – both limbs cumulative. Under the .eu rules the complainant may argue that the registration was abusive at the point of acquisition or that subsequent use became abusive; the precise drafting of the operative provision is a material point your response must address.

The rights recognized by the .eu rules are also broader than under the UDRP. A complainant may rely on unregistered trade name rights, company names, and other identifiers recognized under national EU member-state law – not just registered trademarks. That cuts both ways. A complainant with thin rights may still have standing; a respondent with a legitimate business name or prior commercial use may have a stronger Paragraph 4(c)-equivalent safe harbor than they would on .com. Identifying which rights the complainant is actually asserting, and then testing whether those rights meet the applicable standard, is the first analytical task in any .eu response.

The remedies available at ADR.eu also differ from the pure UDRP menu of transfer or cancellation. A .eu decision may order transfer or revocation, and the complainant must meet EU/EEA eligibility requirements to hold a .eu domain if transfer is ordered. Where the complainant lacks that nexus, revocation rather than transfer may be the only available remedy. That distinction can affect settlement strategy before a decision is issued.

Step 1: Confirm receipt and identify your actual deadline

The moment a .eu complaint is formally commenced at ADR.eu, the panel administrator notifies the registrant of record. The response deadline runs from the date of commencement – not the date you notice the email. That gap can be consequential. Domain contacts managed through privacy services, forwarded mailboxes, or legacy WHOIS addresses sometimes delay actual receipt by days the rules do not recognize as an extension.

The first practical step is to log into the ADR.eu case portal and confirm the exact commencement date. From that date, calculate your response deadline using the rules in force at the time of filing. Do not rely on a date communicated informally by a registrar representative; always verify against the case record in the portal. The trap in this step is assuming the clock runs from the day you open the email rather than the day the proceeding was formally commenced.

If you have any reason to believe the deadline has already begun running before you saw the complaint, contact ADR.eu immediately. Extensions are rare and discretionary, but the panel administrator has powers to address manifest procedural unfairness. Acting within the first twenty-four hours of actual discovery is materially better than acting on day five.

To weigh UDRP against the ADR.eu procedure for your specific .eu dispute, email info@cognomenlaw.com. We regularly advise registrants who first learn of a complaint with only days remaining in the response window.

Step 2: Read the complaint carefully and map the three elements

A well-drafted .eu complaint will assert each of the three required elements: that the registrant's domain is identical or confusingly similar to a name in which the complainant has rights; that the registrant has no legitimate interest in the domain; and that the domain was registered or is being used abusively. Before you draft a single line of response, map what the complainant has actually pleaded under each element – and note what they have not pleaded, because a gap in their argument is a gap you exploit.

Typical complainant tactics in .eu disputes include citing a registered EU trademark as the rights basis while sidestepping the fact that the mark postdates the domain registration, asserting that a generic or descriptive domain inherently targets the brand, or relying on the absence of an active website as evidence of passive abusive use. Each of these arguments has a recognized counter-position. A domain that predates the complainant's trademark filing is not registerable as abusive in relation to rights that did not yet exist. A descriptive term legitimately registered by a party in its own right-line business is a classic safe harbor. Passive holding, while recognized as potentially abusive in some .eu decisions, requires additional circumstantial evidence beyond the mere absence of content.

The trap in this step is the impulse to argue everything at once. A response that identifies two strong, evidence-backed defenses is far more persuasive than a response that raises seven points at unequal depth. Choose your best ground and build the record around it.

How do you build a legitimate-interest record under the .eu rules?

The equivalent of the UDRP's Paragraph 4(c) safe harbors under the .eu rules recognizes legitimate use arising from a bona fide offering of goods or services before notice of the dispute, common identification with the name independently of the complainant's mark, and legitimate noncommercial or fair use. Demonstrating any one of these requires a document trail, not a declaration.

What constitutes a strong legitimate-interest record for a .eu respondent depends on the factual basis of the registrant's claim. Consider the following categories:

• Prior use in trade. Invoices, contracts, supplier agreements, website captures, advertising materials, or social media presence that demonstrate use of the name in connection with goods or services before the complainant first contacted the registrant.
• Registration rationale. Correspondence or business records showing why the domain was registered – for example, a new product launch, a geographic or descriptive term that the registrant uses independently.
• Absence of targeting intent. Evidence that the registrant did not know of the complainant's mark at the time of registration, particularly relevant where the complainant's mark is limited in geographic scope within the EU or was not published or promoted in the registrant's home market.
• Ongoing development or use. Screenshots, archived pages, development logs, or hosting records showing that the domain has been in active or planned use rather than passively parked.

We have consistently advised .eu registrants that the quality of the supporting evidence matters more than its quantity. A single dated invoice showing genuine commercial use of the name predating the dispute will usually outweigh three paragraphs of narrative explanation. Assemble the documents first; write the narrative around them second.

One specific trap: submitting evidence in a language other than the language of the proceeding without a certified translation. The ADR.eu rules specify language requirements, and untranslated annexes may be disregarded by the panel. Verify the required language before finalizing your exhibit list.

Step 3: Assess when an RDNH finding is realistic

Reverse Domain Name Hijacking – a panel finding that the complaint was brought in bad faith to deprive a legitimate registrant – is an available finding under the ADR.eu procedure as well as under the UDRP. It carries no monetary penalty but has genuine reputational and, in some cases, practical value: an RDNH finding is on the public record, which can deter a serial complainant or support a subsequent court action for abuse of process in the relevant national jurisdiction.

RDNH findings are not routinely awarded. They require that the complainant knew or clearly should have known it could not succeed. The clearest grounds are: the domain predates the complainant's rights; the complainant's rights are limited or unregistered and the evidence of secondary meaning is thin; the complainant failed to disclose material facts; or the complainant filed in a jurisdiction with lower cost (ADR.eu) in a transparent attempt to overpower a legitimate registrant.

In a recent matter – a .eu domain, spring 2025, involving a geographic term – we secured an RDNH finding for a registrant who had held and actively used the name for several years before the complainant's trademark was even filed. The complainant had access to the public WHOIS record and the domain's published content and should have known the claim was untenable. The finding did not produce a monetary recovery, but it resolved the dispute cleanly and put the record straight.

The trap in seeking RDNH is overreaching. A respondent who requests an RDNH finding without a strong evidentiary foundation risks drawing attention to weaknesses in the legitimate-interest argument. If the RDNH case is solid, make it explicitly and with cited evidence. If it is merely plausible, reserve it as a secondary argument rather than a primary theme.

If a prior ADR.eu filing produced an adverse outcome or you believe a complaint was filed in bad faith, email info@cognomenlaw.com. A focused review can identify whether RDNH or an appeal path is available.

Step 4: Draft and file the response before the deadline

The ADR.eu response must be filed through the case portal; email submission is not a substitute for portal filing. The response should be organized to address each of the three elements in the same order the complaint raised them – this structure makes the panel's review easier and signals that you are engaged with the actual legal test rather than offering a general narrative defense.

A well-structured .eu response contains: a brief factual background; an element-by-element analysis tied to the applicable rules; an evidence section that identifies each exhibit by number and explains what it proves; a conclusion that specifies the relief sought (dismissal, and where warranted, an RDNH finding); and a signed certification.

Keep the submission tight. Panels read many cases; a response under fifteen pages that makes three clear, documented arguments is more persuasive than one of thirty pages that buries the key facts. If your legitimate-interest case turns on a single dated contract, lead with it. If your RDNH case turns on the fact that the complainant's trademark postdates your registration by three years, state that in the second paragraph, not the twelfth.

The practical trap in this step involves exhibit management. File all supporting documents as numbered, properly formatted PDF or image files through the portal in a single submission. Submitting exhibits piecemeal or in formats the system does not accept can result in the panel disregarding them. Verify format requirements in the current ADR.eu rules before filing – the technical specification for submissions occasionally changes between filing rounds.

Step 5: Understand the decision timeline and what happens next

After the response is filed, the ADR.eu administrator appoints a panelist. For a single-member panel, the decision timeline is typically a matter of weeks after the response deadline closes. Either party may request a three-member panel; if the complainant requested a single panelist and the respondent requests three members, the cost differential is addressed per the applicable ADR.eu fee schedule. Always check current ADR.eu published fees, as the cost structure differs from the WIPO schedule set out in APPENDIX A for gTLD proceedings.

A .eu panel may: dismiss the complaint outright (the domain remains with the registrant); order transfer to the complainant (subject to EU/EEA eligibility); order revocation (the domain is deleted rather than transferred); or decline to find RDNH even while dismissing. There is an appeal mechanism within the ADR.eu rules, but it involves a three-expert panel and its own filing requirements and fees. If you intend to appeal an adverse decision, act promptly – the window is short and the grounds for admission of new evidence on appeal are limited.

One scenario that deserves specific planning: a dispute that spans both a .eu domain and a .com or other gTLD version of the same name. If both domains are in play, the .eu procedure and the UDRP are running simultaneously with different timelines, different panelists, and different legal standards. The evidence assembled for the ADR.eu response is generally re-usable in the UDRP proceeding, but the framing must be adapted to each forum's specific elements. We regularly manage parallel proceedings for registrants holding the same name across multiple zones, and the failure to coordinate the two filings is a recurring source of inconsistency that complainants exploit in their reply submissions.

How does the .eu dispute route compare with UDRP or court action?

Choosing the right route matters, but for a .eu respondent the choice is imposed more than it is elected – the complainant files at ADR.eu, and you respond there. The question of route comparison becomes relevant at the margins: where the registrant also holds a .com, where the complainant is threatening parallel court action in an EU member state, or where the respondent is considering proactive steps such as a declaratory action in the relevant national jurisdiction before or during the ADR.eu proceeding.

The comparative picture runs as follows. ADR.eu offers the registrant the advantage of a neutral, rule-bound process with published fees and a reasoned decision. The disadvantage is that the process is entirely paper-based and does not allow oral argument or cross-examination. Evidence submitted by a complainant cannot be challenged directly; the respondent can only submit contrary evidence and argument. Where the dispute involves a highly contested factual question – for example, whether the registrant had actual knowledge of the complainant's mark at the time of registration – the paper record is the entire record.

Court action in the relevant EU member state can reach the dispute more thoroughly. A national court can award damages, grant injunctions, and hear live evidence. It is also substantially more expensive and slower. For a registrant defending a legitimate registration with good documentation, the ADR.eu paper process is usually preferable. For a registrant who has lost at ADR.eu and holds strong new evidence, court action may be the only available next step.

A UDRP at WIPO for a concurrent .com domain raises its own timing question. The WIPO single-member panel filing fee starts at USD 1,500 and a standard case resolves in approximately two months. The ADR.eu timeline is broadly comparable but the fee structure differs. Where both are pending, we recommend filing the ADR.eu response before finalizing the UDRP response, because the ADR.eu legal standard may be slightly more favorable to the respondent in certain fact patterns, and a successful ADR.eu dismissal can provide persuasive (though not binding) authority for the WIPO panel considering the same name under a parallel complaint.

What evidence actually decides a .eu dispute?

The evidence that most frequently determines the outcome of a .eu respondent proceeding falls into three categories, roughly in descending order of decisiveness.

First, the registration date and the complainant's rights date. A domain registered before the complainant's trademark was filed, published, or in use cannot logically have been registered to target rights that did not yet exist. This is the strongest single fact in a respondent's arsenal, and it is often available from public records alone – the domain's creation date from the registry and the complainant's trademark filing date from the relevant EU or national trademark database.

Second, evidence of the registrant's own prior legitimate use. This has been discussed above. Its decisive weight comes from specificity and dating: an undated screenshot of a website is far less useful than a web archive capture with a verifiable timestamp, or an invoice dated to a specific month and year that predates the dispute by a meaningful margin.

Third, the conduct of the registrant after notice of the dispute. Changing DNS records, attempting to sell the domain to the complainant at a high price, or publicly disparaging the complainant's mark after receiving the complaint can all supply bad-faith evidence that an otherwise strong legitimate-interest defense cannot overcome. The trap is instinctive reaction: do not change anything about the domain between receipt of the complaint and the filing of your response without first obtaining advice on how that change will read in the record.

In a further matter handled in autumn 2024 – a .eu domain registered for a legitimate regional services business – we built the response around a combination of prior-use evidence (regional advertising predating the complainant's EU trademark by approximately two years) and a clear showing that the complainant's mark had no meaningful consumer recognition in the registrant's operating market. The complaint was dismissed. No RDNH finding was sought because the complainant's rights, while thin, were real enough to give them standing to file.

Related at COGNOMEN

• UDRP and ccTLD respondent defense – how COGNOMEN builds the legitimate-interest record and pursues RDNH findings
• FAQ: defending a domain on fair use and descriptive-term grounds across gTLD and ccTLD disputes
• Domain assignment agreements for .com – structuring a transfer with due diligence and clean title

Author: Anton Grant — Respondent defense and reverse domain name hijacking (RDNH). Meet the team.

Speak with Cognomen Law

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

Domain in disputeYour sideI want to recover a nameI received a complaint — I need a defensePortfolio / brand protectionWhat happenedEmailI agree to the processing of my enquiry as described in the privacy policy.Assess my case

No obligation. Confidential. We reply within two hours in business hours.

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