How to defend a .it domain against a UDRP complaint

How to defend a .it domain against a UDRP complaint. UDRP and ccTLD domain recovery and defense across .it. Email the firm to assess your case.

A complaint lands in your inbox. Someone claims your .it domain infringes their trademark. The transfer demand feels urgent. Before you concede anything, understand that the rules governing a .it dispute are specific, the timeline is tight, and a well-prepared defense can defeat a weak complaint entirely – and sometimes produce a formal finding that the complaint itself was abusive.

To defend a .it domain against a UDRP complaint, you must respond within 20 days of commencement, address all three elements of Paragraph 4(a), and demonstrate at least one safe harbor under Paragraph 4(c) of the Policy. The .it zone does not operate its own distinct arbitration procedure for most disputes; rather, UDRP-eligible .it domains are disputed through an applicable ccTLD reassignment mechanism, and in practice many trademark holders bring the case under the standard UDRP before a forum such as WIPO or the Forum. A respondent who misses the response window defaults – and default rarely ends well.

This page covers the procedural framework for .it, the safe-harbor defenses that actually decide outcomes, the evidence you need to assemble, how fees work, and when an RDNH finding is a realistic objective.

What framework governs a .it domain dispute?

Italy's national registry, the Registro .it, operates its own dispute resolution procedure for .it domain names, separate from the UDRP system used for .com and other generic top-level domains. The governing rules center on the concept of "Reassignment" – a procedure under which a rights holder may seek to have an abusively registered .it domain transferred to itself. That procedure applies Italian law principles and EU trademark rights. It is not the same as the UDRP, and a respondent defending under it faces a different substantive test than the three-element UDRP framework.

Where does the UDRP enter the picture? Some trademark owners who hold both a gTLD registration and a corresponding .it domain in dispute file a UDRP complaint naming the .it domain alongside the generic-zone domain, if the registrant of record appears in an ICANN-accredited registrar's system. In that scenario, the .it domain is effectively pulled into the UDRP proceeding by virtue of the registrar's participation agreement. Other complainants file separately under the Registro .it Reassignment procedure. Either way, the respondent must read the complaint carefully to identify which procedure actually governs, because the defense strategy, the timeline, and the applicable tests differ.

In our practice, we regularly advise registrants who receive a complaint that conflates the two systems. The first task is always to confirm the jurisdictional basis: which forum issued the notice, and which rules does it apply? That determination controls everything else.

If you have received a complaint involving a .it domain and are not certain which procedure governs, contact COGNOMEN at info@cognomenlaw.com for an initial assessment before the response deadline passes.

How does the UDRP three-element test apply when defending a .it domain?

Where a .it domain is brought within a UDRP proceeding, the complainant must satisfy all three elements of Paragraph 4(a): confusing similarity to a mark, no legitimate interest on the respondent's part, and registration and use in bad faith. The respondent wins by defeating any one of those three. That asymmetry is the cornerstone of every defense strategy.

Element one – confusing similarity – is the easiest for a complainant to clear. Panels compare the domain string against the trademark; if the mark appears in the string without obvious alteration, the element is typically met. A respondent rarely succeeds by arguing similarity alone, though there are cases where the mark is purely descriptive or generic, and the comparison genuinely fails. In those situations, a challenge on element one is worth raising.

Elements two and three are where defenses are won. On element two, the respondent carries the practical burden of coming forward with evidence of legitimate interest. The safe harbors in Paragraph 4(c) are the primary tools:

• Demonstrable preparations to use the domain in connection with a bona fide offering of goods or services before notice of the dispute.
• Being commonly known by the domain name, even without a registered trademark.
• Legitimate noncommercial or fair use of the domain, without intent to mislead consumers or tarnish the mark.

On element three, the complainant must show the domain was registered and used in bad faith – a cumulative standard. Panels have consistently held that legitimate registration at the outset is a complete defense, even if the complainant later acquired a trademark that resembles the name. If you registered the .it domain before the complainant's mark existed, that chronology is critical evidence.

What evidence actually decides the outcome?

Panels decide on the written record. No hearing. No cross-examination. The quality of the documentary record you submit with your response is the single most important determinant of outcome.

The evidence framework for a .it defense typically includes:

• Registration history: WHOIS records and registrar confirmation showing the date you registered the domain, ideally predating the complainant's trademark filing or first use date.
• Prior commercial use: Screenshots of the site as it was at or before the date of the complaint, archived captures from web-archive services, invoices, contracts, or correspondence showing use of the domain for a genuine business purpose.
• Common-name evidence: Company registration documents, trade names, social-media profiles, or press coverage showing that you or your entity was known by the domain name.
• Absence of targeting intent: Evidence that the domain was chosen for reasons independent of the complainant's brand – for example, a descriptive term with commercial value in Italian, a personal name, or a geographic reference.
• Communication records: Any correspondence between you and the complainant, including any unsolicited purchase offer they made, which may go to who approached whom and on whose initiative.

What weakens a defense? A parked page with pay-per-click links that reference the complainant's industry is the most damaging pattern panels see. Even if registration was innocent, a monetized parking page that targets the complainant's customers can satisfy element three for bad-faith use, even where bad-faith registration is debatable. If your page was parked automatically by the registrar without your active involvement, document that fact and distinguish it from deliberate targeting.

In a recent defense matter – a .com and .it combination complaint, spring 2025 – we built the legitimate-interest record around pre-dispute commercial correspondence and a company registration predating the complainant's trademark by several years. The panel denied the complaint on both elements two and three. No transfer was ordered.

When is an RDNH finding a realistic goal?

Reverse Domain Name Hijacking – an RDNH finding – is the formal declaration that a complaint was brought in bad faith to deprive a legitimate registrant of a domain. It carries no monetary penalty, but it is a reputational sanction recorded in the public decision record. For a respondent wrongly sued, it matters.

Panels issue RDNH findings where the evidence shows the complainant knew at the outset that it could not succeed. Classic patterns include:

• The complainant's trademark postdates the respondent's domain registration by years, and the complainant could have discovered this from the public WHOIS record.
• The complainant is represented by counsel who should have recognized the weakness of the bad-faith element before filing.
• The complaint is filed after the respondent declined a purchase offer – the complaint is then used as leverage, not as a genuine assertion of rights.
• The domain is a common word or phrase with clear descriptive value, and the complainant attempts to monopolize it through the UDRP rather than a court action.

We have pursued RDNH findings in a number of .it-adjacent and gTLD matters where the chronology plainly refuted bad-faith registration. The finding is not automatic; a respondent must affirmatively argue it and point to specific conduct by the complainant that crosses from aggressive advocacy into bad faith. Panels will not issue it simply because the complainant lost.

Is an RDNH argument worth making in your case? That depends on the complainant's conduct and the gap between their trademark date and your registration date. We assess that question as part of the defense engagement.

If you believe the complaint against your .it domain is abusive or opportunistic, email info@cognomenlaw.com to discuss whether an RDNH argument fits your record.

How does the Registro .it Reassignment procedure differ from the UDRP?

The Registro .it Reassignment procedure applies Italian and EU law principles rather than the UDRP's uniform international rules. Several differences are material to how a defense is built.

First, the substantive test under Reassignment is not the three-element UDRP framework. The complainant must demonstrate rights in a name and show that the registration is being maintained in bad faith or is interfering with those rights. The analysis is closer in spirit to Italian unfair competition and trademark principles than to the Paragraph 4(a) structure.

Second, the remedies and the decision body differ. Reassignment is handled through a panel of experts operating under Registro .it's rules, not through WIPO or the Forum. The decision timeline is governed by those domestic rules rather than the approximately 45–60 day UDRP standard.

Third, the respondent's safe harbors under Reassignment are not labeled as Paragraph 4(c) safe harbors, but the underlying logic – prior use, common name, noncommercial fair use – maps broadly onto analogous concepts in Italian IP law. A respondent who can establish genuine commercial use of the .it name predating the complainant's rights is in a strong position under either system.

For a registrant holding a .it domain who faces a Reassignment filing, we work with local litigation counsel in Italy to prepare and coordinate the defense. Where the same domain is also challenged in a parallel UDRP, we manage both proceedings and ensure the evidence record is consistent across forums.

How do costs and fees work for a .it domain defense?

Cost structure depends on which procedure the complaint invokes. If the matter is a standard UDRP filed before WIPO or the Forum, the WIPO filing fee is USD 1,500 for a single-member panel on one to five domains. That fee is paid by the complainant. The respondent pays nothing to WIPO or the Forum for a single-panelist case – there is no defensive filing fee under the standard UDRP. The only respondent-side cost is legal counsel.

If the complainant requests a single panelist but the respondent elects to upgrade to a three-member panel, the parties split the higher three-member fee. At WIPO, that means the respondent pays a share of the difference between the USD 1,500 single-panelist fee and the USD 4,000 three-member fee. Three-member panels are generally worth requesting in high-stakes cases or where the legal issues are genuinely novel.

For a Registro .it Reassignment, the fee structure follows that registry's published rules. Confirm current fees directly with Registro .it or through counsel, as those figures can change.

Legal fees for a respondent defense – assembling the record, drafting the response, building the RDNH argument if applicable – typically run in a range comparable to the complainant-side legal fee market, which for a single-domain straightforward case is often in the USD 3,000–7,000 range for the legal work alone, separate from any forum fee. Complex cases, parallel proceedings, or matters requiring Italian-law analysis will fall toward the higher end or above it. COGNOMEN publishes its service ranges rather than hiding them behind a quote-only process.

What are the cross-zone considerations when both a .com and .it are in dispute?

Multi-zone complaints are increasingly common. A complainant holds a trademark and finds the same string registered both as a .com and as a .it by the same respondent. They file a single UDRP complaint covering both domains, or they file a UDRP for the .com and a Registro .it Reassignment for the .it separately.

A single UDRP complaint covering multiple domains is permissible only when the same registrant holds all the named domains. Where the .com is registered to one entity and the .it to another – even a closely related one – a combined complaint may be procedurally improper, and a respondent should raise that objection.

The more complex scenario is parallel proceedings: a UDRP for the .com running simultaneously with a Reassignment for the .it. In that situation, the evidence submitted in one proceeding may effectively be available to the panel in the other. Inconsistencies between responses in the two forums are dangerous. We coordinate both defenses from the outset to ensure the legal theory and factual record are aligned.

Is court action ever preferable? For a .it dispute where the UDRP does not reach, or where the respondent wants to establish trademark rights affirmatively rather than merely defend, Italian court proceedings – supported by local litigation counsel in Italy – offer the only route to injunctive relief and damages. The UDRP and Reassignment both provide transfer or cancellation only; neither awards money or establishes IP rights going forward.

The right route depends on the relief sought and the strength of the record. If the goal is simply to keep the domain, a well-prepared UDRP response or Reassignment defense is usually faster and less expensive than litigation. If the goal includes damages or a binding declaration of rights, court is the appropriate path.

Related at COGNOMEN

• Respondent defense and RDNH across gTLDs and ccTLDs – full service overview
• Fair-use and legitimate-interest defenses in .org and other open gTLDs – FAQ
• URS versus UDRP for financial-sector domains – decision guide