How to draft a domain assignment agreement for a .fr domain

How to draft a domain assignment agreement for a .fr domain. UDRP and ccTLD domain recovery and defense across .fr. Email the firm to assess your case.

A brand owner agrees to purchase a .fr domain from an independent registrant. The price is agreed, the escrow is funded, and then — three weeks after transfer — a prior claimant surfaces with an Afnic SYRELI dispute history that the buyer never saw. The domain is locked in a new proceeding before the ink is dry on any assignment document. That scenario is not hypothetical. In our practice, we regularly see buyers absorb prior-dispute risk that a proper chain-of-title check would have surfaced before any money changed hands.

To draft a domain assignment agreement for a .fr domain, you must address French-law contract formalities, verify chain of title and prior SYRELI dispute history through Afnic's published records, structure escrow to condition release on confirmed registrar transfer, and include representations and warranties that cover EU-nexus eligibility, absence of encumbrances, and indemnification for pre-transfer claims. The governing ccTLD procedure is Afnic's SYRELI or PARL EXPERT process, distinct from the UDRP. A well-drafted assignment is the single document that protects both parties from that prior-claimant scenario.

This page covers every element of a sound .fr domain assignment: the applicable rules, the chain-of-title checks, the contract structure, escrow mechanics, the evidence that protects your title, and the decision points that separate a clean transfer from a disputed one.

What rules govern a .fr domain assignment?

A .fr domain assignment is governed by a layered set of rules: Afnic's registration policies, French contract law, and EU data and eligibility requirements. No single ICANN-style universal policy applies. The UDRP does not govern .fr. Afnic operates its own dispute procedures — SYRELI and PARL EXPERT — and those procedures can unwind a transfer if the assignment carries a latent defect. Understanding where each layer sits is the first task in drafting a sound agreement.

Afnic, the registry for .fr and related French-zone domains (.re, .pm, .yt, .wf, .tf), requires that registrants maintain eligibility as an EU/EEA entity or natural person with a connection to French territory. Any assignment must pass the same eligibility test that applied at registration. A buyer who does not qualify cannot hold the domain regardless of what the assignment agreement says. That eligibility check is not a formality — it is the threshold question before you draft a single clause.

The SYRELI procedure allows a rights holder to challenge a .fr registration on grounds of infringement of rights, misleading use, or breach of public policy. Crucially, SYRELI can result in transfer or deletion of the domain. A buyer who acquires a domain without checking SYRELI history inherits the reputational and procedural risk attached to any past or pending proceeding. We advise buyers to obtain an Afnic WHOIS/RDDS printout, a full SYRELI search, and confirmation that no proceeding is pending or was decided adversely against the seller.

How do you check chain of title for a .fr domain before drafting the agreement?

Chain-of-title due diligence for a .fr domain covers three layers: registration history, dispute history, and encumbrance status. Each layer requires a distinct check, and skipping any one of them is the commonest reason a buyer ends up with a domain they cannot use or defend. In our practice, we run all three before advising a client to proceed to the assignment stage.

The registration history check uses Afnic's publicly accessible RDDS (Registration Data Directory Services) output. It confirms the current registrant, the creation date, the expiry date, and the registrar of record. A domain with a creation date far predating the seller's claimed ownership is a flag. So is a recent registrar transfer within the past 60 days, which may indicate a hasty repositioning ahead of sale.

The dispute history check requires a direct search of Afnic's published SYRELI and PARL EXPERT decision records. Afnic publishes decision outcomes, and a search against the domain name in question will surface any past adverse or pending proceeding. An adverse SYRELI decision in the seller's favor does not necessarily taint the domain — a prior claimant may have lost — but it confirms contested history that your agreement must address by way of representation and indemnification.

The encumbrance check covers two additional matters. First, is the domain listed as collateral in any financing arrangement? French commercial practice does recognize domain names as intangible assets capable of being pledged; a search of the seller's corporate filings or a direct warranty in the agreement is prudent. Second, is there any court injunction, conservatory measure (saisie conservatoire), or administrative hold on the domain? A domain under judicial hold cannot be validly transferred until that hold is lifted. Both issues must be addressed before escrow is funded.

If you are at the due-diligence stage and need a structured chain-of-title assessment before committing funds, contact info@cognomenlaw.com for a read on the title risks in your specific transaction.

What must a .fr domain assignment agreement contain?

A .fr domain assignment agreement must include, at minimum: identification of the parties, a description of the domain and its current registration details, eligibility representations by the seller, a clear statement of the purchase price and payment mechanism, the escrow structure, representations and warranties, indemnification for pre-transfer claims, the transfer mechanics and the confirming acts required of both parties, and governing law. Each element resolves a specific risk; omitting any one of them shifts that risk silently onto the party who drafted the gap.

Party identification and eligibility. Both parties must be identified with their legal names, addresses, and — for the buyer — the EU/EEA eligibility basis. The buyer's Afnic-eligibility confirmation is not boilerplate; it is the operative prerequisite for registration. If the buyer is a corporate entity, the agreement should confirm the jurisdiction of incorporation and the contact details that will appear in the new WHOIS record.

Domain description and current registration data. The agreement identifies the exact domain name, the registrar of record, the Afnic registrant ID (handle), the creation date, and the current expiry date. A mismatch between any of these and Afnic's live RDDS output is a reason to pause before execution.

Price and payment. The agreement states the purchase price in euros, the payment timeline, and — critically — that release of funds from escrow is conditioned on confirmed completion of the registrar transfer of the domain to the buyer. Payment before confirmed transfer is the single most common source of disputes in domain transactions we handle. It should never happen.

Representations and warranties. The seller warrants: (a) it is the sole registrant of record; (b) the domain is free of any SYRELI or PARL EXPERT proceeding, pending or decided adversely; (c) the domain is not subject to any court order, conservatory measure, or pledge; (d) the domain does not infringe any third-party trademark or name rights to the seller's knowledge; and (e) the seller has full authority to assign the domain. The buyer warrants that it meets Afnic's eligibility requirements.

Indemnification. The seller indemnifies the buyer against claims arising from the seller's acts or omissions before the transfer date. This clause does real work. A prior trademark claimant who launches a SYRELI proceeding the week after transfer, based on the seller's prior conduct, is the buyer's problem without an indemnification clause that reaches pre-transfer acts.

Transfer mechanics. The agreement specifies the steps: (1) seller initiates the registrar transfer (auth-code / EPP transfer token release); (2) buyer confirms receipt of the auth-code; (3) buyer submits the transfer at its chosen registrar; (4) Afnic's registry-level transfer is confirmed; (5) escrow agent releases funds to seller. The timeline for each step should be specified in calendar days. A drop-dead date — after which the transaction unwinds and escrow returns funds — is advisable.

Governing law and jurisdiction. A .fr domain transaction with French-resident parties will almost always elect French law and French courts. A cross-border transaction — for example, a US brand owner acquiring from a French SME — requires a deliberate choice. French courts have jurisdiction over Afnic-registry matters regardless of the parties' choice; the governing-law clause addresses contractual disputes between the parties, not registry-level proceedings.

How should escrow be structured for a .fr domain transfer?

Escrow structure is the single most consequential decision in a .fr domain transaction. The correct structure holds funds in a neutral account and releases them only on verified completion of the registrar transfer — not on signing of the assignment agreement, not on dispatch of the auth-code, and not on the seller's representation that "the transfer is under way." Verified completion means an Afnic RDDS printout showing the buyer as registrant of record.

A suitable escrow service for a .fr domain transaction should be an EU-licensed payment service provider or a law-firm client account operating under applicable professional-conduct rules. The escrow instruction letter should be incorporated by reference into the assignment agreement and should specify: the trigger condition for release (confirmed RDDS registrant change), the currency (euros), the timeline for release once the trigger is confirmed, and the return-of-funds mechanics if the trigger is not met within the drop-dead date.

In a recent transaction (a .fr brand-name domain, spring 2025), we structured escrow with a 10-calendar-day window between auth-code release and confirmed transfer, with automatic return of funds if the RDDS did not reflect the change within that window. The transfer completed in four days. The seller received funds on day five. No dispute arose because no ambiguity existed in the release mechanics.

One structural trap deserves specific attention. Some registrars for .fr domains impose an additional validation step — an Afnic eligibility confirmation for the incoming registrant — that can add several business days to the transfer timeline. The escrow drop-dead date must account for this. A drop-dead date set too tight will trigger automatic escrow return before the registry has had time to complete its own validation, leaving both parties in a procedural bind.

How does Afnic SYRELI affect a .fr domain assignment?

Afnic's SYRELI procedure can invalidate a .fr domain transfer, suspend a domain, or order its deletion — regardless of whether the parties have executed a valid assignment agreement. A private contract cannot override a public registry proceeding. That is the defining difference between a .fr transaction and an arms-length trade in a personal asset.

SYRELI accepts complaints from any rights holder who can demonstrate that a .fr registration infringes its rights, misleads the public, or breaches Afnic's registration rules. Eligible rights include registered trademarks, trade names, corporate names, and in some cases geographical indications and personal names. The procedure is administered through Afnic's published process; remedies include transfer or deletion of the domain.

The PARL EXPERT track is Afnic's full expert procedure, used for complex or contested cases. Both SYRELI and PARL EXPERT produce published, citable decisions. A buyer who has completed the SYRELI search before acquisition and found no adverse history has done the minimum. A buyer who has also read the outcome of any past SYRELI challenge — even one the seller won — understands the full dispute profile of the domain and can price that risk correctly.

One practical implication: the assignment agreement should include a condition precedent confirming that, as of the execution date, no SYRELI or PARL EXPERT proceeding is pending. If one is pending, the agreement should either unwind automatically or be suspended until the proceeding concludes. Proceeding to transfer while a SYRELI complaint is live is the functional equivalent of buying property under a lis pendens notice.

If a SYRELI proceeding is pending against the domain you are seeking to acquire, or if you have received a SYRELI complaint after a recent acquisition, email info@cognomenlaw.com to assess your options.

What evidence protects title after a .fr domain assignment closes?

The assignment agreement itself is the primary evidence of title. After closing, the buyer should retain: the executed assignment agreement (signed by both parties), the escrow release confirmation, the Afnic RDDS printout dated on the day of confirmed transfer, the auth-code exchange record, and the registrar's transfer-completion notification. Together, these documents establish a clean chain of title and will be the first items any future adjudicator — a SYRELI panel, a French court, or a potential subsequent buyer's counsel — will ask to see.

Beyond documentation, the buyer should take three post-closing steps. First, confirm that the Afnic contact record now reflects accurate and current buyer information. An incorrect or stale WHOIS record after transfer is an operational risk — Afnic can suspend a domain for registrant-contact inaccuracy. Second, renew the domain promptly if the expiry date is within six months of the closing date; a lapsed .fr domain is subject to deletion without a grace period comparable to some gTLD regimes. Third, monitor the domain for any new SYRELI complaints using Afnic's published notice mechanisms.

In a second recent matter (a .fr ccTLD used in the fashion sector, autumn 2024), a buyer who had acquired the domain 18 months earlier faced a new SYRELI complaint based on a trademark registered after the original transfer date. Because our client had preserved the full documentation chain — including the assignment agreement and the Afnic RDDS printout from the day of transfer — we were able to establish a clean acquisition date and successfully defend the proceeding. Without that documentation, the outcome would have turned on the seller's testimony alone.

How does a .fr domain assignment compare with a .com transfer?

The core structure of a domain assignment — identification, price, escrow, transfer mechanics, representations, indemnification — is broadly the same across zones. The zone-specific differences, however, are material enough to make a .com-template agreement inadequate for a .fr transaction.

The right route depends on the zone and the goal. For a .com domain, the transaction closes at a single accredited registrar under ICANN's uniform auth-code transfer protocol; no registry eligibility check applies to the buyer; the dispute procedure is the UDRP, which applies a global three-element test. For a .fr domain, Afnic's eligibility requirement applies to the buyer as a condition of registration; the dispute procedure is SYRELI or PARL EXPERT, not the UDRP; and the registry imposes its own validation step that can extend the transfer timeline by several business days. A .com template transplanted into a .fr transaction will almost always miss the eligibility representation, the SYRELI condition precedent, and the Afnic-specific escrow trigger.

For new-gTLD domains — .paris, .alsace, and other locally-administered new gTLDs — a third layer applies: the sponsoring registry's own transfer rules, which may incorporate geographic or professional restrictions on registrant eligibility. Those rules are not uniform, and each should be checked against the specific registry's published policies before drafting begins.

If the same brand name is registered as both a .com and a .fr, a dual-zone acquisition should address both in a single master assignment, with zone-specific schedules for each transfer. A single agreement reduces the risk of the .fr closing without the .com (or vice versa), leaving the buyer holding only half the domain portfolio it intended to acquire.

What are the realistic costs and timelines for a .fr domain assignment?

The cost of a .fr domain assignment has two distinct components: the domain purchase price (a commercial negotiation between the parties) and the transaction-execution costs (escrow fees, registrar transfer fee, and legal fees for drafting and due diligence). These are separate. Conflating them is a frequent source of misaligned expectations in transactions we manage.

Afnic's own transfer fee is modest — a registry-level administrative charge that most registrars absorb or pass through at cost. The registrar transfer fee is similarly small. Escrow fees depend on the escrow provider and the transaction size; for mid-market .fr transactions, published escrow fees at regulated providers are typically a percentage of the transaction value with a minimum floor.

Legal fees for drafting a .fr domain assignment agreement — covering the agreement itself, the due-diligence check, and the escrow instruction letter — fall within the market range for specialist domain transaction work. For a straightforward transaction with a willing seller and a clean title history, a flat-fee engagement is common. For a transaction with contested history, a competing SYRELI claim, or a cross-border eligibility issue, the scope increases and so does the cost. We provide a clear fee estimate before any engagement begins.

The timeline from execution of a letter of intent to confirmed RDDS transfer is typically two to four weeks for an uncomplicated .fr transaction. The principal variables are: the speed of Afnic's eligibility validation for the incoming registrant, the registrar's processing time for the auth-code transfer, and any escrow-provider verification requirements. A transaction with a clean title, a buyer who meets eligibility immediately, and no pending SYRELI proceeding will close at the shorter end of that range.

If a SYRELI proceeding is pending, the timeline is indeterminate until the proceeding concludes. Afnic's SYRELI procedure does not publish fixed decision timelines in the same manner as, for example, Nominet's DRS (which typically runs about 8–12 weeks). Counsel familiar with the current Afnic process can give a more current estimate; we advise clients to verify the current Afnic procedure timeline directly before making a contractual commitment to close.

Related at COGNOMEN

• Domain transactions, due diligence, and brand-protection monitoring across all zones
• How to recover a lapsed domain under the .co zone procedure
• Frequently asked questions on drafting a domain assignment agreement for a .it domain