Step-by-step: escalate a registrar lock to secure a .fr domain

A .fr domain you registered — or that belongs to your brand — has been moved without your authorization. The registrar confirms a lock is in place, but the name has not come back. Now what? The gap between a registrar lock and actual recovery is where most .fr domain disputes stall, and where the right sequence of steps determines whether you succeed.

To escalate a registrar lock and secure a .fr domain, the governing path runs through Afnic — the French registry that administers .fr — and its published dispute procedures, principally SYRELI and PARL EXPERT, alongside parallel registrar escalation and, where arbitration cannot deliver transfer, the French courts. A lock prevents further transfer; it does not itself restore the domain to you. Moving from lock to recovery requires documented evidence of compromise or rights, a formal filing, and — often — court intervention for enforcement.

This guide walks each step, names the trap hidden inside it, and explains where the route forks between an Afnic procedure and a court action.

Why .fr disputes follow a different path than .com

The UDRP does not apply to .fr. Afnic, the French registry, administers .fr under its own rules, and the dispute procedures it offers — SYRELI and PARL EXPERT — operate under French and EU law, not ICANN's Uniform Domain-Name Dispute-Resolution Policy. The distinction matters immediately if you arrive at this problem expecting to file a WIPO UDRP complaint: that route is closed for .fr.

SYRELI is Afnic's streamlined online procedure, designed for clear-cut cases of abusive registration. PARL EXPERT is the expert procedure for more complex disputes. Both can result in transfer or deletion of the domain. Neither awards monetary damages. If you need money — or if the factual record is too complicated for the Afnic procedure — a French court action is the appropriate vehicle, and in our practice we advise clients on exactly that fork early, before filing costs accumulate in the wrong channel.

One more threshold issue: .fr registration is subject to eligibility rules. To receive a transferred .fr domain, the claimant generally must meet Afnic's registrant eligibility criteria, which typically require an EU/EEA nexus — a registered business presence, trademark, or other qualifying link to France or the EU. Confirm eligibility before pursuing transfer; a winning decision that cannot be implemented is wasted effort.

The trap in this step: brand owners who hold a .com assume the .com UDRP win carries over. It does not. Parallel .fr registration by the same cybersquatter requires a fresh, separate action under the Afnic rules or in the French courts.

If you are working out whether the Afnic procedure or a court route is the right path for your .fr domain, our court and domain-recovery service covers both channels. For a preliminary read, email info@cognomenlaw.com.

Step 1: Document the compromise before touching anything else

Before escalating anything with the registrar, assemble your evidence record. This is the step most registrants skip — and the omission weakens every subsequent move. A lock without documentation is a speed bump; documentation turns the lock into a legal instrument.

What to capture immediately:

• A timestamped screenshot of the WHOIS/RDDS record showing current registrant details, nameservers, and registrar.
• Your original registration confirmation email, with the date and the registrar of record at the time.
• Any access-log extracts, password-reset emails, or unauthorized-change notifications from the registrar.
• Bank or payment records showing you funded the registration and renewals.
• Correspondence with the current unauthorized holder, if any — including any buy-back demand.
• Evidence of your trademark or commercial rights in the domain string, if the dispute is about rightful ownership rather than account compromise.

The trap in this step: registrar support portals often overwrite record data when a ticket is opened. Take the WHOIS screenshot before you submit any ticket, because registrar-side intervention can trigger a nameserver change or a privacy-proxy update that obscures the trail you need.

In a recent matter (a .fr account compromise, spring 2025), we recovered a domain for a French SME after the registrar's initial ticket inadvertently triggered a privacy-proxy substitution — making the trail harder to follow. The client had taken a timestamped WHOIS snapshot before calling us. That single document anchored the entire Afnic filing.

Step 2: Place or confirm the registrar lock — and escalate past first-line support

A registrar lock — sometimes labeled a "hold" or "clientHold" in EPP status — prevents the domain from being transferred to another registrar and, depending on the flag set, may also prevent DNS changes. The lock does not reverse a completed unauthorized transfer; it freezes the current state.

First-line registrar support can place a lock. It cannot typically initiate a transfer reversal. That requires escalation to the registrar's abuse team or, for Afnic-registered names, a formal communication to Afnic itself.

The escalation path has three layers:

1. Registrar abuse desk: Submit a written abuse complaint — not a chat ticket — citing the unauthorized transfer or account compromise, attaching your documentary evidence, and requesting a clientHold or clientTransferProhibited status immediately. Request written confirmation of the lock within 24 hours.
2. Afnic registry intervention: If the registrar does not act within two business days, contact Afnic directly. Afnic can apply registry-level locks and has its own abuse-reporting channel. A registry lock is harder to circumvent than a registrar-level flag.
3. Formal dispute filing: If the lock is in place but the unauthorized party refuses to cooperate or the transfer has already moved the domain to a second registrar, a SYRELI or PARL EXPERT filing (or a French court application) is the next instrument.

The trap in this step: requesting only a registrar lock and waiting. A lock stops forward movement; it does not compel the unauthorized holder to relinquish the name. Many registrants hold a lock for weeks while the adverse party monetizes the domain or transfers it onward to a new registrar in a jurisdiction where enforcement is harder. Act on the lock in parallel with preparing the formal dispute.

Step 3: Assess whether SYRELI, PARL EXPERT, or the French courts fit your facts

The choice between an Afnic procedure and a court action is not cosmetic. It determines the available remedies, the timeline, and the evidentiary standard.

SYRELI is an online, relatively rapid procedure best suited to cases where the abusive nature of the registration is clear on the face of the WHOIS record and the documentary evidence. The procedure is administered by Afnic and uses independent experts. Remedies include transfer and deletion. It does not award damages. The official procedure has published fees; confirm current figures with Afnic or counsel, because Afnic publishes its own fee schedule and those figures are not reproduced here.

PARL EXPERT covers more complex disputes — competing rights, disputed chain of title, or cases where the SYRELI threshold of clarity is not met. It remains an Afnic-administered procedure and still does not award damages.

French court action is appropriate in three scenarios: (a) you need monetary damages in addition to transfer; (b) the Afnic procedure has been exhausted or is unavailable in the circumstances; or (c) the unauthorized transfer spans multiple registrars in multiple jurisdictions and enforcement requires injunctive relief from a court. We handle the strategy and preparation; a French court action is conducted with local litigation counsel in the relevant jurisdiction.

The decision matrix in practice: if your evidence shows a clean account compromise — login from an unrecognized IP, a password-reset email you did not trigger, and a WHOIS change within 48 hours — SYRELI is likely the right first move. If the dispute involves competing trademark rights, a reseller arrangement gone wrong, or a chain of transfers through multiple registrars, PARL EXPERT or a court action is more appropriate. If you also need an injunction to preserve assets or prevent the domain being used to defraud your customers, only a court can grant that relief.

The trap in this step: choosing SYRELI because it appears faster, then discovering mid-process that the respondent raises a trademark counterclaim that the SYRELI procedure is not designed to adjudicate. The result is a dismissed filing and a wasted filing fee, with the adverse party now alerted to your evidence. A careful initial assessment — which we routinely provide before advising on route — avoids that outcome.

Step 4: Build the formal filing — and what the expert actually decides on

Once the route is chosen, the quality of the written submission determines the outcome. Afnic's expert reads the complaint, the response (if any), and the documentary record. The standard in the Afnic procedures centers on whether the registration or use was abusive — broadly, whether it takes unfair advantage of, or is unfairly detrimental to, the complainant's rights.

A strong filing under SYRELI or PARL EXPERT contains:

• A clear statement of the complainant's rights: trademark registration, business name registration, or other recognized rights in the domain string.
• Evidence of the registration or use complained of, with dates and WHOIS extracts.
• A factual account of the compromise or bad-faith use, supported by the documents assembled in Step 1.
• A specific remedy sought: transfer (to a named eligible registrant) or deletion.
• Confirmation that the complainant meets Afnic's eligibility requirements to hold .fr if transfer is sought.

The expert is not bound by the UDRP's three-element test. The Afnic procedure applies its own framework, which — like the Nominet DRS for .uk — tends to ask whether the registration or use is abusive in relation to the complainant's rights, rather than requiring the cumulative proof of bad-faith registration AND bad-faith use that the UDRP demands. That is a meaningful difference: a domain registered in good faith but subsequently used abusively can still be challenged under the Afnic rules, whereas it would likely survive a UDRP complaint.

The trap in this step: drafting the submission as if it were a UDRP complaint. The wrong legal standard, the wrong framing, and missing eligibility confirmation are the three most common reasons Afnic filings fail on procedural grounds before an expert ever reads the merits. We draft Afnic filings using the correct procedure-specific structure, not a UDRP template.

If your filing is ready to prepare, or if a prior attempt produced an unfavorable result, a focused review can identify what was missed. Email info@cognomenlaw.com to discuss.

Step 5: Handle the response period and the respondent's possible moves

After a SYRELI or PARL EXPERT complaint is filed, the respondent has an opportunity to answer. A respondent who ignores the filing — a default — does not automatically mean you win. The expert still examines the complaint on its merits.

A respondent who does engage may raise: a competing trademark right; a reseller or licensee relationship with the original registrant; or a claim that the account compromise narrative is false. Each of these requires a specific counter-strategy.

Competing trademark: the expert will weigh the respective rights by territory, priority, and scope. If your French or EU trademark predates the registration, that priority is strong. If the trademark is registered in a third country and the respondent holds a French business name, the comparison is more nuanced.

Reseller or licensee defense: this is among the harder respondent arguments to meet without contemporaneous documentation of the original authorization, its scope, and its termination. If you terminated a reseller agreement and the reseller retained the domain, you need the written agreement, the termination notice, and evidence that the retention is unauthorized.

False-compromise defense: the respondent may claim the transfer was consensual. Your access logs, the IP-address of the login event, and the registrar's own account-activity records are the critical rebuttal documents.

In a recent matter (a .fr dispute, autumn 2025), we successfully countered a false-compromise defense by obtaining — through a formal request — the registrar's IP-address log showing the unauthorized login originated from a jurisdiction entirely inconsistent with the legitimate registrant's location. The expert credited the log over the respondent's self-serving statement.

The trap in this step: treating the response period as downtime. Use it to anticipate the respondent's argument and prepare a supplemental statement, if the procedure allows one, or to marshal the registrar's records before the decision issues.

Step 6: Implement the decision — the last step most guides omit

An Afnic expert decision ordering transfer is not self-executing. It must be implemented through the registrar. A decision ordering deletion is similarly registry-mediated. The winning party must take active steps to confirm the transfer is processed and the lock status is updated.

What to do after a favorable decision:

1. Confirm the decision in writing to Afnic and to the registrar of record, citing the decision reference and requesting implementation confirmation within a stated timeframe.
2. Verify that the WHOIS/RDDS record has updated to show the correct registrant. A transfer that is ordered but not confirmed in the RDDS record is not complete.
3. Check the nameserver configuration immediately after transfer. A transferred domain that still points at the unauthorized party's servers continues to harm the legitimate registrant.
4. Set the domain to auto-renew under the new (or restored) registration and confirm the billing contact is updated.
5. Review whether any harm caused during the unauthorized period — phishing emails sent under the domain, redirected commercial traffic — requires further action in the French courts or elsewhere.

If the decision is adverse, the options are an appeal within the Afnic procedure (if available for the procedure type), a fresh action in the French courts, or — where the domain also has a .com counterpart — a parallel UDRP filing for the gTLD version. The adverse Afnic decision does not estop a court action; it is not res judicata in French civil proceedings.

The trap in this step: assuming the registrar will process the transfer automatically. Registrars handle volume. A decision sitting unacknowledged in a support ticket queue has been transferred — or not — without the winning party's follow-up. Own the implementation process.

Cross-zone considerations: when .fr is one domain in a wider dispute

The .fr domain is often not the only one at stake. A cybersquatter who targets a French brand typically registers the .com, the .eu, and the .fr simultaneously. Each zone requires a separate action under its own rules.

For the .com, the UDRP at WIPO or the Forum is the standard route; the WIPO filing fee starts at USD 1,500 for a single-member panel, with a decision typically within about two months. That can run in parallel with the Afnic procedure for the .fr. For the .eu, the ADR.eu procedure administered by the Czech Arbitration Court applies; eligibility for .eu transfer requires an EU/EEA nexus, which a French complainant will typically meet. For a .de, there is no arbitration route at all: the German courts decide, and a DENIC DISPUTE entry can block transfer while that litigation proceeds.

Managing parallel actions across zones is where cost and coordination complexity multiply quickly. The evidence assembled in Step 1 is often common to all three actions, which is one reason it must be complete before any filing begins. We coordinate multi-zone recovery strategies from a single instruction, engaging local litigation counsel in jurisdictions where court proceedings are required.

What route fits which zone at a glance: a complainant with .com, .fr, and .eu at risk should ordinarily file WIPO UDRP for the .com (transfer, two-month timeline), SYRELI or PARL EXPERT for the .fr (transfer or deletion, Afnic-published fees and timeline), and ADR.eu for the .eu (transfer or revocation, CAC-administered). If the .com and the .fr are both registered to the same unauthorized holder and the evidence is unified, the documentation burden for parallel filings is manageable with proper preparation.

Related at COGNOMEN:

• Court recovery and domain theft: full service overview across gTLDs and ccTLDs
• Reversing an unauthorized domain transfer: mechanics, evidence, and escalation
• New gTLD launch protection strategy: what brand owners need before a zone opens

Author: Adrian Harland — Court anticybersquatting and domain theft recovery. Meet the team.

Speak with Cognomen Law

For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter

Domain in disputeYour sideI want to recover a nameI received a complaint — I need a defensePortfolio / brand protectionWhat happenedEmailI agree to the processing of my enquiry as described in the privacy policy.Assess my case

No obligation. Confidential. We reply within two hours in business hours.

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.