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

A registrant holds a .net that matches your brand exactly, has ignored every outreach, and is routing traffic to a competing storefront. The UDRP is available for .net – but panels have repeatedly declined to award monetary damages, and a transfer order alone may not solve your problem when the registrant has already caused measurable harm. Sometimes the case calls for court.

To bring a court action when UDRP cannot reach a .net domain, a brand owner typically pursues US anticybersquatting litigation or an equivalent national court route where the registrant is located or where the harm occurred. The UDRP at WIPO – where the filing fee starts at USD 1,500 for a single-member panel – delivers only transfer or cancellation, with no monetary damages available. Where harm is financial, the registrant is unidentifiable, or arbitration has already failed, a court action is the route that reaches further.

This page explains the UDRP baseline for .net, when court replaces or supplements arbitration, the evidence that decides both routes, the realistic cost structure, and how to start.

What the UDRP covers for .net – and where it stops

The UDRP governs .net because .net is an ICANN-accredited gTLD, and every accredited registrar is bound by the Policy. A complainant with trademark rights can therefore file a UDRP complaint against any .net registrant at WIPO, the Forum, CAC, or ADNDRC. A standard case is normally decided within about two months. The only remedies available are transfer of the domain to the complainant or cancellation of the registration.

That ceiling matters enormously in practice. The UDRP offers no damages, no injunction against the registrant's broader conduct, no costs award, and no finding that creates preclusive effect in a later court case. It also cannot reach a registrant who has transferred the domain to a third party after notice of the complaint, cannot compel a registrar to reverse an unauthorized transfer in the way a court order can, and cannot force discovery of the person behind a privacy-shielded registration. Those four limitations are the gaps where court action fills in.

Panels under the UDRP apply all three elements of Paragraph 4(a) cumulatively: the domain must be identical or confusingly similar to a mark the complainant holds; the registrant must lack rights or legitimate interests; and the domain must have been registered and used in bad faith. A complainant who cannot satisfy all three — for instance because the registrant registered the .net before the trademark issued, or because the domain has a plausible generic meaning — may lose the UDRP. That loss is not preclusive, but it signals that court is the stronger primary route.

In our practice, we regularly assess .net disputes at the intake stage by asking a direct question: is a transfer without damages good enough, and can we satisfy all three elements on these facts? If the answer to either part is no, we map the court route immediately.

To assess whether UDRP or court is the right route for your .net domain, contact info@cognomenlaw.com.

When does court action outperform UDRP for a .net dispute?

A court action for cybersquatting is warranted – and often superior to UDRP arbitration – in four specific situations.

First, when you need damages. The UDRP cannot award money. US anticybersquatting litigation allows a court to award statutory or actual damages for abusive registration and use of a domain confusingly similar to a distinctive mark. For a brand owner who has documented diverted sales, consumer confusion, or fraud enabled by the .net, the monetary remedy is the point.

Second, when the UDRP has already failed. A panel decision denying transfer is not a final judgment. A court is not bound by the panel's reasoning. If a prior UDRP complaint was denied because the three elements were not all met on the record presented – or because the panel took a conservative view of bad faith – a court action begins fresh, with broader discovery powers and a different evidentiary standard.

Third, when the registrant's identity is shielded. Privacy and proxy registration services mask the underlying registrant in WHOIS/RDDS. A UDRP panel can proceed against the proxy registrant, but a court has subpoena power to compel the registrar or privacy service to disclose the real holder. Once identified, the registrant can be named as a defendant, and the judgment has personal force.

Fourth, when the domain was stolen. Unauthorized transfer – where an account compromise or a fraudulent registrar instruction moved the .net without the owner's consent – is outside the UDRP's design. It is a theft. The correct path is a combination of registrar escalation, domain theft recovery procedures, and, where those fail, a court order compelling the registrar or the current holder to reverse the transfer. We have pursued that combination in a number of .net and other gTLD matters where the UDRP's arbitral limits made it ineffective.

How does registrar-lock and transfer-reversal work in a .net court action?

Registrar mechanics are the operational layer beneath every court action involving a .net domain. Understanding them is essential before filing.

A registrar lock – sometimes called a registrar hold or domain lock – prevents the domain from being transferred to another registrar or registrant without the current registrar's active participation. When a court action is filed, the first practical step is usually to seek an order requiring the current registrar to place or maintain a lock on the domain. Without that order, a bad-faith registrant can transfer the domain to a different registrar or to a nominee holder during litigation, potentially in a jurisdiction with less cooperative enforcement. The lock preserves the status quo.

Transfer reversal is the next step when a domain has already moved. In stolen-domain matters, the chain of title may show one or more unauthorized transfers after account compromise. A court order – or a coordinated registrar escalation under ICANN's Transfer Policy dispute mechanisms – can require the receiving registrar to reverse those transfers. ICANN itself does not adjudicate ownership, but registrars are required to cooperate with valid court orders. Coordinating the legal proceeding with the registrar escalation in real time is what decides whether the domain is recovered or lost permanently.

In a recent matter (a .net domain, spring 2025), we acted for a registrant whose domain had been transferred to a third-party registrar following account compromise. We coordinated a registrar-lock request, documented the account-compromise evidence, and pursued transfer reversal outside arbitration. The domain was recovered in a matter of weeks, not months. That outcome was available only through the court and registrar route – the UDRP has no mechanism to reverse an unauthorized transfer.

If your .net domain has been transferred without authorization, email info@cognomenlaw.com for a focused review of the transfer-reversal route.

What evidence decides a .net court action for cybersquatting?

Evidence is the difference between a court action that moves quickly to a favorable outcome and one that bogs down in contested facts. The following categories are the ones that decide most .net cybersquatting cases.

Trademark rights, clearly established. The complainant must demonstrate rights in a distinctive mark. A registered trademark is strongest. Common-law rights based on use in commerce are recognized but require more evidence – sales figures, advertising spend, market recognition, and the geographic scope of use. The mark must predate the domain registration, or the court must find that the registrant targeted the mark even if the registration came later.

Bad faith at the time of registration and after. Courts look for signals: a pattern of registering multiple marks as domains; an offer to sell the domain to the mark owner at a price reflecting ransom rather than cost; use of the domain to divert traffic, operate a phishing site, or host a competing business; and concealment of identity behind privacy services while engaging in abusive conduct. Each of these maps to a bad-faith factor the court weighs.

Evidence of harm. Diverted sales, customer confusion documented in emails or social media, fraudulent invoices sent from the .net address, brand reputational damage – all are relevant both to liability and to the measure of damages. Courts assess harm concretely, and a party who cannot quantify it will rely on statutory damages where available.

The account-compromise record (theft cases). In stolen-domain matters, the evidence package centers on the chain of custody: original registration records, account logs showing unauthorized access, WHOIS/RDDS change history, and communications from the registrar confirming or denying the legitimacy of the transfer instruction. The more complete and contemporaneous this record, the more readily a court or registrar can act without full evidentiary proceedings.

We regularly advise brand owners who arrive with partial evidence. The strategic question at intake is always which elements are missing and whether discovery in a court action can supply them — or whether a UDRP proceeding first, as a fact-developing exercise, is actually the better sequence.

How does the choice among UDRP, court, and theft recovery work for .net?

The right route depends on the fact pattern and the goal. Three main scenarios describe most .net disputes.

If the .net is held by a cybersquatter who registered it in bad faith, is using it to redirect traffic, and you want it back with no claim for damages, the UDRP at WIPO or the Forum is usually the faster and less costly path. The filing fee at WIPO is USD 1,500 for a single-member panel covering up to five domains, and a decision typically arrives within about two months. Legal fees for a standard UDRP complaint are commonly in the USD 3,000–7,000 range, separate from the filing fee. If the three elements are clearly met, this is the efficient route.

If you also need damages, or if the registrant is using the .net to conduct fraud or cause ongoing financial harm, a US anticybersquatting court action – or a court action in the registrant's jurisdiction – is the right primary route. The procedural timeline is longer and legal fees are substantially higher than UDRP, but the remedies include money and injunctive relief. A court can also compel the registrar to produce the registrant's identity and to comply with a transfer order under threat of contempt.

If the .net was stolen – an unauthorized transfer following account compromise – neither the UDRP nor a cybersquatting court action is the primary tool. The first step is registrar escalation under ICANN's Transfer Policy framework. If that fails or moves too slowly, a court order compelling the registrar is the next layer. Court actions in stolen-domain matters often proceed faster than cybersquatting litigation because the factual record – the account-compromise evidence – is often clear and immediate.

A fourth scenario is a parallel strategy: file the UDRP to lock the domain while the court action is prepared. The UDRP will not stay pending the court case by default, but a complainant can withdraw or suspend the UDRP if the court action is the primary proceeding. We have used both sequenced and parallel approaches in .net matters, depending on the urgency of the domain lock and the strength of the trademark record.

For comparison: a .de dispute cannot use the UDRP at all and goes directly to the German courts, with a DENIC DISPUTE entry to block transfer while litigation proceeds. A .net dispute always has the UDRP available, but that availability does not make it mandatory. The strategic choice is made on facts, not reflex.

What is the realistic cost structure for a .net court action?

Cost transparency is part of how COGNOMEN operates, and we are direct about it: court actions cost more than UDRP proceedings, and the gap is significant.

The WIPO filing fee for a UDRP complaint covering up to five .net domains is USD 1,500 for a single-member panel, or USD 4,000 for a three-member panel. Legal fees for a straightforward single-domain UDRP complaint are commonly in the USD 3,000–7,000 range. These are flat-fee matters for most standard cases.

Court anticybersquatting actions are billed on an hourly basis, not flat fees, and the total cost depends on whether the case is contested, whether discovery is needed, and how many procedural steps the defendant forces. The total legal cost of a contested cybersquatting litigation is substantially higher than the UDRP equivalent. For that reason, court actions are typically reserved for matters where the stakes justify the cost: a high-value brand, documented financial harm, a large damages claim, or a domain that is the operational center of an active fraud.

A UDRP partial refund is available from WIPO if the case is withdrawn or terminated before panel appointment – commonly around USD 1,000 of the USD 1,500 standard fee. That refund can be factored into a parallel-strategy plan where UDRP is filed first to lock the domain, then withdrawn in favor of the court route.

We separate forum filing fees from legal fees in every engagement. We do not bundle them or present an opaque total. When you contact us, we will tell you what the filing fee is, what the legal work is likely to cost, and which route gives you the best outcome at the most appropriate cost for your specific situation.

What are the cross-border considerations when the registrant is outside the US?

A .net domain can be registered by anyone, anywhere. The registrant for your .net may be in the EU, in Asia, or in a jurisdiction with no bilateral enforcement treaty with the country where your trademark is registered. That cross-border dimension shapes both the route and the tactics.

The UDRP is forum-agnostic: the panel applies the Policy regardless of where the registrant is located, and the registrar implements any transfer order regardless of the registrant's objection. That is the primary advantage of UDRP for a .net dispute: it bypasses national jurisdiction entirely. The registrant cannot resist a panel decision by arguing that the panel has no personal jurisdiction over them.

A court action, by contrast, requires a jurisdictional basis – typically the defendant's location, the plaintiff's location, or a statutory hook such as the registrar's location or the domain's registry operator's location. US anticybersquatting legislation creates a specific in rem jurisdiction over the domain itself in the judicial district where the registrar or registry is located. That in rem route is particularly useful when the registrant is anonymous or located in a jurisdiction where personal-jurisdiction service would be difficult. The in rem action targets the domain, not the person.

Where the registrant is identifiable and located abroad, local litigation counsel in the relevant jurisdiction may be needed alongside or instead of a US court action. We coordinate that work and provide the strategic direction, working with local litigation counsel on the ground in the relevant jurisdiction. The choice among UDRP, US court in rem, and foreign-court action is made at the outset of the matter, based on where the evidence is, where enforcement is most reliable, and how quickly you need the domain locked.

One practical note: the UDRP allows a complaint to cover multiple domains in one filing if the same registrant holds them all. If the registrant has registered multiple .net variations of your mark, a single UDRP filing reaches all of them. A court action would typically address the specific .net at issue, with additional domains added to the case by amendment if they surface later.

Related at COGNOMEN

• Court recovery and anticybersquatting litigation across all zones and forums
• FAQ: recovering a hijacked domain when national procedures apply
• National ccTLD dispute procedures and cross-border enforcement strategy

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.