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

A brand owner discovers that its exact trading name is registered as a .global domain by a stranger who has no connection to the business. The UDRP is available — .global is a new gTLD and accredited registrars are bound by the Policy — yet sometimes a UDRP complaint is not the right move, or it has already failed to produce the result the brand owner needs. What then?

When the UDRP cannot reach a .global domain — because the registrant has mounted a credible legitimate-interest defense, because the registration predates the trademark, or because the situation involves an account compromise and transfer reversal rather than a classic cybersquatting dispute — a court action under applicable anticybersquatting legislation becomes the primary route. Court proceedings can reach monetary relief, injunctions, and declaratory judgment; the UDRP cannot. The correct forum, the governing law, and the evidentiary record all depend on facts that must be assessed before filing.

This page explains when and how to bring a court action for a .global domain, what the UDRP can and cannot do in this zone, how registrar-lock and transfer-reversal mechanics interact with litigation, and what evidence decides the outcome.

What does the UDRP cover for .global — and where does it stop?

The UDRP applies to .global because .global is a new generic top-level domain operated under an ICANN-accredited registry. Every registrar that allocates .global names is contractually bound to enforce UDRP remedies — meaning transfer or cancellation — when a panel orders them. That is a meaningful starting point.

However, the Policy has firm limits. The only remedies are transfer or cancellation; no monetary damages, no costs award, no injunction against further conduct. If a registrant has used the domain to divert customers, intercept payments, or tarnish the brand, the harm already done lies entirely outside the panel's reach. A UDRP transfer order stops the bleeding; it does not compensate for it.

The second limit is substantive. A complainant must satisfy all three elements of Paragraph 4(a): confusing similarity to a trademark the complainant holds, absence of legitimate interest in the registrant, and registration and use in bad faith — both limbs of the third element must be met simultaneously. Where the registrant has a plausible legitimate interest, or where registration preceded trademark rights, the cumulative test creates real risk of denial. Panels also apply a consensus view that passive holding — parking a domain without active use — can still satisfy the bad-faith use limb, but that consensus is not universal, and a sophisticated respondent can contest it.

Third, account compromise and domain theft are categorically different problems. When a registrant's account is hacked and the domain is transferred without authorization, the UDRP is the wrong vehicle entirely — the issue is not bad faith at the time of registration but a fraudulent transfer that the registrar's own policies must address first, with litigation available when those internal escalations fail.

For a read on whether the three UDRP elements are met for your .global name, or whether a court route is the better first step, reach us at info@cognomenlaw.com.

When does a court action beat a UDRP complaint for a .global domain?

A court action is the stronger choice in four distinct situations. Understanding which applies to your .global domain determines both the strategy and the timeline.

Situation one: damages are needed. If a cybersquatter has used the .global name to divert customers, solicit payments under your brand, or damage your commercial relationships, the financial harm is real and documented. US anticybersquatting litigation, for instance, permits statutory damages and actual damages in addition to transfer. The UDRP delivers only the name; the court delivers the name plus potential compensation. If the conduct is serious, filing a UDRP complaint first and then pursuing a court action later is a sequential option — the UDRP decision is not binding on the court, but a transfer order removes the operational harm while the monetary claim proceeds.

Situation two: the UDRP complaint failed or carries unacceptable RDNH risk. If an earlier complaint was denied or if a realistic assessment of the respondent's position suggests a credible legitimate-interest claim, the UDRP is a trap. A denial does not prevent a court action, but a finding of Reverse Domain Name Hijacking — a panel's conclusion that the complaint was brought in bad faith to deprive a legitimate registrant — is a reputational mark that complicates the litigation posture. Where the facts are genuinely close, going directly to court avoids the RDNH exposure while still producing a transfer remedy.

Situation three: the transfer was unauthorized. An account compromise that moves a .global domain to a third party without the registrant's knowledge is a theft, not a cybersquatting dispute. The correct first steps are registrar escalation and an emergency lock request. When the registrar fails to reverse the transfer — or when the domain has already passed through multiple accounts — litigation for conversion, fraud, or unauthorized transfer is the route that reaches the registrar and the downstream transferee. In our practice, we regularly advise registrants who have exhausted internal escalation channels and need a court order to compel the registry to freeze the name while the ownership dispute is resolved.

Situation four: injunctive relief is needed immediately. Courts can issue preliminary injunctions and temporary restraining orders on an expedited basis. A domain used to impersonate a brand, redirect its customers, or conduct a phishing campaign causes compounding harm every day it operates. A court can order the registrar to lock the domain within days of filing, before any final resolution. WIPO's expedited option can deliver a decision in roughly one month — and that is fast for an arbitration — but it is not the same as a temporary restraining order obtained in hours.

In a recent matter (a .global typosquat, spring 2025), we assessed whether a UDRP complaint or a court filing better served a brand owner whose domain was being used for an active phishing campaign. The combination of ongoing harm and a need for immediate operational shutdown made injunctive relief the controlling factor. The court route produced a lock within the first week.

How do registrar-lock and transfer-reversal mechanics interact with litigation?

Before any court order issues, the domain must be frozen — otherwise a defendant can transfer it to another registrar or another registrant while proceedings are pending. Registrar lock is the first defensive action, and it does not require a court order to initiate.

Most accredited registrars will place a hold on a domain when presented with a formal dispute notice or a law enforcement referral. For .global specifically, the registry operator maintains its own abuse-reporting channel. A formal written demand to the registrar, citing the dispute and requesting a registrar lock under ICANN's transfer policy, is the first step before any proceeding — UDRP or court — is filed. Registrars generally honor these requests where the basis is documented, even absent a court order, because a transfer that occurs after notice of a dispute exposes the registrar to its own liability.

Where the registrar refuses to lock or delays, a court can compel it. ICANN-accredited registrars operating in or serving registrants in the United States are subject to US court jurisdiction in that respect. A temporary restraining order directed at the registrar — not merely the registrant — is an available remedy in US anticybersquatting litigation, and we have pursued this route for clients whose registrar escalations produced no response.

Transfer reversal — unwinding a completed fraudulent transfer — is harder. The domain may have moved to a privacy proxy, changed hands multiple times, or been pushed to a registrar in a jurisdiction that does not respond to foreign court orders. The litigation strategy in those cases requires identifying each link in the transfer chain through RDDS/WHOIS history, subpoena, and formal discovery, then seeking an order against the last-known holder and the registry simultaneously. This is fact-intensive and time-consuming. It is also, in our experience, one of the situations where acting within the first 48 hours — locking the name or placing a hold before it moves again — is worth more than the most carefully crafted legal argument filed a week later.

To plan recovery of a stolen or hijacked .global domain, or to weigh UDRP against a court action for your case, email info@cognomenlaw.com.

What evidence decides the outcome of a court action for a .global domain?

Court actions for cybersquatting and domain theft succeed or fail on documentary evidence assembled before the first filing. The categories below define what a court needs and what a defendant will contest.

Trademark rights. Unlike the UDRP, where panels accept unregistered rights in some circumstances, most anticybersquatting statutes require a registered trademark or a close equivalent. The registration date, the goods and services covered, and the geographic scope all matter. If the .global domain was registered after the trademark, that sequence supports the claim. If the trademark postdates the domain, the analysis shifts entirely — and may point back to a claim of legitimate interest by the registrant.

Evidence of bad faith. The factors considered by courts in anticybersquatting actions broadly parallel the Paragraph 4(b) bad-faith factors under the UDRP: an offer to sell the domain at an above-cost price, a pattern of registering others' marks, deliberate use to attract users by creating confusion, and the absence of any prior use of the name in commerce by the registrant. Each factor requires documentary proof — screenshots, archived web pages, demand correspondence, WHOIS history, and any communications in which the registrant acknowledges the trademark owner's rights.

Evidence of account compromise or unauthorized transfer. For theft claims, the evidentiary record is different. Account access logs, email correspondence from the registrar, timestamps of the unauthorized transfer, and any phishing messages received by the legitimate registrant are the core documents. If the compromise involved credential theft — a spear-phishing attack on the registrant's email account — those forensic records must be preserved immediately. Delay destroys them.

Harm documentation. Courts awarding damages need evidence of actual harm: lost sales, customer confusion, diverted payments, brand rehabilitation costs. Statutory damages in US anticybersquatting litigation can be significant without proving specific loss, but actual damages require a damages analysis. We work with clients early to identify and preserve this evidence, because most brand owners do not think to document diversion losses until they are asked to prove them.

In a separate matter (a .global impersonation campaign, late 2024), the registrant had used the domain to send fraudulent invoices to the brand owner's customers. The documentary chain — from the first fraudulent email to the last wire-transfer instruction — became the evidentiary backbone of a damages claim that far exceeded what any UDRP transfer would have addressed.

Choosing the right court and governing law for a .global dispute

The right venue depends on where the registrar is located, where the registrant is identifiable, and where the trademark owner can establish jurisdiction. This is the cross-border dimension of any .global court action, and it is where the choice of route has the largest practical consequences.

US anticybersquatting litigation is available when the registrar is US-based or when the registrant has a US connection — including, in some cases, an in rem action against the domain name itself, which is available in the judicial district where the registry or registrar is located. An in rem action can proceed even when the registrant is anonymous or offshore, because it is the domain — not the person — that is the defendant. This is a powerful tool when WHOIS privacy makes personal jurisdiction over the registrant unavailable.

If the registrar is not US-based, the governing national procedure applies. For a .global domain held at a European registrar, litigation in the relevant European jurisdiction — whether Germany, France, or another member state — is the path, relying on national trademark law and the EU's own anticybersquatting doctrine. We engage local litigation counsel in the relevant jurisdiction for those matters; the strategy is coordinated from COGNOMEN, and the local filing is handled by counsel admitted in that court.

A third option that sits between UDRP arbitration and full litigation is worth considering for .global names: where the harm is ongoing and damages are sought, some brand owners file both a UDRP complaint and a court action simultaneously. The UDRP Panel will normally suspend the UDRP proceeding if a court action is pending, so the sequencing matters. Filing the UDRP first to obtain a quick transfer, then pursuing a court damages claim against the now-former registrant, is a common sequence when the bad-faith case is strong and the financial harm is documented.

What a court action cannot do — and why that shapes strategy

Understanding the limits of litigation is as important as understanding its advantages. Court proceedings for a .global domain take significantly longer than a UDRP complaint. The UDRP at WIPO typically concludes in about two months; court proceedings — even in well-resourced jurisdictions — run to months or years for a final decision. An injunction can issue quickly, but final judgment takes time.

Cost is the second constraint. Legal fees for court anticybersquatting actions are substantially higher than UDRP legal fees and are billed hourly in most jurisdictions, in addition to court filing fees. For a dispute over a single .global domain with no ongoing harm and a weak damages case, the cost-benefit calculation may favor the UDRP despite its limitations. A realistic pre-filing assessment — what the domain is worth, what harm has actually occurred, and whether the evidence of bad faith is strong — should precede any decision to litigate.

The third limit is enforcement. A court order against an anonymous registrant in an uncooperative jurisdiction is difficult to enforce. The in rem route sidesteps the personal-jurisdiction problem, but it still requires the registry operator to comply with the order. Most major registries operating in ICANN-compliant jurisdictions will comply with a final court order from a competent court. But the process is not automatic, and confirmation of enforcement is a step that must be tracked.

A common objection at this stage is that the UDRP is faster and cheaper, so litigation is rarely worth pursuing. That objection is correct as a generalization but wrong as a case-specific conclusion. Where harm is ongoing, damages are provable, the registrant is identifiable, and the trademark record is strong, a court action produces a result the UDRP structurally cannot. The analysis is always fact-specific.

Related at COGNOMEN

• Court action and domain theft recovery across all zones and forums
• Reversing an unauthorized domain transfer: registrar escalation and court action
• ccTLD mediation and dispute procedure: how national rules compare to the UDRP

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.