How to prove a legitimate interest in your .eu domain

How to prove a legitimate interest in your .eu domain. UDRP and ccTLD domain recovery and defense across .eu. Email the firm to assess your case.

A complaint lands in your inbox. Someone is claiming that your .eu domain violates their trademark rights, and the ADR.eu procedure has begun. You have a limited window to respond – and your answer must do more than deny the allegation. It must prove, affirmatively, that you have a legitimate interest in the name.

To prove a legitimate interest in your .eu domain, you must satisfy one of the recognized safe harbors under the ADR.eu rules: demonstrable use of the domain in connection with a bona fide offering of goods or services before notice of the dispute, recognition as a person or entity commonly known by the name, or legitimate noncommercial or fair use without intent to mislead. The Czech Arbitration Court administers .eu disputes, and the filing fee begins at approximately USD 500–800 – but the legal record you build before a panelist reviews your case is what actually decides the outcome.

This page sets out the governing rules, the evidence that supports each safe harbor, the fact patterns that produce wins and losses, and when an RDNH finding against the complainant is realistic.

What governs .eu disputes, and why ADR.eu is not the UDRP

The .eu dispute procedure is administered through the Czech Arbitration Court's ADR.eu platform under rules that differ in meaningful ways from the UDRP that applies to .com and other gTLDs. Understanding those differences is the first task in building a defense.

Under ADR.eu, the complainant must establish three elements: that the domain is identical or confusingly similar to a name in respect of which a right is recognized under EU or national law; that the respondent has no rights or legitimate interests in the domain; and that the domain was registered or used in bad faith. That third element reads "registered or used" – a materially lower bar than the UDRP's cumulative "registered and used." A complainant who cannot show bad-faith registration may still succeed by showing bad-faith use, and vice versa.

What does that mean for a respondent? It means your legitimate-interest evidence must be strong enough to neutralize both limbs of the bad-faith analysis simultaneously. A showing that you registered in good faith is necessary but not sufficient if your use of the domain later became problematic. Equally, consistent legitimate use throughout the registration period can address a weak registration narrative.

There is a further structural point. The ADR.eu rules allow a wider set of "rights" on the complainant's side than registered trademarks alone. A complainant may invoke unregistered marks, trade names, or other commercial designations recognized under EU or member-state law. That flexibility sometimes produces complaints against registrants who hold names that happen to overlap with a mark the complainant is assembling – which is one reason a respondent must scrutinize the claimed right carefully at the outset, not just accept the complainant's characterization.

In our practice, we find that a significant share of .eu complaints rests on a claimed right that is weaker than it appears at first reading. Identifying that weakness is as important as building your own legitimate-interest record.

How to prove a legitimate interest in your .eu domain: the three safe harbors

The legitimate-interest question has three recognized pathways, each requiring a distinct body of evidence. A respondent may rely on any one of them; in practice, the strongest defenses document more than one.

Safe harbor one: bona fide use before notice of the dispute. This is the most commonly invoked pathway. "Before notice" means before the complaint was filed or before the complainant sent a cease-and-desist communication – whichever is earlier. The operative word is "bona fide": the use must be genuine, directed at ordinary commercial or community activity, and not constructed solely to manufacture a defense after the threat materialized.

Evidence in this category includes: dated screenshots of the active website tied to the domain; sales records, invoices, or service agreements referencing the domain; registered business names or company registrations that predate the complaint; advertising expenditure linked to the domain; and third-party references (press mentions, directory listings, customer correspondence) that establish public association of the name with your activity. The timestamps on these materials matter enormously. A website cached by an independent archival service carries more weight than a screenshot you produce yourself.

Safe harbor two: commonly known by the name. If the domain corresponds to your personal name, a business name, or a brand under which you are publicly recognized – and that recognition predates the dispute – you may argue this pathway. Evidence includes business registration documents, official correspondence addressed to the name, trademark registrations (even in a different class or jurisdiction), press coverage, and customer-facing materials. The less formal your public profile, the harder this pathway is to establish; a well-documented paper trail is essential.

Safe harbor three: legitimate noncommercial or fair use. Commentary, criticism, fan activity, and community projects have all been recognized under this heading, but panels apply it narrowly where there is any suggestion of commercial intent. The domain must not be used to divert consumers or to tarnish the mark. A criticism site that clearly identifies itself as such, displays no advertising, and does not redirect visitors to a competitor's offering is the clearest example. Mixed-use sites – part commentary, part commerce – produce unpredictable outcomes.

One practical note that applies to all three pathways: the burden of proof shifts once the complainant makes a prima facie case that you lack a legitimate interest. At that point, silence or a bare denial is not enough. You must come forward with affirmative evidence. This is the juncture at which a respondent who has not kept good records is most exposed.

For an assessment of whether your .eu registration fits one of these safe harbors, contact info@cognomenlaw.com.

What evidence actually decides .eu disputes: a closer look at the record

Panels deciding .eu disputes weigh the totality of the record, and the quality of the evidence a respondent produces almost always matters more than the volume of it. Here is what separates a convincing defense from one that fails on the facts.

Contemporaneous documentation is the foundation. A registration made years before the complainant's mark was filed, supported by business records from that period, is far harder to attack than a registration that followed the complainant's market entry. Panels look at whether the chain of evidence is internally consistent: do the business registration, the domain registration date, the earliest website capture, and the first customer reference all tell the same story?

In a matter we handled in spring 2025 – a .eu domain held by a regional services company, with the domain targeted by a complainant who had filed a trademark application only after the domain was already active – the registrant's invoices and archived site pages from the relevant period produced a clear chronological record that predated the claimed mark. The complaint did not survive the legitimate-interest analysis.

Independent corroboration carries the greatest weight. A web archive capture from a neutral third-party service, a government-issued business registration document, a news article referencing the domain, or a supplier invoice with the domain in a signature block all represent evidence that the respondent did not generate for purposes of the dispute. Panels treat such materials differently from self-authored declarations or after-the-fact screenshots.

Gaps in the record are exploited by complainants. If you registered the domain and then let the associated website go dark for an extended period, the complainant will argue that passive holding – with no active use – evidences bad faith. Passive holding is not automatically fatal to a defense, but it creates a narrative problem. The remedy is either a well-documented explanation for the dormancy (a genuine business pause, a redesign period documented internally) or evidence of resumed use before the complaint was filed.

The domain's purchase price matters in a transaction context. If you acquired the domain in the secondary market for a significant sum, and the price bears no relationship to ordinary market value for a generic term, a panel may draw inferences about the registrant's intent. Conversely, a market-rate acquisition of a genuinely descriptive or generic string, documented through a standard escrow transaction, supports a good-faith narrative.

What should you not do? Alter website content after the complaint is filed, manufacture correspondence predating the dispute, or build a use record retroactively. Panels have seen these tactics before. They are not just ineffective – they actively damage credibility on every other point in the response.

If a prior filing or response produced a bad outcome, a focused second read can find the element that was missed. Reach us at info@cognomenlaw.com to review the record.

When is a reverse domain name hijacking finding realistic in a .eu dispute?

Reverse domain name hijacking (RDNH) is a finding that the complaint was brought in bad faith – essentially, that the complainant used the dispute process as a tool to deprive a legitimate registrant of a domain it has every right to hold. ADR.eu panels recognize this concept, and in our practice we assess RDNH potential in every respondent matter we take on.

An RDNH finding is most realistic when several conditions are present together. The complainant's claimed right is thin or arose after the domain registration. The complaint makes claims about the respondent's conduct that the evidence plainly does not support. The complainant is a sophisticated commercial actor who retained counsel – meaning the filing cannot be attributed to ignorance of the rules. And the complainant failed to conduct basic diligence before filing (the domain registration date is public; the complainant's own trademark filing date is a matter of record).

In a matter we defended in autumn 2024 – a .eu domain held by an individual who had operated a personal-name-based consulting practice for several years – the complainant filed a trademark application one month before the complaint and then asserted priority over a domain registered three years earlier. The panel found the complaint abusive and entered an RDNH finding. No monetary award followed – that is consistent with the ADR.eu approach, which does not provide damages or costs sanctions in the same way a court would – but the reputational consequence for the complainant was significant and the registrant retained the domain.

RDNH is a finding of last resort for panels. They do not make it on the basis of a weak complaint alone; the record must show that the complainant knew, or clearly should have known, that the complaint could not succeed on the merits. For respondents, seeking RDNH proactively means arguing it explicitly in the response, pointing to the specific facts that reveal the improper purpose, and not simply hoping the panel will reach it on its own.

How does the .eu procedure compare to the UDRP and to national court?

The right route depends on which name is threatened and what remedy you need. A registrant facing a cross-zone dispute – for example, a complaint targeting both a .eu and a .com variant of the same brand – must manage two different procedures simultaneously, under two different legal tests.

For the .eu: the ADR.eu procedure at the Czech Arbitration Court is the primary dispute-resolution path. The filing fee begins at approximately USD 500–800 – the lowest entry point among the major dispute forums. The procedure is administrative; the panelist does not hold a hearing, and the record is built entirely on written submissions and documentary evidence. The remedy can include transfer to the complainant or revocation of the registration. Unlike UDRP, the complainant may rely on a broader class of rights, including unregistered marks and trade names recognized under EU or member-state law.

For a .com running alongside the .eu: a parallel UDRP complaint would be filed at WIPO or the Forum. The WIPO filing fee for a single domain starts at USD 1,500 for a single-member panel. The UDRP test requires the complainant to show bad faith in both registration and use – a higher bar than the ADR.eu "or" formulation. A registrant who wins an ADR.eu proceeding does not automatically prevail in the parallel UDRP; the legal standards are genuinely distinct, and the record must be tailored for each.

For a .de domain in the same portfolio: there is no UDRP for .de. A dispute over a German-zone domain proceeds through the German courts, and DENIC offers a DISPUTE entry to block transfer while litigation proceeds. That is a materially different cost structure and timeline from administrative arbitration. Where a registrant holds names across .eu, .com, and .de – a common portfolio configuration – we coordinate the response strategy across all three zones rather than treating each in isolation.

What about going to a national court for a .eu dispute instead of ADR.eu? A complainant (or a respondent seeking a declaratory judgment) may file in a national court of a member state. Courts can award damages and injunctions that the ADR.eu procedure cannot. The trade-off is cost, time, and the uncertainty of litigation. For most registrants defending a legitimate registration, the ADR.eu procedure is the faster and less expensive path; national court is reserved for situations where the stakes justify the investment or where a declaratory judgment is strategically necessary.

What a respondent defense actually involves: the process step by step

A .eu respondent has a defined window to file a response after commencement of the ADR.eu proceeding. Missing that window results in a default, and a default – while not automatic grounds for transfer – removes your ability to present any legitimate-interest evidence. Acting promptly is not optional.

The defense process, as we work through it with clients, follows this sequence.

First, assess the complaint. Read the complainant's claimed right carefully. When was the trademark filed or registered? Is it an EU mark or a national mark, and in which class? Does the alleged similarity between the mark and the domain actually meet the confusing-similarity threshold, or is the overlap superficial? A complaint that fails at element one does not require a legitimate-interest analysis at all.

Second, gather the contemporaneous record. Pull domain registration confirmations, earliest website captures, business registration documents, and all dated materials that establish use or recognition before the dispute notice. The older the materials, the stronger the chronological story.

Third, match the evidence to the applicable safe harbor. Each of the three pathways above has a distinct evidentiary profile. We identify which safe harbor or combination best fits your factual record, and we build the response around that argument rather than producing a general denial decorated with documents.

Fourth, evaluate RDNH potential. If the complainant's conduct meets the standard described above, we argue RDNH explicitly. This is not routine in every defense; it requires a threshold assessment of the complainant's state of knowledge and a deliberate strategic choice.

Fifth, submit the response within the deadline and monitor the proceeding. Supplemental filings in ADR.eu are uncommon and typically require panel permission; the written record you submit at the response stage is the record on which the case is decided.

Throughout, we document both what we do and why. The logic of the defense strategy is recorded so that if the decision goes against you and you consider further options – an appeal within the procedure, or a national court challenge – the foundation is already laid.

Common myths that cost registrants their .eu domain

Two misconceptions appear repeatedly in respondent-side work, and both are costly.

The first myth is that a domain registration certificate, by itself, proves a legitimate interest. It does not. Registration proves that you are the holder of record on the date shown. It says nothing about the purpose of the registration, the use made of the domain after registration, or whether that use was genuine. A panel will want to see what happened after you registered the name – not merely that you hold it.

The second myth is that because the complainant's mark is registered in a different EU member state, or in a class unrelated to your activity, their complaint will fail automatically. ADR.eu panels take a broader view of cognizable rights than the UDRP, and a complaint grounded in a national mark from another member state is not automatically dismissed on that basis. The question is whether the right is recognized under applicable EU or national law – a fact-specific inquiry that deserves careful analysis rather than a threshold dismissal.

A third myth, less common but still encountered: that you can cure a weak registration history by building a strong website during the dispute period. Panels distinguish between use that predates the dispute and use constructed after the complaint was filed. The latter is given little weight. What matters is the record that existed before notice of the dispute arrived.

How COGNOMEN approaches .eu respondent defense

We act exclusively in domain-name disputes. That means every matter we handle – whether a complainant case, a respondent defense, or an RDNH pursuit – sits within the same narrow body of law we work in every day. In our respondent practice, we build the legitimate-interest record, document good-faith registration, and where the facts warrant it, seek an RDNH finding explicitly.

For .eu matters specifically, we work within the ADR.eu procedure at the Czech Arbitration Court, assess cross-zone exposure where the registrant holds related names in other zones, and coordinate with local litigation counsel in the relevant jurisdiction where a national court proceeding becomes necessary.

We are equally available to a registrant who held a .eu domain for years and faces an aggressive complaint, and to one who acquired the domain recently and needs to establish the bona fide business context from the ground up. The strategy differs; the analytical process is the same.

Related at COGNOMEN

• Respondent defense and RDNH across gTLDs and ccTLDs
• FAQ: defending a UDRP complaint for .org domains
• Recovering a stolen or hijacked .io domain through court action