Step-by-step: enforce a UDRP decision a registrar will not im… (.cn 2)

Step-by-step: enforce a UDRP decision a registrar will not im… (.cn 2). UDRP and ccTLD domain recovery and defense across .cn. Email the firm to assess your ca…

A UDRP panel has ruled in your favor. Transfer ordered. You expect the domain to land in your account within days. Instead, the registrar goes silent – or sends a message explaining that implementation is paused, disputed, or subject to local requirements you were not warned about. For a .cn domain, that scenario is not unusual. It reflects a structural gap between international arbitration and Chinese registry enforcement that catches brand owners off guard every time.

To enforce a UDRP decision a registrar will not implement for a .cn domain, you must work through a layered process: ICANN registrar-compliance escalation, parallel engagement with CNNIC and the ADNDRC as the governing dispute mechanism for .cn, and – where arbitration cannot reach – Chinese court action coordinated with local litigation counsel. The UDRP's only remedies are transfer or cancellation; when implementation stalls, you need to know which enforcement channel applies to your specific registrar's position and why. There is no single lever.

This guide walks each step in sequence, identifies the trap inside each one, and maps the decision the reader must make at every fork.

Why does a .cn domain create a distinct enforcement problem?

The .cn country-code top-level domain is administered by CNNIC – the China Internet Network Information Center – under Chinese law. That is the foundational fact that shapes everything else. CNNIC does not operate under the UDRP. It operates under the CNDRP, the China National Domain Name Dispute Resolution Policy, administered primarily through the ADNDRC. If the original UDRP complaint named a .cn domain, the panel had jurisdiction only because the registrar was an ICANN-accredited registrar that had contractually submitted to the UDRP, not because .cn is a UDRP zone in the ordinary sense.

That jurisdictional seam is where implementation fails. When a registrar receives the UDRP transfer order, it may face a competing obligation to CNNIC that prevents it from executing the transfer without approval from the Chinese registry. Some registrars in this position do nothing. Others write back citing regulatory uncertainty. Neither response is a blank refusal; both are gap-exploitation.

The trap: treating this as a simple registrar-compliance issue when it is actually a dual-authority problem. Brand owners who send a single ICANN escalation email and wait have lost months while the registration renewed, changed hands, or became further entrenched.

Step 1: Read the UDRP decision and the registrar's exact position

Before any enforcement action, obtain the full panel decision and the registrar's most recent written communication – or document the absence of one. These two documents define your legal position at every subsequent stage. Do not rely on the forum's case-closure email; retrieve the PDF decision directly from WIPO or the Forum's case portal.

Check four things immediately. First, identify whether the registrar is ICANN-accredited or operates solely under CNNIC authority. An ICANN-accredited registrar has signed the Registrar Accreditation Agreement and is contractually required to implement UDRP decisions; a CNNIC-only registrar may not be. Second, confirm the exact wording of the panel's order – transfer to the complainant, or cancellation? Third, note whether the registrar communicated a reason for non-implementation, or simply failed to respond. Fourth, confirm that the ten-business-day implementation window that the UDRP specifies has passed without action.

The trap: acting before the ten-business-day window closes gives the registrar a procedural basis to dismiss your escalation as premature. Document the date the forum notified the registrar of the decision, and count precisely.

Step 2: File a formal registrar-compliance complaint with ICANN

ICANN's Contractual Compliance team handles failures by accredited registrars to implement UDRP decisions. Submit a compliance complaint at ICANN's published portal, attaching the panel decision, all forum communications, and evidence of the registrar's non-response or stated reason for non-implementation. Describe the timeline in precise dates.

ICANN compliance is not fast. Resolution takes weeks to months, and ICANN's principal remedy is to pressure the registrar through its accreditation obligations. It does not itself execute transfers. But the formal complaint record matters: it creates documented notice of breach that supports subsequent court or regulatory action in China, and it prevents the registrar from later claiming that implementation was merely delayed rather than refused.

The trap: ICANN compliance is a necessary step, not a sufficient one. Brand owners who treat it as the final escalation path find themselves three months later with an open complaint number and a domain still pointing at a competitor's site.

The procedure above is the standard path for any UDRP non-implementation. Your domain, your registrar's exact position, and the evidence you hold decide which of the parallel routes must run alongside it. For an assessment of your domain dispute, contact info@cognomenlaw.com.

Step 3: Engage CNNIC and assess the CNDRP route for the .cn layer

Because .cn operates under CNNIC authority, any transfer of a .cn domain ultimately requires registry-level cooperation. Even a technically compliant registrar cannot complete a transfer if CNNIC has placed a hold on the domain or if the domain's registration record does not permit modification under CNNIC's rules. Your ICANN complaint may resolve the registrar's contractual position while leaving the registry-side obstacle in place.

Engage CNNIC directly – in writing, in Chinese where possible – identifying the UDRP panel decision number, the registrar involved, and the specific registry action you are requesting. At the same time, assess whether the CNDRP provides an independent path. The CNDRP, administered through the ADNDRC, applies its own three-part test to .cn registrations. Filing a parallel CNDRP complaint based on the same underlying trademark rights forces a Chinese-law analysis of the same domain. Panels in this forum operate under Chinese procedural norms, and a CNDRP transfer order carries registry authority that a UDRP order alone does not.

The trap here is duplication risk. Some CNDRP panel decisions have considered a prior UDRP ruling as persuasive evidence of bad faith, but CNDRP panels are not bound by UDRP outcomes. File the CNDRP complaint on its own merits, assembling fresh evidence under the CNDRP standard. Do not assume the UDRP decision speaks for itself in this forum.

In a recent matter – a .cn typosquat targeting a European consumer brand, spring 2025 – the brand owner had a UDRP transfer order in hand but faced registry-level inaction. We initiated a parallel CNDRP filing through ADNDRC and coordinated a CNNIC registry notification simultaneously. The CNDRP proceeding broke the deadlock that ICANN compliance alone could not resolve.

Step 4: Secure the domain against transfer during the dispute

While enforcement steps proceed, the domain remains under the registrant's control. A domain in active dispute can be transferred to a third party, renewed, or allowed to expire – each of which can defeat or substantially complicate your UDRP-based transfer claim. Preventing those outcomes requires parallel action.

Request a registrar lock through the registrar directly, citing the pending ICANN compliance complaint. If the registrar is unresponsive, escalate the lock request through ICANN compliance as an additional ground. Separately, contact CNNIC to request that no transfer of the domain be permitted while the matter is pending. CNNIC does not always accede to such requests from foreign complainants, but making the request in writing establishes the record.

Where the domain is registered at a registrar for which ICANN or CNNIC has an expedited lock procedure – some Chinese-based ICANN-accredited registrars respond to this kind of notice – act within hours of identifying the non-implementation. The longer the gap between the panel decision and the lock request, the greater the risk. We have seen a .cn domain pushed through a transfer to a new registrant within 48 hours of a UDRP decision, which required an entirely different recovery path.

The trap: treating the registrar lock as something that will happen automatically once the UDRP proceeding is over. It will not. Locks must be requested, and where a non-compliant registrar is involved, the request is the beginning of a new fight, not the end of the old one.

For the mechanics of registrar-lock escalation in more complex situations, see our guide to registrar lock escalation.

Step 5: Decide whether Chinese court action is necessary

When does a court route beat arbitration for a .cn domain? The answer depends on what you need that arbitration cannot deliver.

The UDRP and CNDRP both offer only transfer or cancellation. Neither awards damages, legal costs, or injunctive relief against ongoing harm. If the infringing domain has been used to divert commercial traffic, siphon payments, or damage your brand in the Chinese market, the monetary harm is real and unaddressed by any arbitral decision. A Chinese court action – handled through local litigation counsel in China – can pursue both domain recovery and financial remedies under Chinese trademark and unfair competition law. It can also obtain a court-ordered domain lock that carries more coercive authority than a CNNIC administrative request.

Court action is substantially more expensive than arbitration, proceeds on a longer timeline, and requires local counsel with the relevant Chinese court experience. It is not the right first step. But it becomes the necessary step when: the registrar has conclusively refused to implement despite ICANN compliance pressure; the CNDRP proceeding has produced an unfavorable result on procedural grounds; the domain is actively causing financial harm; or the registrant has structured ownership across multiple parties to defeat arbitral transfer orders.

The decision matrix runs like this. If your registrar is ICANN-accredited and the only obstacle is bureaucratic delay, ICANN compliance plus a CNDRP filing is usually sufficient and far faster. If the registrar is CNNIC-only, the CNDRP is the primary path, and ICANN cannot compel action. If both fail or if active harm is ongoing, court action in China is the route, coordinated by COGNOMEN's court-recovery practice with qualified local litigation counsel in the relevant jurisdiction.

If a prior filing or response produced a bad outcome, or if your UDRP decision has sat unimplemented for more than a month, a focused review can identify exactly which step was missed. To weigh UDRP against a court action for your case, email info@cognomenlaw.com.

What evidence decides the outcome at each stage?

Evidence requirements shift as the case moves through stages, and assembling the right record from the beginning saves time and money at every subsequent step.

For the ICANN compliance complaint: the panel decision, all forum notifications with timestamps, and the registrar's response or documented silence. A certified email trail is more useful than a forwarded inbox screenshot. Screenshot the registrar's WHOIS record as of the decision date, and at regular intervals thereafter, to capture any ownership or technical changes.

For the CNDRP: your trademark registration certificate (Chinese trademark rights carry the most direct weight, but international registrations designating China are relevant), evidence of the domain's registration date relative to your rights, and evidence of use in bad faith under the CNDRP standard. The CNDRP does not require showing bad faith at both registration and use in the same cumulative way the UDRP does; in practice, panels have accepted evidence of bad-faith use alone in certain fact patterns. Verify the current CNDRP rules with counsel before filing.

For Chinese court proceedings: all of the above, plus a certified translation of the UDRP panel decision into Chinese, evidence of financial harm, and any evidence of the registrant's identity. Chinese courts may require apostilled or notarized foreign trademark certificates. An evidentiary package assembled for a UDRP complaint in English is rarely sufficient for a Chinese court without reprocessing.

The trap common to all stages: treating English-language evidence as self-evident. Every document submitted in a Chinese forum – arbitral or judicial – that was originally created in English requires a qualified translation, and the quality of that translation affects the outcome more than brand owners expect.

Addressing the myth that a UDRP win is self-executing

The most common misconception we encounter in this practice area is this: a UDRP transfer order means the domain transfers. Full stop. It does not. The UDRP is a contractual mechanism that binds accredited registrars; it is not a court judgment enforceable by a state. A registrar that decides – or is positioned by regulatory complexity – not to implement faces no immediate legal sanction from the arbitration process itself. The only direct enforcement lever over a non-compliant ICANN registrar is ICANN's contractual authority, and that authority operates slowly and through persuasion, not coercion.

For .cn domains specifically, this matters more than in any other major zone. The intersection of Chinese registry authority with ICANN accreditation creates a space in which a registrar can argue, sometimes in good faith, that it is caught between competing obligations. Resolving that argument requires tools beyond the UDRP panel decision.

COGNOMEN regularly advises brand owners who assumed the hard part was winning the UDRP. In our practice, the harder work often starts after the decision arrives. We assess the three UDRP elements, assemble the bad-faith evidence, and select the forum – but equally, we build the legitimate-interest record and document good-faith registration on the respondent side, and we identify when arbitration has hit its ceiling and a court route is the next necessary step.

For a comparison of URS and UDRP options, including how they apply to new-gTLD domains where .cn is not the relevant zone, see our URS vs. UDRP guide for tech domains.

Related at COGNOMEN

• Court recovery and anticybersquatting litigation for domain disputes worldwide
• Registrar lock escalation: a step-by-step guide for stolen or disputed domains
• URS vs. UDRP for new-gTLD tech domains: how to choose the right procedure