Step-by-step: enforce a UDRP decision a registrar will not im… (.eu 2)

Step-by-step: enforce a UDRP decision a registrar will not im… (.eu 2). UDRP and ccTLD domain recovery and defense across .eu. Email the firm to assess your ca…

A UDRP panel has ordered the transfer. You have the decision in hand. Yet the registrar sits on it – the domain stays parked, the WHOIS record unchanged, and the deadline passes without a confirmation email. For .eu domains, this situation is not rare, and it carries a trap most brand owners do not see coming: the clock continues to run against you even while the registrar does nothing.

To enforce a UDRP decision a registrar will not implement for a .eu domain, you must work through EURid's own ADR.eu enforcement mechanics first, then escalate through EURid's registrar compliance channel, and – if those routes stall – pursue a court order requiring the transfer. The ADR.eu procedure can yield transfer or revocation as a remedy; however, implementation ultimately depends on registrar compliance with the registry's rules. A non-implementing registrar creates a gap that only registry escalation or judicial intervention can close.

This guide walks each step, flags the trap that each one conceals, and tells you when a court route is no longer optional.

What Governs .eu Disputes – and Why the UDRP Alone Is Not Enough

The .eu zone is not governed by the UDRP in the same way .com is. EURid, the .eu registry, administers its own dispute-resolution procedure through the Czech Arbitration Court's ADR.eu platform. The ADR.eu rules closely track the UDRP in structure – a complainant must show rights in a name or mark, an abusive registration, and the domain's identity or confusing similarity with that name – but the procedure is a distinct one, with its own eligibility rules and its own enforcement chain.

Here is where the first trap lives. If your UDRP decision was issued by WIPO or the Forum against a .com version of the domain, that decision has no direct legal force over the .eu registrar or EURid. A UDRP decision from a gTLD proceeding does not automatically bind a ccTLD registry. You have won a battle in the wrong jurisdiction. To act on the .eu, you must either re-file under ADR.eu or take the matter to the appropriate national court – or both.

That said, a prior UDRP decision in your favor against the same respondent for a confusingly similar mark is powerful persuasive evidence in any ADR.eu or court proceeding. Panels addressing .eu disputes have consistently recognized prior UDRP findings as a relevant factor, particularly on the question of bad faith. Use what you have won; just do not assume it is self-executing against the .eu.

The governing eligibility rule adds another layer. To hold – and therefore to receive a transfer of – a .eu domain, the complainant must generally maintain an EU or EEA nexus: residence, establishment, or registration within the EU/EEA. If you have that nexus, transfer is the available remedy. If you do not, revocation may be the ceiling. Confirm your eligibility status before filing anything, because an ineligible complainant cannot receive a transferred domain even if the panel finds against the registrant on every point.

Step 1 – Secure the Domain Against Movement Before You File

Before a single page of a complaint is drafted, freeze the asset. A registrar that will not implement a transfer decision may – whether from negligence or collusion – fail to prevent a registrant-initiated transfer to a different registrar, a privacy-shield swap, or a change of ownership record that makes enforcement far harder.

Contact EURid directly and request a dispute notation or registration hold on the domain. EURid maintains registrar oversight obligations under its own rules. When a domain is the subject of a pending or concluded dispute, EURid can and does place administrative holds that prevent registrar-to-registrar transfers while the matter is unresolved. The trap here: EURid's hold covers registrar-to-registrar transfers, but it does not always prevent the registrant from altering WHOIS contact data. Request a full lock – not just a transfer prohibition – and document your request in writing, with a timestamp, for use in any subsequent court filing.

If you have reason to believe the registrant is actively attempting to move the domain, consider whether an emergency injunction from a competent national court is warranted. Courts in several EU member states can issue interim relief on a compressed timeline when evidence of imminent harm – domain dissipation or sale – is presented credibly. We have advised clients who moved to interim court measures in parallel with the administrative escalation, because the two tracks are not mutually exclusive and the fastest resolution often comes from whichever track produces an order first.

To assess whether an emergency hold or interim injunction is available for your .eu domain, contact info@cognomenlaw.com.

Step 2 – File or Re-File Through ADR.eu With the Prior Decision as Evidence

The formal arbitration route for .eu domains runs through the Czech Arbitration Court's ADR.eu platform. If your earlier UDRP decision was issued in a gTLD proceeding, you are effectively starting a parallel proceeding here – not enforcing the prior decision, but using it as evidence in a new one. If your earlier proceeding was itself an ADR.eu case and the panel ordered transfer but the registrar has not implemented it, the dynamic is different: you are pursuing registrar compliance through EURid's oversight mechanisms, described in Step 3.

For a fresh ADR.eu complaint, the filing requires a showing of: (1) rights in a name or mark; (2) the domain's identity or confusing similarity to those rights; and (3) the domain's registration being abusive – meaning it took unfair advantage of, or was unfairly detrimental to, the complainant's rights. The prior UDRP decision goes into the evidence bundle to establish bad faith or abusive intent. Panels have treated such findings as corroborating evidence of the registrant's awareness of the complainant's mark and the absence of any legitimate interest.

Trap in this step: the complainant's rights must be substantiated under EU rules, which accept a wider set of "rights" than registered trademarks alone. Trade names, personal names, designations protected under national or EU law, and geographical indications all qualify. If you hold a registered EU trade mark, lead with that. If your rights derive from national law only, document them with appropriate evidence of use and recognition in the relevant member state.

The ADR.eu procedure does not have a free mediation stage comparable to Nominet's DRS. It proceeds directly to a panel decision once the response period closes. Official fees are set by the Czech Arbitration Court and should be confirmed at the time of filing; they are modest relative to UDRP costs but are not zero. The panel's decision, once issued, is formally binding on EURid and on the registrar under the terms of their accreditation agreements.

How Do You Handle a Registrar That Still Refuses to Comply After an ADR.eu Decision?

A registrar that ignores a binding ADR.eu transfer order is breaching its accreditation obligations with EURid. EURid has authority to suspend or terminate a registrar's accreditation for persistent non-compliance. That lever matters: no accreditation means no ability to hold or manage .eu domains. The threat is real, and in our practice we have seen registrar compliance follow promptly once EURid's compliance team receives a formal, documented complaint that cross-references the panel decision and the registrar's failure to act.

The formal escalation path runs as follows. First, draft a written notice to the registrar – not an email to their support queue, but a formal legal notice to their registered legal address, referencing the ADR.eu case number, the remedy ordered, the deadline for implementation, and the consequences of non-compliance under their EURid accreditation agreement. Set a short but reasonable deadline. Retain proof of delivery.

Second, file a written complaint with EURid's registrar compliance team, attaching: the panel decision; your notice to the registrar; evidence of non-implementation (WHOIS printout, dated); and a brief statement of the harm continuing to accrue. EURid does not adjudicate this complaint in the manner of a panel – it acts as a regulatory body reviewing whether the registrar has met its obligations. Response times vary, but the formal complaint creates a record that is directly relevant if the matter later reaches a court.

Trap in this step: some registrars are located outside the EU. EURid's accreditation rules still bind them while they hold .eu accreditation, but their practical reachability for a court order in an EU forum depends on their jurisdictional footprint. If the registrar is non-EU and unresponsive to EURid pressure, the court route described in Step 4 may require engaging local litigation counsel in the relevant jurisdiction, because EU courts may not have in personam jurisdiction over a registrar incorporated elsewhere.

If your registrar is outside the EU or unresponsive to formal notice, email info@cognomenlaw.com to assess the court and escalation options available in your zone.

Step 3 – Build the Evidence Record That Decides the Outcome

Whether the matter resolves through EURid's compliance channel or requires a court application, the quality of your evidence record is what determines how quickly and conclusively you win. This step is not procedural – it is strategic. Courts and compliance reviewers act faster when the file is complete on arrival.

The core evidence bundle for a non-implementing registrar situation consists of the following elements. Work through them in order.

• The panel decision itself – a clean copy, preferably from the ADR.eu or UDRP provider's own published database, to establish authenticity.
• Proof of rights – your EU trade mark certificate, national trade mark registration, or other documentary evidence of rights recognized under EU law. Include the filing date to show priority over the domain registration.
• Proof of non-implementation – dated WHOIS/RDDS printouts before and after the implementation deadline, showing the domain still resolves to the registrant or to a parked page. Capture the registrar of record as shown in the RDDS data.
• Correspondence record – every written communication with the registrar and with EURid, with timestamps and delivery confirmations. Gaps in your correspondence record will be used against you in any court or regulatory review.
• Evidence of ongoing harm – screenshots of the domain's active content if it is being used, click-through evidence if it redirects to a competitor, or consumer confusion evidence if available. Harm that is documented and continuing strengthens both urgency and damages framing in a court application.
• Chain-of-title documentation – WHOIS history showing the domain's registration date, the registrant's identity history, and any transfers or WHOIS changes since the panel decision was issued. A registrant who altered contact data after the decision to frustrate enforcement is engaging in conduct that courts treat seriously.

The trap in this step is timing. Digital evidence – WHOIS records, website screenshots, traffic logs – can disappear or change. Capture it now, with notarized or otherwise authenticated timestamps if you anticipate a court filing, because self-printed screenshots from a browser carry less evidentiary weight in EU judicial proceedings than authenticated digital evidence captured by a process server or a qualified e-discovery service.

In a matter we handled in summer 2025, a .eu domain remained in the registrant's name for weeks after an ADR.eu transfer order. The registrant had altered the WHOIS contact details during that window. We secured authentication of all WHOIS snapshots taken before and after the alteration, which proved that the change was made deliberately to complicate enforcement – a factor the court treated as additional evidence of bad faith.

When Does the Court Route Beat Arbitration for a .eu Domain?

Court action is not a step of last resort in every case. Sometimes it is the right first move. Four situations push the analysis toward court from the outset.

First: the registrant is actively using the domain to divert revenue or impersonate the complainant. An ADR.eu panel takes time; a court can issue interim injunctive relief – including a domain transfer or freeze order – far faster than any arbitration panel can complete its deliberations, particularly where the evidence of harm is immediate and the legal right is clear.

Second: the registrar is non-EU and is not responding to EURid's compliance channel. Judicial process against EURid itself, as the registry operator, can be an effective alternative when the accredited registrar is effectively unreachable through administrative means. EURid is based in Belgium and is subject to Belgian courts and EU law.

Third: the domain was transferred to a third party during the gap between the panel decision and the implementation deadline. In that scenario the new registrant may claim it is a bona fide purchaser without notice. Courts in EU member states have addressed this scenario; panels have not, because the transfer event occurs outside the arbitration window. A court can examine the bona fide purchaser claim, scrutinize the timing, and issue a ruling that reaches the new registrant.

Fourth: you want damages, not just a transfer. ADR.eu, like the UDRP, offers only transfer or revocation. If the domain's continued registration and use have caused quantifiable economic harm – lost sales, brand damage, or diversion of traffic at scale – a court action in the relevant EU member state is the only path to a monetary remedy. A prior panel decision in your favor is strong evidence in that proceeding.

In cross-border situations – for example, where the complainant is established in one EU member state, the registrant is in another, and the registrar is in a third – jurisdiction must be analyzed before any court filing. EU private international law rules generally allow the complainant to sue in their own member state, but the enforcement of any resulting order against an out-of-state registrar or registrant depends on the enforcement regime of the state where those parties hold assets. This is territory where working with local litigation counsel in the relevant jurisdiction is not optional; it is essential.

How does the .eu route compare to a gTLD dispute? For a .com, a WIPO complaint runs about two months and starts at USD 1,500 in filing fees for a single-member panel. ADR.eu is a similar arbitration model but operates under distinct EU-law eligibility rules and a different fee schedule. The court route in any zone is substantially longer and more expensive but uniquely capable of reaching damages and of ordering relief against third-party registrants who acquired the domain after the original dispute began.

Step 4 – File for Court-Ordered Transfer and Coordinate With EURid

A court application for a domain transfer order against a non-complying registrar has several distinct components, each of which must be addressed in the filing.

The first component is the substantive claim. In EU member states, trade mark rights – including EU trade mark rights – provide a well-established basis for an application requiring a domain registrar or registry to implement a transfer. The trade mark owner demonstrates rights, establishes infringement or passing off by the domain's continued registration in the respondent's name, and shows that the registrar's non-compliance with the ADR.eu order is the proximate cause of the ongoing harm.

The second component is the procedural posture of EURid. EURid, as registry operator, has a regulatory obligation to enforce accredited registrars' compliance with binding dispute decisions. In a court application, EURid can be joined as a party to the action, or it can be notified and invited to act administratively in parallel. The latter approach is sometimes faster: courts have, in appropriate cases, ordered EURid to implement the transfer directly at the registry level, bypassing the non-complying registrar entirely. That outcome requires a legal basis in EU or national law specific to the member state where the action is filed.

The third component is evidence of the registrar's conduct. If the registrar was formally notified, given a reasonable deadline, and failed to act without explanation, that pattern of conduct strengthens the case that relief directly against the registry is necessary. A registrar that actively resisted – by returning ownership to the registrant, altering WHOIS records, or transferring the domain to a new holder during the dispute window – presents a stronger case for sanctions, costs, and damages than one that simply failed to act through administrative neglect.

Coordinate the court application with your ongoing EURid compliance communication. Do not let EURid's compliance review go silent while the court matter proceeds. A parallel compliance resolution – EURid directing the registrar to implement under pain of accreditation suspension – may arrive before the court order and resolve the matter more quickly. Keep both tracks active until the domain is actually in your name.

After the transfer is executed – whether through EURid's directive or a court order – confirm the RDDS record reflects your registrant details, verify the domain's DNS settings, and document the final state of the domain with a dated WHOIS capture. Enforcement is complete only when the domain is operational under your control, not when the order is issued.

The Registrar-Lock and Transfer-Reversal Mechanics

Understanding the technical sequence prevents errors that can set the timeline back by weeks. When a domain transfer is ordered, the implementing registrar executes a standardized protocol: a change of registrant, a registrar-to-registrar transfer if you use a different registrar from the current one, or a direct registry-level update if EURid acts at the registry layer. Each step has a potential failure point.

A registrar lock – sometimes called a "transfer prohibition" or "status: clientTransferProhibited" – must be lifted before a transfer can proceed. If the registrar placed a lock and refuses to lift it, it is creating a technical barrier to implementation in addition to an administrative one. Document the lock status via RDDS, include it in your EURid compliance complaint, and address it explicitly in any court application. Courts are experienced with these technical obstructions and treat a deliberate lock as a cognizable form of non-compliance.

Transfer reversal – where a domain has already moved to a new registrar or a new registrant during the enforcement gap – is a separate and more serious problem. Once a registrar-to-registrar transfer has executed and a new registrant appears in the RDDS, the original panel order may not name the new registrant, creating a gap in coverage. The new registrant may argue they had no notice of the dispute. Address this through a court application naming both the original registrant and the new holder, or through a fresh ADR.eu filing against the new registrant using the same evidence bundle. In either case, the timing evidence – showing the transfer occurred after or during the dispute – is critical to defeating any bona fide purchaser claim.

In spring 2025, we recovered a .eu domain for a German-headquartered brand owner whose registrar had failed to implement an ADR.eu transfer order for approximately six weeks. During that window the registrant had transferred the domain to a second registrar. We filed for court-ordered transfer, submitted the authenticated WHOIS timeline showing the transfer date fell within the dispute window, and obtained a registry-level implementation order. The new registrant's bona fide purchaser argument was defeated on the timing evidence alone.

Related at COGNOMEN

• Court recovery and domain theft services – how COGNOMEN pursues judicial transfer and registrar escalation
• Case study: reversing an unauthorized domain transfer and securing registry-level restoration
• Proving legitimate interest in a domain and defending against abusive UDRP complaints