How to enforce a UDRP decision a registrar will not impleme… (.info 2)

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

You won. The panel issued a transfer order for your .info domain. The deadline passed. And the registrar has not moved. That gap — between a UDRP decision and an actual transfer — is a recognized failure point in the domain recovery process, and it requires a different set of tools than the arbitration that produced the order in the first place.

When a registrar fails to implement a UDRP transfer decision for a .info domain, the winning complainant must escalate outside the arbitration process entirely. The UDRP panel has no enforcement arm. ICANN's accreditation framework gives the governing body leverage over registrars, but the fastest routes for a complainant who needs the domain moved are a direct ICANN compliance report, a targeted court action, or — where the failure stems from a domain theft or account compromise — a registrar-lock escalation combined with a transfer-reversal demand. The choice of route depends on why the registrar is not acting and on how much time has passed since the panel's decision.

This page covers what the .info zone rules permit, why registrars stall, the mechanics of each enforcement path, the evidence that decides which route to take, and what realistic next steps look like when you come to us at this stage.

Why a Registrar May Not Implement a UDRP Decision for a .info Domain

A UDRP transfer order does not automatically move the domain; it instructs the registrar of record to implement it, and that instruction can stall for several distinct reasons. Understanding which one applies to your situation determines everything that follows.

The UDRP implementation window is typically 10 business days after notification of the decision to the parties. Within that window the losing registrant may file a court action in the registrar's jurisdiction of mutual jurisdiction to suspend the transfer. If a court proceeding is filed in time, the registrar is obligated to maintain the status quo — and so a deliberate delay by a sophisticated registrant exploiting that window is entirely within the rules. The registrar is not defying the UDRP; it is waiting for a court stay that may or may not materialize.

A second, more troubling scenario is simple non-compliance. The registrar is unresponsive, has become insolvent or dormant, is located in a jurisdiction with limited ICANN contractual reach, or is actively dragging its feet. This is where ICANN's compliance process and, where necessary, court action become the operative tools.

A third scenario — increasingly common in our practice — is that the domain was transferred or deleted during the pendency of the UDRP proceeding itself, either by the registrant attempting to frustrate the award or as a consequence of an account compromise that preceded your complaint. That is a different problem with a different legal framework, touching on domain theft and registrar liability, not merely non-implementation.

What Rules Apply to the .info Zone?

The .info gTLD is operated under ICANN's accreditation rules, and registrars servicing .info domains are bound by the UDRP as a condition of their accreditation. That means every accredited registrar handling a .info registration must implement a final UDRP transfer or cancellation order once the implementation window closes without a court stay being filed.

.info is not a ccTLD and there is no separate national policy or alternative dispute body that governs it. The procedure that produced your transfer order — almost certainly before WIPO or the Forum — is the correct and only arbitration route. There is no further UDRP appeal; panels do not re-hear decided cases. What exists after a final order is enforcement, not appeal.

The ICANN Registrar Accreditation Agreement is the contractual spine of enforcement. A registrar that fails to implement a UDRP decision without a court stay in place is in breach of that agreement. ICANN's Contractual Compliance team can investigate that breach and, in serious cases, can suspend or terminate accreditation. That threat is meaningful to most registrars. For some, particularly those operating at the margins of the accredited community, it is not.

For an assessment of your domain dispute, contact info@cognomenlaw.com.

How Does the ICANN Compliance Process Work as an Enforcement Tool?

Filing a complaint with ICANN's Contractual Compliance team is the first administrative step when a registrar is non-responsive after the implementation window closes. ICANN will formally contact the registrar and request an explanation. In many cases, that contact alone is sufficient: the registrar implements the order to avoid an investigation that could jeopardize its accreditation.

ICANN compliance is not a fast process. The team operates on its own schedule, prioritizes systemic issues, and cannot compel a transfer in the way a court injunction can. If the registrar responds to ICANN by asserting it received a court filing from the registrant — even a procedurally defective one — ICANN will generally defer to that claim and wait for the court process to resolve.

Practically speaking, the ICANN compliance route works best when the delay is bureaucratic rather than strategic. A registrar that simply missed the notification or has an internal processing backlog will usually act within a few weeks of an ICANN inquiry. A registrant who has deliberately triggered the court-stay mechanism to frustrate the transfer will not be stopped by an administrative complaint alone.

The ICANN process should therefore be treated as a parallel track, not a substitute for the faster options available when time and domain value are material concerns.

When Does Court Action Beat the Administrative Route?

A court action targeting either the non-compliant registrar or the losing registrant — or both — becomes the right tool when the administrative process is too slow, when the registrant filed a sham court proceeding to trigger the stay, or when the domain has been transferred or deleted since the panel's award and you need a court to restore it or award damages.

The relevant jurisdiction for a court action is typically the registrar's jurisdiction of mutual jurisdiction as identified in the registrar's registration agreement, or the registrant's jurisdiction. This is a fact-specific determination. Registrars operating in jurisdictions with well-functioning courts and respect for UDRP decisions are relatively straightforward targets; registrars in jurisdictions where ICANN's contractual leverage is limited may require local litigation counsel in the relevant jurisdiction to pursue the matter effectively.

Consider two situations. First: the panel ordered transfer of a .info domain, the implementation window closed with no court stay, but six weeks later the registrar has still done nothing. That is a breach of the Registrar Accreditation Agreement and a candidate for targeted court action seeking a mandatory injunction compelling implementation. Second: the registrant filed a bare-bones complaint in a local court the day before the implementation deadline, solely to trigger the stay mechanism with no real claim on the merits. Courts in ICANN's jurisdictions of mutual jurisdiction are familiar with this tactic and, where local procedure allows for expedited relief, a motion to dismiss or a cross-motion can resolve it in weeks rather than months.

In a recent matter — a .info domain, spring 2025 — we coordinated a court filing in the registrar's primary jurisdiction roughly five weeks after the UDRP panel issued its transfer order, when the registrar acknowledged receiving the WIPO notification but cited an internal hold it could not explain. The registrar implemented the transfer within ten days of service of process, without the matter proceeding to a hearing.

US anticybersquatting litigation is also available where the registrant has a US nexus. That route allows for statutory damages and is sometimes the most persuasive lever when a registrant — not the registrar — is the obstacle and has assets reachable in a US court. It is, however, substantially more time-consuming and expensive than the administrative routes described above, and should be reserved for situations where the domain value or the registrant's conduct justifies the investment.

To weigh UDRP enforcement against a court action for your case, email info@cognomenlaw.com.

What If the Registrar-Lock and Transfer-Reversal Path Applies?

Where the non-implementation problem traces back to a domain theft or account compromise that preceded or ran alongside the UDRP proceeding, the enforcement logic shifts. The registrar-lock escalation and transfer-reversal process is distinct from UDRP enforcement and operates on a different legal basis.

In the theft scenario, the domain may have been transferred to a new registrant — or even a new registrar — during the UDRP proceeding without the panel's knowledge, leaving the award pointing at a domain whose WHOIS record no longer reflects the respondent named in the complaint. In that situation the UDRP decision may still be valid but unenforceable against a registrar that did not hold the domain when the order issued.

We regularly advise registrants and brand owners who encounter this problem. The operative steps are: document the unauthorized transfer with WHOIS history and account-access logs; escalate through the registrar's abuse team and formal dispute process; and, where the registrar participated in or failed to prevent an unauthorized transfer in breach of ICANN transfer policies, pursue a registrar-liability claim in the appropriate jurisdiction. ICANN's Inter-Registrar Transfer Policy also contains provisions that can be used to reverse a transfer that violated the policy's lock requirements.

Timing is critical. Registrar abuse teams operate with internal service-level expectations that are not always published, and the faster a documented escalation is filed — with a clear chain of evidence showing the unauthorized nature of the transfer — the more likely a prompt administrative reversal becomes. We have seen reversals secured within days of a well-documented escalation. We have also seen cases where a poorly documented request sat for weeks before being acted upon.

For a practical guide to the registrar-lock and transfer-reversal process more broadly, see our guide to recovering a hijacked domain.

What Evidence Decides Which Enforcement Route to Take?

The right enforcement route is determined by the facts on the ground, not by a preference for one forum over another. These are the questions that decide the analysis.

Did the registrant file a court proceeding before the implementation deadline? If yes, confirm it was filed in a jurisdiction of mutual jurisdiction identified in the registration agreement; if not, or if it was filed in a forum the agreement does not contemplate, the stay may be procedurally defective and challengeable. Did the registrar acknowledge the WIPO notification in writing? Acknowledgment combined with inaction is the cleanest fact pattern for a mandatory-injunction application. Has the domain changed registrar or registrant since the panel decision? If yes, review the WHOIS history and the ICANN transfer logs before filing anything, because the enforcement target may have shifted.

The evidence you should gather immediately includes: the full text of the UDRP decision with the panel's transfer order; the registrar's written acknowledgment of notification (or evidence it was sent and received); any court filing number or case reference cited by the registrar as the basis for its hold; and WHOIS snapshots taken before, during, and after the UDRP proceeding. Where the issue is a theft or unauthorized transfer, add account-access logs, registrar correspondence, and any ICANN transfer confirmation emails to that record.

In a second recent matter — a .info dispute, autumn 2024 — a brand owner came to us after receiving the UDRP transfer order and finding that the domain had been quietly transferred to a new registrant two weeks before the panel's decision. The prior registrant had sold the domain mid-proceeding to a buyer who claimed to have no notice of the dispute. We assembled the WHOIS chain, the ICANN transfer-confirmation timestamps, and the registrar's own policy on registrar locks during pending UDRP proceedings. That documentation supported both an ICANN compliance filing and a registrar-liability claim. The domain was restored to the brand owner's control approximately eleven weeks after we were retained, without a court hearing.

How Does the .info Zone Compare to Other gTLD and ccTLD Enforcement Routes?

The enforcement gap — the space between a final UDRP order and an actual transfer — exists across all gTLDs, not just .info. But the practical experience differs by zone and by the quality of the registrar serving that zone.

For .com and .net registrations held by major accredited registrars, implementation is typically routine. The WIPO or Forum notification reaches a compliance team that has handled thousands of transfers; the process is automated in many cases. For .info registrations held by smaller or non-US registrars, the process can be less reliable, and the ICANN leverage over distant registrars is less immediate.

Where the same brand dispute spans a .info and a national ccTLD — say, a .de or a .uk — the enforcement frameworks diverge entirely. The DENIC dispute for .de is a registration block, not a transfer order, and the underlying dispute must go to the German courts. The Nominet DRS for .uk produces its own transfer or cancellation decisions under a distinct procedure. Neither of those forum decisions enforces the other. If you are managing a multi-zone dispute involving .info alongside a ccTLD, the enforcement strategy must address each zone separately and with the tools appropriate to that zone.

URS suspension orders for new gTLDs present a further contrast: the remedy is suspension, not transfer, and the mechanics of implementation are managed at the registry level rather than the registrar level. That distinction matters because a non-compliant URS implementation escalates to a different part of ICANN's structure. For the .info zone specifically, URS is not the operative procedure — the full UDRP applies — so a URS suspension analysis is not relevant here.

Our court recovery practice covers enforcement situations across gTLDs and ccTLDs where arbitration has produced a result the registrar or registry has not honored.

What Is the Realistic Next Step When You Come to Us?

When a client reaches us with an unimplemented UDRP transfer order for a .info domain, our first step is a structured read of the decision, the registrar's conduct since notification, and the current WHOIS record. That assessment typically takes one to two business days. It produces a clear answer on which enforcement route is most likely to move the domain within the client's time and cost tolerance.

If the registrar is simply slow, we file an ICANN compliance report immediately and draft a demand letter to the registrar that identifies the specific breach of the Registrar Accreditation Agreement. That combination resolves the majority of straightforward non-compliance situations without court involvement.

If the registrant filed a court proceeding to block the transfer, we assess the procedural validity of that filing and advise on whether a challenge is warranted in that jurisdiction or whether a separate action in a more favorable forum is the better path.

If the domain has moved since the panel's decision, we build the WHOIS chain and the transfer-policy analysis before recommending any escalation, because the evidence record assembled at that stage determines whether the registrar or the new registrant — or both — are the appropriate targets.

We handle UDRP enforcement, registrar-compliance escalations, and the court actions that follow when administrative tools are not enough. Fees depend on the specific route and the jurisdiction; we will tell you the realistic range at the assessment stage, not after you have committed. For context on the Trademark Clearinghouse and claims-notice process that can intersect with .info registrations, see also our TMCH claims notice FAQ.

Related at COGNOMEN

• Court Recovery — enforcing domain rights when arbitration reaches its limits
• Guide to recovering a hijacked or stolen domain, including registrar-lock escalation
• TMCH and claims notice — how the Trademark Clearinghouse affects new gTLD registrations