FAQ: enforce a UDRP decision a registrar will not implement for a .it…
FAQ: enforce a UDRP decision a registrar will not implement for a .it. UDRP and ccTLD domain recovery and defense across .it. Email the firm to assess your cas…
A UDRP panel orders transfer of a domain. The registrar delays, misroutes the instruction, or simply refuses to act. For a .it domain, the problem is compounded by one structural reality: the UDRP does not govern .it at all. The Italian country-code zone operates under its own dispute procedure – the Registro.it Reassignment procedure – and a UDRP decision carries no automatic authority over it. So what can a brand owner or domain holder actually do when the enforcement chain breaks down?
Enforcing a UDRP decision that a registrar will not implement for a .it domain requires understanding that .it is not a UDRP zone. The Registro.it Reassignment procedure is the governing mechanism for .it disputes; a UDRP award is not self-executing against a .it registrar. Where a registrar fails to implement a valid order in any zone, escalation paths include formal registrar complaints with ICANN (for gTLD registrars), the applicable national ccTLD registry dispute process, and, where arbitration cannot reach, court action with local litigation counsel in the relevant jurisdiction.
The questions below address the enforcement gap in practical terms: the .it procedure, the registrar-lock mechanics, the court route, and the evidence that decides each outcome.
Does Reassignment or a court decide a .it dispute?
For .it domains, the Registro.it Reassignment procedure is the primary administrative route – not the UDRP. Registro.it is the registry for the Italian country-code zone, and it administers a distinct set of rules that govern who may hold a .it domain and on what grounds a reassignment may be ordered. A UDRP decision from WIPO or the Forum has no binding force over a .it registrar or over Registro.it itself. If you hold a UDRP transfer order and the domain in question is a .it, that order addresses the gTLD side of the dispute only; the .it domain must be pursued separately under the applicable national procedure.
Where the Reassignment procedure is unavailable or insufficient – for instance, where the registrant has obscured eligibility, the timeline is too slow to prevent commercial harm, or the facts involve fraud rather than a simple naming conflict – court action through the Italian courts is the alternative. Italian courts have jurisdiction over .it domains and can order injunctive relief and transfer. We work with local litigation counsel in Italy when court action is the right path. The choice between an administrative reassignment and litigation turns on the nature of the dispute, the remedy sought, and the urgency of the matter.
When can I enforce a UDRP decision a registrar will not implement for a .it domain?
You can act to enforce – or work around – a stalled UDRP implementation the moment you identify that the registrar has failed to carry out the panel's transfer order within the implementation window. For a gTLD domain, a UDRP transfer order is directed to the accredited registrar, which is required under the Policy and the registrar accreditation agreement to implement a final panel decision absent a court filing by the respondent. If the registrar does not act, a formal complaint with ICANN's contractual compliance function is the first lever.
For a .it domain specifically, there is no UDRP transfer order to implement in the first place. The question then becomes: when should you initiate the Reassignment procedure, or escalate to the Italian courts? The practical trigger is the moment you have clear evidence that the .it domain is being used in a way that harms your trademark rights – whether through consumer confusion, diversion of traffic, phishing, or blocking your legitimate use of the name in Italy. Delay runs against you. The longer an abusive registration continues, the more evidence of harm accumulates on one side, but the longer the registrant has to entrench a use that clouds the legitimate-interest inquiry.
In our practice, we regularly advise brand owners who discover the .it version of their name held by a party connected to a gTLD dispute. The right move is almost always to treat the .it and the gTLD as separate proceedings that run in parallel rather than sequentially.
For an assessment of your domain dispute, contact info@cognomenlaw.com.
Who can enforce a UDRP decision a registrar will not implement for a .it domain?
For a gTLD dispute, only the prevailing complainant (the party awarded transfer by the panel) has standing to press the registrar for implementation and to escalate to ICANN if the registrar stalls. Third parties have no direct enforcement right under the Policy. For the .it zone, the right to initiate a Reassignment or court action belongs to any party with rights in a distinctive sign – typically a registered trademark, a well-known mark, or a business name – that is confusingly similar to the .it domain in question. Italian eligibility rules for .it also require that the complainant meet the registration criteria for holding a .it domain; a foreign trademark owner without an EU or Italian nexus may face additional hurdles and should confirm current registry eligibility requirements with counsel before filing.
Where the registrar itself is the problem – whether through inaction, an administrative error, or, in the worst cases, complicity in a hijacking – the registrar's accreditation status (for gTLD registrars under ICANN) or its contractual obligations to Registro.it (for .it registrars) become the basis for the escalation. We have advised registrants who discovered that a transfer had been processed against their instructions; in those situations, the enforcement question runs in reverse: the true holder needs to document the compromise and pursue transfer reversal. That process is fact-specific and time-sensitive.
What is the deadline once a case starts?
Under the UDRP, the respondent has 20 days to file a response after the case formally commences. That window is fixed by the Rules and does not extend automatically. A standard UDRP case is normally completed within about two months of filing, absent procedural complications such as a request for a three-member panel or a suspension for settlement. Once a final decision issues, the registrar has a set implementation period to carry out the transfer or cancellation order, and the respondent has a parallel window to file a court action to block implementation – typically around ten business days under the standard Rules, though registrars and registries vary in how they manage the lock period.
For the Registro.it Reassignment procedure, the published procedural timetable applies under the registry's own rules. Timelines are set by Registro.it and are not aligned with the UDRP schedule. If you are coordinating a gTLD UDRP and a .it Reassignment simultaneously, the two processes will run on different clocks. Court proceedings in Italy operate on a separate, typically longer, timetable, though interim injunctive relief can in appropriate cases be sought on an expedited basis through local litigation counsel.
Missing a response deadline in either the UDRP or the Reassignment procedure is among the most consequential errors in domain disputes. A default does not mean the complainant wins automatically on the merits, but it removes the respondent's opportunity to present any defense at all.
What if the registrant does not respond?
Under the UDRP, if the respondent files no response by the 20-day deadline, the panel proceeds to a decision on the complaint alone. A default is not a concession of liability; the panel still must be satisfied that all three elements of Paragraph 4(a) are met on the evidence submitted by the complainant. In practice, panels have consistently held that a well-evidenced complaint supported by clear trademark rights, an implausible legitimate interest, and recognizable bad-faith conduct will succeed even without a response. Weak or unsupported complaints can still fail on default.
For the .it Reassignment procedure, a similar principle applies: the absence of a response does not create an automatic right to reassignment, but it forecloses the registrant's ability to put forward any affirmative defense. The evidentiary weight then falls entirely on what the complainant filed. This is why the quality of the complaint document and the supporting evidence matters so much in both forums: if the respondent does not appear, the complaint is the entire record.
From a strategic standpoint, a non-responding registrant in a .it dispute may still hold the domain through procedural inertia if the complainant's filing is incomplete. We prepare filings to carry the full evidentiary burden without relying on the respondent to fill any gaps.
Can the decision be appealed or challenged?
UDRP decisions are final in the administrative sense: there is no internal appellate body within the UDRP. The losing party – whether complainant or respondent – cannot file a second UDRP complaint on the same facts (re-filing is generally dismissed as an abuse of the process). The only formal route to challenge a UDRP decision is to file a court action in the jurisdiction designated in the registration agreement before the transfer is implemented. A court can stay the registrar's implementation while the litigation proceeds. This is a meaningful constraint on the enforcement timeline: a respondent who files promptly in the right court can delay or block a transfer order for months or years.
For the .it Reassignment procedure, the registry's rules provide the applicable review mechanism; confirm the current rules with counsel rather than relying on any general description, as registry procedures may be updated. Italian court challenges to administrative reassignment decisions follow the ordinary rules of Italian civil procedure.
Reverse Domain Name Hijacking (RDNH) – a panel finding that a complainant brought the UDRP complaint in bad faith to deprive a legitimate registrant – is not an appeal mechanism, but it is a significant outcome for a wrongly targeted respondent. An RDNH finding carries reputational weight and appears permanently in the panel's published record. No monetary award follows under the UDRP, but the finding can support a subsequent court damages claim in some jurisdictions. In our practice, we actively seek RDNH findings where the facts support them, and we have defended registrants in proceedings that were transparently brought to leverage a sale rather than to vindicate genuine trademark rights.
To weigh the Reassignment procedure against a court action for your .it domain, email info@cognomenlaw.com.
What evidence decides a .it domain dispute or a stalled UDRP enforcement?
For a gTLD UDRP – including the enforcement stage – the evidence that matters is what supports or undermines the three Paragraph 4(a) elements: trademark rights (registration certificates, use evidence, registration date relative to the domain), the registrant's absence of legitimate interest (no bona fide offering, no prior association with the name, no fair-use argument), and bad faith (the Paragraph 4(b) indicia: an offer to sell at a premium, a pattern of abusive registrations, a parking page monetizing confusion, or passive holding of a mark-identical domain).
For the .it Reassignment, the evidence package maps onto the Registro.it test rather than the UDRP elements, though the practical categories are similar: the complainant's rights in a distinctive sign, the registrant's lack of eligibility or legitimate purpose, and the conduct that makes the registration objectionable. If the dispute involves a registrar failure or a suspected account compromise, additional evidence becomes critical: authentication logs, registrar communications, WHOIS/RDDS history, prior transfer records, and any correspondence with the registrant or the registry. In a theft or hijacking scenario, the chain-of-custody evidence for the account – login records, registrar support tickets, and transfer authorization records – is often the determinative material.
What to exclude from the file is as important as what to include. Unverified WHOIS data, generic claims of confusion without consumer-level evidence, and allegations of bad faith that rest entirely on the domain's value rather than its use pattern are recurring weaknesses in filings that fail. The strength of the evidence record is the primary variable a party can control before filing.
Related at COGNOMEN
When can I enforce a UDRP decision a registrar will not implement for a .it domain?
You can act the moment a registrar fails to carry out a final UDRP transfer order within the implementation window. For a .it domain specifically, a UDRP order has no direct authority – you must pursue the Registro.it Reassignment procedure or Italian court action separately. The practical trigger is confirmed abusive use of the .it domain that harms your trademark rights. Parallel proceedings on the gTLD and the .it are usually the right approach rather than waiting for one to conclude before starting the other.
Who can enforce a UDRP decision a registrar will not implement for a .it domain?
Only the prevailing complainant can press a gTLD registrar for UDRP implementation and escalate to ICANN if the registrar stalls. For .it, standing belongs to any party with rights in a distinctive sign – typically a registered trademark or well-known mark – that is confusingly similar to the domain. Foreign trademark owners should confirm current Registro.it eligibility requirements with counsel, as an EU or Italian nexus may be relevant to the right to hold a .it domain on reassignment.
What is the deadline once a case starts?
Under the UDRP, the respondent has 20 days to respond after commencement, and a standard case concludes in approximately two months. For the Registro.it Reassignment procedure, the registry's own published timetable applies. The two processes run on different schedules. Missing a response deadline in either forum is among the most damaging errors a registrant can make, as it eliminates the opportunity to present any defense regardless of the underlying merits.
About COGNOMEN
COGNOMEN is an independent boutique focused exclusively on domain-name disputes. We recover, defend, and transact internet domains across generic and country-code zones, before WIPO, the Forum, CAC, ADNDRC, and national procedures, and in court where arbitration cannot reach. We act for brand owners, domain investors, and registrants – including respondent-side defense and reverse domain name hijacking. Our focus is on the ccTLD and cross-border enforcement questions that fall outside the UDRP's reach. To discuss a domain, contact info@cognomenlaw.com.
Disclaimer: This article is general information about domain-name dispute procedures and does not constitute legal advice. Outcomes depend on the specific facts, the zone, and panel or court discretion. For advice on your domain, contact info@cognomenlaw.com.
Speak with Cognomen Law
For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter
Related
This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.