Assess my case

Step-by-step: enforce a UDRP decision a registrar will not implement for a .group domain

By Adrian Harland, Court anticybersquatting & domain-theft recovery ·

A WIPO panel has ruled in your favor. The three-element test is satisfied, the decision orders transfer of the .group domain, and the registrant has not sought court review within the ten-day lock period. Yet days pass, then weeks, and the registrar does nothing. This is not a rare edge case. It is a predictable friction point in the UDRP's implementation chain – and it has its own remedies.

To enforce a UDRP decision a registrar will not implement for a .group domain, you must first identify why implementation has stalled – technical lock, a claimed court filing by the respondent, or registrar non-compliance – then escalate through ICANN's registrar accountability channel, and, where that stall is deliberate or a court filing is filed merely to obstruct, pursue US anticybersquatting litigation or a targeted court order. The decision itself does not expire, but delay lets the registrant prolong control. Twenty days after a UDRP decision is issued, the registrar must implement transfer unless it receives notice of a court proceeding initiated by the respondent.

This guide walks each step, flags the trap inside each one, and sets out the evidence you will need at every stage.

How Does the .group Zone Fit into the UDRP Implementation Chain?

The .group top-level domain is a new generic TLD launched under ICANN's new gTLD program, and its registry agreement requires accredited registrars to comply with the UDRP as a condition of accreditation. WIPO serves as a leading dispute-resolution provider, and a WIPO decision ordering transfer carries the same mandatory weight for a .group domain as it does for a .com. The registrar of record is contractually obligated to implement it.

That obligation sounds absolute. It is not self-executing. The registrar relies on a ten-business-day waiting period following notification of the decision before it acts. During that window the respondent may file a court action in a jurisdiction of mutual jurisdiction – typically the registrar's location or the registrant's location, as designated in the registration agreement. If the respondent files and notifies the registrar, the registrar will suspend implementation indefinitely until the court proceeding is resolved or abandoned. The trap: any filing, however weak, triggers that hold. A bad-faith respondent can buy months of additional control with a frivolous suit.

In our practice, we regularly advise complainants who have won at WIPO but find the registrar's ticket portal silent. Understanding the .group registrar's specific processes matters. Not all accredited registrars handle new-gTLD transfer orders through the same internal workflow, and some have a documented history of implementation delays.

Step 1 – Confirm the Decision Status and the Waiting Period

Before escalating, verify the exact date WIPO notified the registrar of the decision, because the ten-business-day implementation window runs from that notification date, not from the date you received the decision. WIPO publishes decisions on its online case portal; the notification letter to the registrar is a separate document and often carries a later date than the panel's decision itself.

The trap in this step: complainants often count calendar days, not business days. A decision issued on a Thursday can appear to be in default when the registrar is still inside its legitimate window. Miscounting leads to premature escalation, which can irritate the registrar's compliance team and slow the process further.

Confirm the following before moving to any escalation:

Step 2 – Make a Formal Written Demand to the Registrar

Once the waiting period has expired without a court-filing notice, send the registrar a written demand – not a ticket, a formal letter – citing the UDRP, the panel's decision, the notification date, and the expiry of the ten-business-day window. Attach the decision and the WIPO notification letter. State clearly that continued non-implementation is a breach of the registrar's ICANN accreditation agreement and demand implementation within a short, defined period.

The trap here is in the medium. A support ticket can be closed, re-routed, or ignored by a frontline agent with no authority over UDRP transfers. A letter addressed to the registrar's legal or compliance department, sent by email with read-receipt and also by courier to its registered address, creates a documented record for the ICANN escalation that follows. Keep every reply, every timestamp, and every auto-response.

If the registrar acknowledges the demand and cites an internal processing queue, ask for a written commitment to a specific date. A vague "we are working on it" is not sufficient. Your letter should state that absent a date-certain commitment, you will escalate to ICANN.

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

Step 3 – Escalate to ICANN's Registrar Compliance Team

ICANN's Contractual Compliance department accepts formal complaints against registrars that fail to implement UDRP decisions within the required window. This is not an arbitration; it is a contract enforcement mechanism. ICANN can require the registrar to show cause, impose contractual remediation, and in extreme cases initiate the process of terminating the registrar's accreditation agreement.

A well-drafted ICANN compliance submission includes: the UDRP decision and WIPO notification; your written demand and the registrar's non-response or inadequate response; a timeline showing the number of business days elapsed; and a statement that no court proceeding notice has been received. ICANN publishes its compliance intake process on its public site; follow it precisely.

The trap: ICANN compliance is not fast. Processing times vary, and ICANN typically gives the registrar an opportunity to cure before taking further steps. Do not rely on ICANN compliance as your only lever if the domain is actively being used to harm your business. Run it in parallel with the next steps, not instead of them.

In a recent matter – a .group domain and a parallel new-gTLD dispute, spring 2025 – we filed an ICANN compliance submission on day twenty-two of a stalled implementation. The registrar implemented the transfer within ten days of receiving ICANN's inquiry. That outcome is plausible, not guaranteed; the registrar's responsiveness to ICANN pressure varies considerably by the registrar's size and compliance culture.

What Happens When the Respondent Files a Court Action to Block Transfer?

If the respondent has filed a court action and notified the registrar, the registrar is entitled – indeed required under the UDRP – to wait for that proceeding to resolve before transferring the domain. Your UDRP win is on hold. This is the most difficult scenario, and it requires a parallel litigation strategy rather than continued escalation to ICANN.

Your first question is whether the court filing has merit. A complainant who won on all three UDRP elements with strong evidence faces a respondent who must now prove a positive case in court – that it does have rights, that it did not register and use the domain in bad faith. That is an uphill burden for a party a WIPO panel has already found against. In our practice, we regularly advise brand owners in this position that a court respondent relying on a weak filing often has no appetite for full merits litigation and will eventually abandon the proceeding.

The trap: "eventually" can mean years, and abandonment is not guaranteed. Two strategic responses are available. First, you can intervene in the respondent's court action – or file your own parallel claim – in a jurisdiction with courts that can move quickly on cybersquatting matters. US anticybersquatting litigation, for example, allows a complainant to seek a court-ordered transfer, and a court in the relevant jurisdiction may be persuaded to dismiss a transparently obstructive filing on an expedited basis. Second, you can seek an injunction ordering the registrar to hold the domain in trust pending resolution, preventing the respondent from transferring or monetizing it while the proceedings run.

Both routes require working with court recovery counsel and, where the registrar or respondent is in a foreign jurisdiction, local litigation counsel in the relevant jurisdiction. COGNOMEN coordinates that engagement on the client's behalf.

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

What Evidence Decides the Outcome at Each Stage?

The evidence that matters shifts at each step. For the ICANN compliance submission, the critical record is procedural: notification dates, response windows, written demands, and the registrar's non-response. For the court route – whether you are reinforcing your UDRP win or countering a blocking action – the substantive evidence from the UDRP proceeding becomes central again.

Gather and preserve the following:

The quality of this record is the difference between a quick resolution – a registrar who implements on ICANN's first inquiry, or a court that dismisses the obstructive filing on the papers – and a drawn-out proceeding.

How Does the Court Route Compare to Continued ICANN Escalation?

This is a genuine decision point, and the right answer depends on three variables: how urgently the domain's continued misuse is harming you, how much the respondent appears willing to litigate, and in which jurisdiction the registrar and respondent are located.

If the registrar is simply slow – not bad-faith – ICANN escalation is the proportionate response. It is lower cost, moves the contractual compliance mechanism, and usually resolves the stall within weeks without litigation. If the registrar is located in a jurisdiction where ICANN's leverage is weaker, or if the respondent has filed a court action that is not frivolous on its face, then a court route becomes necessary sooner. US anticybersquatting litigation is one path that allows both transfer and, in appropriate cases, monetary damages – something the UDRP cannot deliver. That route is substantially more expensive and slower than UDRP, but it is also the only mechanism that reaches money and can resolve a stalemate where a respondent has filed in court.

A third scenario arises where the registrar itself appears to be acting in bad faith – processing transfers for the respondent after the decision, or facilitating a change of registrant. That is a more serious situation, closer to domain theft, and warrants both an ICANN compliance emergency escalation and immediate court action. See our service on court action for cybersquatting for how that route is structured.

For context on the broader dynamics at play when new gTLDs are involved, our analysis of new gTLD launch protection sets out the trademark-protection mechanisms available at the registry level – mechanisms that can be useful in parallel with enforcement of a decision.

In a recent matter – a .group registrant with a pattern of new-gTLD cybersquatting, winter 2025 – we advised a brand owner to pursue ICANN escalation and a parallel injunction simultaneously. The registrar implemented within three weeks of the ICANN inquiry; the injunction application was never served. The dual-track approach resolved the matter faster than waiting to see whether ICANN alone would move the registrar.

What Is the Myth That Stops Complainants from Enforcing?

The most common misconception we encounter is that a UDRP win is, for practical purposes, self-executing – that winning the panel decision means the domain will transfer automatically, and that any delay is just administrative lag. It is not. The UDRP transfers the right to receive the domain; it does not physically move it. The registrar is the gatekeeper, and if that gatekeeper is slow, absent, or facing an obstructive court filing, the decision sits in limbo.

A related myth: that there is nothing further a complainant can do once the respondent files a court action. In fact, that filing opens up a court docket – and a court docket can be used by both sides. A complainant who won at UDRP has strong evidence to bring to a court, and in many jurisdictions can seek to have a dilatory filing dismissed efficiently or to convert the proceeding into a vehicle for full cybersquatting relief including damages.

What decides the enforcement outcome is not the strength of the original UDRP decision alone – that is already settled. What decides it is the quality of post-decision procedural action: the speed and form of the registrar demand, the completeness of the ICANN submission, and the strategic choice about whether and when to enter court proceedings.

Related at COGNOMEN

Frequently asked questions

What are the chances to enforce a UDRP decision a registrar will not implement for a .group domain?

Enforcement outcomes turn on why the registrar has stalled. Where the stall is purely administrative – a processing queue or a missed ticket – ICANN compliance escalation typically resolves it within weeks, and the decision is implemented. Where the respondent has filed a court action, enforcement depends on the merits and jurisdiction of that action. No outcome can be predicted with certainty, but a complainant holding a WIPO decision on all three elements has strong grounds for both ICANN escalation and, if needed, court proceedings. The UDRP decision itself does not expire.

What evidence do I need to enforce a UDRP decision a registrar will not implement for a .group domain?

For ICANN escalation, you need the WIPO notification date to the registrar, proof that the ten-business-day window has passed, your written demand and the registrar's response or silence, and confirmation that no court-proceeding notice has been filed. For a court route, you need the full UDRP record – complaint, exhibits, and decision – plus post-decision screenshots showing continued domain use, any court filing made by the respondent, and certified trademark documentation in the form the court requires. Preserving this record from the day of the decision is essential.

Can I enforce a UDRP decision a registrar will not implement for a .group domain without going to court?

Yes, in most cases where the stall is registrar non-compliance rather than a respondent court filing. The ICANN contractual compliance channel gives ICANN authority to require the registrar to show cause and implement the decision. That channel is free to use and does not require litigation. If the respondent has filed a court action and notified the registrar, however, the registrar is entitled to wait for that proceeding to resolve, and a court route becomes necessary to move the matter forward or to seek interim relief preventing further harm while proceedings run.

Author: — Court anticybersquatting and domain theft recovery. Meet the team.

Speak with Cognomen Law

For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter

No obligation. Confidential. We reply within two hours in business hours.

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.