How to bring a court action when UDRP cannot reach a .xyz domain

A brand owner discovers that a .xyz registration matching its trademark is redirecting customers to a fraudulent storefront. The UDRP complaint is filed, the transfer order is issued — and then the registrar reports that the domain was locked mid-process following a suspected account compromise. No transfer occurs. The arbitration remedy has run its course, yet the domain remains in hostile hands.

When UDRP arbitration cannot deliver a .xyz domain transfer — because the registrar is unresponsive, the registration was obtained through account compromise, or a court injunction is needed to compel compliance — a court action under applicable anticybersquatting legislation or general civil jurisdiction provides the path forward. The UDRP filing fee at WIPO starts at USD 1,500 for a single-panel case, but court proceedings carry substantially higher costs and timelines; the decision whether to litigate turns on the strength of the evidence and the value of the asset. The only UDRP remedies are transfer or cancellation — no damages, no costs. Court provides what arbitration cannot: injunctive relief, potential monetary recovery, and a binding order enforceable against an uncooperative registrar.

This page covers: when the UDRP reaches .xyz; when it does not and court action becomes necessary; how to build the evidence record; what the process looks like end to end; and the realistic next step for a brand owner or registrant ready to act.

Does the UDRP apply to .xyz domains, and when does it fall short?

.xyz is a generic top-level domain operated under ICANN accreditation, which means all three UDRP elements of Paragraph 4(a) apply: confusing similarity to a trademark, absence of legitimate interest, and registration and use in bad faith. WIPO and the Forum both administer .xyz disputes at the standard published fees. In the ordinary case — a straightforward cybersquatting registration — UDRP arbitration is the right tool and the fastest one.

The UDRP falls short in four concrete situations. First, when the registrar is non-compliant: the panel issues a transfer order but the registrar fails to implement it, either because it is operating outside effective ICANN oversight or because it disputes the order's scope. Second, when the domain was obtained by account compromise or theft — the true registrant is the victim, the current WHOIS/RDDS record reflects a fraudulent transfer, and no arbitration panel has authority to reverse a registrar-level transaction that was not the result of a policy dispute. Third, when the complainant needs damages: the UDRP offers only transfer or cancellation, never money. Fourth, when a respondent obtains a court injunction in its home jurisdiction blocking the registrar from complying with the UDRP order — a tactic panels cannot counter and that only a court order from a competent jurisdiction can override.

We regularly advise brand owners who reach us after a UDRP transfer order sits unimplemented for weeks. The frustration is understandable. The solution, in most cases, is a targeted court filing that compels the registrar directly.

For an assessment of your domain dispute and whether a court action is the right next step, contact info@cognomenlaw.com.

What evidence decides whether a court action will succeed against a .xyz registrant?

Court proceedings in cybersquatting matters — whether under US anticybersquatting legislation or a comparable national law — evaluate substantially the same factual record as the UDRP, but with higher procedural formality and a broader remedial toolkit. The evidence that decides outcomes falls into three categories: rights evidence, conduct evidence, and harm evidence.

Rights evidence is the foundation. A registered trademark — national or international — is the clearest basis. In our practice, complainants with registered marks in the jurisdiction where they intend to sue face far fewer threshold challenges than those relying on unregistered common-law rights. For .xyz, the registration date of the mark relative to the domain registration date matters: courts expect the mark to predate the domain, or at minimum to have substantial reputation at the time of registration. Where the complainant can also show that the mark was prominent — press coverage, substantial sales volume, an established web presence — the rights element strengthens considerably.

Conduct evidence is where most cases are won or lost. Panels and courts look for the indicators in Paragraph 4(b) of the UDRP — registration primarily to sell back to the mark owner at a profit, use to attract users by confusion for commercial gain, a pattern of abusive registrations — but courts also examine the registrant's intent more broadly. A demand letter asking for five figures, a pattern of registering variants of well-known marks, and use of false WHOIS/RDDS contact data are each significant. Where the domain was obtained through account compromise, the forensic trail — server logs, authentication records, registrar access logs — becomes the central exhibit.

Harm evidence matters for damages and for injunctive relief. Courts granting a preliminary injunction typically require a showing of irreparable harm: customer confusion, diversion of traffic, damage to reputation that money cannot repair after the fact. Screenshot evidence of the infringing use, customer complaints or confusion reports, and analytics data showing traffic diverted from the brand owner's own site all contribute.

In a recent matter (a .xyz cybersquatting dispute, spring 2025), we assembled a rights-and-conduct package that combined trademark registration certificates, a demand-letter chain in which the registrant asked for a six-figure payment, and archived screenshots of the domain redirecting to a counterfeit storefront. That package formed the basis of a successful injunction application filed in the registrant's apparent home jurisdiction, with local litigation counsel handling the in-court steps.

How does registrar-lock and transfer-reversal mechanics affect the litigation strategy?

A registrar lock — sometimes called a "hold" or "client transfer prohibited" status — prevents a domain from moving between registrars or changing registrant WHOIS/RDDS data while a dispute is pending. For legitimate registrants who have suffered an account compromise, the lock is protective: it freezes the domain at its current state while the victim gathers evidence and escalates to the registrar. For brand owners pursuing a court order, the lock's existence matters because it defines who must be named as a defendant and which registrar must be served.

Transfer reversal after account compromise follows a different track from a standard cybersquatting complaint. The UDRP is designed for policy disputes, not for undoing fraudulent registrar-level transactions. The correct escalation sequence in a compromise scenario is: immediate registrar escalation (most registrars have an abuse or account-recovery desk); a formal dispute submission to the registrar with the forensic evidence of the unauthorized transfer; and, if the registrar is non-compliant, a court action naming both the registrant and the registrar as defendants, seeking an order requiring restoration of the original registration data.

When the domain is already subject to a UDRP transfer order that the registrar refuses to implement, the court action typically seeks a declaratory judgment confirming the panel's outcome and an injunction compelling the registrar to execute the transfer. That injunction, once obtained, has direct legal force that the registrar cannot ignore without contempt exposure. The process is more expensive and slower than the UDRP itself, but it closes the gap the arbitration system leaves open.

To plan recovery of a stolen or hijacked .xyz domain, or to enforce an existing UDRP order, contact info@cognomenlaw.com.

When does a court route beat UDRP arbitration for a .xyz dispute?

The right route depends on the goal and the specific obstacle. The decision matrix for .xyz disputes runs as follows.

Where the goal is a quick transfer of an ordinarily cybersquatted .xyz and the registrant is reachable, UDRP at WIPO or the Forum is the starting point: the filing fee is USD 1,500 for a single-member panel covering up to five domains, the case typically concludes in about two months, and the transfer remedy is automatic if the complaint succeeds. Speed and cost favor arbitration in the straightforward case.

Where the goal is a transfer but the registrar is non-compliant, UDRP alone is insufficient. Here, a court filing in the jurisdiction where the registrar or the respondent is located — or in the US under anticybersquatting legislation, if the parties or the registry have a US nexus — adds the enforcement lever that arbitration lacks. The additional cost is substantial, and timeline extends to months rather than weeks, but the outcome is enforceable.

Where the goal includes monetary damages — lost revenue, investigative costs, reputational harm — only a court action reaches money. The UDRP categorically excludes damages. US anticybersquatting litigation, for example, can reach statutory damages under the applicable national act; describe the precise range with local litigation counsel in the relevant jurisdiction, as the figures vary and are not verified in the sources we rely on for factual claims.

Where the domain was stolen through account compromise and the current registrant is a bad actor who obtained it fraudulently, neither a UDRP complaint (which addresses policy disputes, not fraud) nor the URS (which suspends rather than transfers, and only for new gTLDs where it applies) is the natural vehicle. A court action for fraud, conversion, or an equivalent civil wrong — filed with local litigation counsel in the registrant's or registrar's jurisdiction — is the correct path.

And where the respondent has already obtained a foreign court order blocking the UDRP transfer, the only counter is a competing court order from a jurisdiction with priority or concurrent power. Panels have no authority to override court injunctions; courts can override each other's orders through recognition proceedings or by asserting primary jurisdiction. That is specialized cross-border litigation requiring coordination between COGNOMEN and local litigation counsel in the relevant jurisdiction.

In a second matter we handled (a .xyz account-compromise case, autumn 2024), the registrar declined to reverse a fraudulent transfer despite three escalation attempts. We coordinated with local litigation counsel to obtain an ex parte injunction freezing the domain at the registrar level within approximately ten days of filing. The domain was restored to the legitimate registrant shortly after service of the order on the registrar.

What is the step-by-step process for bringing a court action when UDRP cannot reach a .xyz domain?

The process is linear but each step carries a decision that shapes the cost and timeline.

Step 1: Preserve the current state. Before filing anything, document the domain's WHOIS/RDDS record, the content to which it resolves, and any demand letters or communications from the current registrant. Screenshot everything with timestamps. If the registrar offers a dispute hold or lock mechanism, activate it immediately — once a domain transfers to a new registrar during litigation, serving process becomes significantly more complicated.

Step 2: Assess jurisdiction and the applicable law. For .xyz, the registry is operated by XYZ.com LLC, which has a US nexus. The registrar of record is the entity to be compelled. The respondent's location matters for personal jurisdiction. COGNOMEN maps the jurisdictional options and identifies the forum most likely to issue interim relief quickly. Local litigation counsel in the relevant jurisdiction handles any in-court steps.

Step 3: File for interim relief before the main action. In most jurisdictions, a preliminary injunction or a temporary restraining order freezing the domain is available on an ex parte basis where the applicant can show urgency and irreparable harm. The evidentiary package assembled in advance (rights, conduct, harm) is submitted in support. The registrar is served as a respondent or as a necessary third party.

Step 4: Serve process on the registrant. If the registrant used false WHOIS/RDDS data — a common tactic in cybersquatting — service may require substituted service through the registrar or publication. US anticybersquatting legislation includes an in rem provision allowing suit against the domain name itself where the registrant cannot be found; that provision is particularly useful for .com and other gTLDs with a US nexus, and may extend to .xyz given the registry's location.

Step 5: Main proceedings and the transfer or damages order. If the respondent does not consent to transfer after the interim injunction, the case proceeds to a merits hearing. Evidence is tested — trademark records, domain registration history, WHOIS/RDDS forensics, conduct evidence. A final order directing the registrar to transfer the domain, and awarding damages where sought, concludes the proceedings.

Step 6: Registrar compliance and post-transfer steps. Once the court order is served on the registrar, compliance is typically prompt: a court order carries contempt exposure that an arbitration award does not. After transfer, immediate steps include updating registrant contact data, placing a registrar lock, and monitoring for re-registration of variant domains.

How does this compare to UDRP enforcement routes for other gTLD zones?

Brand owners managing disputes across multiple zones need a clear picture of how .xyz court action sits relative to other enforcement routes. See our overview of court recovery across gTLD and ccTLD zones for the broader picture, and our analysis of enforcing a UDRP decision in the .tv zone for a parallel case study in registrar enforcement.

For ccTLDs, the picture is structurally different. A .de dispute has no UDRP route at all — it proceeds through the German courts, with a DENIC DISPUTE entry blocking transfer while litigation runs. A .uk dispute under the Nominet DRS operates on an "abusive registration" test — notably, the DRS asks whether the domain was registered or used abusively, a lower standard than the UDRP's cumulative "registered and used in bad faith" requirement. The .eu procedure through the CAC's ADR.eu platform has its own eligibility rules and can result in revocation or transfer depending on the complainant's EU/EEA nexus. For those procedures, see our analysis of national dispute procedures in the .de zone.

The cross-zone lesson is consistent: the UDRP is an efficient first tool for gTLDs in the ordinary case, but its limits — no damages, no registrar-compulsion, no fraud remedy — create situations where court is not a fallback but the only avenue. For .xyz, the ICANN-gTLD architecture means the UDRP applies as a first layer; court action becomes necessary at the specific junctures described above.

What should a brand owner do right now if the UDRP has not resolved the .xyz problem?

Is the UDRP order sitting unimplemented? Has the registrar failed to respond to escalation? Has the domain been hijacked through account compromise and the WHOIS/RDDS data changed without authorization? Each of these is a distinct legal situation requiring a distinct immediate step — but in all three, delay is the common enemy.

A domain pointing at a fraudulent or competing storefront is generating confusion every hour it stays live. An injunction that might have been obtained on an ex parte basis in week one becomes harder to justify — and more expensive to obtain — if the brand owner has waited months. Courts evaluate urgency; a long delay before seeking interim relief is routinely used by respondents to argue that the harm cannot be truly irreparable.

The practical first step is a documented evidence package: WHOIS/RDDS records, screenshots of the domain's current use, trademark registration certificates, any communications from the current registrant or registrar, and the UDRP decision or escalation history if one exists. That package is what COGNOMEN reviews to assess the jurisdictional options and recommend the filing sequence. We assess the three UDRP elements, assemble the bad-faith evidence, identify the court route and local litigation counsel in the relevant jurisdiction, and coordinate the filing.

We have defended and prosecuted domain disputes across gTLD and ccTLD zones. What we do not do is promise a transfer — the facts, the registrar's conduct, and the court's discretion determine that. What we do is build the strongest possible record and pursue the route most likely to deliver the outcome the evidence supports.

Related at COGNOMEN

• Court recovery across gTLD and ccTLD zones — when arbitration is not enough
• Enforcing a UDRP decision in the .tv zone — registrar compliance and court back-up
• National dispute procedures in the .de zone — how German courts handle cybersquatting

Author: Adrian Harland — 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

Domain in disputeYour sideI want to recover a nameI received a complaint — I need a defensePortfolio / brand protectionWhat happenedEmailI agree to the processing of my enquiry as described in the privacy policy.Assess my case

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.