Step-by-step: file a UDRP complaint for a .net domain

Step-by-step: file a UDRP complaint for a .net domain. UDRP and ccTLD domain recovery and defense across .net. Email the firm to assess your case.

A registrant you have never heard of holds the .net version of your brand. The domain sits on a parking page loaded with competitor ads, or worse – it forwards to a site designed to confuse your customers. You want it back. The question is whether filing a UDRP complaint is the right move, and exactly what that process requires.

To file a UDRP complaint for a .net domain, you must satisfy all three elements of Paragraph 4(a) of the UDRP: confusing similarity to a mark you hold, the registrant's absence of legitimate interest, and registration and use in bad faith. A standard case runs approximately two months from filing to decision, with the WIPO filing fee starting at USD 1,500 for a single-member panel on up to five domains. The only remedies available are transfer or cancellation of the domain.

This guide walks each step of the filing process, identifies the trap each one conceals, and explains what evidence separates winning complaints from dismissed ones.

Why the UDRP applies to .net domains – and what that means in practice

The UDRP applies to .net because .net is a generic top-level domain administered by an ICANN-accredited registrar, and all such registrars are bound by the Policy as a condition of their accreditation. That makes .net fully subject to the UDRP – there is no separate procedure, no local eligibility requirement, and no need to show a connection to any particular jurisdiction. A brand owner in Tokyo and one in Toronto face exactly the same three-element test.

This is where .net differs sharply from country-code zones. A .de dispute has no UDRP path at all – it travels through the German courts, with a DENIC DISPUTE entry available to block transfer while litigation proceeds. A .uk dispute goes through the Nominet DRS, which applies a different test ("abusive registration," read as "registered or used" abusively, a meaningfully lower bar than the UDRP's cumulative "registered and used in bad faith"). A .eu dispute proceeds through the Czech Arbitration Court's ADR.eu platform under its own rules. If your dispute touches both a .net and one of those zones, you are managing two concurrent proceedings under two different legal standards simultaneously.

For .net, the full UDRP machinery is available: you may file at WIPO, the Forum, the Czech Arbitration Court (CAC), or the ADNDRC. WIPO and the Forum together handle roughly 97% of all UDRP proceedings. In our practice, WIPO is the default choice for .net recovery where the mark has international dimensions, given its panel depth and the persuasive weight of its published jurisprudential overview.

Step 1: Confirm you meet the three UDRP elements before you draft a word

The single biggest trap in a UDRP filing is pressing ahead before the three elements are honestly assessed. A complaint that fails on any one element is dismissed, and a panel that finds the complaint was brought in bad faith to deprive a legitimate registrant will issue a Reverse Domain Name Hijacking (RDNH) finding – a public reputational mark against the complainant and its counsel.

Element one – identical or confusingly similar. You must hold trademark rights, and the disputed domain must be identical or confusingly similar to those rights. "Rights" here includes registered marks and, under the consensus view, unregistered or common-law marks supported by evidence of secondary meaning. The comparison is largely mechanical: panels strip the TLD and punctuation, then compare the remaining string to your mark. The trap is a mark application that has not yet registered – applications do not satisfy Element one in most circumstances, though a pending filing with a priority date predating the domain's registration can carry some weight.

Element two – no rights or legitimate interests. The complainant bears the initial burden, but that burden shifts to the respondent once a prima facie case is made. Panels have consistently held that a respondent who was commonly known by the disputed domain name, or who was making a bona fide offering of goods or services before notice of the dispute, or who was engaged in legitimate noncommercial or fair use, can defeat Element two under the Paragraph 4(c) safe harbors. The trap: generic or dictionary-word domains. A respondent who holds cloudbridge.net and runs a legitimate services site under that name may have a strong Element-two defense regardless of your trademark.

Element three – registered and used in bad faith. "And" is the operative word. Panels apply the test cumulatively: a domain registered in good faith at the time of creation cannot be retroactively rendered bad-faith by later conduct in most circumstances, though bad-faith use has been found to support an inference of bad-faith intent at registration where the mark was clearly established. Paragraph 4(b) lists four non-exhaustive indicators: registration to sell to the mark owner at a profit, registration to disrupt a competitor, attracting users for commercial gain through confusion, and a pattern of abusive registrations. Passive holding – the registrant does nothing with the domain – is not automatically safe; panels have found bad faith in passive holding where the mark was well known and no plausible good-faith use of the domain could be imagined.

If you are weighing whether those three elements are satisfied for your .net domain, reach us at info@cognomenlaw.com for an assessment before you file.

Step 2: Gather the evidence that decides the outcome

Evidence submitted with the complaint is the record. There are no depositions, no discovery requests, and no live hearings under the UDRP. What you file is what the panel sees. That makes the evidence-gathering stage – often underestimated – the most important preparation step.

For Element one, submit your trademark registration certificate, or for an unregistered mark, evidence of continuous commercial use, advertising spend, press coverage, and consumer recognition predating the domain's creation date. Check the domain's creation date via WHOIS/RDDS before you finalize the complaint; a mark that postdates the registration creates a significant Element-three problem.

For Element two, compile evidence that the registrant is not and has never been known by the disputed string. Review the registrant's WHOIS record (as much as is accessible), any content the domain has carried over time (using archival sources), and any prior correspondence. What you want to show is absence: no business name match, no license from you, no legitimate prior use.

For Element three, document the bad-faith conduct specifically. Screenshots of the parking page, copies of any ransom offer from the registrant (particularly powerful: an email quoting a sum "well above out-of-pocket costs"), evidence of a pattern if this registrant holds other abusive domains. Archive your screenshots with metadata intact – date-stamp and URL in the image frame, not just in the file name.

In a recent matter (a .net brand-match squatting case, spring 2025), the difference between success and failure turned on a single archived email in which the registrant quoted a sum representing several multiples of any conceivable registration cost. That email made the Paragraph 4(b)(i) bad-faith indicator self-proving. We assembled the full evidentiary package over two weeks before filing; the case resolved by transfer roughly eight weeks later.

Step 3: Choose the forum and prepare the complaint document

For a .net single-domain complaint, the realistic forum choice is WIPO or the Forum. Both accept complaints electronically and publish their rules and model complaint forms on their respective websites. The WIPO filing fee for a single-member panel on one to five domains is USD 1,500; the Forum's fee begins at approximately USD 1,300 for one to two domains on a single-member panel. The CAC is the lowest-cost entry point, beginning around USD 500–800, but it handles a smaller share of the UDRP caseload and its panel pool is narrower.

The complaint itself must satisfy the formal requirements set by the applicable forum's Supplemental Rules. At a minimum it must identify the disputed domain, the forum where the complaint is filed, the complainant's contact details, the grounds (Element one, two, and three addressed in sequence), the remedies sought (transfer or cancellation), and the mutual jurisdiction submission – the complainant's agreement to submit to the courts of the registrar's principal office or the registrant's domicile if the domain is transferred and the registrant then challenges that transfer in court.

The trap in Step 3 is word limits. WIPO's Supplemental Rules cap the complaint at 5,000 words in the main body. Complainants who attempt to litigate every angle in the complaint itself – pre-empting defenses, over-explaining the trademark history – routinely bump against that limit or produce a document so long that the dispositive arguments are buried. Panels have noted unfavorably when a complaint reads more like a brief for a court action than a focused presentation of the three elements.

If you want a three-member panel rather than a single panelist, you request it in the complaint. The fee rises to USD 4,000 at WIPO for a three-member panel on one to five domains. A three-member panel is worth considering where the domain has high commercial value, where the bad-faith case is not straightforward, or where an RDNH finding against the respondent (and its reputational effect) is part of the goal.

Step 4: File, track the response window, and decide on supplemental submissions

After the complaint is filed and the filing fee paid, the forum conducts a formal review for compliance before formally commencing the proceeding. Once commencement is confirmed, the 20-day response window opens. That deadline is strict. A respondent who misses it is in default – and panels regularly draw adverse inferences from default, particularly on Element two. Default is not, however, automatic transfer; the panel still evaluates the complaint on its merits, and an improperly structured complaint can still be dismissed even against a non-responding registrant.

The complainant's role during the response window is to monitor, not to supplement. Neither WIPO nor the Forum routinely permit supplemental filings as of right; they require a showing that the new material could not reasonably have been included in the complaint and that it responds to genuinely new arguments in the response. Filing supplemental materials without leave, or filing them primarily to rebut anticipated arguments, is a procedural risk that panels do not look on favorably.

If the respondent files a response and requests a three-member panel when the complainant asked for a single panelist, the higher three-member fee applies and the parties generally split the difference. Budget for that possibility if the domain is commercially significant.

WIPO offers an expedited option delivering a decision within approximately one month, available for single-panel cases of up to five domains. If speed is the controlling factor – a product launch, a live brand confusion event – the expedited path is worth considering, though both parties must consent or meet the expedited criteria under WIPO's supplemental rules.

If a response has arrived in your matter and you are uncertain whether to seek leave to file a supplemental submission, email info@cognomenlaw.com before the supplemental window closes.

Step 5: After the decision – what happens when a panel orders transfer

Once the panel issues its decision, there is a 10-business-day waiting period before the registrar implements the order. That period exists to allow the losing registrant to seek court relief in a court of mutual jurisdiction. In practice, court challenges to UDRP decisions are rare; most registrants accept the outcome. After the waiting period, the registrar executes the transfer to the registrant/complainant's account at the registrar of their choice, or cancels the domain, per the decision's terms.

Transfer is not unconditional. The domain is transferred in its current state: with any remaining registration term, any existing privacy service removed, and with any liens or legal holds that may exist under the registrar's terms. Before filing, it is worth checking whether the domain's registration is within the first 60 days (the ICANN transfer lock window applies differently in this context, but it is a factor in post-decision implementation timing). In our practice, we routinely brief clients on what to expect from the registrar in the weeks following a transfer order to avoid administrative delay on the receiving end.

If the panel denies the complaint, the domain stays with the registrant. A denial does not permanently preclude a second filing, but a re-filed complaint on materially the same facts and against the same domain will be dismissed as an abuse of process under the consensus view. A denial on Element three for insufficient bad-faith evidence may, however, leave room for a court action – including US anticybersquatting litigation where damages are available – if the jurisdictional and factual basis supports it.

In a recent matter (a .net denial in late 2024, single-panel decision), the panel found Element one and two satisfied but held the bad-faith evidence fell short. The client elected to pursue a court route with local litigation counsel in the relevant jurisdiction rather than re-file. That path carries substantially higher cost and timeline, but it was the appropriate next step given the commercial value of the domain and the availability of a damages claim.

How does filing a UDRP for .net compare to other zones and other routes?

The right route depends on the zone, the remedy you need, and how urgent the situation is. For a .net domain where the goal is transfer, the UDRP is almost always the starting point: the timeline is fixed at roughly two months, the cost is predictable, and the process is fully online. Compare that to a .com – same process, same cost, no meaningful difference. Both are gTLDs under ICANN accreditation, and the UDRP applies identically.

If the same party also holds a .uk version of your brand, the Nominet DRS runs in parallel but under different rules. The DRS test is "abusive registration" – and critically, it reads "registered or used" abusively, which makes a case that might fail on the UDRP's stricter cumulative standard (registration and use) still viable under the DRS. A free mediation stage comes first; if mediation fails, the expert fee at Nominet is GBP 750 + VAT for a full expert decision. Two proceedings, two fee schedules, two evidence packages – but a coordinated strategy can address both efficiently.

If the .net registrant's conduct is severe – significant commercial damage, fraudulent impersonation, multiple zones – a US anticybersquatting court action may be warranted alongside or instead of the UDRP. That route reaches monetary damages; the UDRP does not. The trade-off is cost: court litigation runs substantially higher than the UDRP's filing-fee-plus-legal-fee structure, and timelines are measured in months to years rather than weeks. We assess that combination with clients where the facts support it and refer court work to local litigation counsel in the relevant jurisdiction.

URS – the Uniform Rapid Suspension system – is not available for .net. URS applies to new gTLDs (.shop, .tech, .online, and similar). If the infringing domain is in one of those zones, URS suspends the domain within days at lower cost, though it does not transfer ownership. The UDRP remains the correct route for transfer in any new-gTLD context as well.

Related at COGNOMEN

• UDRP domain recovery – the full service, from element assessment to registrar implementation
• Case study: recovering a tech-sector domain after a buy-back demand failed
• Court recovery and registrar lock escalation for .org and related zones