How to enforce a UDRP decision a registrar will not implem… (.store 2)

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

You won. The panel ordered the transfer of a .store domain. The registrar has not moved. Days pass, then weeks, and the domain still resolves to the same parking page or the same bad-faith site. This situation – a UDRP decision that sits unimplemented – is rarer than a flat refusal, but it happens, and it demands a different response than the original dispute filing.

To enforce a UDRP decision a registrar will not implement for a .store domain, the winning complainant has two primary routes: an escalation through ICANN's registrar compliance process, which can compel a contracted party to act, and direct court action in the registrar's jurisdiction seeking a court order that mirrors or reinforces the panel's transfer mandate. The standard UDRP implementation window is 10 business days after the decision, absent a mutual written stay or a court filing by the respondent. If the registrar is unresponsive beyond that period, a compliance complaint to ICANN and, where necessary, a court enforcement action are the operative tools.

This page covers the UDRP implementation mechanics for .store domains, the escalation ladder when a registrar stalls, the court route and when it is warranted, and the evidence that makes enforcement succeed.

Why Does a .store Registrar Fail to Implement a UDRP Transfer Order?

A registrar's failure to transfer following a UDRP decision is almost never a simple oversight. The .store new gTLD operates under the standard ICANN accreditation framework, meaning any accredited registrar managing .store domains is contractually bound to implement a UDRP transfer order within the prescribed period. When that does not happen, the cause typically falls into one of three categories.

First, the registrant may have filed a court action in its own jurisdiction, triggering a mandatory hold on implementation. Under the UDRP Rules, the registrar must suspend the transfer for a stated period – normally 10 business days – after which, if no court proceeding is notified, implementation proceeds. A registrant who files a placeholder or bad-faith lawsuit to extend that hold can stall a transfer for months. Second, there may be a technical lock on the account: a registrar-side hold, an expired authorization code, or an account-compromise situation where the real registrant no longer controls the interface. Third, the registrar may simply be non-compliant, either due to operational failure or because it is itself acting in concert with the bad-faith registrant.

In our practice, we encounter all three patterns. The response differs in each case. A court-triggered hold requires litigation strategy in the respondent's jurisdiction. A technical lock requires registrar escalation and, in some cases, ICANN Registry Services involvement at the .store registry level (Radix is the .store registry). An unresponsive or non-compliant registrar requires a formal ICANN compliance complaint and, where the registrar remains defiant, court action targeting the registrar directly.

What Is the Standard UDRP Implementation Procedure for .store Domains?

The UDRP and its Rules set a clear post-decision sequence that applies to .store domains exactly as it applies to any gTLD. Understanding the sequence is essential before choosing an enforcement path, because missteps in the sequence can prejudice the complainant's position in subsequent court proceedings.

After a panel issues a transfer order, the provider (WIPO or the Forum, depending on where the original complaint was filed) notifies the registrar and both parties. The registrar then imposes a registrar lock on the domain to prevent the registrant from transferring it to a different registrar before the transfer to the complainant is completed. The registrar must wait 10 business days to allow the registrant to seek court intervention. If the registrant notifies the registrar of a court filing within that window, the registrar suspends the transfer pending the outcome. If there is no such notification, the registrar must implement the transfer promptly.

"Promptly" is not defined in calendar days by the UDRP Rules themselves. ICANN's Registrar Accreditation Agreement (RAA) and the relevant ICANN consensus policy obligations fill that gap: a registrar's failure to implement a valid UDRP decision within a reasonable period is a breach of its ICANN accreditation obligations. That breach is the hook for a compliance complaint.

For a complainant holding a transfer order in hand, the checklist is: confirm the 10-business-day window has passed with no court-filing notice from the registrant; confirm the provider has sent the transfer instructions to the registrar; and document all communications with the registrar's abuse or compliance contact. That documentation is the evidentiary foundation of every enforcement step that follows.

If the 10-day window has closed and your .store domain has not transferred, the time to act is now. To assess your enforcement options, contact info@cognomenlaw.com.

How Does the ICANN Registrar Compliance Escalation Work?

ICANN's Contractual Compliance team has the authority to investigate and sanction accredited registrars that fail to implement UDRP decisions. This is often the fastest first step, and it costs nothing in filing fees – though, like all procedural escalations, it requires careful preparation to be effective.

A compliance complaint is filed directly with ICANN using its online Registrar Compliance Complaint Form. The submission should include the case number and decision from the original UDRP proceeding, evidence that the 10-business-day period has elapsed, any correspondence with the registrar about the failed transfer, and a clear statement of what the registrar has or has not done. ICANN will contact the registrar and request a response. In straightforward cases – a registrar that simply failed to act rather than one that is actively obstructing – this process can produce implementation within a few weeks.

Where the registrar responds that the registrant has notified it of a court filing, the complainant needs to verify whether that court filing is genuine, still active, and in a jurisdiction with authority over the domain. Fraudulent or dismissed court filings are sometimes used to indefinitely delay UDRP implementation. If the claimed court proceeding has lapsed or was filed in bad faith, that evidence should be provided to ICANN Compliance and, where necessary, raised in a parallel court proceeding.

ICANN compliance escalation has real limits. ICANN can terminate a registrar's accreditation in extreme cases, but it moves deliberately, and it cannot by itself order a court-confirmed transfer. Where the registrar is located in a jurisdiction with a functioning court system and the domain is of significant commercial value, a court enforcement action running in parallel with the ICANN complaint is the stronger posture.

When Does Court Action Beat the Compliance Route for .store Enforcement?

Court action is the more powerful tool, and it is the right choice in four situations. The right route depends on the registrar's location, the registrant's conduct, and the domain's commercial significance.

First, if the registrant has filed a court action of its own to overturn the UDRP decision, a competing filing in the appropriate jurisdiction – often the same court – is essential to defend the transfer order and, where possible, convert it into a court-confirmed judgment that is harder to resist. Second, if the registrar is actively non-compliant rather than merely slow, a court order directed at the registrar compels transfer under legal sanction rather than a policy request. Third, if the domain has been transferred to a different registrar (a registrar-transfer escape, sometimes called a "snap" transfer) during or after the dispute, reclaiming it requires a court order that reaches across the new registrar's compliance obligations – ICANN compliance alone will not move quickly enough. Fourth, if there is a theft or account-compromise dimension – where the domain was hijacked from the original registrant before or after the UDRP – court action with injunctive relief is the only route that can freeze all transfers in real time.

Consider a recent matter (a .store domain, a US-based registrar, spring 2025): the respondent had notified the registrar of a state court filing in its home jurisdiction within the 10-business-day window, using that filing to hold the transfer in suspension. We coordinated with local litigation counsel in the relevant jurisdiction to challenge the merits of the respondent's court claim and to seek a declaratory order confirming the UDRP transfer mandate. The state court dismissed the respondent's claim within approximately 12 weeks of the original filing, and the registrar completed the transfer shortly thereafter.

The cost calculus matters here. An ICANN compliance complaint is free to file. Court action – particularly cross-border – involves court fees, retaining local litigation counsel in the relevant jurisdiction, and potentially several months of proceedings. For a domain with significant brand equity or commercial value, that investment is rational. For a domain of modest value, the calculus may favor sustained ICANN compliance pressure and patience over litigation.

If a court filing by the respondent is blocking your .store transfer, or if your registrar has gone silent, we can assess whether a court enforcement route or parallel ICANN escalation fits your situation. Email info@cognomenlaw.com.

What Evidence Is Required to Enforce a UDRP Decision Against a Stalling Registrar?

Evidence in a UDRP enforcement action is different from evidence in the original dispute. The panel's decision has already resolved the substantive trademark and bad-faith questions. The enforcement question is narrower: has the registrar breached its implementation obligation, and if so, how is the breach best characterized?

The core evidentiary package for any enforcement step – ICANN complaint or court filing – includes the following: the full text of the panel's decision, with the case reference from the provider; the provider's official notification to the registrar of the transfer order; the registrar's confirmation (or absence of any confirmation) of the registrar lock; timestamped screenshots of the domain's WHOIS or RDDS record showing the current registrant has not changed; all correspondence with the registrar's compliance or abuse desk; and, if a court hold is claimed, a certified copy of the registrant's court filing.

Additional evidence matters in specific scenarios. If the domain has been transferred to a new registrar in apparent breach of the UDRP lock obligations, the complainant needs RDDS/WHOIS records at multiple timestamps showing the change in registrar of record, together with any evidence that the transfer was made after the panel decision. If an account-compromise or theft dimension is involved – where the registrant changed after the UDRP complaint was filed – the chain of custody for the domain registration must be reconstructed from registrar logs, RDDS history, and any available administrative access records.

One point practitioners miss: the original UDRP complaint's evidentiary record can itself be used in enforcement proceedings to demonstrate that the registrant's bad faith was adjudicated and found proven. Courts in many jurisdictions will treat a WIPO or Forum panel's factual findings as persuasive (though not binding) when evaluating a registrar's or registrant's conduct in an enforcement proceeding. Organizing that record for maximum persuasive effect is part of what effective enforcement counsel does.

Does the .store Registry Have a Role in Enforcement?

The .store gTLD is operated by Radix, a registry operator subject to ICANN oversight. In cases where a registrar is non-compliant, the registry itself may be drawn into enforcement in limited circumstances. A registry can, in principle, be directed by ICANN to take action at the registry level – for example, placing a registry-level lock on the domain to prevent outbound transfers – where a registrar is unresponsive or has had its accreditation terminated.

In practice, registry-level intervention is a tool of last resort and moves slowly. It is most useful as a supplementary step when an ICANN compliance complaint against the registrar is already in progress and the complainant needs to prevent the domain from being transferred away during the compliance investigation. A registry lock request, made through ICANN's escalation channels, creates a belt-and-suspenders protection while the compliance or court process plays out.

We have coordinated registry-level escalation in situations where a registrar appeared to be closing or transferring its book of business, creating a risk that the .store domain in question would be orphaned or transferred to a new registrar of unknown compliance disposition. Early identification of that risk – through monitoring the registrar's ICANN status and the domain's RDDS record – is the key to avoiding the more complex multi-registrar recovery scenario.

How Does .store Enforcement Compare to Enforcement in Other Zones?

The enforcement mechanics for .store are substantively identical to those for .com, .net, or any other gTLD under ICANN's accreditation regime. The 10-business-day implementation window, the ICANN compliance complaint route, and the availability of court action are universal. What differs is the registrar population and the registry operator.

For .com domains, the registrar pool is deep and the largest registrars have well-staffed compliance teams that generally implement UDRP decisions without intervention. For .store – a newer, lower-volume gTLD – the registrar mix may include smaller operators with less established compliance infrastructure, which can produce more friction in implementation even without any bad-faith intent on the registrar's part.

Compare the .store situation to a .de domain dispute. For .de, there is no UDRP mechanism at all. Disputes proceed through the German courts, and DENIC offers a dispute entry (a registration block) while litigation is pending. A transfer order from a German court is implemented directly by DENIC under its own procedures. The enforcement question never arises from a panel decision because no panel issues one. The .store position – a gTLD with a panel decision and a potentially non-compliant registrar – is categorically different, and the available enforcement tools reflect that difference.

For .uk domains under the Nominet DRS, the enforcement dynamic is again distinct: Nominet itself is the registry, and it implements decisions directly without an intermediary registrar in the traditional sense. A Nominet expert decision ordering transfer is implemented by Nominet on its own timeline, making non-implementation by a third-party registrar a near-impossibility in that zone.

For a parallel analysis of UDRP enforcement in the .biz zone – another gTLD with similar registrar-compliance dynamics – see our analysis at enforcing UDRP decisions in the .biz zone. For a comparison of the UDRP against national court procedures in the .me zone, see UDRP vs. national court: the .me comparison.

A second illustrative situation: in a matter handled in late 2024 (a .store domain, a European-registered registrar), the registrar had suspended implementation citing an unresolved internal compliance review triggered by the respondent's claim of an account-compromise affecting its own registration. We documented the chain of domain-registration history through RDDS snapshots and registrar correspondence, demonstrated that the account-compromise claim post-dated the UDRP panel's decision by a suspicious margin, and filed a parallel ICANN compliance complaint. The registrar completed the transfer approximately eight weeks after we engaged, resolving without court action in that instance.

What Is the Realistic Next Step When Your .store Transfer Is Stalled?

The first step is a complete audit of the implementation record: what the provider sent to the registrar, what the registrar has communicated in response, and whether any court-filing notice has been received. That audit takes one to two days and determines whether the situation is a compliance failure, a contested court hold, a technical lock, or an outright bad-faith evasion.

From there, the path is either a carefully prepared ICANN compliance complaint (best for registrar inaction without a court filing), a coordinated litigation strategy with local litigation counsel in the relevant jurisdiction (best for active court resistance or registrar defiance), or a combination of both running in parallel. In our experience, the combination – ICANN compliance escalation creating institutional pressure while court proceedings create legal jeopardy for the registrar and registrant – produces faster resolution than either route alone.

What this is not: a situation where additional UDRP filings help. The UDRP decided the substantive question. Enforcement is a procedural and, where needed, a judicial exercise. Re-filing a complaint that has already been won does nothing to move the registrar and may create confusion in the record. The right tool for enforcement is enforcement counsel, not a second dispute filing.

For a broader view of the court recovery and domain theft practice, see COGNOMEN's court recovery services.

Related at COGNOMEN

• Court recovery and anticybersquatting litigation for domain disputes across all zones
• Enforcing a UDRP decision a registrar will not implement: analysis for .biz domains
• UDRP versus national court procedures: a comparative analysis for .me disputes