Step-by-step: bring a court action when UDRP cannot reach a .it domain

Step-by-step: bring a court action when UDRP cannot reach a .it domain. UDRP and ccTLD domain recovery and defense across .it. Email the firm to assess your ca…

A brand owner discovers a .it domain registered in its company name, pointing visitors to a rival's site or a parking page demanding a five-figure purchase price. The first instinct is to file a UDRP complaint. The problem: Italy's country-code zone is not covered by the UDRP, and the governing national procedure has its own rules, its own evidence standard, and its own traps at every step.

To bring a court action when UDRP cannot reach a .it domain, a complainant must work through Italy's own Reassignment procedure before the Registro.it arbitration body, or pursue a claim in the Italian civil courts where arbitration is unavailable or insufficient. The process requires a rights basis in an Italian or EU trademark, documented evidence of bad-faith registration, and — in court actions — local litigation counsel in the relevant jurisdiction. The official arbitration route typically resolves in a matter of weeks; a full civil action takes substantially longer and carries litigation costs that the Reassignment route avoids.

This guide walks each step in sequence, names the trap hidden in each one, and explains when the court route is the right call rather than a fallback.

Why the UDRP does not apply to .it — and what fills the gap

The UDRP applies to generic top-level domains and to ccTLDs that have formally adopted it. Italy's registry, Registro.it, has not adopted the UDRP, so a complaint filed at WIPO or the Forum against a .it domain will be rejected at the eligibility check. The zone is governed instead by Registro.it's own dispute-resolution rules, which provide a Reassignment procedure as the primary administrative route.

Reassignment is the Italian equivalent of a transfer remedy: if the procedure succeeds, the domain is transferred to the complainant. The test centers on whether the respondent registered or is using the domain in a manner that infringes the complainant's rights — principally trademark rights recognized in Italy or across the EU. Registration of an EU trademark, even without an Italian national mark, is a recognized basis.

What happens when Reassignment is unavailable or produces an unsatisfactory result? Two scenarios trigger a court route. First, if the respondent has also registered equivalent domains across multiple zones and a court injunction is needed to cover them all, a single civil action may be more efficient than parallel arbitrations. Second, if the conduct involves actual fraud — phishing, brand impersonation, or an account compromise that caused domain theft — the evidence record and the remedies available in court (interim injunctions, potential damages, criminal referral) go far beyond what Reassignment offers.

The practical decision is not "UDRP or court." It is "Reassignment or Italian court." The choice turns on the nature of the harm, the relief needed, and the urgency.

To assess which route fits your situation with a .it domain, contact info@cognomenlaw.com.

Step 1: Establish your rights basis before anything else

Before any filing — Reassignment or court — a complainant must identify and document the trademark rights that will carry the claim. This is the step where cases stall before they begin.

The Registro.it Reassignment rules require a mark recognized in Italy. An EU trademark satisfies this requirement; a national Italian trademark satisfies it directly. A common-law mark or an unregistered brand name may support a court claim under unfair-competition grounds in the applicable national law, but it adds complexity and risk. If your only mark is registered in, say, the United States without EU or Italian coverage, your rights basis for Reassignment is weak. The court route may still be available, but the analysis changes.

The trap at this step: many brand owners assume that owning the equivalent .com is itself evidence of rights. It is not. A domain registration is not a trademark. The claim must rest on a registered mark or a demonstrably established trade name with recognized goodwill in the Italian market.

Practical action before filing: pull the registration certificate for each relevant mark, note the Nice classes, and map them against the goods or services the respondent appears to be offering or targeting at the domain. A mismatch in classes is an early warning that the rights basis needs bolstering.

Step 2: Identify the respondent and lock the domain before filing

The second step is investigative. You need the registrant's identity, the registrar's identity, and — critically — a record that the domain is locked so it cannot be transferred while proceedings are pending.

Italian RDDS (WHOIS) data for .it domains is published through Registro.it. In many cases, the registrant details are privacy-redacted. The registrar of record is usually visible. For Reassignment, formal identity disclosure can be obtained through the procedure itself; for a court action, an interim injunction application or a discovery request to the registrar may be necessary.

The domain-lock trap: in UDRP proceedings, the registrar imposes an automatic lock on commencement. In a .it court action, no such automatic lock exists. A respondent who becomes aware of impending litigation can transfer the domain to a new holder — potentially outside Italy — before an interim order is in place. The first procedural move in any Italian court action involving a domain should be an application for a preliminary injunction (a provvedimento cautelare under the applicable national rules) to freeze the domain's registration status.

In a matter we managed in autumn 2025 — a .it domain impersonating a European financial-services brand — the respondent had pre-registered both the .it and a close variant across a second ccTLD. We coordinated the interim-relief application in Italy with a parallel Reassignment filing on the variant, securing a freeze on both registrations within days. Moving on only one while the other remained live would have left the abuse ongoing.

When does a court action beat Reassignment for a .it domain?

Reassignment is faster and cheaper for most straightforward cybersquatting cases. Court action is the stronger route in four specific situations, and recognizing them early saves both time and cost.

Situation one — Domain theft by account compromise. If someone obtained the domain by hijacking the registrant's account (phishing the registrar login, social-engineering a transfer, exploiting a weak password), the domain was not voluntarily registered by an abusive third party — it was stolen. Reassignment addresses abusive registration, not theft from a legitimate holder. The correct route is registrar escalation to reverse an unauthorized transfer, and where that fails, a court action asserting wrongful conversion with an interim order directing the registrar to freeze and reverse. We regularly advise registrants in exactly this situation, and the evidence record needed is entirely different from a Reassignment complaint.

Situation two — Damages are needed. Reassignment, like the UDRP, provides no monetary remedy. If the infringing use has caused quantifiable commercial harm — diverted sales, phishing losses, reputational damage — a civil action before the Italian courts is the only path that reaches money.

Situation three — Criminal conduct is in play. Brand impersonation combined with phishing, fraudulent invoicing redirected through a domain, or identity fraud calls for a criminal complaint alongside the civil action. Reassignment has no criminal dimension.

Situation four — The respondent is outside Italy and has assets there. Italian courts have enforcement tools — including asset freezes and bank account attachments — that no arbitration body can replicate. If enforcement across borders is part of the strategy, starting in court preserves those options.

The inverse is also true: if the domain was registered to sit on a brand name and demand a premium, and the registrant is reachable and resident in Italy, Reassignment is typically faster and more cost-effective. A civil action adds months and legal cost for no additional remedy.

If you are uncertain which route fits your .it dispute, email info@cognomenlaw.com for an initial read.

Step 3: Prepare the evidence record for either route

The evidence that decides a .it dispute — whether through Reassignment or a court action — follows a recognizable structure. Assembling it before filing avoids the most common cause of procedural delay: supplemental requests for documents that should have accompanied the original complaint.

For Reassignment, the core record includes: the trademark certificate (with translation if not in Italian), screenshots of the domain's current and historical use (archived captures from a web-archive service are admissible), the WHOIS/RDDS record as of the filing date, and a statement of rights connecting the mark to the domain string.

For a court action, the record expands. The trap here is underestimating the evidentiary standard for interim relief. A Italian court granting a provvedimento cautelare needs to see fumus boni juris (prima facie right) and periculum in mora (risk of irreversible harm from delay). The domain-lock application must therefore include evidence that the respondent is likely to transfer or alter the domain if not restrained. Screenshots of prior transfer attempts, communications demanding payment, or evidence of the domain changing registrars recently all support the urgency element.

For a domain-theft case specifically, the evidence record differs again. You need: server logs or account-access logs from the registrar showing an unauthorized login, communications from the registrar about the transfer, a timeline reconstructing the account compromise, and any prior security measures in place (two-factor authentication logs, authorized contacts). This record is submitted first to the registrar through an escalation — and only to the court if the registrar fails to act.

One consistent error we see: brand owners photograph the website once, note the domain registration date, and file. A single static screenshot is rarely sufficient. Web archives providing a longitudinal record of use, evidence of pay-per-click revenue generation, and documented instances of user confusion all strengthen the case substantially.

Step 4: File Reassignment or initiate the court action — and sequence the moves correctly

The sequence in which you file matters as much as what you file.

For Reassignment, the filing is made to Registro.it's designated dispute-resolution body. The procedure accepts complaints in Italian or English. A response period is provided to the respondent. If the respondent defaults, the complainant is not automatically awarded the domain — the body still evaluates the merits, though a default record assists. The remedy, if the claim succeeds, is transfer of the .it domain to the complainant.

For a court action, the sequence is: (1) interim relief application first — filed without notice to the respondent where urgency justifies it; (2) service of the main action; (3) merits hearing; (4) enforcement of the transfer order against the registrar. Local litigation counsel in the relevant jurisdiction handles steps one through four. COGNOMEN coordinates the strategy, prepares the domain-law evidence record, and works alongside that counsel.

The trap in sequencing: filing the main action without the interim application first. The moment the respondent is served with a civil claim, they have notice. Without a prior lock order in place, the domain can be transferred before the court reaches a decision on the merits. The interim application is not optional in a contested court action — it is the procedural foundation.

A parallel-filing scenario from our recent practice: in winter 2025, a European consumer-goods brand held an EU trademark that had been infringed across a .it domain and approximately a dozen country-code variants. We coordinated Reassignment on the .it registration, UDRP complaints on the .com and .net equivalents (where the Policy applies), and — where court action was warranted on the .it — the interim application was filed the same day the UDRP complaints were submitted. Synchronizing the filings prevented the respondent from transferring any individual domain in response to one proceeding while others were pending.

Step 5: Handle the respondent's response — and the RDNH risk if you over-reach

A respondent who files a substantive response will contest one or more elements: the existence of the complainant's rights, the legitimacy of the respondent's own interest, or the bad-faith characterization. In court, a respondent may also cross-claim for a declaration of non-infringement or raise the Italian-law equivalent of reverse domain-name hijacking.

The RDNH risk is real and applies beyond the UDRP. A complainant who files a Reassignment complaint against a registrant with a clearly documented legitimate interest — a domain held for years and used in connection with a genuine business — faces a finding that the complaint was an abuse of the procedure. That finding is reputational in an arbitration context; in a court action, abusive litigation can carry cost consequences under the applicable national rules.

The core question at this step: have you honestly assessed the registrant's side? A registrant who registered the .it before your trademark was filed, or who has traded under the name in Italy for years, may have a legitimate interest that the rights-holder failed to investigate. The decision to proceed past a preliminary assessment is a decision that should be made with full visibility of the respondent's profile — registration date, actual use history, and any prior dealings with your organization.

We advise complainants to run a reverse lookup on the registrant across other domains, review archive records of the site's use history, and check for prior correspondence before filing. Overlooking those steps is the single most common cause of weak complaints that invite a successful defense.

Step 6: Enforce the transfer order and close the loop

A decision in your favor — whether a Reassignment order or a court judgment directing transfer — is not the end of the process. Enforcement against the registrar is a distinct step, and in cross-border situations it adds complexity.

For a Reassignment success, Registro.it implements the transfer order through its standard process once the decision is final and no appeal is pending. The timeline from decision to live transfer depends on the registrar's responsiveness and any appeal window. No additional court action is required.

For a court judgment, the order must be served on the registrar and, if the registrar is outside Italy, the enforcement mechanism depends on the jurisdiction of the registrar's incorporation and its contractual relationship with Registro.it. An Italian court order directing an Italian registrar to transfer a domain is straightforward to enforce. An Italian order directed at a registrar incorporated in a third country requires separate analysis of enforcement routes — local litigation counsel in the relevant jurisdiction handles that dimension.

The trap at this step: assuming the transfer happens automatically. It does not. After a favorable decision, a formal notification to the registrar — citing the order, identifying the gaining registrant, and requesting registrar action within a stated period — is required. If the registrar does not act, an enforcement motion or regulatory complaint to Registro.it is the next step.

Once the domain is transferred, the post-transfer checklist matters: update the WHOIS record, install DNS correctly, check that no redirect or subdomain structure left behind points outward to a third party's infrastructure, and document the full chain of title. That documentation is relevant if the dispute re-emerges or if the domain needs to be valued or sold in the future.

Related at COGNOMEN

• Court action and domain theft recovery services across gTLDs and ccTLDs
• Step-by-step guide: bring a court action for .in domain cybersquatting
• URS suspension for new gTLD domains: when and how to use it