Assess my case

Defend a .fr domain against a UDRP complaint: what panels actually decide

By Anton Grant, Respondent defense & RDNH ·

A complainant files against your .fr domain. The filing arrives – either an Afnic SYRELI notice or, where WIPO has been appointed as provider for the French zone, a UDRP complaint – and you have a short window to respond. The instinct is to assume the complainant wins automatically. It does not work that way.

To defend a .fr domain against a UDRP complaint (or its French-zone equivalent), a respondent must demonstrate at least one of the Paragraph 4(c) safe harbors under the Policy – a bona fide offering before notice of the dispute, being commonly known by the name, or legitimate noncommercial or fair use. Where the complaint is filed through Afnic's own SYRELI procedure rather than the UDRP, a distinct but parallel test applies. In both routes, the burden of production on legitimate interest shifts to the respondent once the complainant establishes a prima facie case, and the evidence assembled before the response deadline decides the outcome.

This analysis covers the applicable procedure for .fr domains, the substantive defense arguments panels find persuasive, the evidence that tips a case, and the realistic circumstances in which a reverse domain name hijacking finding is available.

Which procedure governs a .fr domain dispute?

The French registry, Afnic, operates two distinct procedures for .fr disputes: the SYRELI procedure and the PARL EXPERT procedure, each governed by published Afnic rules rather than the UDRP itself. Neither is the same as a WIPO UDRP complaint filed against a .com. However, in some situations – particularly where a complainant holds international trademark rights and the domain closely mirrors a brand – a complainant may also file a UDRP complaint if the applicable registry rules or contractual chain permits it; this is uncommon for pure .fr registrations but does arise where a broader domain portfolio is in dispute.

The SYRELI procedure is the primary administrative route for .fr. It is decided under French and EU rules. The remedy can include transfer or deletion of the domain. A complainant may rely on a wider set of "rights" than registered trademarks alone – prior trade names, company names, and certain descriptive rights are all recognized under the French framework. That breadth cuts both ways: it can make it easier for a complainant to establish rights, but it also means a respondent can sometimes raise a competing prior right that would not be cognizable in a standard UDRP.

Where a UDRP complaint is filed against a .fr (a rarer but real scenario), the three elements of Paragraph 4(a) apply in full: identical or confusing similarity to a mark the complainant holds; no rights or legitimate interests on the respondent's side; and registration and use in bad faith. That cumulative test – registration AND use – is important. A domain registered years before any trademark filing, and never used to target the complainant, is structurally hard to condemn under the UDRP's standard even if the name now conflicts with a later-arising brand.

If you have received a SYRELI or UDRP filing against your .fr domain, the response window is short and the preparation window is shorter. For an assessment of your domain dispute, contact info@cognomenlaw.com.

How do the Paragraph 4(c) safe harbors apply in a .fr context?

The three safe harbors in Paragraph 4(c) of the UDRP each offer a distinct path to defeat a complaint. Understanding which one fits the facts is the first task of any competent defense.

The first safe harbor – a bona fide offering of goods or services before any notice of the dispute – requires evidence of genuine commercial activity using the domain predating the complainant's contact or the complaint itself. In our practice, respondents who can show invoices, order confirmations, or a live and substantive website tied to the domain from before any dispute notice are in a strong position. Panels distinguish between a website that was genuinely operational and one that was dressed up after a demand letter arrived. The distinction matters enormously.

The second safe harbor – being commonly known by the domain name – is most useful where a registrant operates under a trade name, company name, or personal name that corresponds to the domain. French respondents, in particular, often hold company registrations (SIREN numbers, Kbis extracts) and trade name registrations that document this association. That documentation should go into the response. A company that registered "marqueexample.fr" the same month it incorporated under a similar name has a credible story; one that registered the domain three days after a competitor's press release does not.

The third safe harbor – legitimate noncommercial or fair use – covers commentary, criticism, and nominative reference without commercial intent. This path is narrow in practice. Panels scrutinize whether the site genuinely communicates the noncommercial purpose clearly and whether the registrant is using the domain to redirect traffic for gain. A genuine criticism site that is transparent about its purpose fares far better than a site that mimics the complainant's brand.

Under the SYRELI framework, the legitimate interest analysis draws on comparable concepts but applies Afnic's published rules and French administrative practice. The substantive alignment between SYRELI and UDRP safe-harbor thinking is real enough that UDRP panels' reasoning is often instructive, even if not binding.

What does "registered and used in bad faith" actually mean for a .fr defense?

The cumulative "registered AND used in bad faith" requirement is one of the most misunderstood elements of UDRP doctrine – and one of the most useful for respondents. Both limbs must be satisfied simultaneously. A domain registered without any intent to target the complainant, even if later associated with infringing content, may fail the registration-in-bad-faith limb. Conversely, a domain registered opportunistically may fail the use limb if the registrant parks it passively without directing it at the complainant.

Panels have developed a nuanced "passive holding" doctrine that has complicated this analysis. The consensus view is that passive holding of a domain – with no active website – can still constitute bad faith use in the right circumstances: where the respondent cannot plausibly claim any legitimate use, where the complainant's mark is famous, and where there is no conceivable good-faith use of the domain. But the consensus also makes clear that passive holding alone does not automatically equal bad faith. A respondent with a plausible legitimate explanation for holding the domain without an active site is in a different position.

For .fr specifically, registration timing relative to trademark priority dates is often decisive. French trademark filings are publicly searchable. If the respondent registered the domain before the complainant filed or began using its mark in France, the bad-faith registration limb is difficult to establish. Panels will not impute knowledge of a brand that did not exist at registration. We regularly advise registrants to pull the INPI trademark registry history and produce a clear chronological timeline of registration vs. mark priority as a core element of the defense.

The Paragraph 4(b) bad-faith indicators work in the complainant's favor – registering to sell back at a premium, a pattern of cybersquatting, commercial exploitation by confusion – but each is rebuttable. Demonstrating that the domain was not offered for sale to the complainant (or to anyone, let alone at a premium) dismantles the first indicator. Showing the domain is an isolated registration, not part of a pattern, addresses the fourth.

How should a respondent build the legitimate-interest record?

Building the legitimate-interest record begins the moment the respondent receives notice of the dispute – but ideally before. The documents that matter most are those that existed at or before the date of registration, not those assembled for the response.

The core evidentiary package for a .fr respondent typically includes: the domain registration confirmation with its date; business records showing use of the corresponding name (Kbis extract, SIREN number, invoices, contracts); screenshots of the site as it existed at registration and during the period leading up to the complaint; evidence of expenditure on the domain (hosting, development, content creation); and correspondence showing the respondent did not initiate or encourage contact with the complainant about a sale.

The Wayback Machine (web.archive.org) is underused by respondents. Archived snapshots of the respondent's website at the relevant date can corroborate that a site was live and substantive well before any dispute notice. Panels treat these captures as credible, particularly when combined with server logs or analytics exports showing genuine user traffic.

One critical error respondents make is assuming that a registration certificate alone suffices. It does not. A registration date proves only that the domain was registered. What panels want to see is the course of conduct after registration: what was the registrant doing with the domain, when, and for what purpose?

In a recent matter (a .fr domain in a travel-adjacent category, spring 2025), we defended a registrant who had held the domain for several years with a modest but genuine service offering. The complainant, a later-arriving trademark holder in the same sector, had sent demand letters before filing. We produced the original registration confirmation, archived site captures going back to the year of registration, and a modest revenue record from the domain's associated service. The panel denied the complaint. The outcome turned entirely on the contemporaneous evidence, not on legal argument alone.

If a prior filing against your .fr domain produced an unfavorable outcome, or if you are assessing whether to respond to a complaint that just arrived, email info@cognomenlaw.com – a focused second read often finds the element that was missed.

When is a reverse domain name hijacking finding realistic?

Reverse domain name hijacking – an RDNH finding – is available when a panel determines that the complaint was brought in bad faith, typically to deprive a legitimate registrant of a domain to which the complainant had no genuine entitlement. The finding carries no monetary penalty, but it is a significant reputational statement and is increasingly cited by registrants in subsequent disputes.

Panels are conservative in making RDNH findings. The mere fact that a complaint fails does not mean RDNH follows. A complainant who had a legitimate argument, even one that ultimately did not succeed, is unlikely to face an RDNH finding. But patterns that do attract RDNH findings include: a complainant who knew or should have known that the respondent had priority rights but filed anyway; a complainant who misrepresented the date or scope of its trademark rights; and a complainant using the UDRP as a substitute for a legitimate trademark dispute that belongs in court.

For .fr specifically, the scenario that arises most often involves a complainant with a mark of limited geographic scope filing against a registrant who holds a domain predating the trademark and using it genuinely in France. If the complainant proceeded knowing the registration pre-dated its mark, RDNH is a realistic ask. We have defended .fr registrants in this posture and pursued RDNH arguments where the record supported them.

The minority view on RDNH is more permissive than the consensus. Some panels have signaled that an RDNH finding is appropriate whenever a complaint fails clearly on even one element, not merely where the complainant exhibited actual bad faith. That minority approach is not dominant, but it is not negligible. Respondents who have a clear, documented legitimate interest and face a weak complaint are in the best position to argue for the broader standard.

The decision to request RDNH should be made as part of the response strategy, not appended as an afterthought. It requires its own section in the response, with specific factual allegations about the complainant's conduct, and it must be grounded in the record.

What evidence decides the outcome in a .fr defense?

The documentary record controls almost every .fr defense. Panels decide on the written submissions and annexed evidence; there is no live hearing, no cross-examination, and no opportunity to introduce evidence after the response deadline without a procedural motion that is rarely granted. What goes into the response annexes is, functionally, what the panel has to work with.

The evidence hierarchy in practice:

In a second matter we handled (a .fr domain in a financial services context, autumn 2024), the respondent had held the domain for over a decade under a trade name that predated the complainant's French trademark. The complainant argued bad faith registration and cited the domain's current inactive status as passive holding. We produced archived evidence showing years of active use, followed by a documented period of business wind-down, and a clear trademark chronology showing the complainant's registration postdated the domain. The complaint was denied.

How does defending a .fr domain compare to defending in other zones?

The choice of forum and zone is not always the respondent's to make – it depends on where the complainant files – but understanding the comparative landscape helps a respondent assess the strength of a filing and calibrate the response.

Under the UDRP, the "registered AND used in bad faith" requirement is cumulative, as noted above. Under the Nominet DRS for .uk domains, the test reads "registered OR used" abusively, which is a materially lower bar for complainants and, correspondingly, a narrower path for respondents. A registrant who could defeat a UDRP complaint on registration-era grounds might not prevail under the Nominet standard if current use is independently problematic.

The Afnic SYRELI framework for .fr is closer to the UDRP in its structure than the Nominet DRS is, but it admits a broader range of complainant rights (trade names, company names, non-registered rights under French law). For respondents, that broader complainant-rights pool can be a problem: it reduces the likelihood of defeating the first element. The defense focus accordingly shifts to the second and third elements – legitimate interest and bad faith.

Where a complainant holds marks in multiple jurisdictions and the domain dispute spans a .com and a .fr simultaneously, the respondent faces two separate proceedings under two separate procedures. We have advised registrants in this multi-zone posture. The strategy is not identical across zones: evidence that resolves the UDRP bad-faith question may not be configured optimally for a SYRELI submission, and the response deadlines may not align. Coordinated cross-zone defense is a material advantage.

If a .fr dispute cannot be resolved through SYRELI or an equivalent administrative procedure – or where the complainant has chosen court action directly under French law – the matter moves into French civil litigation. That route is handled with local litigation counsel in the relevant jurisdiction. The domain-administrative procedures are generally faster and cheaper than court, but court action can reach remedies (including damages) that administrative procedures cannot.

A useful comparison:

For most .fr respondents facing an administrative complaint, the response filed in that procedure is the primary and usually only opportunity. It needs to be complete. There is no mid-process correction.

Related at COGNOMEN

Frequently asked questions

What are the chances to defend a .fr domain against a UDRP complaint?

No outcome can be guaranteed – every case turns on its specific facts, the quality of the respondent's evidence, and the panel's assessment. What the record shows, across UDRP proceedings generally, is that a meaningful proportion of complaints are denied, particularly where the respondent files a substantive response and can demonstrate a registration predating the complainant's trademark or a genuine commercial use. Defaulting – filing nothing – is the single most reliable way to lose. A well-prepared response with contemporaneous evidence gives the panel the material it needs to deny the complaint.

What evidence do I need to defend a .fr domain against a UDRP complaint?

The core evidentiary package includes: the domain registration confirmation with its date; business records showing use of the corresponding name before any dispute notice (Kbis extract, invoices, contracts); archived screenshots of the website at registration and throughout the period of use; a trademark chronology showing when the complainant's marks were filed and registered versus when the domain was registered; and evidence that the domain was not offered for sale to the complainant or used to target its customers. Revenue records and developer invoices corroborate genuine use. The Wayback Machine provides independent contemporaneous evidence of site content.

Can I defend a .fr domain against a UDRP complaint without going to court?

Yes. The UDRP (and Afnic's SYRELI procedure for .fr) are administrative processes decided on written submissions; no court appearance is required. The respondent files a written response with evidence within the applicable deadline – 20 days after commencement under the UDRP – and the panel issues a written decision. Court action is a separate route available to either party before or after the administrative decision, but it is not a prerequisite for defense. If the administrative complaint is denied, the domain stays with the registrant. Court becomes relevant only where a party chooses to pursue remedies (such as damages) that administrative procedures cannot reach.

Author: — Respondent defense and reverse domain name hijacking (RDNH). Meet the team.

Speak with Cognomen Law

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

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.