Step-by-step: choose between WIPO and the Forum for a .net dispute

Step-by-step: choose between WIPO and the Forum for a .net dispute. UDRP and ccTLD domain recovery and defense across .net. Email the firm to assess your case.

A stranger registers the .net version of your brand, parks it, and waits. You want it back. Two forums can decide the case under the UDRP – WIPO in Geneva and the Forum in Minneapolis – and the choice between them affects your timeline, your cost exposure, and, in a narrow set of cases, the composition of the panel deciding your dispute.

To choose between WIPO and the Forum for a .net dispute, understand that both apply the same UDRP rules – all three elements of Paragraph 4(a) must be proved – but they differ on filing fees, panel rosters, and available procedural options. WIPO's standard single-panel fee starts at USD 1,500; the Forum's comparable entry point is approximately USD 1,300 for one or two domains. Both deliver a decision in roughly two months under a standard single-panel track.

This guide walks the decision step by step, flags the trap in each step, and closes with a cross-zone comparison for registrants holding both a .net and a .com.

Step 1: Confirm that the .net domain falls under the UDRP at all

Every .net domain registered through an ICANN-accredited registrar is subject to the UDRP as a condition of registration. That is not negotiable. The registrant agreed to it when the domain was created, regardless of where they are in the world or what registrar processed the registration.

The practical trap here is chain-of-title. Before filing, verify that the current WHOIS/RDDS record names the respondent you intend to name in the complaint. Registrars occasionally show a privacy or proxy service as the registrant of record. If they do, the complaint must name that proxy service and trigger the registrar's disclosure procedure. Filing against the wrong named party is a correctable error, but it costs time and can complicate commencement.

A second check: is the domain still pointing somewhere? A domain resolving to a parked page, a competitor site, a pay-per-click farm, or even an inactive DNS entry can satisfy the "use in bad faith" limb. A domain that has genuinely never resolved and was registered in good faith by someone with a plausible non-infringing reason may not. Clarify both facts before committing to a filing route.

We regularly advise brand owners who discover the .net version of their mark registered by a party that also holds the .com or .org. Where the same registrant holds multiple infringing domains, a single UDRP complaint can cover all of them – a procedural efficiency that matters when you are calculating cost per domain.

Step 2: Apply the three UDRP elements to your .net facts

The UDRP is the same rulebook at WIPO and the Forum; the three elements of Paragraph 4(a) do not change by forum. What changes is how each panel roster tends to weigh contested facts, a nuance addressed in Step 4.

The first element – confusing similarity – is usually the easiest to satisfy for a .net dispute involving a registered trademark. The gTLD suffix is generally disregarded in the comparison. A domain that is identical to your mark, or differs only in a generic addition ("buy," "shop," "official") or a minor spelling variant, will ordinarily clear this bar. Your trademark registration is the fastest evidence. Common-law rights work too, but require evidence of use and acquired secondary meaning, which adds weight to the evidentiary bundle.

The second element – no legitimate interest – is a negative that the complainant must initially establish. The consensus approach under the Policy is that a complainant raises a prima facie case by showing the registrant is not commonly known by the disputed name and has no license from the trademark owner. The burden then shifts evidentially to the respondent to produce evidence of a legitimate interest. Safe harbors under Paragraph 4(c) include a bona fide offering of goods or services before notice of the dispute, being commonly known by the name, or legitimate noncommercial or fair use. A respondent who has built a genuine business around the name can use these safe harbors. One who bought it with no discernible use is unlikely to do so.

The third element – bad faith in registration and use – is cumulative. Both limbs must be satisfied. This is where .net disputes most often turn. A domain registered after your trademark became well known, pointed at a pay-per-click page monetizing traffic from users looking for your brand, carries strong bad-faith indicators under Paragraph 4(b). Passive holding – a domain that resolves nowhere and has done so since registration – can also constitute bad faith where the registrant could not have had a plausible legitimate use, but panels are more cautious about passive holding claims, and the evidence needs to be thorough.

For a read on whether the three UDRP elements are met in your .net matter, reach us at info@cognomenlaw.com.

Step 3: Decide between WIPO and the Forum – the practical criteria

Once the three elements appear satisfied, the forum choice is the next decision. Both WIPO and the Forum are competent to decide any .net dispute; neither has jurisdiction over .net to the exclusion of the other. The choice is the complainant's.

Consider five practical criteria.

Filing fee at entry level. WIPO charges USD 1,500 for a single-member panel covering one to five domains; the Forum's entry point is approximately USD 1,300 for one or two domains on a single-member track. For a single .net domain, the Forum is marginally less expensive. The difference narrows as domain count rises, and for cases above five domains, both providers quote individually.

Three-member panel cost. A three-member panel at WIPO costs USD 4,000 for one to five domains. If the complainant requests a single panelist but the respondent requests three members, the parties generally split the higher fee. That split-fee trap catches brand owners who budget for a single-panel filing and then face a respondent who escalates. Build the three-member cost into your contingency budget regardless of which forum you choose.

Expedited track. WIPO offers an expedited option designed to deliver a decision within about one month for single-panel cases involving up to five domains. The Forum does not publish an equivalent accelerated track. If speed is a priority – a product launch is approaching, a campaign is running, or the respondent is actively redirecting traffic – WIPO's expedited path is a material advantage and worth the marginally higher entry fee.

Panel selection and roster composition. Neither WIPO nor the Forum permits parties to select their panelist for a single-member case. WIPO appoints from its own roster; the Forum from its own. Both rosters are large and experienced. The practical difference is that WIPO's roster is more internationally distributed, which can matter for disputes involving non-US complainants or respondents where cultural and jurisdictional context in the reasoning is important. For a purely domestic US dispute over a .net, that difference is less significant.

Precedent orientation. WIPO publishes a regularly updated Jurisprudential Overview that consolidates the consensus view on contested doctrinal questions. Panels at both forums cite it. Filing at WIPO does not guarantee a more favorable doctrinal outcome, but if the theory of your case turns on a nuanced point – passive holding, a generic or descriptive mark, prior use by the respondent – WIPO's larger published body of decisions and its Overview give clearer advance visibility into how the question is likely to be framed.

In our practice, straightforward .net cases where cost is the primary constraint typically go to the Forum. Cases where speed is paramount, where the panel roster's international composition matters, or where a novel doctrinal point needs to be framed carefully tend to go to WIPO.

How do the two timelines actually compare in a .net dispute?

Both WIPO and the Forum operate under the same procedural Rules, so the structural timeline is identical. After the complaint is filed and formal compliance is verified, commencement occurs and the respondent receives 20 days to file a response. No extensions are granted automatically; extensions are discretionary and rare.

After the response window closes – whether a response was filed or the respondent defaulted – the provider appoints a panel. The panel then has a set period (typically 14 days under the Rules) to issue a decision, with a possible extension by the provider. Total elapsed time from filing to decision, at either forum on a standard single-member track, is roughly two months absent a procedural detour.

WIPO's expedited track compresses that to approximately one month. That matters concretely: in a recent matter (a .net domain pointed at a competitor's site, spring 2025), we obtained a transfer decision at WIPO in under five weeks from the date of filing, with no extension sought by the respondent. Standard track would have added another three to four weeks.

After the decision, the registrar implements the transfer. Implementation typically takes a few days to two weeks; the registrar's process is ministerial once the decision is transmitted. Budget that into your planning if the transfer triggers a downstream activity.

Step 4: Assemble the evidence before you file

Evidence is where most UDRP complaints are actually won or lost. A complaint that identifies the correct registrant, states the three elements correctly, and then provides thin evidentiary support will lose – or, at minimum, will expose the complainant to a supplemental filing request, which adds weeks and signals unpreparedness to the panel.

For the first element, the trademark registration certificate (or, for unregistered marks, a detailed use declaration with sales figures and market recognition evidence) is the foundation. Append the WHOIS/RDDS printout of the disputed .net domain. Show the date of first use and the date of registration; if your rights predate the domain, say so plainly.

For the second element, establish that you have no relationship with the respondent: no license, no permission, no authorization. Check whether the respondent is commonly known by the domain name. A simple business name search and a review of the respondent's website (or lack thereof) usually suffices. If the domain resolves to a pay-per-click page, capture screenshots with timestamps and note any category of advertising appearing – competitor ads, ads in your product category, or ads generally are all probative, though in different degrees.

For the third element, document what the domain resolves to, when the domain was registered relative to your trademark, and any direct communications in which the registrant demanded payment or threatened to sell to a competitor. Paragraph 4(b) bad-faith indicators include registration primarily to sell to the mark owner at a profit above cost, registration to disrupt a competitor, and use to attract users for commercial gain by creating a likelihood of confusion with your mark. Each indicator has a documentary footprint. Find it.

One trap: panels expect consistency between the complaint's factual narrative and the exhibits. A complaint that asserts "the domain was registered the day after our product launch" must attach evidence of the launch date. A complaint that asserts "the registrant is using the domain to sell competing goods" must attach screenshots of those goods. Assertions without exhibits carry little weight.

In a contested .net matter (a well-known software brand versus a reseller site, autumn 2024), we built the bad-faith evidence around a sequence of registrant communications, a set of archived pay-per-click landing pages, and a product-launch press release predating the domain registration by eleven months. The panel transferred the domain in the standard timeline with a clear finding on all three elements.

Step 5: Weigh the cross-zone angle before committing to filing

Does the same party also hold a .com, a .org, or a ccTLD version of your mark? If yes, the forum-choice question expands into a multi-zone strategy.

A single UDRP complaint can cover multiple domains only if the registrant is the same holder across all of them. If the .net and the .com are held by the same entity, combine them in one complaint. That reduces total filing fees and obtains a single decision on consistent facts. The trap: if WHOIS privacy services show different nominal holders for each domain, combining may not be possible, and separate complaints – potentially at different forums – become necessary.

For country-code zones, the UDRP does not apply. A .uk version of the same mark goes to Nominet's DRS, with its own "abusive registration" test and its free mediation stage. A .de domain dispute generally requires German court action with a DENIC dispute entry to block transfer during litigation. A .eu dispute runs through the ADR.eu procedure administered by the Czech Arbitration Court. Each of those proceedings runs in parallel with, not instead of, the UDRP proceeding for the .net. We identify the governing national procedure for each ccTLD, check eligibility, and prepare the filing for that registry, coordinating timelines to avoid the situation where a transfer in one zone tips off the registrant in another before the second filing is served.

If the conduct is serious and you want monetary damages – which the UDRP cannot award – a US anticybersquatting court action is the only route that reaches money. Court litigation is substantially more expensive and time-intensive than UDRP arbitration, and it runs on a different timeline. For a .net domain that is costing you measurable business, the calculus between the UDRP's fast transfer remedy and the court route's damages potential is worth setting out explicitly before you file anything.

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

What happens if the respondent defends – and what is RDNH?

A respondent who files a response within the 20-day window converts a potentially straightforward case into a contested one. That is their right. It also triggers a more demanding procedural phase: the panel must read and weigh both submissions, resolve factual disputes, and in some cases allow supplemental filings where new facts emerge.

If the respondent can demonstrate a legitimate interest – a bona fide business using the name, documentary evidence of use before the dispute arose, or a plausible non-infringing purpose – the second UDRP element becomes contested. Panels do not rubber-stamp transfer where legitimate interest is genuinely at issue.

More acutely: if the respondent believes the complaint was brought in bad faith to deprive a legitimate registrant of a domain, they may seek a finding of Reverse Domain Name Hijacking (RDNH). An RDNH finding carries no monetary penalty, but it is a public reputational sanction. Complainants who file against a generic or descriptive term, who lack trademark rights that clearly predate the domain, or who rely on weak evidence of bad faith are most exposed to this finding. We assess RDNH risk as a standard part of pre-filing due diligence – not only for respondent clients, but for complainants who need to know whether their complaint, as currently framed, could be characterized as abusive.

For registrants who receive a complaint they believe is unfounded or abusive, the reverse side of this process – building the legitimate-interest record, documenting good-faith registration, and seeking an RDNH finding where warranted – is a separate practice that we handle with the same step-by-step analysis. See the guide linked below on defending a generic domain.

Related at COGNOMEN

• UDRP domain recovery service – how COGNOMEN files and manages UDRP complaints end to end
• How to prove bad faith in a .co domain dispute – evidence strategy and panel patterns
• How to defend a generic domain online – respondent strategy and RDNH grounds