Update: changes affecting how to enforce a UDRP decision a registrar…

Update: changes affecting how to enforce a UDRP decision a registrar. UDRP and ccTLD domain recovery and defense across .store. Email the firm to assess your c…

A UDRP panel orders transfer of a .store domain. The registrar does not act. What options remain — and have the mechanics for forcing compliance recently shifted?

When a registrar fails or refuses to implement a UDRP transfer order, the winning complainant must pursue enforcement through a separate channel: typically, an escalation to ICANN, a direct court action against the registrar or the current holder, or both. For .store domains, WIPO administers the UDRP and the applicable registry rules require an accredited registrar to give effect to a valid transfer decision — but those rules do not guarantee swift voluntary compliance. The path forward depends on why the registrar is not acting and what evidence of the underlying dispute is already in hand.

This alert covers what has changed in the enforcement picture for .store, who is most affected, and what a complainant holding an unenforced panel decision should do now.

What changed — and why it matters for .store complainants

The .store gTLD operates under ICANN-accredited registrars bound by the standard Registrar Accreditation Agreement (RAA). That agreement requires registrars to implement valid UDRP decisions — but the enforcement mechanism when a registrar stalls has grown more complicated in practice. Several recent procedural developments at the registrar and registry level have sharpened the distinction between a registrar that is administratively slow and one that is actively obstructing a transfer. Knowing which situation applies dictates the next move.

A registrar may decline to implement a UDRP decision for several reasons: the losing registrant has filed a court challenge (the standard "10-business-day hold" pause applies); the registrar itself is in dispute with the registry; the domain has been transferred away between filing and decision — a practice sometimes called "cyberflight"; or the account credentials that hold the domain have been compromised, making registry-level action the only lever.

In our practice, we have seen an uptick in situations where a .store registrant moves a domain during the pendency of a proceeding, triggering a registrar-change event that an existing lock does not always catch. That is the practical change most affecting complainants right now.

Who is affected

Brand owners who have already obtained a UDRP transfer order for a .store domain but have not yet seen the domain appear in their registrar account. Complainants in active proceedings where the registrant appears to be planning a transfer-away. And any party who has discovered that the domain was moved, sold, or re-registered in a third-party name between the complaint date and the decision date.

If you hold an unenforced UDRP decision for a .store domain, an early assessment can identify whether the registrar's delay is administrative or structural. For an assessment of your domain dispute, contact info@cognomenlaw.com.

What to do now

Three routes exist when a UDRP decision goes unimplemented, and the right one depends on the precise reason for the delay.

First, document everything. Pull the current WHOIS/RDDS record immediately. Note the registrar of record, the registry-assigned status codes, and any lock flag. If the registrant status codes show "clientTransferProhibited" or "serverTransferProhibited," those are protective — the domain has not moved. If the domain has transferred to a new registrar, you need a copy of that WHOIS snapshot with a timestamp, because cyberflight to a new registrar is the strongest evidence supporting a court action for contempt-style enforcement or for an independent ACPA-style claim.

Second, escalate to ICANN. ICANN maintains a compliance function specifically for registrar failures to implement UDRP decisions under the RAA. Filing an ICANN Compliance complaint is low-cost and often produces a response within a matter of weeks. It is not a guarantee of action, but it creates a formal record that the registrar received notice of its obligation.

Third, assess the court route. Where the registrar is the US-based entity or the domain holder is within a reachable jurisdiction, US anticybersquatting litigation — referencing the same evidence already assembled for the UDRP — can compel transfer and, unlike the UDRP, can reach monetary damages. We coordinate that work with local litigation counsel in the relevant jurisdiction. The evidence threshold is higher than the UDRP, but a panel decision already in hand is powerful foundational proof.

For situations involving actual account compromise — where a domain was stolen from the winning party's own registrar account rather than merely not transferred — the mechanics shift again. Registrar escalation, documentary evidence of the compromise event, and in some cases registry-level intervention are the tools. That is a distinct track from an unimplemented UDRP decision, though the two sometimes overlap when the theft occurred after the decision was issued.

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

Related at COGNOMEN

• Court action and domain theft recovery — when arbitration cannot reach
• Registrar lock escalation and transfer reversal for compromised accounts
• Respondent defense and RDNH — domains registered before the trademark