How to recover a .net domain through a UDRP complaint

A registrant you have never dealt with holds the .net version of your brand. It points at a parked page, a competitor's site, or a pay-per-click farm. You want it transferred. The UDRP – the Uniform Domain Name Dispute Resolution Policy – is the fastest, least expensive route available for .net domains, and in our practice it is the starting point for almost every recovery mandate we receive.

To recover a .net domain through a UDRP complaint you must satisfy all three elements of Paragraph 4(a): the domain is identical or confusingly similar to a trademark you hold; the registrant has no rights or legitimate interests in the name; and the domain was registered and is being used in bad faith. A standard case closes in roughly two months, the WIPO filing fee starts at USD 1,500 for a single-member panel, and the only available remedies are transfer or cancellation.

This page sets out each element, the evidence that decides cases, the timeline, the choice of forum, and what happens at the registrar once a transfer order issues.

Why the UDRP applies to .net domains

The UDRP applies to .net because every ICANN-accredited registrar sponsoring .net registrations is contractually bound to it. That binding is the UDRP's foundation: it is not a court rule and it is not a statute, but it is a mandatory condition every registrant accepts at the time of registration. When you file a UDRP complaint targeting a .net domain, the registrar is obliged to implement any transfer or cancellation order a panel issues.

.net sits alongside .com and .org as one of the original generic top-level domains. It carries no nationality restriction, no industry eligibility requirement, and no registration policy that limits who can hold it. That openness is an advantage for brand owners: a complainant in any jurisdiction, holding a trademark in any country, may bring a UDRP complaint against a .net registrant anywhere in the world. The only gatekeeping is the three-element test.

For the narrow set of ccTLDs that have adopted the UDRP by their own agreement, the same policy applies. .net, however, needs no such secondary adoption: it is a generic TLD and the UDRP has governed it since 1999. Any registrar offering .net registrations administers the UDRP as a condition of their ICANN accreditation. There is no parallel national procedure to exhaust first and no territorial eligibility requirement to satisfy before filing.

The three UDRP elements for a .net recovery

Proving all three elements of Paragraph 4(a) is a necessary and sufficient condition for a transfer order. Panels evaluate each element separately. A strong showing on two elements does not compensate for a weak showing on the third. We build every complaint around each element independently, because a gap in any one of them terminates the case regardless of how compelling the other two appear.

Element 1 – Identical or confusingly similar

This element is largely mechanical. The panel compares the domain – stripping the .net suffix, which is ignored as a technical necessity – against the complainant's trademark. If the domain is the mark, or the mark with a generic addition (a descriptor, a geographic term, a misspelling), panels routinely find confusing similarity. Trademark registration is the cleanest proof; an unregistered mark supported by evidence of acquired distinctiveness can also satisfy the element, though it adds a factual burden.

Element 2 – No rights or legitimate interests

The complainant does not have to prove a negative absolutely. Making a prima facie showing – the registrant is not a licensee, has no authorization, and is not commonly known by the domain name – shifts the burden to the respondent to come forward with evidence of a right or legitimate interest. Paragraph 4(c) sets out the safe harbors: a bona fide offering of goods or services made before any notice of the dispute; being commonly known by the name; or legitimate noncommercial or fair use without intent to mislead. A registrant who can document any of those with credible evidence has a real defense. A registrant who defaults or relies only on assertion tends to lose on this element.

Element 3 – Registered and used in bad faith

This is where most cases are won or lost. Both limbs must be met: the registration must have been made in bad faith and the domain must be being used in bad faith. Paragraph 4(b) lists non-exhaustive indicators: registering to sell to the mark owner at a supra-value price; preventing the mark owner from reflecting the mark in the corresponding domain; disrupting a competitor's business; or attracting users for commercial gain by creating a likelihood of confusion. Passive holding – parking the domain without active content – is not automatically a free pass. Panels have consistently held that passive holding can constitute bad faith use when combined with other circumstances: the mark is highly distinctive, the registrant cannot plausibly claim innocent adoption, and there is no plausible good-faith use for the name.

If you are ready to assess whether the three elements are met for your .net domain, reach us at info@cognomenlaw.com.

What evidence decides a .net UDRP case?

Evidence is not filed in the same volume as in civil litigation, but it carries the same weight. A UDRP panel reads a complaint, an optional response, and the documents attached to each. There is no cross-examination, no discovery, and no oral hearing. The record you file is the record that decides the case.

For element one, the complainant should attach trademark registration certificates or, for unregistered marks, dated business records establishing continuous use and public recognition of the mark before the domain was registered. For element two, WHOIS records showing the registration date relative to the mark's first use are useful context; a screenshot showing the current page content (or lack of content) is standard evidence. For element three, the most persuasive documents are: the WHOIS registration date matched against the mark's priority date, screenshots of the domain's live use or parking page, any demand from the registrant to purchase the domain, evidence that the registrant has previously held other domains that targeted brands, and correspondence. A registrant who reached out to demand payment after you contacted them has, in most cases, handed you element three.

In a recent matter – a .net typosquat, spring 2025 – we assembled a complaint against a registrant who had parked a domain incorporating a well-known retail brand and then sent an unsolicited email quoting a five-figure sale price. The panel found bad faith on that correspondence alone, alongside the parking page monetizing the brand's traffic. The domain transferred in approximately eight weeks from filing.

What undermines a complaint? Weak trademark rights, a delay of years between the mark's registration and the UDRP filing without explanation, a domain registered before the mark existed, or evidence that the registrant is a legitimate dealer or reseller of the complainant's goods. None of these are necessarily fatal, but each requires a direct answer in the complaint. Panels are not advocates; they do not fill gaps for the complainant.

How long does a UDRP complaint take for a .net domain?

A standard .net UDRP case runs approximately two months from filing to registrar implementation. That timeline is set by the procedural rules, not by the parties. The registrant has 20 days to file a response after the case formally commences. After the response window closes, the provider appoints a panelist. The panelist then issues a decision, and the registrar implements any transfer order after a short implementation window unless the losing party files a court action in the registrant's jurisdiction to stay the transfer.

Where time is the priority, WIPO offers an expedited procedure that aims to deliver a single-panel decision within roughly one month. That option is available for cases covering up to five domains in a single complaint. If you are dealing with a cluster of .net registrations by the same registrant, a single complaint covering all of them is procedurally available and efficient – provided the registrant is verified as the same holder across each name.

A three-member panel adds cost and can add time. We generally recommend a three-member panel only where the case is genuinely close on the facts, where the respondent is sophisticated and likely to seek a three-member bench themselves, or where the outcome will have significant precedent value across a portfolio. In most clear-cut .net recovery cases, a single-member panel is adequate and faster.

Choosing the right forum: WIPO, the Forum, or another provider?

Four providers are accredited by ICANN to hear UDRP complaints: WIPO, the Forum (formerly the National Arbitration Forum), the Czech Arbitration Court (CAC), and the ADNDRC. The complainant selects the provider at filing. The respondent cannot override that choice.

WIPO and the Forum together account for roughly 97% of all UDRP proceedings. WIPO is the most widely used, with a deep institutional record and a published jurisprudential overview that allows us to predict with reasonable confidence how a given fact pattern will be decided. WIPO's filing fee starts at USD 1,500 for one to five domains before a single-member panel. The Forum's filing fees begin around USD 1,300 for one to two domains. CAC offers the lowest entry point, beginning around USD 500–800, but it is the least used provider.

For most .net recovery matters, WIPO is our default recommendation. Its panel pool is large and international, its published decisions give the complainant clear guidance on which arguments succeed, and its institutional standing is recognized by every major registrar. For a respondent-heavy case where you anticipate a contested response and want the widest panel pool, WIPO's three-member option at USD 4,000 covers that need. If the Forum's lower entry fee is a material factor and the fact pattern is clean, the Forum is a sound alternative. CAC can be appropriate for lower-value disputes where budget is the controlling constraint.

What about filing in court instead? A UDRP complaint and a court action are not mutually exclusive, but they serve different purposes. The UDRP delivers only transfer or cancellation; it awards no damages and no costs. If you need damages – because the registrant diverted your customers or defrauded your supply chain – US anticybersquatting litigation in federal court is the path to monetary relief. Court is slower and substantially more expensive, but it can reach money that the UDRP cannot. We regularly advise complainants at this fork: where only the domain matters, UDRP is usually the right first step. Where damages matter, or where the registrant is not subject to UDRP's arbitral mechanism for some procedural reason, court action with local litigation counsel in the relevant jurisdiction is the appropriate parallel route.

To weigh UDRP against a court action for your .net domain, email info@cognomenlaw.com.

What happens at the registrar after a UDRP transfer order?

A panel decision ordering transfer does not move the domain automatically. The registrar implements the order after a mandatory waiting period. During that window, the losing registrant may file a court action in the jurisdiction specified in the domain's registration agreement to block implementation. In practice, that step is rare. Most registrants who lose a UDRP case do not mount a court challenge; the domain transfers within days of the window closing.

Once the transfer order is implemented, the domain moves into the complainant's control. The registrar will typically require the complainant to have an account with them, or will coordinate a push transfer to the complainant's preferred registrar. We manage that coordination as part of our service, ensuring that the transfer does not stall at the administrative stage after the legal work is done.

One scenario worth flagging: if the losing registrant threatens court proceedings to delay implementation, the complainant should not assume the threat is idle. A small percentage of respondents do pursue post-UDRP court action, and a panelist's finding of bad faith does not automatically become a court judgment. The strength of the UDRP record – the quality of the evidence filed and the breadth of the bad-faith analysis – is the best insulation against a successful court reversal.

Respondent-side angle: what if you received the complaint?

Not every UDRP complaint against a .net registrant is legitimate. Brand owners occasionally file against registrants who have a genuine right to the name – a legitimate dealer, a person who shares the trademarked surname, a domain investor who registered the name before the mark existed. The 20-day response window is tight, and a default almost always results in a transfer. Acting early is the only option.

In our practice, we regularly advise registrants who face a complaint they believe is abusive. The defense strategy turns on documenting the legitimate interest under Paragraph 4(c), and where the complaint is brought in bad faith to deprive a legitimate registrant of their name, we seek a finding of Reverse Domain Name Hijacking (RDNH). An RDNH finding carries no monetary penalty, but it is a reputational consequence that deters future abusive filings. We have successfully defended .net registrants against complaints that were filed without credible evidence of bad faith – including a matter in autumn 2024 where a complainant asserted a trademark registered after the domain was acquired, a fact the complaint omitted but the WHOIS record made plain.

The myth we encounter most often is that .net registrants have no defense because they are "just parked" – that a parked domain automatically signals bad faith. That is not accurate. Parking a domain can be legitimate commercial behavior, and panels distinguish between a registrant who parks opportunistically after targeting a known brand and one who holds a name for years, generating generic pay-per-click revenue, and then receives a complaint from a late-arriving trademark owner. If you registered your .net before the complainant's mark existed, your position is substantially stronger than the complaint may suggest.

Received a UDRP complaint on your .net domain? The 20-day response window starts from the date of formal commencement – not the date you first see the complaint. Contact info@cognomenlaw.com immediately.

Cost structure: filing fee versus legal fee for a .net UDRP

Two costs apply in every UDRP proceeding: the forum's filing fee, paid by the complainant, and legal fees for preparing and filing the complaint (or the response). These are entirely separate and should be budgeted separately.

The WIPO filing fee for a .net complaint covering one to five domains before a single-member panel is USD 1,500. A three-member panel at WIPO costs USD 4,000 for the same domain count. If the complainant requests a single panelist but the respondent requests a three-member bench, the parties generally split the higher three-member fee – typically USD 2,000 each. WIPO offers a partial refund if the complaint is withdrawn or terminated before panel appointment; this is commonly around USD 1,000 of the initial USD 1,500.

Legal fees for preparing a UDRP complaint on a single, relatively straightforward .net domain typically fall in the USD 3,000–7,000 range, billed by the engagement, not the hour. The fee reflects the evidence assembly, the complaint drafting, and the forum submission – not ongoing litigation in a court sense. Respondent defense runs in a comparable range. COGNOMEN publishes this range openly; the domain-disputes market often withholds fee guidance, and we think that is a disservice to clients who need to make a cost-benefit decision before filing.

The full cost of a single-panel UDRP complaint at WIPO, including both the filing fee and legal fees, typically falls in the USD 4,500–8,500 range. That compares favorably to virtually any alternative: a court action, even a successful one resolved quickly, will cost multiples of that figure. Where the domain has commercial value that exceeds that range – and most contested .net domains do – the UDRP is the rational economic choice.

A micro-case illustrates the point. In early 2025 we recovered a .net domain for a software company whose brand had been registered as a .net by a serial filer holding approximately a dozen similarly structured domain names. The complaint covered one domain; the filing fee was USD 1,500; the entire matter resolved by transfer in under ten weeks. The company's legal spend was a fraction of the five-figure renewal-and-transfer price the registrant had quoted in an unsolicited message.

Related at COGNOMEN

• UDRP domain recovery – the full service across gTLDs and ccTLDs
• Targeting a serial cybersquatter – strategy for portfolio-level UDRP complaints
• Recovering a hijacked or stolen domain through court and registrar escalation

Author: Cordelia Roe — UDRP complainant practice & gTLD recovery; domain transactions and brand protection. 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.