How to enforce a UDRP decision a registrar will not implement… (.it 2)

How to enforce a UDRP decision a registrar will not implement… (.it 2). UDRP and ccTLD domain recovery and defense across .it. Email the firm to assess your ca…

You won the UDRP. The panel issued a transfer order. And then nothing happened. The registrar – or the registry – has not moved the domain, days have stretched into weeks, and your .it name sits where it was before the proceedings began. This situation is rarer than it should be, but it does occur, and it leaves a complainant with a hard question: what now?

When a registrar fails to implement a UDRP decision ordering transfer of a .it domain, the primary institutional remedy is the Reassignment procedure administered by the .it Registry (Registro.it). That route bypasses the non-compliant registrar by having the registry itself execute the transfer. Where Reassignment is unavailable or insufficient, Italian court action provides a parallel path that can compel the registrar to act, impose interim measures, and – uniquely – open the door to monetary relief. Timelines and costs depend on which route is pursued and how quickly the registry or court can be engaged.

This page explains both routes, the evidence each demands, the decision between them, and the step COGNOMEN takes at each stage of a stalled .it enforcement matter.

Why a Registrar Sometimes Fails to Implement a UDRP Transfer Order

A registrar's failure to implement a UDRP decision is not always deliberate obstruction. Understanding the cause shapes the correct response. Implementation lapses generally fall into three categories: administrative inertia (the registrar has received notice but has not processed the transfer within the standard period); a disputed lock status (the domain is under a registrar or registry lock that the registrar claims prevents transfer); and active non-compliance (the registrar refuses to act, disputes the decision's scope, or has itself become unreachable).

The UDRP Rules specify that the registrar must implement the panel's decision within a defined period after the decision is communicated – unless the registrant files a court action and notifies the registrar within that window. If the registrant has filed no court challenge and the registrar has simply not acted, the complainant's position is strong. The failure is procedural, not substantive. But the complainant must still choose the right enforcement lever.

In the .it zone specifically, Registro.it maintains direct authority over the zone file and can, in defined circumstances, act independently of the sponsoring registrar. That authority is the foundation of the Reassignment route.

What Is the Reassignment Procedure Under Registro.it?

Reassignment is the mechanism by which Registro.it transfers a .it domain name to a new registrant (or to the registry's own control) without the cooperation of the sponsoring registrar. It is the closest the .it zone has to an administrative override of a stalled transfer. The procedure is governed by Registro.it's own rules and operational documentation, which should be verified with counsel at the time of filing, since registry policies are updated periodically.

To invoke Reassignment following a stalled UDRP transfer order, the complainant typically must: (1) demonstrate to Registro.it that a competent dispute-resolution body has issued a final transfer decision; (2) establish that the decision was communicated to the registrar and that the implementation window has elapsed without action; and (3) confirm that no court suspension of the decision is in effect. Registro.it then engages directly with the registrar or, where the registrar is unresponsive, acts through the zone-file level to reassign the domain.

The practical advantage of Reassignment is speed. Because the registry itself executes the transfer, the outcome does not depend on the registrar's continued cooperation. The limitation is that Reassignment is a transfer remedy only. It does not produce monetary compensation, it does not sanction the registrar, and it does not create a record of wrongdoing useful in subsequent proceedings. Where those objectives matter, the court route is the stronger instrument.

In a recent matter – a .it cybersquatting case, spring 2025 – we initiated the Reassignment procedure on behalf of a complainant whose registrar had simply not processed the order in the weeks following a panel decision. Registro.it completed the zone-level transfer without the registrar's further involvement. The domain was operational under the client's management within a short period of invoking the procedure.

How to enforce a UDRP decision a registrar will not implement for a .it domain Through Italian Courts

When Reassignment is either unavailable or insufficient, Italian court action is the alternative. Unlike the UDRP, Italian courts can order injunctive relief, impose sanctions for non-compliance, and in principle award damages. The jurisdictional basis for compelling a registrar to implement a UDRP decision typically rests on contract (the registrar's accreditation obligations) combined with the Italian legal treatment of intellectual property rights in domain names.

The court route proceeds through Italian specialized IP courts – the so-called "Tribunali delle imprese" or sections with intellectual property competence – under the applicable Italian procedural rules. An application for an interim measure (provvedimento cautelare) can often be filed on an expedited basis, asking the court to compel transfer or to freeze the registrar's ability to further deal with the domain while the main action proceeds. The standard for interim relief requires showing a right (fumus boni iuris) and an urgency (periculum in mora) – in practice, a final UDRP transfer order plus a documented refusal to implement supplies both elements with relative force.

We work with local litigation counsel in the relevant Italian jurisdiction for all court-based enforcement steps. Cross-border complainants, including those outside the European Union, are entitled to engage Italian counsel; there is no residency requirement that limits the complainant's standing to seek enforcement. The choice between Reassignment and court action should be assessed against the registrar's specific conduct, the age of the UDRP decision, and whether the complainant also seeks damages or a sanctions record.

For an assessment of your enforcement options following a stalled .it UDRP decision, contact info@cognomenlaw.com.

What Evidence Decides Whether Enforcement Will Succeed?

The strength of an enforcement filing – whether at Registro.it via Reassignment or in an Italian court – turns on the documentary record. A complainant who arrives with a complete paper trail will almost always move faster than one reconstructing communications after the fact. The evidence that matters most is: (1) the final, unredacted panel decision with its service confirmation; (2) proof that the decision was transmitted to the registrar (WIPO or the Forum will have records of notification); (3) the registrar's accreditation agreement and any written exchange following the decision; (4) a timestamped WHOIS/RDDS printout showing that the domain has not transferred; and (5) confirmation that no court stay has been filed by the registrant.

If the registrar's non-compliance is active rather than passive – meaning the registrar has written back disputing the transfer, claiming a lock, or asserting some competing interest – that written position becomes critical evidence in court. It shows a deliberate refusal, not an administrative delay, and shifts the court's analysis toward compulsion.

One evidentiary point specific to .it: Registro.it maintains its own WHOIS and registration records for the .it zone. Those records are authoritative for the zone file and can be obtained directly to supplement any RDDS printout that the registrar's own platform might fail to display correctly. In enforcement proceedings, we routinely obtain registry-level registration data rather than relying solely on the registrar's WHOIS feed.

A second specific consideration: if the domain has been transferred – whether to a new registrant or to a connected entity – after the UDRP decision was issued, the enforcement picture changes materially. Post-decision transfers that circumvent a pending order are treated differently from ordinary registration changes, and both Registro.it and Italian courts have mechanisms to address conveyances made in breach of a registry lock or in defiance of a pending decision.

When Does a Court Route Beat the Reassignment Procedure?

The decision between Reassignment and Italian court action is not purely a question of speed versus thoroughness. The two routes serve different strategic purposes, and the right choice depends on the specific obstruction the complainant faces.

Reassignment is the right first move when: the registrar is simply slow or unresponsive but is not actively contesting the decision; the complainant's only objective is to obtain the domain; and the UDRP decision is recent, final, and uncontested by the registrant. In these circumstances, Reassignment is faster and costs less than court proceedings, and the outcome – a zone-level transfer – is identical to what a court would order.

Italian court action becomes the better instrument when: the registrar has in writing refused to transfer, is asserting a competing claim, or is itself the source of the obstruction; the registrant filed a court action in Italy or elsewhere to stay the UDRP decision and that action is still pending; the complainant also needs damages or a sanctions order against the registrar; or the domain has been transferred to a third party after the decision, requiring the court to reach a different legal entity.

There is also a third scenario. Where the .it domain dispute has both a UDRP angle (a generic top-level domain variant of the same mark registered by the same bad actor) and the .it enforcement problem, it may be necessary to pursue parallel tracks simultaneously: Reassignment for the .it domain and a new UDRP filing – or a court action – for the .com or other gTLD variants. COGNOMEN coordinates both tracks and advises on sequencing to avoid any action in one forum prejudicing the position in another.

In a second recent matter – a multi-domain dispute involving a .it name and a .com typosquat, summer 2025 – the registrar of the .it domain had frozen the domain under a lock that pre-dated the UDRP decision. We initiated Italian court proceedings on an interim basis while simultaneously coordinating the UDRP filing for the .com with the Forum. The parallel tracks resolved within a matter of weeks of each other, with the .it domain reassigned at the registry level and the .com transferred by UDRP order.

If a prior filing or response produced a bad outcome, a focused second read can find the element that was missed. Email info@cognomenlaw.com to review your enforcement record.

How Are .it Registrar-Lock and Transfer-Reversal Mechanics Handled?

Domain locks exist to protect registrants from unauthorized transfers. They become a problem when they prevent an authorized transfer following a final dispute-resolution decision. In the .it zone, locks can be placed at the registrar level or at the registry level. The two are distinct, and the correct release mechanism differs.

A registrar-level lock can ordinarily be released by the sponsoring registrar. If the registrar refuses, Registro.it – under its accreditation rules – has authority to require the registrar to release the lock or to intervene at the zone level. This is precisely the context in which Reassignment is most cleanly available: the registrar holds a lock, refuses to release it, and the registry's own administrative authority can step over the registrar's position.

A registry-level lock is placed by Registro.it itself, typically in response to a dispute, a court order, or a detected security incident. Only Registro.it can release a registry-level lock. If a registry lock was placed at the complainant's own request – for example, to freeze the domain during the UDRP – the complainant must formally request release once the UDRP decision is final and Reassignment is requested. Missing this step is a common cause of delay that we pre-empt by filing the lock-release request concurrently with the Reassignment application.

Transfer reversal – where a domain has already moved after the UDRP decision was issued – is a more complex situation. The analysis depends on whether the post-decision transfer was made in breach of the registry lock (in which case Registro.it may treat it as void), in breach of the registrar's accreditation obligations (in which case court action against the registrar is the primary remedy), or by a third party with no notice of the pending decision (which raises a bona-fide-purchaser question that Italian law decides on its own terms). We assess which of these factual patterns applies before advising on the sequencing of steps.

What Is the Realistic Timeline and Cost Structure?

Timelines and costs for enforcing a stalled UDRP decision in the .it zone vary with the route chosen and the complexity of the obstruction.

For Reassignment through Registro.it, the official procedure time is determined by the registry's processing schedule and the speed with which the registrar responds to the registry's own directions. In our experience, a well-documented Reassignment application – where the panel decision is final, the registrar's non-compliance is documented, and no court stay is in effect – is typically processed in a matter of weeks. Registro.it's own published fee schedule governs any official registry charge; the complainant should verify the current fee directly with the registry at the time of filing, as official fees are subject to change.

For Italian court enforcement, interim proceedings can be initiated relatively quickly, but the timeline is subject to court scheduling. An application for urgent interim relief – a provvedimento cautelare – is heard on the court's own timetable, which can range from days to several weeks depending on the court, the urgency established, and whether an ex-parte (without notice) application is appropriate. Full proceedings take longer. The overall cost of court enforcement is substantially higher than Reassignment and is best assessed case-by-case with Italian counsel.

Legal fees for either route are separate from official fees and depend on the complexity of the registrar's non-compliance, the evidentiary record, and whether the matter proceeds to a contested hearing. We advise on the realistic cost range at the assessment stage, before any filing commitment is made. COGNOMEN publishes its pricing approach transparently: assessments are provided by email following an initial review, and engagement terms are confirmed in writing before work begins.

Cross-Zone Considerations: .it Enforcement and the Broader Domain Portfolio

Brand owners with registrations across multiple zones frequently encounter the .it enforcement problem as part of a wider pattern. A bad actor who registers a .it domain alongside a .com, a .eu, or other ccTLDs poses a multi-front problem. The UDRP addresses gTLDs; the .it zone has its own procedure; the .eu zone has the ADR.eu mechanism administered by the Czech Arbitration Court; and the German .de zone has no equivalent arbitration route at all, relying on the German courts and the DENIC DISPUTE entry.

Where the enforcement problem spans zones – for example, where a UDRP decision on a .com has been implemented, but the .it variant remains in the registrant's hands and the .it registrar has not cooperated – the portfolio strategy matters as much as the individual filing. We advise on which domains to pursue first (typically the most commercially significant), which routes to use in parallel (Reassignment for .it, ADR.eu for .eu), and when a single coordinated court application in Italy or another competent jurisdiction is more efficient than multiple administrative filings.

One key cross-border point: a UDRP decision against a .com does not automatically bind the .it registry or a .it registrar. Each proceeding is jurisdictionally separate. But the existence of a prior UDRP finding – particularly a finding of bad faith against the same registrant – is strong supporting evidence in a .it Reassignment application or Italian court action. We structure submissions to make that evidentiary use explicit.

Related at COGNOMEN

• Court action and domain theft recovery across gTLD and ccTLD zones
• Recovering a hijacked or stolen .com domain through registrar escalation and court action
• FAQ: defending a generic domain name in a .ca dispute