Step-by-step: draft a domain assignment agreement for a .eu domain

Step-by-step: draft a domain assignment agreement for a .eu domain. UDRP and ccTLD domain recovery and defense across .eu. Email the firm to assess your case.

A brand acquires a desirable .eu domain through private negotiation, hands over the purchase price, and then discovers the domain carries a disputed chain of title – or that EURid's eligibility rules mean the transferee cannot lawfully hold it. The deal unravels. The money may not come back. Knowing how to draft a domain assignment agreement for a .eu domain, and what traps each step conceals, is the difference between a clean transfer and an expensive lesson.

A .eu domain assignment agreement must address EURid eligibility verification before any money changes hands, because only entities with an EU/EEA nexus may hold a .eu registration. The transfer itself must be executed through EURid's registrar-mediated process; a private contract alone does not move the domain. If a dispute arises after the transfer, the governing procedure is the ADR.eu platform administered by the Czech Arbitration Court, which can order revocation or transfer. Due diligence on prior-dispute history and chain of title is therefore not optional – it is a condition of a sound acquisition.

This guide walks every step, flags the trap in each one, and covers what to do when a .eu transaction intersects a live or historic ADR.eu proceeding.

Step 1: Confirm eligibility before anything else

A .eu domain may only be registered and held by an entity that has an EU or EEA nexus – a company incorporated in a Member State or Norway, Iceland, or Liechtenstein; an EU/EEA resident natural person; or an organization with a registered office or central administration in those territories. This is not a formality. EURid enforces it.

The trap here is timing. Many buyers confirm eligibility in the abstract ("we are an EU company, so we qualify") without verifying that the specific legal entity that will hold the domain meets the requirement. A holding-company acquisition, a post-merger entity change, or a UK company post-Brexit may all introduce a gap. Verify the exact holding entity against EURid's published eligibility criteria before the agreement is signed. If the buyer's structure has changed recently, require a legal opinion on eligibility as a condition precedent.

The seller's eligibility matters too. A domain held by an entity that no longer qualifies – a company that moved its registered office outside the EEA, for example – may already be subject to revocation proceedings. Acquiring it without catching this means buying a revocable asset. Run the WHOIS/RDDS record now, not later.

Step 2: Conduct a full chain-of-title and prior-dispute search

Chain-of-title for a .eu domain is the sequence of registrants from the domain's creation to the present seller. A gap in that chain – an undocumented transfer, a lapsed registration re-registered by a different party, or a forced transfer ordered in a prior ADR.eu proceeding – can mean the seller's title is defective. A buyer who takes a defective title takes the defect with it.

What does a prior-dispute search cover? It should include the ADR.eu case database for any proceeding involving the domain or the seller as a registrant. It should also cover WIPO and the Forum for any gTLD proceedings involving the same underlying brand or mark – because a pattern of abusive registrations across zones can signal that the current .eu is itself a bad-faith registration that a brand owner is preparing to challenge. We regularly advise acquirers who discover, mid-negotiation, that the seller is a serial cybersquatter whose .eu registration was the last in a portfolio of abusive names. That discovery changes both the price and the risk calculus entirely.

Pull the registration history from the registrar and from public RDDS records. Request that the seller warrant, in the agreement, that no ADR.eu, UDRP, or court proceeding is pending or threatened. Make that warranty a condition of closing, not merely a representation.

For an assessment of chain-of-title risk in a .eu domain acquisition, contact info@cognomenlaw.com.

Step 3: Structure the agreement – the essential clauses

A domain assignment agreement for a .eu domain is not a generic IP assignment form. It must reflect the procedural realities of the EURid registry. These are the clauses that decide whether the document holds up.

Identification of the asset. The domain name must be stated exactly, with the TLD. Include the current registrar, the registrar account reference (where the seller can provide it), and the WHOIS/RDDS-confirmed registrant of record at the date of signing.

EURid eligibility representation. Both parties represent that the buyer is eligible to hold a .eu domain under the current EURid registration rules. This is a mutual representation: the seller confirms it has no reason to believe the buyer is ineligible; the buyer confirms its own eligibility in writing. A breach of this representation – for example, if the buyer is later found ineligible – should be addressed in the indemnity clause.

Scope of the assignment. The assignment transfers all of the seller's right, title, and interest in the domain name, including any associated registrar account credentials required to complete the transfer. It should also address any content, subdomains, or DNS configuration that the buyer requires, if any.

Consideration and payment mechanics. State the purchase price in a defined currency. Reference the escrow arrangement (see Step 4). Tie the release of funds to confirmed completion of the EURid registrar transfer, not to the signing of the agreement.

Seller's warranties. The seller warrants: (a) it is the registered holder of the domain; (b) it has the authority to transfer it; (c) no prior, pending, or threatened dispute (ADR.eu, UDRP, or court) affects the domain; (d) the domain is not subject to a registrar lock, a registry hold, or any legal proceeding that would prevent transfer; (e) to the seller's knowledge, the registration does not infringe any third party's trademark rights. Warranty (e) is where sellers push back. Do not accept its deletion.

Transfer mechanics and timing. Specify the registrar through which the transfer will occur, the authorization code (AUTH/EPP code) delivery obligation, and a maximum number of business days for the seller to initiate the transfer after the escrow trigger. A transfer that is not initiated within, say, five business days of the escrow trigger should give the buyer a right to rescind and recover the purchase price in full.

Dispute-resolution clause. Identify the governing law and the forum for any contractual dispute between the parties. This is separate from the ADR.eu procedure, which governs third-party challenges to the registration. Agree on governing law that is familiar to both parties and name a court or arbitration body with clear jurisdiction.

Indemnity. Each party indemnifies the other for breach of its representations. In particular, the seller indemnifies the buyer for any loss arising from a successful ADR.eu complaint filed by a third party based on facts existing at or before the transfer date. This is the clause sellers resist most. It is also the clause buyers need most.

Step 4: Set up escrow – and do not skip it

The cardinal rule of domain transactions is this: neither party should move first without protection. The seller should not release the authorization code before payment is secured. The buyer should not release payment before the transfer is confirmed. Escrow resolves this by holding the purchase price until both conditions are met.

How does escrow work in a .eu domain transfer? A neutral escrow agent holds the buyer's payment. The seller delivers the authorization code and initiates the transfer at EURid's registrar level. Once EURid's system confirms the registrant of record has changed to the buyer, the escrow agent releases the funds to the seller. If the transfer fails – because of a registry hold, an eligibility block, or a third-party lock – the escrow agent returns the funds to the buyer. The agreement should name the escrow agent, specify the release conditions precisely, and set a deadline after which funds are returned if the transfer has not completed.

The trap in this step is imprecision about the release trigger. "Completion of the transfer" is not enough. The trigger should be: confirmation from EURid's RDDS that the domain's registrant of record has changed to the buyer's name and that the domain is in active status, free of registry holds. Define it with that specificity in the agreement.

In a recent matter – a .eu brand-name domain acquisition, autumn 2024 – we structured escrow with an explicit RDDS-confirmation trigger and a fifteen-day outside date. The seller's registrar introduced an unexpected delay. Because the outside date was in the agreement, the buyer's funds were returned promptly and the parties renegotiated. Without that clause, the buyer would have had no clean exit.

To structure escrow and agreement terms for a .eu domain purchase, email info@cognomenlaw.com.

Step 5: Execute the registrar transfer and verify completion

Signing the assignment agreement does not transfer the domain. Only EURid's registrar process does. This is a distinction that surprises some buyers – and that sellers occasionally exploit by delaying the registry-level steps after receiving payment outside escrow.

The mechanics are straightforward. The seller obtains an authorization code (also called an EPP code or AUTH code) from the current registrar. The buyer provides this code to its chosen registrar, which submits a transfer request to EURid. EURid processes the request. The domain moves to the buyer's registrar account. The process typically takes a matter of days under EURid's rules, though delays can arise from domain status flags – a clientTransferProhibited lock, for example – that the seller must clear before the transfer can proceed.

The assignment agreement should require the seller to: (a) remove any registrar-imposed transfer locks before the transfer is initiated; (b) deliver the authorization code within a specified period; and (c) not place any new lock or hold on the domain from the date of signing to the date of confirmed transfer. Each of these is a separate obligation, and each should carry its own remedy for breach.

After the transfer completes, verify the RDDS record independently. Confirm the registrant name, the registrar of record, and the expiration date. Update DNS configuration promptly. A domain sitting in a transferred but unconfigured state is a technical vulnerability.

Step 6: Understand the ADR.eu risk window after transfer

A completed .eu transfer does not make a third-party challenge disappear. Under the .eu dispute procedure administered through the ADR.eu platform at the Czech Arbitration Court, a complainant may file a challenge based on facts that pre-date the transfer. A brand owner who has been monitoring the domain since the seller registered it does not lose standing simply because ownership changed hands. This is the risk that the seller's indemnity in the agreement is designed to address.

What is the .eu dispute standard? The ADR.eu procedure allows a complainant to seek revocation or transfer of a .eu domain where the complainant demonstrates rights in a name or mark and the registration is speculative or abusive – meaning the domain was registered or acquired primarily to sell it at a profit to the rights-holder, to block the rights-holder from reflecting the name in a .eu registration, or to disrupt the rights-holder's business. The procedure allows a broader set of "rights" than registered trademarks alone: unregistered marks, geographical indications, and trade names may qualify, depending on the applicable national law.

Critically, the .eu procedure also allows revocation based purely on ineligibility. If a prior registrant was ineligible and the acquisition was structured to cure that ineligibility, a complainant or EURid itself may still challenge the registration. Due diligence on the seller's original eligibility is therefore not only a buyer's protection – it is a condition of the buyer's own long-term security of title.

Where a third-party ADR.eu challenge is filed after the transfer, we advise buyers to act immediately: review the complaint, confirm that the seller's indemnity is in force, and prepare a response. The buyer is now the respondent. A default – no response filed – produces a summary decision against the new registrant, potentially resulting in revocation or forced transfer to the complainant.

Step 7: Address the cross-zone dimension

Few brands hold only a .eu domain. Most operate across .eu, .com, and one or more national ccTLDs. A .eu domain acquisition should always be assessed in that multi-zone context. Several scenarios arise in our practice.

First, a brand may acquire the .eu while a third party controls the matching .com. The .eu acquisition strengthens the brand's European position but does not resolve the .com issue. If the .com is cybersquatted, a UDRP complaint – before WIPO or the Forum – is the standard route, separate from and parallel to the .eu transaction. The two proceedings do not interfere with each other, but evidence gathered in one may assist the strategy in the other.

Second, a brand may be acquiring the .eu from a seller who also holds national ccTLDs – .de, .fr, .nl – and wishes to sell the entire portfolio. Each ccTLD transfer requires its own registrar process. The .de, for example, involves DENIC's transfer rules, and any dispute there proceeds through the German courts, not through ADR.eu or UDRP. A portfolio acquisition agreement should address each zone individually, with zone-specific warranty and transfer mechanics for each domain.

Third, if the brand is concerned that a competitor might register the .eu immediately before or after the transaction closes, consider a monitoring arrangement for the relevant names in the relevant zones. Pre-acquisition brand-protection monitoring identifies those risks before the deal closes, not after.

The right route depends on the goal. If a .eu is the only asset and the transaction is straightforward, a focused assignment agreement with escrow is sufficient. If the acquisition spans zones or is accompanied by a parallel dispute, coordinated strategy across the relevant procedures saves both time and cost.

Related at COGNOMEN

• Domain purchase, sale, and pre-acquisition due diligence across gTLDs and ccTLDs
• Brand-protection monitoring: how ongoing surveillance protects domain portfolios
• Recovering a hijacked domain: registrar escalation, account compromise, and transfer reversal