Step-by-step: recover multiple .net domains in one UDRP complaint

Step-by-step: recover multiple .net domains in one UDRP complaint. UDRP and ccTLD domain recovery and defense across .net. Email the firm to assess your case.

A brand owner discovers that the same registrant has claimed a dozen .net variations of its trademark – typosquats, hyphenated versions, plural forms – and each one redirects visitors to a competing service or sits parked waiting for a ransom offer. Filing twelve separate complaints is expensive and slow. The UDRP offers a better path: a single complaint covering all the domains, provided the conditions are met.

To recover multiple .net domains in one UDRP complaint, you must satisfy all three elements of Paragraph 4(a) across every domain in the filing, and every domain must be registered to the same registrant. A standard UDRP proceeding runs roughly two months from filing to decision, with the registrant given 20 days to respond once the case commences. The only remedies available are transfer or cancellation – no damages, no costs.

This guide walks each step in sequence, names the trap hidden inside it, and shows where multi-domain .net complaints succeed or fail.

Why does .net fall under the UDRP – and what does that mean for you?

The UDRP applies to all ICANN-accredited registrar gTLDs, and .net is squarely within that group. Every .net registrar is contractually bound to implement a UDRP decision, meaning a successful transfer order is enforced by the registrar without any separate court proceeding. That is the first structural advantage: the mechanism is global, and the registrar acts automatically on a final panel decision.

For multi-domain recovery, the practical implication is significant. You do not need to identify the governing national law, locate courts in three jurisdictions, or rely on registrar cooperation beyond what the contract already compels. You file one complaint before a single approved provider – WIPO, the Forum, CAC, or ADNDRC – and the provider's rules govern the entire proceeding.

WIPO and the Forum together handle roughly 97% of all UDRP proceedings, and each publishes its own supplemental rules. Choosing between them is itself a decision with strategic implications, which this guide addresses in Step 3.

Step 1: Confirm the same-registrant requirement before you do anything else

The single most important threshold question in any multi-domain complaint is whether all the disputed domains are held by the same registrant. The UDRP rules permit one complaint to cover multiple domains only when the registrant is the same holder across all of them. This is not a technicality; panels have dismissed or severed complaints where the registrant names differed, even slightly, because the Policy treats each registrant as a separate respondent.

The trap here is WHOIS privacy and proxy registration. Many registrants list a privacy service rather than their own name. Panels generally look through a privacy shield and assess whether the underlying registrant is the same person or entity. But that assessment happens at the panel stage, not at filing. If you file assuming identity and a panel disagrees, you may face severance – the complaint splits into separate proceedings, each requiring its own fee and panel appointment.

Before filing, gather every available signal of common ownership: identical registrar accounts where discernible, identical name servers, identical content or redirects, identical contact details in historical WHOIS data, and registration dates that cluster in a pattern. Document each one. The stronger that record, the less exposed you are to a severance argument.

If the registrant identity is ambiguous across your .net portfolio, that question should be resolved before any complaint is drafted. For an assessment of the three UDRP elements as they apply to your specific domains, contact info@cognomenlaw.com.

Step 2: Map every domain to all three UDRP elements

Each domain in a multi-domain complaint must independently satisfy all three elements of Paragraph 4(a). Panels do not average the evidence across the portfolio; they test each registration separately, even when the opinion is written as a single decision. A complainant who wins on eight domains and loses on four still loses four – and if those four turn on weak evidence, the loss may affect how the panel reads the stronger ones.

Element 1: Confusing similarity. The domain must be identical or confusingly similar to a trademark in which you hold rights. For .net disputes this is generally the least contested element, because the comparison is between the disputed domain name (minus the TLD suffix) and the trademark. Panels typically set aside the .net extension for this comparison. Typosquats, phonetic equivalents, and brand-plus-generic-term combinations (e.g., "brandnames.net", "buy-brandname.net") almost always satisfy this element if you hold a registered or common-law mark. Document each domain-to-mark comparison in a table: domain → mark → basis for similarity → supporting evidence.

Element 2: No rights or legitimate interests. You bear the initial burden of making a prima facie case that the registrant lacks rights or a legitimate interest. The burden then shifts. Panels look to Paragraph 4(c) safe harbors: was the registrant making a bona fide offering before the dispute arose? Is the registrant commonly known by the name? Is the use legitimately noncommercial? In a multi-domain complaint, where the registrant holds numerous .net variations of a single trademark, a pattern of identical or near-identical registrations is itself strong evidence against a legitimate interest. Each domain still needs an individual analysis, though.

Element 3: Registration and use in bad faith. Both limbs are required cumulatively under the UDRP. Common patterns panels recognize under Paragraph 4(b): registration to sell the domain to the trademark owner at a price exceeding acquisition costs; registration to disrupt a competitor; use to attract users by creating confusion with the mark; a demonstrable pattern of abusive registrations. A multi-domain registrant holding typosquats and brand variations across .net almost always presents at least one of these patterns. The risk is a domain that looks slightly different – one that might be a generic word – where bad faith is harder to establish. Identify that weak link early and consider dropping it from the complaint rather than letting it contaminate the stronger filings.

Step 3: Choose your forum and understand what that decision costs

For a multi-domain .net complaint, WIPO and the Forum are the realistic choices. WIPO charges USD 1,500 for a single-member panel covering 1–5 domains; USD 2,000 for 6–10 domains. The Forum's entry fee begins around USD 1,300 for 1–2 domains, with its own scale for additional domains. CAC is the lowest-cost provider, beginning around USD 500–800, and handles a smaller caseload. ADNDRC handles matters primarily with an Asia-Pacific nexus, at fees beginning around USD 1,300 for a single-member panel.

The forum choice also affects how supplemental rules are applied, the pool of panelists available, and administrative practice around procedural submissions. WIPO's published jurisprudential overview is the most widely cited reference for consensus panel positions. In our practice, we evaluate the forum against the specific profile of the complaint – the number of domains, the respondent's likely conduct, and the strength of the evidence – rather than choosing a default provider.

One structural decision that follows from forum choice: single-member or three-member panel. A single panelist is cheaper and faster. The complainant selects this option unless the respondent, in its response, requests a three-member panel. If the respondent does so, the parties generally split the higher three-member fee. For a multi-domain complaint where the evidence is strong and the legal questions are straightforward, a single member is typically adequate. Where the complaint raises a novel or contested point – say, whether a privacy-shielded set of registrations all belong to the same registrant – a three-member panel may produce a more defensible outcome.

Step 4: Draft the complaint for a panel that reads it domain by domain

A multi-domain complaint is not a single argument applied in bulk. It is a structured document that first establishes common facts – your trademark rights, the registrant's identity, the pattern of conduct – and then walks each domain through the three elements systematically. Panels flag complaints that apply a boilerplate argument across all domains without individual analysis. That approach risks denial or a finding that the complaint is deficient as to specific registrations.

The practical structure we follow: an opening section establishing complainant identity and mark ownership (with copies of trademark registrations or evidence of secondary meaning for unregistered marks); a section establishing registrant identity across all domains (the same-registrant showing from Step 1); then an individual analysis for each domain addressing all three elements; then a consolidated bad-faith section addressing the overall pattern. The evidence package mirrors this structure: trademark registration certificates, WHOIS printouts for each domain, screenshots of the websites or parking pages as of a specific date, and any communications from the registrant (demand emails, broker solicitations).

The trap in the drafting stage is the complaint that reads as if the trademark is self-evident to a panelist who has never heard of it. State your rights clearly and early. If you rely on an unregistered mark, explain the acquired distinctiveness and the geographic scope. Panelists see hundreds of complaints; yours needs to make the legal case without requiring inference.

If you have assembled evidence for a multi-domain .net filing and want a structured read of how each domain maps to the three elements, reach us at info@cognomenlaw.com.

Step 5: File, manage the response window, and prepare for a default

Once the complaint is filed and the provider confirms it is formally compliant, the proceeding commences and the 20-day response window opens for the registrant. That window runs from the date of commencement, not from filing. The registrant may ask for an extension – providers grant extensions in limited circumstances – but cannot stop the proceeding.

In our experience, multi-domain complaints against serial registrants frequently result in default. The registrant does not appear, files nothing, and the panel decides on the record before it. A default is not an automatic win. The panel still applies the three elements to each domain and may deny transfer as to domains where the evidence is thin. Prepare the complaint as if the respondent will mount a full defense, even if history suggests they will not.

If the respondent does appear, expect a response that challenges registrant identity (claiming the domains are held by different people), asserts a generic-word defense (claiming no trademark significance), or argues legitimate interest through a purported business use. Each of these arguments has a standard counter in the case record, and the complaint structure from Step 4 should already anticipate them. Where the respondent's reply raises new factual claims, some panels accept a supplemental filing, but that is discretionary and not the norm.

Step 6: Understand the decision and the implementation step

A standard single-panelist UDRP case resolves in roughly two months from filing. After the panel issues its decision, the registrar is notified and implements the order – transfer to the complainant's designated registrar account, or cancellation – unless the losing party commences a court action within the implementation window. That window is typically ten business days from notification; if no court action is filed, the registrar acts.

Transfer is the more useful remedy in almost all cases. Cancellation drops the domain into the available pool, where it could be re-registered immediately by anyone, including the same registrant through a different account. If your objective is to hold the domain rather than simply remove it from the current holder, request transfer and have your registrar account ready to receive it.

In a recent multi-domain matter – a cluster of .net typosquats and hyphenated brand variants, summer 2025 – we secured transfer orders for nine of eleven domains in a complaint filed on behalf of a technology brand. The remaining two were dropped before filing after our pre-complaint review identified insufficient evidence of bad-faith use for those registrations. That narrowing decision – cutting weak filings before the complaint goes in – is one of the clearest value points in the process.

What happens when the complaint spans .net and other zones?

It is common for a serial registrant to hold the same or similar names across multiple TLDs: .net, .com, .org, and perhaps a relevant ccTLD. The UDRP permits a single complaint to cover multiple domains under multiple gTLDs – .com, .net, and .org in one filing – provided the same-registrant condition is met. That cross-gTLD filing can be efficient and is generally accepted by WIPO and the Forum.

The analysis changes when a ccTLD enters the picture. A .de registration is not recoverable through a UDRP complaint; that dispute requires action in the German courts, with a DENIC DISPUTE entry available to block transfer during litigation. A .eu domain follows the EURid/ADR.eu procedure, not the UDRP, and the remedy may be revocation rather than transfer depending on the complainant's EU eligibility. A .uk registration goes before Nominet's DRS, where the legal test – "abusive registration" – differs from the UDRP's cumulative "registered and used in bad faith" standard.

Where the portfolio spans gTLD and ccTLD registrations, the efficient path is a parallel strategy: one UDRP complaint covering the gTLDs, separate national or ccTLD procedures for the country-code domains. We regularly advise clients managing cross-zone recovery on how to sequence these proceedings to avoid inconsistent outcomes and to control aggregate cost. The ccTLD procedures have their own evidence requirements and timelines, and a loss in one forum can occasionally be cited in another – a risk worth mapping before the first filing is submitted.

If you only need suspension of a new-gTLD domain (not .net, but a newer extension such as .shop or .online), the URS offers a faster and cheaper alternative. The URS remedy is suspension for the registration term, not transfer, and the evidentiary standard – clear and convincing – is higher than the UDRP. For most brand owners focused on .net, the UDRP remains the correct primary route.

Related at COGNOMEN

• UDRP recovery services – how COGNOMEN files and manages domain complaints
• How to prove no legitimate interest in a domain dispute (alert)
• Step-by-step guide to recovering a hijacked .biz domain