FAQ: enforce a UDRP decision a registrar will not implement for a .ap…

FAQ: enforce a UDRP decision a registrar will not implement for a .ap. UDRP and ccTLD domain recovery and defense across .app. Email the firm to assess your ca…

A WIPO panel has ordered transfer of your .app domain. The 10-day implementation window has closed. The registrar has not moved. This situation — a decided UDRP case stalled at registrar implementation — is more common than most brand owners expect, and the path forward depends on why the registrar has paused and what options the .app zone leaves open.

When a registrar fails to implement a UDRP transfer order for a .app domain, the complainant must escalate outside the arbitration process. The UDRP itself provides no enforcement mechanism beyond the registrar's contractual obligation to ICANN. Where that obligation is not honored, a court action — typically in the registrar's home jurisdiction — is the primary route to compel compliance. The filing fee for the WIPO proceeding that produced the original order starts at USD 1,500 for a single-member panel; court enforcement adds separate legal and filing costs.

The questions below address the mechanics, the evidence, the timeline, and the realistic next steps when a .app registrar refuses or delays implementation of a decided UDRP case.

What does it mean to enforce a UDRP decision a registrar will not implement for a .app domain?

It means the UDRP has done its job — a panel has found all three elements under Paragraph 4(a) of the Policy — but the registrar, which holds the technical lever for the transfer, has not acted. Under the UDRP Rules, a registrar is required to implement a transfer or cancellation order within 10 business days of receiving it, unless a court order staying the decision is filed in that window. A refusal or unexplained silence after that period places the registrar in apparent breach of its ICANN Registrar Accreditation Agreement.

For .app specifically, the zone is operated by Google Registry. Accredited registrars must agree to ICANN's standard accreditation terms, which include the obligation to implement UDRP decisions. That obligation does not disappear because the registrar is slow, confused, or subject to competing instructions from its registrant. When implementation stalls, enforcement is the complainant's problem to solve — not the panel's, not WIPO's.

In our practice, we see implementation delays arise in two distinct patterns. The first is a registrar compliance failure: the registrar received the decision but failed to act on it, often because of internal process gaps. The second is a contested stay: the respondent has filed — or claims to have filed — a court action to halt the transfer, triggering the registrar's right to pause. Each pattern demands a different response.

How long does it take to enforce a UDRP decision a registrar will not implement for a .app domain?

The timeline depends entirely on why the registrar has not acted and what jurisdiction it is based in. A straightforward ICANN compliance escalation — filing a complaint through ICANN's registrar compliance portal — can produce a registrar response within days, though resolution may take several weeks. A court action to compel transfer is a longer path: in the US, for example, an action under anticybersquatting legislation typically runs months, not weeks, and may involve emergency injunctive relief if the domain is at risk of being transferred away or allowed to expire.

Where the respondent has filed a legitimate stay — a real court order in the right jurisdiction — the registrar is correct to pause. The complainant then faces a court proceeding on the merits, which substantially extends the timeline beyond the roughly two months a standard UDRP case runs from filing to decision. In our experience, a contested court enforcement matter in a US jurisdiction regularly extends past six months before a final order is obtained.

The most important variable is speed of action. A .app domain can expire, be deleted, or change status while court proceedings are pending. Securing a registrar lock on the domain — preventing any transfer or deletion — is the first practical step, and it should be taken before any enforcement filing.

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

What does it cost to enforce a UDRP decision a registrar will not implement for a .app domain at WIPO?

The WIPO proceeding that produced the original decision cost a minimum of USD 1,500 for a single-member panel covering one to five domains. That fee is spent; it does not carry over to enforcement. WIPO has no role in compelling a registrar to act after a decision is issued. Enforcement is a separate matter that generates its own costs.

An ICANN compliance escalation carries no direct filing fee but requires time and correspondence. If it resolves the problem, it is the lowest-cost path. A court action to enforce the UDRP order — whether an anticybersquatting claim, a breach-of-contract theory against the registrar, or an application for injunctive relief — carries court filing costs and legal fees that are substantially higher than the original UDRP filing fee. Legal fees for court enforcement are typically quoted on a matter basis and are fact-dependent; they are not comparable to the flat-fee structure commonly available for UDRP complaints themselves.

Registry-level escalation to Google Registry as the .app zone operator is a parallel option. Google Registry has no obligation to override its accredited registrar, but a documented pattern of non-compliance with a UDRP order is precisely the kind of registrar conduct ICANN and registries take seriously. In a recent matter involving a .app domain (spring 2025), a combined ICANN compliance escalation and direct registry contact resolved a stalled transfer within three weeks, avoiding court entirely.

What evidence is needed to enforce a UDRP decision a registrar will not implement for a .app domain?

The foundation is the WIPO decision itself, together with the official commencement and decision notices. These establish the panel's findings on all three UDRP elements and the date the registrar received the order. Add to that a precise record of the registrar's non-action: timestamps of every communication sent to the registrar, any response received, and the current WHOIS or RDDS record showing the domain remains in the respondent's name.

If the registrar claims a court stay is in place, obtain and review the actual court order. A registrar cannot simply assert that a stay exists; a complainant is entitled to see the document. Where no court order materializes, the registrar's position is unsupported and the compliance escalation gains force.

For a court enforcement action, the evidence set broadens. The original trademark registration or unregistered-mark evidence supporting the UDRP complaint remains relevant. The panel's reasoning — its express findings on confusing similarity, the absence of legitimate interest, and bad faith — is admissible evidence of the merits. Any conduct by the registrant in the period after the UDRP decision (attempts to transfer the domain out, deletion attempts, or monetization continuing during the delay) supports an argument for emergency relief.

We regularly advise complainants who have a clean WIPO decision but are missing pieces of the enforcement record. A single gap — no timestamp on the registrar notification, a misaddressed compliance email — can delay a court application by weeks.

Can I enforce a UDRP decision a registrar will not implement for a .app domain for more than one domain at once?

Yes, provided the original UDRP complaint covered multiple domains and named the same registrant across all of them. The UDRP permits a single complaint to address multiple domains where they are held by the same registrant. If the decision ordered transfer of several .app domains and the registrar is not implementing any of them, the enforcement action — whether an ICANN complaint or a court filing — can address all of them in a single proceeding.

Where the non-implementing registrar holds some domains and a different registrar holds others, separate escalations are required for each registrar. The UDRP decision is the same document, but each registrar's obligation runs independently under its own accreditation agreement. This is not an uncommon fact pattern when a respondent has spread a portfolio across multiple registrars to complicate enforcement.

A court action can, in principle, join multiple registrars as defendants, though that significantly increases litigation complexity and cost. The simpler path — where it is available — is ICANN compliance action against each registrar in sequence or in parallel, using the single UDRP decision as the governing instrument.

What are the possible outcomes when you enforce a UDRP decision a registrar will not implement for a .app domain?

There are four realistic outcomes. First, the registrar implements the transfer after an ICANN compliance escalation or registry contact — the most efficient result, and the one that requires no court involvement. Second, the registrar implements after being served with court proceedings, before a final order is needed — common where the registrar's delay was process-based rather than contested. Third, a court issues a compelled-transfer order after full proceedings, which the registrar must then implement under the court's authority. Fourth, in rare cases, the respondent successfully argues in court that the UDRP decision was procedurally flawed, and the transfer is blocked — though courts generally treat a WIPO panel's findings as persuasive evidence of the underlying facts.

The UDRP itself offers only transfer or cancellation as remedies. A court enforcement action, by contrast, can in appropriate circumstances add monetary relief — such as recovery of costs — depending on the jurisdiction and the theory of recovery. That is one reason a complainant facing a bad-faith delay by both the registrant and the registrar may prefer court proceedings over a purely administrative escalation.

What the court cannot do is retry the UDRP on the merits in a way that strips the complainant of a clean panel decision. The respondent must show a substantive ground to challenge the transfer — not simply that the registrar failed to act in time.

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

Related at COGNOMEN

• Court action and domain recovery — when arbitration cannot reach the registrar
• Registrar lock escalation mechanics for .uk disputes explained
• ccTLD transfer remedy for .tv — procedure and eligibility