Step-by-step: enforce a UDRP decision a registrar will no… (.online 2)

Step-by-step: enforce a UDRP decision a registrar will no… (.online 2). UDRP and ccTLD domain recovery and defense across .online. Email the firm to assess you…

A WIPO panel has ruled in your favor. The decision orders the .online domain transferred to you. Then nothing moves. The registrar acknowledges the order, issues a holding response, and the domain sits exactly where it was. This is not an edge case – it is a recognized failure point in the post-decision mechanics of .online disputes, and it requires a specific sequence of escalation steps to resolve.

To enforce a UDRP decision a registrar will not implement for a .online domain, the winning complainant must work through a defined escalation path: confirm the mandatory 10-business-day implementation window has lapsed, submit a formal default notice to ICANN's Contractual Compliance team, and – where registrar non-compliance persists – pursue a court action in the registrar's jurisdiction to compel transfer. WIPO administers the .online UDRP procedure; the filing fee for a single-member panel starts at USD 1,500. The arbitration award itself is not self-executing; only a court or ICANN's compliance mechanism can force a non-responsive registrar to act.

This guide walks each step in order, identifies the trap that hides inside each one, and explains when – and why – court action overtakes the administrative channel as the faster path.

Why does .online use the UDRP, and what did the panel actually order?

The .online registry operates under ICANN accreditation and requires all registrars serving .online registrations to implement the Uniform Domain Name Dispute Resolution Policy as a condition of the registration agreement. WIPO, the Forum, the Czech Arbitration Court, and ADNDRC each handle .online complaints under the same three-element test drawn from Paragraph 4(a) of the UDRP: confusing similarity to a mark, absence of legitimate interest, and registration and use in bad faith – all three must be met.

The panel's order is either transfer or cancellation. Transfer is the common outcome when the complainant wants to operate the domain. Cancellation is available but uncommon – it simply deletes the registration without conveying it. Neither order carries a damages component, and neither compels the registrar under a separate legal obligation. The registrar's duty to implement flows from ICANN's Registrar Accreditation Agreement, not from the panel decision itself. That distinction is where non-implementation problems begin.

What does the decision document say, specifically? Before escalating, re-read it. Confirm the remedy ordered is transfer to the named complainant, that the registrant's name in the decision matches the registrar's current WHOIS record, and that no court action was filed by the registrant to stay implementation. A mismatch in any of those three fields can stall a legitimate implementation attempt and is sometimes exploited by a registrant as a delaying tactic.

Step 1 – Confirm the 10-business-day window and check for a court-stay filing

Under the UDRP Rules, the registrar must implement a transfer decision within 10 business days of receiving WIPO's notification – unless the registrant files evidence of a court proceeding in a jurisdiction of mutual submission. That court-stay mechanism is the most common legitimate cause of delayed implementation, and it is also the most common bad-faith delay tactic. The trap at this step is assuming silence means the window is running. It may not be.

Write to the registrar within one business day of the 10-day window closing. Request written confirmation of either: (a) the transfer completion date, or (b) the court filing that triggered the stay, including the jurisdiction, docket reference, and the date filed. Registrars that have received a valid court filing are required to hold the domain and may not transfer it until the court proceeding is resolved. A registrar that cannot produce a court filing but still refuses to implement is in breach of its ICANN obligations – that breach is the basis for the next step.

Document every communication. Screenshot the WHOIS record before and after the window closes. If the registrar's control panel shows a registrar-lock or a redemption hold that was placed after the panel decision, note the date and time. That kind of post-decision lock, placed without a corresponding court filing, is exactly the type of conduct ICANN's Contractual Compliance team investigates.

Step 2 – Submit a formal complaint to ICANN Contractual Compliance

ICANN maintains a Contractual Compliance team that receives complaints against accredited registrars for failure to implement UDRP decisions. A formal submission here is not optional escalation – it is the designated remedy within the ICANN system before any external action. The trap at this step is sending a vague message. ICANN's compliance intake requires specificity: the case caption, the decision date, the notification date from WIPO, the 10-day expiry, and the registrar's exact response.

Compile a single submission package before filing. It should contain: the WIPO case confirmation email with the commencement and notification dates, the full panel decision document, your written demand to the registrar with timestamps, the registrar's response (or a record of non-response), and the current WHOIS printout showing the domain remains with the original registrant. Attach a single-page cover letter identifying the breach: the registrar's failure to implement within 10 business days under the UDRP and the Registrar Accreditation Agreement, with no valid court stay on file.

ICANN's compliance process does not operate on a fixed public timeline. In our practice, we have seen registrar responses come within two to three weeks of a compliance submission when the filing was complete and the breach was clearly documented. Incomplete submissions invite requests for more information and add weeks to the process. Send everything in the first filing.

For a read on whether the three UDRP elements are met, or to assess whether your registrar's post-decision conduct warrants immediate escalation, reach us at info@cognomenlaw.com.

Step 3 – Assess whether a court action is now the faster path

When the registrar's non-implementation is not a procedural delay but a deliberate refusal – or when the registrant has filed a stay action in a court that will not act quickly – the ICANN compliance channel can run slower than a direct court proceeding. The UDRP does not bar a court action; it explicitly preserves each party's right to independent judicial proceedings. The question is which route reaches a binding order on the registrar faster.

The right route depends on the registrar's location and the facts. If the registrar is incorporated or has a registered agent in a US state, a federal anticybersquatting action can seek a court order compelling transfer directly against the registrar as a party or as a neutral stakeholder. That path reaches a different audience than ICANN compliance: a federal judge, not an ICANN compliance officer. If the registrar is in another jurisdiction, local litigation counsel in the relevant jurisdiction handles the court filing; we coordinate the strategy and prepare the documentation package for handoff.

In a recent matter – a .online typosquat, autumn 2025 – a registrar that had not moved on a WIPO decision within three weeks was served with a court demand through local litigation counsel in the registrar's jurisdiction. The transfer was completed within days of that demand being formally served. ICANN compliance remained open in parallel; the court pressure accelerated it. The two channels are not mutually exclusive.

Consider the cost structure honestly at this step. The ICANN compliance path carries no additional filing fee. A court action in a US jurisdiction adds legal fees that are substantially higher than UDRP legal fees and hourly rather than flat; in other jurisdictions, the fee structure varies. The calculus turns on the value of the domain and the time cost of waiting. For a high-value .online brand identifier, court action in parallel with ICANN compliance is routinely the better choice.

How does the evidence of registrar non-compliance differ from evidence in the original UDRP?

The evidence needed to enforce a stalled transfer is a record of procedural breach, not a trademark case. The panel already decided the trademark question. What you now need to show – to ICANN compliance or to a court – is a clean timeline: decision issued, notification received, 10-day window opened, window closed without implementation, no valid court stay filed by the registrant, and no legitimate technical obstacle acknowledged by the registrar.

Build your enforcement evidence file around five documents. First, the final WIPO decision with the notification confirmation email. Second, your written demand to the registrar, timestamped, clearly identifying the decision and the implementation obligation. Third, the registrar's full response, or a clear record that no response was received. Fourth, a WHOIS printout dated after the 10-day window closed. Fifth, any ICANN compliance correspondence already exchanged.

What evidence defeats an enforcement action? A valid court-stay filing by the registrant is the primary defense. A registrar's documented technical error – a system failure during the transfer window, properly notified to WIPO and to you – may also excuse a brief delay. A registrar's unexplained silence, or a holding response citing unspecified "verification requirements," does not. We regularly advise complainants who receive those holding responses. The appropriate reaction is to demand the specific verification requirement in writing and set a 48-hour deadline for a substantive answer.

What if the registrant has also filed a parallel court proceeding to reverse the decision?

A registrant that loses at UDRP has the right to file a court action within the 10-business-day window to preserve the status quo. If that filing is legitimate and properly notified to the registrar, the registrar is required to hold the domain pending the court outcome. The UDRP decision does not disappear – it remains a strong piece of evidence in the court proceeding – but it is not self-executing once a court stay is in place.

In that scenario, the dispute has moved from arbitration to litigation. Your task shifts from registrar escalation to defending the court proceeding. Courts reviewing UDRP outcomes vary in how much weight they give to the panel's findings: some treat the decision as persuasive; others conduct a de novo review on the trademark merits. Either way, the panel record – the complaint, the response if any, and the decision – becomes exhibit material for the court filing.

Is this a common tactic? It is used more often as a delay mechanism than as a genuine reversal attempt, because full court proceedings are expensive for both sides and the UDRP panel record is often decisive. We have defended registrant clients against this tactic and have seen it used against complainants we represent. The outcome in court generally tracks the strength of the underlying trademark evidence and bad-faith record assembled for the UDRP itself. A well-built UDRP complaint file is the best insurance against a reversal attempt.

If the registrant in your case has filed a court action to stay implementation, email info@cognomenlaw.com to assess the litigation position and coordinate the enforcement strategy.

Step 4 – Closing the transfer: mechanics and the post-transfer trap

Once a registrar is either compelled by ICANN compliance or by court order, or agrees to proceed voluntarily, the transfer itself follows a technical sequence. The registrar initiates an outbound transfer from the registrant's account. That transfer requires an authorization code – often called an EPP code or auth-info code – and the domain must not be locked at the registry level.

The post-transfer trap is this: if you have not already secured a receiving registrar account and confirmed the target registrar will accept an inbound .online transfer, the authorization code the current registrar issues may expire before the transfer completes. EPP codes have short validity windows. Have your receiving registrar account set up, verified, and ready before you request or expect the transfer. Confirm in writing with the current registrar the exact method by which they will initiate the transfer – push or pull – and the timeline they will follow.

In a matter involving a .online brand domain in winter 2025, a complainant experienced a five-day delay because the receiving registrar required additional identity verification that was not completed in advance. The authorization code issued by the losing registrar expired. A second request had to be made and a second ICANN compliance note had to be filed. The lesson is procedural: close the receiving-side logistics before the enforcement reaches its final stage.

After transfer, confirm the WHOIS record reflects you as the new registrant. Place the domain under a registrar lock immediately. Document the completed transfer with a timestamped WHOIS printout. That record closes the chain of evidence in any subsequent dispute about ownership.

Choosing the right forum if you need to re-file or expand scope

If the original UDRP complaint covered only one of several infringing .online registrations – or if new infringing registrations have been created by the same registrant since the decision – a second UDRP complaint may be warranted. The right forum for that second filing depends on the same factors as the first: caseload, timeline, and fee structure.

WIPO handles the largest share of .online UDRP filings and offers an expedited procedure for single-panel cases of up to five domains, delivering a decision in approximately one month. The filing fee for one to five domains before a single-member panel is USD 1,500. The Forum also accepts .online filings, with fees beginning around USD 1,300 for one to two domains. The Czech Arbitration Court offers a lower entry point. For a respondent who has created multiple .online variants to circumvent a prior order, a single complaint covering all domains in the same registration name is more efficient than sequential single-domain filings.

A court action, where available, adds the possibility of monetary relief and a broader injunction. The UDRP remedies – transfer or cancellation – do not reach repeat offenders who create new registrations after a transfer order. US anticybersquatting litigation, for example, can seek a judgment that covers future registrations of confusingly similar marks. That route is handled with local litigation counsel in the relevant US jurisdiction and involves substantially higher legal fees. It is the right path when the registrant is a serial offender with identifiable US assets.

Related at COGNOMEN

• Court recovery and domain theft: litigation and registrar escalation across zones
• Case study: recovering a stolen .biz domain through registrar escalation and ICANN compliance
• Filing a UDRP complaint for a .online domain: procedure, evidence, and forum selection