How to structure escrow for a .eu domain purchase

How to structure escrow for a .eu domain purchase. UDRP and ccTLD domain recovery and defense across .eu. Email the firm to assess your case.

You have identified the .eu domain you want. The registrant has indicated a willingness to sell. Now the central question is not whether to buy — it is how to complete the transfer without losing the purchase price, taking on a tainted registration, or discovering post-closing that the domain carries a pending dispute. Structuring escrow correctly is the step that separates a clean acquisition from an expensive problem.

To structure escrow for a .eu domain purchase, a buyer must verify EURid eligibility before committing funds, run a chain-of-title check for prior ADR.eu dispute history, appoint a neutral escrow agent to hold the purchase price, and sequence the registrar transfer so that funds release only upon confirmed delegation to the buyer's registrar account. The .eu zone is governed by EURid, and any domain that has been subject to an ADR.eu proceeding carries a dispute record that can affect both validity and future transferability. The escrow arrangement must be built around that zone-specific reality.

This page covers the EURid eligibility rules, the pre-acquisition due diligence steps, how to structure the escrow mechanism itself, and what to do when a seller's title is uncertain or a prior dispute clouds the registration.

Why .eu domain purchases need a different escrow approach than .com

A .eu domain is not interchangeable with a generic top-level domain. EURid, the registry operator, enforces a territorial eligibility requirement: the registrant must be an EU or EEA citizen, an organization established within the EU or EEA, or an undertaking with a registered office or central administration there. That requirement applies both at registration and upon transfer. If a buyer does not meet the eligibility criteria at closing, the transfer will be refused — and any escrow that has already released funds to the seller leaves the buyer with no domain and a contractual dispute as the only remedy.

The ADR.eu platform, administered through the Czech Arbitration Court, governs dispute resolution for .eu. Unlike the UDRP — which asks whether a domain was registered and used in bad faith — the ADR.eu procedure allows complaints based on a wider set of rights and does not require the cumulative registration-plus-use bad-faith test in the same form. A domain that survived an ADR.eu challenge, or that was the subject of a complaint withdrawn before decision, may carry reputational or legal baggage that affects value. A buyer who fails to discover this history before closing may find the domain challenged again, with the prior record available to a future panel.

In our practice, we routinely encounter buyers who treated a .eu acquisition as procedurally identical to a .com purchase. The first discovery call reveals that neither eligibility nor dispute history was checked. At that point, the deal is either paused expensively or proceeded with blind risk.

To assess eligibility and pre-acquisition risk for a .eu domain, contact info@cognomenlaw.com before committing to a price.

What pre-acquisition due diligence should cover for a .eu domain

Due diligence on a .eu domain purchase has four mandatory components: eligibility verification, chain-of-title review, dispute history check, and trademark clearance. Each can independently kill a deal or require a price adjustment. Skipping any one of them shifts risk entirely onto the buyer.

Eligibility verification means confirming that the seller currently holds the domain validly and that the buyer will qualify under EURid's rules after transfer. EURid eligibility rules have evolved over time and the current criteria should be verified directly against the registry's published requirements at the time of each transaction. Where the buyer is a non-EU entity acquiring through a European subsidiary or affiliate, the structure of that entity and its registered office must be documented before the transfer is initiated — not after.

Chain-of-title review examines the registration history: how many times the domain has changed hands, whether any of those transfers coincided with a period of disputed ownership, and whether the current registrant's title is clean. A .eu domain that was transferred during a pending ADR.eu case, or shortly after one, warrants particular scrutiny. We regularly advise buyers to request a full WHOIS history — recognizing that RDDS data under current privacy rules may be incomplete — and to require the seller to warrant clean title in the purchase agreement.

Dispute history is searchable through the CAC's ADR.eu case database. Any filed case against the domain, whether decided, settled, or withdrawn, will appear. A transfer finding against the current registrant in a past proceeding is a red flag: it may indicate that the registrant re-acquired the domain after a decision in circumstances that themselves warrant review. A withdrawn complaint may signal that an adversary retains trademark rights and chose not to pursue the matter only because the economics did not justify a filing at the time.

Trademark clearance confirms that the domain string does not correspond to an active trademark that a third party could use to mount a post-closing ADR.eu challenge. A buyer who acquires a domain only to face an ADR.eu complaint six months later has paid for a dispute liability, not an asset. Clearance should cover EU trademark registers and, where the domain has any geographic or industry meaning, national registers in the relevant member states.

How to structure the escrow mechanism for a .eu transfer

The escrow mechanism for a .eu domain purchase follows a sequenced hold-and-release model built around the registrar transfer process. The core principle is simple: the buyer's funds should not reach the seller until the domain has been confirmed as delegated to the buyer's chosen .eu-accredited registrar. Deviating from that sequence is the most common source of transaction disputes we handle.

A working escrow structure for a .eu purchase operates in five stages.

1. Escrow agreement execution. Before any funds move, both parties sign an escrow agreement that defines the purchase price, the release conditions, the timeline for each transfer step, and the dispute-resolution mechanism if a step fails. The escrow agent — a neutral party, not the seller's registrar — holds the funds under that agreement.
2. EURid transfer authorization. The seller initiates the transfer process by generating an authorization code (commonly called an Auth-Info or EPP code) from their current registrar. That code, alone, does not transfer the domain; the buyer's registrar must use it to request the transfer within the applicable window.
3. Registrar-level transfer initiation. The buyer lodges the transfer request with their .eu-accredited registrar, using the Auth-Info code. EURid's transfer process then runs through its standard steps, which include a confirmation period. The buyer should confirm in writing with their registrar that the domain is in active transfer status before the escrow agent is notified to prepare for release.
4. Delegation confirmation. The escrow release trigger is confirmed delegation — the domain appearing in RDDS under the buyer's registrar, with the buyer named as registrant (subject to any privacy settings). Screenshots and registrar confirmation emails are the contemporaneous record. Verbal confirmation from the seller is not sufficient.
5. Funds release. Once delegation is confirmed to the escrow agent's satisfaction, per the release conditions in the agreement, the purchase price is released to the seller. Any pro-rated registration fees, brokerage commissions, or legal fees are disbursed from the escrow account according to the agreement terms.

The escrow agreement should also address failure scenarios: what happens if EURid refuses the transfer on eligibility grounds; what happens if the Auth-Info code expires before the buyer's registrar processes it; and what happens if the domain enters a lock period triggered by a third party's dispute filing during the transfer window. Each of those events has occurred in transactions we have handled, and each is manageable if the agreement addresses it in advance.

A domain that enters an ADR.eu proceeding while the escrow is open will typically be locked by EURid pending the outcome. The escrow agreement must specify whether that event terminates the transaction, extends the closing window, or entitles either party to withdraw.

What happens if the seller's title is uncertain or a prior dispute clouds the domain?

A clouded title is not automatically a deal-breaker. It is, however, a negotiation point and a structure problem. The right approach depends on the nature of the cloud and the buyer's risk tolerance.

If the prior dispute was an ADR.eu complaint that resulted in a transfer to the current seller — meaning the seller won — the domain's history is adverse to the previous registrant, not to the seller. That record may actually support the seller's clean title. The panel's decision, if accessible through the CAC's published decision database, should be reviewed to confirm that the seller is the party who prevailed.

If the prior dispute was a complaint that the seller (then respondent) successfully defended, the domain is clean from that challenge but the complainant's trademark rights still exist. Whether that complainant could file a fresh ADR.eu complaint based on new evidence or changed circumstances is a risk question that requires substantive analysis — not a check-box answer.

If the prior dispute ended in withdrawal without a decision, the situation is more ambiguous. The complainant retained their rights to refile. The buyer should assess whether the trademark that underpinned the original complaint is still active and whether its owner appears to be monitoring the domain.

In a transaction we managed in spring 2025 — a .eu domain in the financial services vertical, where the prior registrant had defeated an ADR.eu complaint approximately three years earlier — we structured a conditional escrow with a ninety-day post-closing dispute buffer. The buffer period allowed funds to remain partially withheld pending confirmation that no new ADR.eu complaint had been filed in the window immediately following the publicized transfer. No complaint was filed, and the full balance released at day ninety-one.

Where a title cloud is material, buyers have three structural options: (1) negotiate a price reduction that reflects the litigation risk and proceed; (2) require the seller to obtain a title warranty from a creditworthy guarantor, with the escrow agreement specifying that a successful post-closing challenge entitles the buyer to a refund; or (3) walk away and identify a cleaner alternative registration path, including applying for a fresh .eu registration if the domain string can be obtained through other means.

How does the ADR.eu process affect an in-progress or post-closing purchase?

The ADR.eu procedure, administered by the Czech Arbitration Court, is the mandatory dispute-resolution route for .eu domains. It can affect a purchase transaction at two distinct points: during the escrow period (pre-closing) and after the transfer completes (post-closing). Understanding both exposure windows is essential before funds are committed.

Pre-closing exposure arises when a third party files an ADR.eu complaint against the domain while the escrow is open. EURid will typically lock the domain upon notification of a pending proceeding, which freezes the transfer. The escrow agreement must specify what happens to the purchase price and the parties' obligations in that event. Without that language, both parties may have conflicting interpretations of their rights — and the escrow agent cannot act without a clear instruction.

Post-closing exposure arises when a complaint is filed after the buyer has become the registrant. The buyer is now the respondent in the ADR.eu proceeding. The prior ADR.eu history of the domain — including any decisions, settlements, or withdrawn complaints — is available to the new panel and may inform its assessment of the buyer's bona fides. A buyer who acquired the domain knowing of a live trademark dispute, and who did not take steps to assess or mitigate that risk, may find that knowledge cited in a bad-faith analysis.

The ADR.eu procedure also allows complainants to rely on a wider range of rights than registered trademarks alone, including unregistered rights where demonstrable. That broadens the pool of potential complainants relative to a pure UDRP context. Buyers in markets where the domain string corresponds to a descriptive term, a trade name, or a geographic designation should factor this into their clearance analysis.

For transactions where post-closing exposure is assessed as non-trivial, we have structured representations and warranties in the purchase agreement requiring the seller to disclose all known trademark conflicts and to indemnify the buyer for costs arising from any ADR.eu complaint based on pre-closing facts. Whether such an indemnity is collectible depends on the seller's creditworthiness and jurisdiction — factors that should be evaluated before the agreement is signed, not after a complaint is filed.

Comparing the .eu escrow structure to other zones: where the process diverges

The right route and structure differ materially depending on the zone. A buyer who has completed .com transactions should not assume that the same mechanics apply to .eu.

For a .com purchase, the primary due diligence concern is UDRP complaint history, which can be searched through WIPO and the Forum's published decision databases. The UDRP's three-element test — requiring proof that a domain was registered and used in bad faith — provides a relatively defined framework for assessing whether a prior challenge was well-founded. Escrow for a .com is simpler in one respect: there is no territorial eligibility requirement for the buyer. Any entity, anywhere, may hold a .com.

For a .uk purchase, the applicable dispute procedure is the Nominet DRS, which uses an "abusive registration" test rather than the UDRP's cumulative bad-faith requirement. The DRS reads "registered or used" abusively — a materially lower bar for a complainant. Nominet's WHOIS data has historically been more transparent than gTLD equivalents, which aids chain-of-title review. The escrow structure is otherwise similar to a .eu transaction, though there is no territorial eligibility concern for most buyers.

For a .de purchase, there is no UDRP or equivalent administrative procedure: disputes go to the German courts. DENIC offers a DISPUTE entry that blocks transfer while litigation proceeds. A .de escrow must account for the possibility that a third party files a DISPUTE entry against the domain during the transfer window — a scenario with no clean administrative timeline, because court proceedings in the relevant jurisdiction can take substantially longer than an ADR proceeding.

For a new gTLD purchase (domains in extensions such as .shop, .online, or .brand), the applicable dispute procedure is the UDRP (for most) or the URS for rapid suspension. The URS remedy is suspension, not transfer; a buyer acquiring a new gTLD domain should be aware that a URS proceeding, if commenced by a third party, will suspend the domain without transferring it to the complainant, but the suspension lasts for the registration term — effectively nullifying the buyer's investment during that period.

In each zone, the structural principle is the same: funds should not release until the domain is confirmed under the buyer's registrar account, and the escrow agreement must address zone-specific procedural events that could interrupt or invalidate the transfer.

What evidence and documentation should the escrow file contain?

A well-constructed escrow file for a .eu domain purchase serves two purposes: it provides the escrow agent with the instruction set needed to execute the release, and it creates a contemporaneous record that can be produced if either party later disputes the transaction or a third party challenges the acquisition. The file should contain at minimum the following items.

• The signed purchase agreement, including representations and warranties as to clean title and seller eligibility.
• EURid WHOIS / RDDS printouts at the time of agreement signing, showing the current registrant's details and registration dates.
• CAC ADR.eu dispute history search results for the domain string, dated and printed contemporaneously.
• EU trademark register search results covering the domain string, dated at the time of the clearance check.
• The seller's EURid eligibility documentation (for the seller's current registration) and the buyer's eligibility documentation (for the post-transfer registration).
• The Auth-Info / EPP code transmission record, confirming the date and channel of delivery from the seller's registrar.
• The buyer's registrar confirmation that the transfer request was submitted and accepted.
• The delegation confirmation — RDDS printout and registrar confirmation email — showing the buyer as the current registrant after transfer.
• The escrow agent's release instruction and payment confirmation.

Where the transaction involves a broker, the broker's engagement letter and fee confirmation should also be included. Commission disputes are among the most common post-closing disputes in domain transactions, and the escrow file is the primary record for resolving them.

We advise buyers to store the complete escrow file for at least three years after closing. ADR.eu and UDRP complaints do not carry a strict statute of limitations in the manner of national court actions, and a complaint based on facts that predated the acquisition can arise well after closing. The escrow file is the buyer's primary evidence that the acquisition was conducted in good faith.

To weigh the escrow structure against the specific facts of your .eu acquisition, email info@cognomenlaw.com.

What are the realistic next steps once due diligence is complete?

Due diligence completion is the entry point to the transaction, not the exit. Once the chain-of-title check, dispute history review, trademark clearance, and eligibility verification are done, the buyer and seller are in a position to finalize the purchase agreement, appoint the escrow agent, and begin the transfer sequence.

The purchase agreement should be executed before any funds are deposited. The escrow agent should receive funds only after both parties have signed and the escrow account details have been confirmed in writing — not by telephone, not by a follow-up email chain without the agreement attached. Wire fraud targeting domain transactions is a documented risk; the escrow agent's banking details should be confirmed through a separately authenticated channel, not solely through email.

The timeline from escrow opening to closing for a straightforward .eu transfer is typically a matter of days to a few weeks, depending on the responsiveness of the registrars involved and EURid's transfer processing. Where one or both registrars are not among the more active .eu-accredited providers, delays are more common. The purchase agreement should specify a long-stop closing date, with agreed consequences for failure to meet it, to avoid an open-ended escrow.

In a second transaction we handled in late 2024 — a .eu domain in the technology sector acquired by a European subsidiary of a non-EU buyer — the eligibility structure required formal registration of the subsidiary in an EEA member state before EURid would process the transfer. That step added approximately six weeks to the timeline. The escrow agreement had been drafted with a fixed long-stop date that did not account for the eligibility cure period; we renegotiated the closing date with both parties' consent and amended the escrow terms before funds were released. The transaction closed without loss to either party. The lesson is structural: eligibility issues discovered after the agreement is signed are expensive to cure. They are cheap to identify in advance.

Related at COGNOMEN

• Domain transactions, due diligence, and escrow services across all zones
• How to verify chain of title for a .uk domain before purchase
• Frequently asked questions on enforcing a UDRP decision