Step-by-step: seek a reverse domain name hijacking finding for a .it…

Step-by-step: seek a reverse domain name hijacking finding for a .it. UDRP and ccTLD domain recovery and defense across .it. Email the firm to assess your case.

A Neapolitan design studio has held its .it domain for over a decade. Then a trademark filing appears – registered after the domain – and a Reassignment complaint follows. The complaint claims bad faith without explaining how a registration predating the mark could be abusive. This is not an unusual fact pattern. It is, increasingly, the profile of a case where a respondent can do more than merely defend: they can seek a finding of reverse domain name hijacking.

To seek a reverse domain name hijacking (RDNH) finding for a .it domain, a respondent must show that the complainant brought the proceeding in bad faith – typically because the complainant knew or should have known it could not satisfy the test for abusive registration. Under the Reassignment procedure that governs .it disputes, the applicable standard tracks the UDRP framework, requiring the respondent to establish a legitimate interest and document the complainant's tactical overreach. No monetary penalty attaches, but an RDNH finding is a public, permanent reputational consequence for the complainant.

This guide follows each step in sequence, naming the trap concealed inside each one.

Step 1: Understand the governing procedure for .it – what is Reassignment and how does it differ from the UDRP?

The .it registry (Registro.it) is administered by the Italian National Research Council, and .it disputes proceed under the Reassignment procedure rather than the UDRP directly. The Reassignment procedure incorporates a test substantially similar to the three UDRP elements – confusing similarity, absence of legitimate interest, and bad-faith registration or use – but it is administered under Italian national rules and before Italian arbitral bodies. The applicable panel draws on UDRP consensus views as persuasive authority, and RDNH is a recognized outcome under those rules.

The trap in Step 1 is assuming that UDRP procedure maps perfectly onto a .it complaint. It does not. Eligibility rules, language requirements, the composition of the panel, and the treatment of default all vary. A respondent who files a defense drafted entirely around WIPO UDRP procedure risks missing procedural requirements that could undermine an otherwise strong RDNH argument. Confirm the current rules with counsel before drafting.

One practical point matters immediately: unlike the UDRP's 20-day response window, the .it procedure has its own deadline for the respondent's submission. Missing that window forfeits the respondent's standing to seek any finding, including RDNH. Check the commencement notice as the very first act.

Step 2: Identify whether the complaint has the hallmarks of an abusive filing

Not every unsuccessful complaint supports an RDNH finding. Panels reserve it for cases where the complainant demonstrably knew the claim was weak and pressed it anyway. The clearest indicators are: a trademark filed or registered after the domain; a complainant who is a competitor of the respondent seeking to acquire a commercially valuable name; a complaint that ignores an obvious Paragraph 4(c) safe harbor; and a representation about registration date that the public WHOIS record immediately contradicts.

Ask three questions at the outset. First, does the complainant's mark predate the domain registration? If the domain is older than the mark, the bad-faith-at-registration limb of the UDRP-aligned test almost certainly fails. Second, did the complainant contact the respondent before filing and propose a purchase? An unsolicited offer to buy the domain, followed by a complaint when the respondent refused, is strong circumstantial evidence of a reverse hijacking motive. Third, is the complainant a competitor or a serial filer? Panels scrutinize both categories carefully.

The trap in Step 2 is overconfidence. A domain that predates a trademark is a powerful fact, but it is not automatically dispositive. The respondent still needs to demonstrate a positive legitimate interest, not merely the absence of bad faith on their own part.

If you have received a .it Reassignment notice and you are uncertain whether the complaint is abusive, a focused review of the filing can clarify the strength of an RDNH argument. Contact us at info@cognomenlaw.com to assess your position.

How do the Paragraph 4(c) safe harbors apply – and how do you build a legitimate-interest record?

The Paragraph 4(c) safe harbors – bona fide use before notice of the dispute, being commonly known by the name, and legitimate noncommercial or fair use – apply by analogy in Reassignment proceedings because the Italian procedure follows the same substantive architecture. A respondent who demonstrates any one of these circumstances establishes a legitimate interest, defeating the second element and undermining any bad-faith inference.

Building that record is active work. It is not enough to assert that the domain predates the trademark. The respondent should gather: dated screenshots of the website as it existed from registration forward (including archived captures), evidence of commercial activity under the domain name (invoices, client correspondence, company registry filings), and any communications from the complainant prior to filing. Panels in UDRP-aligned proceedings have consistently found that a respondent who uses a domain in connection with a genuine business interest – predating any notice of the dispute – satisfies the bona fide use standard.

The trap in Step 3 is leaving gaps in the timeline. A legitimate-interest argument collapses if the domain was parked for three years in the middle of an otherwise active commercial history. Panels look at the whole period, not just the earliest and most recent activity. Address any gaps explicitly rather than hoping the panel will not notice.

An important secondary record is what the respondent did NOT do. Did they ever offer the domain for sale to the complainant? Did they ever point it at a site mimicking the complainant's brand? Absence of predatory conduct corroborates the legitimate-interest argument and can push a borderline case toward an RDNH finding.

Step 3: Draft the response – structure the RDNH argument without overreaching

An RDNH argument belongs in its own clearly labeled section of the response, not buried in the legitimate-interest analysis. It should identify the specific ground on which the complainant's conduct is characterized as bad faith – whether that is filing with knowledge that the mark postdates the domain, advancing a complaint that ignores available public records, or using the procedure as a pressure tactic after the respondent declined to sell.

The response must first defend the three elements competently. Panels dismiss RDNH requests that appear in responses where the respondent has provided a thin or disorganized defense. The implicit message is that if a respondent cannot demonstrate their own legitimate interest clearly, they are not well-placed to characterize the complainant's case as abusive. In our practice, the RDNH requests that succeed are those embedded in responses that would have won on the merits regardless.

The trap in Step 4 is rhetorical excess. Describing the complainant's conduct in inflammatory language – "obvious bad faith," "cynical abuse," "deliberate fraud" – signals to the panel that the respondent is arguing emotionally rather than analytically. Panels respond to the evidence, not to the characterization of it. State what the documents show; let the panel draw the inference.

One structural choice matters: if the panel is single-member, weigh whether to request a three-member panel. A three-member panel is more likely to issue a reasoned RDNH finding when the facts are strong, but it increases the forum cost – typically the parties share the difference between the single and three-member fee. The decision requires a realistic read of the record.

What evidence actually decides whether a panel issues an RDNH finding?

Panels in UDRP-aligned proceedings have consistently held that RDNH is not a consolation prize for winning a defense. It requires affirmative evidence that the complaint was brought abusively. The evidence that tends to be dispositive falls into three categories: the chronological record (domain older than the mark by a clear margin); the complainant's knowledge (they had access to public WHOIS data before filing, showing the registration date); and conduct prior to the filing (settlement demands, purchase inquiries, or communications suggesting the real motive was acquisition rather than enforcement).

Secondary evidence that supports an RDNH finding: the complainant is represented by counsel who would have identified the chronological issue through basic due diligence; the complaint contains material misrepresentations about the registration date or the respondent's use; and the complainant has a history of filing aggressive proceedings against legitimate registrants.

In a recent matter – a .it dispute, winter 2025 – we built the RDNH argument around a paper trail showing the complainant had emailed the respondent twice with purchase offers before filing. The panel transferred nothing; instead it found the complaint was filed as leverage after the respondent refused to sell, and issued an RDNH finding against the complainant.

The trap in Step 5 is relying solely on the chronological argument. Domain age is necessary but not sufficient. The panel wants to understand why the complaint was filed despite the obvious weakness, and the answer to that question – supported by documents – is what elevates a successful defense into an RDNH finding.

Step 4: Understand the realistic scope of an RDNH finding and what it does not provide

An RDNH finding has no monetary consequence under the Reassignment procedure or under the UDRP. The complainant pays no damages. The respondent receives no costs award. The panel cannot refer the matter to a court. The finding is published with the decision and remains part of the public record.

What the finding does accomplish: it creates a permanent public record that the complainant abused the dispute process. For a repeat corporate complainant, that record carries reputational consequences in subsequent filings, where panels will note the prior RDNH history. For a brand owner considering future enforcement actions, it signals that the particular dispute strategy is not viable.

Managing the client's expectations at this stage is essential. In our practice, we regularly advise registrants who expect a financial remedy when the UDRP-aligned procedure simply does not provide one. The value of an RDNH finding is reputational and strategic, not compensatory. If the registrant sustained actual losses from the abusive filing – lost business, forced legal expenditure – the court route is the forum for those claims, handled with local litigation counsel in the relevant jurisdiction.

If a prior filing produced an adverse outcome, or if you are assessing whether the facts here support an RDNH request, a second read focused on the evidence can clarify what was missed. Email info@cognomenlaw.com to discuss.

How does the .it route compare to alternatives – when should you use the court instead?

The right route for a .it respondent depends on what the respondent actually needs. If the goal is to keep the domain, defeat the complaint, and if warranted signal that the complaint was abusive, the Reassignment procedure accomplishes all three. It is faster than Italian civil litigation and substantially less expensive.

If the goal is also to recover costs or damages sustained because of the complainant's abusive filing, the Reassignment procedure cannot help. Italian civil litigation – handled with local litigation counsel in the relevant jurisdiction – can reach monetary relief and injunctive orders, but on a timeline of months to years, and at cost levels that require a realistic damages estimate to justify.

A third scenario: the same bad actor has registered the corresponding .com as well. In that case, a parallel UDRP complaint filed by the respondent against the complainant's .com is not possible under the procedural architecture – the UDRP is a complainant's remedy. But the RDNH finding in the .it proceeding, if obtained, is citable evidence in the .com defense, and vice versa. We have coordinated parallel .it and .com defenses where a single factual record supported both proceedings. The key is ensuring the .it response and the UDRP response are consistent and mutually reinforcing, not filed independently by different counsel without coordination.

For new-gTLD domains, the URS (Uniform Rapid Suspension) operates differently – suspension rather than transfer – and its standards and fee structure do not apply to .it. Any comparison between URS and Reassignment is instructive only as contrast; the two procedures do not overlap in practice.

In a recent matter – a .it and .com parallel defense, autumn 2024 – we coordinated the evidentiary record across both proceedings. The .it panel declined transfer and noted the complainant's trademark postdated the registration by approximately four years. The .com UDRP panel reached the same conclusion and went further, issuing an RDNH finding that the complaint was filed to acquire a commercially valuable name the respondent had legitimately held.

Step 5: After the decision – next steps whether RDNH is granted or denied

If the panel issues an RDNH finding, the decision is published and the domain remains with the registrant. The practical next steps are to preserve the decision in the respondent's commercial records, monitor for any subsequent complaint by the same complainant in other zones, and – where the abusive filing caused documented loss – evaluate with local litigation counsel whether a civil claim is viable.

If the panel declines to issue an RDNH finding but the respondent wins the defense on the merits, the outcome is still a complete victory: the domain is retained. The RDNH finding is a separate layer. Its absence does not weaken the underlying win.

If the panel finds against the respondent and orders transfer, the Reassignment procedure has its own appeal mechanism. The respondent should immediately consult counsel on the appeal deadline and ground. Unlike the UDRP, which has no internal appeal path – only a court challenge – some national ccTLD procedures, including those modeled on Italian arbitration rules, provide a supervisory review step. The exact mechanics depend on the current registry rules; verify them immediately after any adverse decision.

The trap in Step 6 is inaction after a win. A domain recovered through a successful defense is only secure if the registrant monitors the registration and its renewal. An unrenewed domain, or one lost through registrar account compromise, creates an opening for the same complainant to register it again. Consider registering across adjacent zones and setting renewal reminders well in advance.

Related at COGNOMEN

• Respondent defense and RDNH across UDRP and ccTLD proceedings
• Defending a UDRP complaint: frequently asked questions for respondents
• URS and new-gTLD launch protection: how suspension differs from transfer