Step-by-step: prove bad faith registration of a .net domain

Step-by-step: prove bad faith registration of a .net domain. UDRP and ccTLD domain recovery and defense across .net. Email the firm to assess your case.

A brand owner discovers a .net matching their mark is pointed at a pay-per-click parking page — or held blank while the registrant waits for a five-figure offer. Recovery looks straightforward. It rarely is. The UDRP requires proving three separate elements, and the third — bad faith registration — is where cases are won or lost on the evidence submitted.

To prove bad faith registration of a .net domain under the UDRP, a complainant must satisfy all three elements of Paragraph 4(a): confusing similarity to a mark, the registrant's lack of legitimate interest, and registration and use in bad faith. The WIPO filing fee starts at USD 1,500 for a single-member panel covering one to five domains; a decision typically arrives within about two months. The only available remedies are transfer or cancellation — no damages, no cost award.

This guide walks each step, identifies the trap hidden inside it, and explains what evidence actually decides the outcome on a .net.

Why .net follows the same UDRP rules as .com — and one practical difference

.net is a generic top-level domain (gTLD) administered under ICANN's accreditation regime, which means the Uniform Domain Name Dispute Resolution Policy applies in full — the same three-element test, the same panelist pool at WIPO and the Forum, and the same remedies of transfer or cancellation. No court step is required to open a case.

The practical difference is positioning. Panels are aware that .net was historically marketed to network and infrastructure businesses. A complainant whose brand has no obvious technology dimension should expect the registrant's side to argue that the .net was registered for a generic or descriptive networking purpose. That argument rarely succeeds against a well-known mark, but it adds a litigation variable worth anticipating before you file. Build your filing to foreclose the generic-use angle from the first paragraph of the complaint.

A second consideration: if the same registrant controls both the .com and the .net of your brand, a single UDRP complaint can cover both domains — provided the registered holder is the same entity. That is an efficiency that complainants often miss. We regularly advise brand owners to audit the full zone footprint before selecting a filing strategy.

Step 1 — Establish your trademark rights (and the trap inside this step)

The first element of Paragraph 4(a) requires that the domain be identical or confusingly similar to a trademark in which the complainant has rights. Panels examine the domain itself against the mark — they do not weigh overall commercial context at this stage. A registered trademark satisfies the rights requirement most cleanly, but panels have also credited common-law rights based on sustained use and demonstrated reputation.

The trap is timing. Panels scrutinize whether the complainant's trademark rights predate the domain's registration date. If the .net was registered before the mark was filed — let alone registered — the confusing-similarity element may survive, but the bad-faith limb becomes very difficult to establish. A registrant cannot have known about rights that did not yet exist. Pull the domain's creation date from the WHOIS or RDDS record on day one, and map it against your earliest mark priority. Where the dates are close, gather evidence of pre-filing reputation: press coverage, sales figures, trade-show presence, whatever establishes that the brand was in the market and recognizable before the domain was taken.

Common-law rights require a heavier evidentiary lift. Panels expect declarations, revenue data, and third-party references — not simply a website screenshot. We have seen complaints fail at the first element because the complainant submitted only a logo and a URL. Do not let that be the reason.

Step 2 — Show the registrant has no legitimate interest (and the defense to pre-empt)

The second element of Paragraph 4(a) asks whether the registrant has any rights or legitimate interests. Paragraph 4(c) of the Policy sets out the three primary safe harbors the registrant may invoke: a bona fide offering of goods or services using the domain before notice of the dispute; being commonly known by the domain name; or a legitimate noncommercial or fair-use purpose with no intent to mislead.

Because a complainant cannot prove a negative, panels apply a burden-shifting approach. The complainant makes a prima facie showing — typically by demonstrating that the mark is well-known and the registrant has no apparent license or affiliation — and the burden then shifts to the registrant to present evidence of a legitimate interest. Default (where the registrant does not respond) generally means no evidence is offered. Panels in that scenario find for the complainant on this element far more often than not.

The defense to pre-empt is a claim that the domain reflects a generic word in common use on the internet. ".net" reinforces this argument if your mark contains a common English word. Counter it with evidence that your mark has acquired distinctiveness — third-party recognition, media coverage, customer declarations — such that a reasonable observer would associate the domain with you specifically, not with a generic concept.

The second element is often where experienced respondents focus their defense. For a read on whether your evidence is sufficient to shift the burden, email info@cognomenlaw.com before you file.

Step 3 — Prove bad faith registration of a .net domain: what the evidence must show

This is the critical step — and the one most complaints underestimate. Paragraph 4(b) of the Policy sets out four non-exhaustive circumstances that panels recognize as evidence of bad faith: registration primarily to sell the domain to the mark owner or a competitor at a price exceeding out-of-pocket costs; registration to block the mark owner from reflecting its mark in a domain, as part of a pattern of such registrations; registration to disrupt a competitor's business; and registration to attract users for commercial gain by creating a likelihood of confusion with the mark.

The trap in this step is the word "registration." Bad faith must exist at the moment of registration, not merely arise later. A domain registered in apparent good faith that is subsequently abused does not automatically meet the standard. Panels look for evidence of what the registrant knew — or reasonably should have known — at the time of registration.

What evidence carries weight? The following fact patterns have consistently influenced panel outcomes across thousands of UDRP decisions:

• Timing relative to the brand's public profile: Registration shortly after a major product launch, press announcement, or funding round is treated as constructive notice of the mark.
• Offer to sell at an inflated price: An unsolicited message to the mark owner demanding a five-figure sum — or even a public "for sale" listing at a price far above typical registration costs — is a classic Paragraph 4(b)(i) indicator.
• Parking page with pay-per-click links: Where those links resolve to the complainant's competitors or to the complainant's own product category, panels regularly find bad-faith use under Paragraph 4(b)(iv).
• Pattern of abusive registrations: Prior UDRP losses by the same registrant, or a portfolio of names that matches the marks of multiple brand owners, supports Paragraph 4(b)(ii).
• No plausible legitimate use: Where the domain is a coined or highly distinctive term, the absence of any credible explanation for registration in the registrant's own name — other than to target the complainant — is itself persuasive.

In a recent matter (a .net typosquat, spring 2025), we assembled a timeline showing the domain was registered within ten days of a widely covered product announcement, and the registrant's parking page carried advertising links directed to the complainant's direct competitors. The panel found bad faith under both Paragraph 4(b)(i) and 4(b)(iv). The domain was transferred in approximately eight weeks from filing.

Passive holding — where the domain resolves to nothing at all — is not a safe harbor. Panels have consistently held that passive holding of a domain incorporating a well-known mark, with no plausible good-faith explanation, satisfies the use-in-bad-faith requirement. The burden on the complainant in those cases is to show the totality of circumstances makes legitimate use implausible.

How do you choose between WIPO, the Forum, and CAC for a .net complaint?

All three are approved UDRP providers for .net domains, and the legal test is identical across them. The choice turns on fee, speed, and panel culture. WIPO is the largest and most internationally recognized forum; its single-panel filing fee is USD 1,500 for one to five domains. The Forum begins around USD 1,300 for one to two domains. The Czech Arbitration Court (CAC) offers the lowest entry point — in the range of USD 500–800 — but handles a much smaller share of overall caseload. WIPO and the Forum together account for roughly 97% of all UDRP proceedings.

For most .net complainants, WIPO is the default. Its published jurisprudential overview is the most comprehensive reference for panelists, and its name carries institutional weight that can matter when implementing a transfer order with an uncooperative registrar. Where budget is a primary concern and the case is clear-cut, CAC is worth considering.

The Forum has historically attracted a slightly different panel pool and processes complaints at comparable speed to WIPO. If the mark is US-centric and the infringement pattern is straightforward, the Forum is a credible alternative. We have filed successfully at all three forums and advise on the selection as part of the initial case assessment.

What about court instead? If you also want monetary damages — not just the domain — the UDRP cannot deliver them. A US anticybersquatting action in court is the only route that reaches money. Court litigation is substantially more expensive and slower, but it is the correct instrument when the harm exceeds the domain itself. For a .net where the registrant has also operated a fraudulent site using your brand, a parallel or sequential court filing may be warranted — handled with local litigation counsel in the relevant jurisdiction if the defendant is outside the US.

What does the UDRP timeline look like from filing to transfer?

A standard .net UDRP case proceeds through five stages: complaint submission and provider review, commencement and service on the registrant, the 20-day response window, panel appointment and deliberation, and finally registrar implementation of any transfer or cancellation order.

End to end, a single-panel case with no procedural complications typically concludes in about two months. WIPO also offers an expedited option delivering a decision in approximately one month, available for single-panel cases of up to five domains — a useful tool when commercial urgency is high (for example, a product launch date is approaching or the domain is actively diverting customers).

Three procedural events extend the timeline. First, if you request a single-member panel but the registrant requests a three-member panel, the case converts and you generally split the higher three-member fee — USD 4,000 at WIPO for one to five domains — and the panel appointment takes longer. Second, the parties may agree to suspend the case for settlement discussions; that suspension pauses the clock. Third, supplemental filings, if permitted by the panel, add days.

In a further recent matter (a .net impersonation case, autumn 2024), the registrant filed a response and requested a three-member panel. The case concluded in approximately thirteen weeks — still a fraction of the time a court action would have required, and with a transfer order at the end.

Once a decision issues, the registrar is typically directed to implement the transfer within about ten business days, barring a court challenge filed by the registrant in that window. Such challenges are rare on clear-cut cases.

If you have already received a UDRP complaint and the response deadline is approaching, time is critical. Email info@cognomenlaw.com for an urgent assessment of the record.

What evidence actually decides the outcome?

Panels decide on the written record — no live testimony, no cross-examination. The complaint and any exhibits are the only tools available to establish bad faith. Evidence that consistently carries the most weight falls into four categories.

WHOIS and RDDS records establish who registered the domain and when. Preserve a contemporaneous screenshot; registrant data can change after a dispute is filed. If privacy or proxy registration masks the registrant's identity, panels treat the listed proxy service as the named respondent, and may draw adverse inferences from the concealment where the mark is well-known.

Communication records are often decisive. An email from the registrant offering to sell the domain, a demand via a domain broker, or a social-media message referencing the complainant's brand by name gives the panel a direct view into the registrant's motive. Save every message in its original format with full metadata — screenshots without headers are weaker than exported email files.

Screenshots of the domain's resolution history — ideally taken at multiple points and preserved with timestamps — document how the domain has been used. Web archive services provide historical snapshots where current screenshots would only show an empty page. Gaps in resolution history are not damaging to the complainant; panels draw inferences from what was shown when something was there.

Trademark registration certificates and priority documents confirm the mark and its date. For common-law rights, supplement with declarations from the brand's representative attesting to first use, sales figures, and geographic reach — then support those declarations with objective third-party evidence: press articles, Nielsen or similar market reports, industry-association references.

What the panel does not want: unsupported assertion. "We are well-known" in the complaint narrative, unaccompanied by evidence, counts for little. Show; do not tell. Every factual claim in the complaint should point to a numbered exhibit.

Can the registrant's silence work against them?

Yes — and this matters. When a registrant does not file a response within the 20-day response window, the panel decides on the complaint record alone. Default is not the same as automatic transfer; the complainant must still establish all three elements. But the absence of a response means no safe-harbor evidence is placed before the panel, and no explanation for the registration is offered. Panels in default cases rarely deny transfer where the complaint is competently assembled.

The myth to address here: some brand owners assume that if the registrant ignores the case, the panel will simply award the domain. That is not always correct. We have reviewed default decisions where the panel denied the complaint because the complainant's bad-faith evidence was thin — a single assertion about the mark's fame without supporting exhibits, or a failure to establish that the mark predated the registration. Default shifts the practical burden of going forward, but it does not eliminate the complainant's obligation to prove all three elements.

Build the complaint as though a sophisticated respondent will contest every point. That discipline produces better outcomes in both contested and default cases.

Related at COGNOMEN

• UDRP domain recovery service: assessment, filing, and forum selection for gTLD complainants
• Case study: recovering a domain after a failed private buyback negotiation
• Guide: registrar lock escalation after domain theft or unauthorized transfer