Assess my case

Step-by-step: bring a court action when UDRP cannot reach a .info domain

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

A brand owner discovers that a third party has registered its exact trading name as a .info domain, redirected it to a competitor's site, and is now demanding a six-figure transfer fee. The UDRP is available for .info – it is a gTLD under ICANN's standard accreditation framework – yet there are specific situations where arbitration simply cannot deliver what the brand owner needs. Damages are unavailable under the UDRP. Account-compromise cases, injunctive relief against hosting providers, and fact patterns requiring witness testimony can all push a dispute from the panel room to the courtroom.

When you need to bring a court action when the UDRP cannot reach a .info domain, the governing path is US anticybersquatting litigation or an equivalent national action, depending on where the registrant and registrar operate. The UDRP's only remedies are transfer or cancellation – no money, no injunction, no disclosure of documents. A court action can reach all three. The trade-off is cost and time: court proceedings run substantially longer and at higher expense than a UDRP filing, whose standard process resolves in about two months at a WIPO filing fee starting at USD 1,500.

This guide walks the decision to go to court, the step-by-step mechanics, the evidence that decides each stage, and the traps that wait inside every step.

When does the UDRP fail to reach a .info dispute?

The UDRP applies to .info in the same way it applies to .com: any accredited registrar for a gTLD domain must comply with the Policy. That means arbitration is almost always technically available. The real question is not availability – it is adequacy. Three situations arise in our practice where a court action is the necessary route.

First: the registrant wants money. A complainant who prevails under the UDRP gets a domain transfer or cancellation. Nothing else. If the infringement has caused measurable financial harm – diverted customer orders, spoofed invoices, reputational damage attracting a quantifiable loss – only a court can award compensation. The UDRP panel has no power to do so.

Second: the domain was stolen rather than registered in bad faith. Account-compromise cases – where a registrant's credentials were hijacked and the domain transferred without authorization – do not fit neatly inside the UDRP's Paragraph 4(a) test, which presupposes a willing registration by the current holder. A court action, combined with registrar-lock escalation and a transfer-reversal demand, addresses the unauthorized transfer directly. We regularly advise registrants in exactly this situation: the registrar's internal dispute process stalls, and a court order is the instrument that forces a reversal.

Third: the brand owner needs emergency relief before a decision can issue. A UDRP panel issues no injunction. If the .info domain is actively operating a phishing site or a fraudulent shop, a court's temporary restraining order can shut it down in days, not months.

If you are weighing whether a court action is the right move for your .info dispute, the first step is a clear-eyed read of which remedy you actually need. Email info@cognomenlaw.com to assess the three UDRP elements and the grounds for a court filing in parallel.

Step 1 – Exhaust or preserve the UDRP record before filing in court

The first concrete step is deciding whether to run UDRP and litigation in parallel, in sequence, or to skip arbitration entirely. That choice has tactical consequences that are easy to get wrong.

If a UDRP complaint has already been filed, most courts treat the panel record as relevant background. A prior UDRP loss is not a bar to court action – the UDRP is contractual, not judicial – but a panel finding against you on bad faith will be cited by the other side. Conversely, a prior UDRP win that the registrar has not yet implemented can be enforced through a court order directed at the registrar.

If no UDRP has been filed, ask whether preserving the option matters. Filing in court first does not forfeit the UDRP; the two procedures are independent. However, the evidence standard differs. A court requires discovery, pleadings, and live witnesses. A UDRP panel decides on the documents. Running both in parallel burns resources on two fronts.

The trap in Step 1 is assuming the UDRP result governs the court. It does not. Panels have consistently held that a UDRP decision is a contractual remedy between the registrant and registrar, not a judicial determination. Courts are not bound by it in either direction.

Step 2 – Identify the correct jurisdiction and cause of action

For a .info domain, jurisdiction turns on where the registrant is located, where the registrar is incorporated, and where the brand owner suffered harm. These three anchors often point to different countries. Getting jurisdiction wrong is fatal – not just a delay.

In the United States, US anticybersquatting litigation provides a dedicated cause of action for domain names. It permits a court to order transfer, cancellation, or damages. For a registrant who cannot be located or has concealed their identity behind privacy service, the statute allows an in rem action against the domain name itself, which is deemed to be located where the registrar or registry is based. For .info, the registry operator has historically maintained US infrastructure, making a US in rem filing a viable option even when the registrant is outside US reach.

Outside the United States, national trademark and unfair competition laws provide equivalent routes. A brand owner with EU rights may file in a member-state court with jurisdiction over the registrant or over the harm caused in that territory. We work with local litigation counsel in the relevant jurisdiction for any matter requiring foreign court process.

The trap in Step 2 is choosing the forum for speed rather than for power. The fastest court is not always the court with jurisdiction over the registrar. A registrar that ignores a foreign court order because the order is unenforceable against it produces the worst outcome: cost spent, domain unmoved.

Step 3 – Obtain and preserve evidence of cybersquatting or compromise

Evidence in a court action must meet a higher threshold than in UDRP arbitration. A panel decides on documentary submissions; a court may require authentication, witness declarations, and chain-of-custody records. Building that record starts at the moment the problem is identified, not at the moment of filing.

For a classic cybersquatting case – bad-faith registration of a .info domain identical or confusingly similar to a mark – the evidence checklist covers:

For a domain-theft or account-compromise case, the additional evidence layer is critical. You need: authentication logs from the registrar showing unauthorized access; email headers from any spoofed communication used to initiate the transfer; and a timeline of the legitimate registrant's actions, including any prior WHOIS record confirming original ownership. We have defended and prosecuted account-compromise cases where a single authentication log entry proved – or disproved – the entire narrative.

The trap in Step 3 is over-reliance on automated archive services. Courts have admitted and excluded web-archive captures depending on authentication method and jurisdiction. Counsel for the other side will challenge anything that was not captured and notarized at the time. Contemporaneous, authenticated captures are worth far more than a screenshot printed the day before filing.

How does registrar-lock escalation fit into a court strategy for .info domains?

Registrar-lock escalation is a parallel track, not a substitute for the court action, and it can run from the first day of the dispute. A registrar lock – sometimes called a "registrar hold" or a transfer-lock flag – prevents the domain from being transferred away, deleted, or modified while the dispute is live. Obtaining that lock is often the single most time-sensitive act in the whole process.

For .info domains, the standard registrar-escalation path runs through the accredited registrar of record. Most registrars have an internal dispute or abuse team. The first contact is a formal legal notice setting out the claimed rights, identifying the domain, and demanding a transfer lock pending resolution of proceedings. Some registrars respond within days; others require a court order before they will act.

If the registrar is unresponsive, a court's temporary restraining order or preliminary injunction directed at the registrar is the enforcement tool. That order instructs the registrar not to allow any transfer, deletion, or modification of the domain pending the outcome of the case. Importantly, ICANN's registrar accreditation agreements impose obligations on registrars to comply with court orders from the relevant jurisdiction – which gives a US court order particular reach over US-based registrars holding .info domains.

The trap in this step is waiting for the registrar to act voluntarily before filing in court. Registrars are neutral; they follow instructions from courts, not from brand owners. A registration can be deleted rather than transferred if a registrant acts preemptively, which means the brand owner loses the name entirely rather than recovering it. Move for a lock at the same time as, or before, the formal court filing.

For details on the mechanics of registrar-lock escalation in the UK context, see our guide to registrar lock escalation and UK domain recovery procedures.

Step 4 – Draft and file the complaint with the court

A court complaint in a .info cybersquatting action must plead: the claimant's trademark rights; the domain's identity with or confusing similarity to those rights; the registrant's bad faith or, in a theft case, the unauthorized nature of the transfer; and the specific remedy sought – transfer, cancellation, damages, or a combination.

The complaint must also identify the defendant correctly. Where the registrant used privacy or proxy service, the initial filing may name the registrar and the privacy service as parties, or proceed in rem. The privacy service's obligation to disclose the underlying registrant's identity varies by registrar policy and jurisdiction. A subpoena or court order directing disclosure is frequently required as an early step in the litigation.

An in rem complaint, available in the US where the registrant is unknown or unreachable, names the domain name itself as the defendant and requires only notice to the registrar and the last known WHOIS contact. This is a practical option for .info domains held behind privacy layers, particularly where the registrant is outside the US. The remedy available in rem is limited to transfer or cancellation – monetary damages require an in personam defendant.

The trap in Step 4 is pleading only one theory of recovery. A complaint that relies solely on the narrow cybersquatting cause of action may fail if the registrant demonstrates prior legitimate use – even marginal – of the string. Pleading trademark infringement, unfair competition, and the cybersquatting theory in parallel provides multiple bases for relief and makes it harder for the registrant to prevail on a single-argument defense.

Step 5 – Pursue interim relief and manage the parallel UDRP track

Once the court complaint is filed, the immediate objective is interim relief: a temporary restraining order directing the registrar not to transfer, delete, or alter the domain. Courts in jurisdictions with strong trademark enforcement can issue a TRO on an ex parte basis within days, particularly where the risk of irreparable harm – an active phishing site, diversion of customer traffic – is clearly documented.

In a summer 2025 matter involving a .info domain used in a spoofing campaign against a financial services company, we assisted US litigation counsel in documenting the harm evidence that supported a TRO application. The registrar locked the domain within approximately one week of the order. That alone stopped the active harm while the merits proceeded.

On the parallel UDRP track: if the court action has been filed, the UDRP is not automatically stayed. However, panels may exercise discretion to suspend a UDRP proceeding where litigation is pending over the same domain. A complainant who wants both to run simultaneously should be aware that a court judgment may moot the UDRP entirely – or may be delayed while the panel delivers its decision. The sequencing decision should be made deliberately, with a view to which forum will deliver the first enforceable result.

The trap in Step 5 is filing for a TRO with insufficient harm evidence. Courts require more than a statement that the domain infringes a trademark. They require evidence of actual or imminent irreparable harm – customer confusion, financial loss, ongoing fraudulent use – supported by declarations, analytics data, and ideally third-party corroboration. A TRO denied at the first application can prejudice the preliminary injunction hearing that follows.

If a prior UDRP filing or a registrar escalation has stalled without result, a reassessment of the court route can identify what element was missed. Email info@cognomenlaw.com to review the record and map the next step.

What evidence decides the outcome?

Court outcomes in domain cybersquatting cases turn on the quality of the bad-faith evidence far more than the strength of the trademark itself. A registered trademark gives you the threshold – a right – but panels and courts alike focus on what the registrant's conduct reveals about intent.

Evidence that has consistently supported findings of bad faith in cybersquatting actions includes: a demand for a sum substantially in excess of the registrant's out-of-pocket costs; a pattern of similar registrations across multiple brands; use of the domain to host competing or counterfeit goods; activation of the domain after notice of the brand owner's rights; and WHOIS records showing registration on the exact date of, or immediately after, a major brand announcement or trademark filing.

In contrast, evidence that has undermined claims includes: the registrant's prior use of the string in a business unrelated to the complainant; registration substantially predating the complainant's trademark rights; and evidence that the registrant attempted in good faith to resolve the conflict before being sued.

For a domain-theft or account-compromise claim, the decisive evidence is the authentication record showing unauthorized access to the registrar account. Registrars maintain access logs. Those logs are obtainable through discovery in court proceedings – they are not available in a UDRP. That single fact is often the reason to choose court over panel: the evidence needed to prove theft is locked behind a discovery subpoena, and only a court can issue one.

Consider the decision route this way. If the domain is a .info, the registrant is located in the US, the harm is ongoing and quantifiable, and you need either damages or documented proof of unauthorized access: court is the route. If the same domain presents a straightforward bad-faith registration with clear trademark rights and no damages claim: UDRP at WIPO or the Forum delivers the result in roughly two months at substantially lower cost. If you need the domain stopped today and cannot wait for either: a TRO application with a concurrent registrar-lock demand is the fastest path, with the court filing as the anchor. For further background on the full spectrum of court recovery routes, see our court action and domain theft recovery service.

How does a .info court action compare to a UDRP filing?

The comparison matters practically. A UDRP proceeding at WIPO carries a filing fee starting at USD 1,500 for a single-member panel and resolves in about two months. Legal fees for a straightforward single-domain complaint typically fall in the USD 3,000 – USD 7,000 range, separate from the filing fee. The only remedies are transfer or cancellation.

A court action – whether US anticybersquatting litigation or an equivalent national proceeding – costs substantially more. Legal fees are hourly and case-dependent; realistic estimates for a contested cybersquatting action run well into five figures and higher for a fully litigated case. Timeline extends to months or years if the registrant defends vigorously. The upside is the full range of remedies: transfer, cancellation, damages, injunctive relief, and – in the US – attorneys' fee awards in exceptional cases.

Where does the URS sit? For new-gTLD domains, the Uniform Rapid Suspension procedure offers a lower-cost path to suspension – not transfer – at a higher evidentiary standard ("clear and convincing"). The .info zone, being an original gTLD rather than a new-gTLD round domain, is not typically subject to the URS. Confirm the current applicability with counsel before filing.

The realistic decision matrix looks like this: if you need transfer only and bad faith is clear, UDRP is faster and cheaper. If you need money, or proof of theft, or emergency injunctive relief, or the registrant is a judgment-worthy defendant: court is the only route that reaches those remedies. If your .info domain dispute also touches a parallel .uk or .eu registration, Nominet's DRS and EURid's ADR.eu procedure each run on their own tracks – the court action for the .info does not resolve those ccTLD registrations. We address the multi-zone problem in our analysis of three-member panel strategy in complex domain disputes.

Related at COGNOMEN

Related at COGNOMEN

Frequently asked questions

How do I start to bring a court action when UDRP cannot reach a .info domain?

Begin by confirming which remedy you actually need: transfer only, or transfer plus damages, injunctive relief, or documentary discovery. If transfer alone will suffice and bad faith is clear, the UDRP remains the faster route. If you need more, identify the jurisdiction based on the registrant's location and the registrar's incorporation, obtain a registrar lock through a formal legal notice, preserve all WHOIS and use evidence with authenticated captures, and instruct litigation counsel to file the complaint and, where appropriate, apply for a temporary restraining order. The court route and a UDRP filing can run in parallel; the sequencing choice turns on which forum will deliver the first enforceable result.

What are the realistic outcomes when you bring a court action when UDRP cannot reach a .info domain?

A successful court judgment can order transfer of the .info domain, its cancellation, monetary damages for infringement, a permanent injunction against further misuse, and – in US proceedings where the registrant acted in bad faith – attorneys' fees in exceptional cases. Where a registrant cannot be located, an in rem proceeding limits the remedy to transfer or cancellation. An unsuccessful action, or one where the registrant demonstrates a legitimate pre-existing interest in the string, results in no transfer and the claimant bears its own costs. Outcomes depend entirely on the specific facts, the quality of the evidence, and the jurisdiction's applicable law.

How do fees split if the case escalates?

UDRP fees are fixed and predictable: USD 1,500 to WIPO for a single-member panel on one domain, plus legal fees typically in the USD 3,000 – USD 7,000 range for a straightforward matter. Court proceedings carry no fixed forum fee equivalent, but filing fees, service costs, discovery expenses, and legal fees – billed hourly – can reach well into five figures for a contested case. Where both a UDRP and a court action run concurrently, both fee tracks apply simultaneously. Budget planning should account for the registrant's potential to defend vigorously at every stage, which is the single largest driver of cost escalation in litigation.

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.