Recover a typosquatted .net domain: what panels actually decide

Recover a typosquatted .net domain: what panels actually decide. UDRP and ccTLD domain recovery and defense across .net. Email the firm to assess your case.

A brand owner runs a search and finds a domain that looks almost like its mark – one letter transposed, a doubled consonant, a missing vowel – registered in the .net zone and pointing at a pay-per-click parking page. The domain harvests search traffic meant for the brand. Every click is a lost impression, a misdirected customer, or worse, a phishing vector. The question is not whether this feels wrong. The question is what panels actually do about it.

To recover a typosquatted .net domain under the UDRP, a complainant must satisfy all three elements of Paragraph 4(a): confusing similarity to a mark, no legitimate interest in the respondent, and registration and use in bad faith. A standard case at WIPO takes roughly two months from filing to decision, with the respondent given 20 days to answer. The only remedies available are transfer or cancellation – there are no monetary damages under the Policy.

This analysis walks through the governing test, the specific evidence patterns that decide typosquat cases in the .net zone, where panels agree, where they diverge, and what that means for a brand owner deciding whether to file.

Why .net typosquatting is a distinct enforcement problem

The .net zone sits in an unusual position. It is a legacy gTLD – governed by the UDRP in full, filed at WIPO or the Forum, subject to the same three-element test as .com disputes – yet it attracts a specific class of abusive registrant. Typosquatters who cannot hold .com counterparts (or who register both simultaneously) frequently target .net as a secondary zone. The result is a body of panel practice that mirrors the .com consensus in most respects but shows distinct patterns on the bad-faith analysis, particularly where the zone mismatch itself is part of the scheme.

Panels have consistently treated the TLD extension as irrelevant to the first-element analysis. The comparison is made between the domain's second-level label and the complainant's trademark. A one-character deviation that would be immediately apparent when the two strings are placed side by side is routinely held to create confusing similarity. Deliberate misspellings, homoglyph substitutions, and phonetic equivalents all fall within this principle. The .net suffix adds nothing to distinguish the domain from the mark.

We regularly advise brand owners who discover .net typosquats alongside .com registrations. In those situations the complainant can ordinarily bundle domains under a single complaint, provided both are held by the same registrant. That point matters for budgeting: a consolidated filing at WIPO covers multiple domains at the same base filing fee tier if the count stays within the published range.

How does the three-element UDRP test apply to typosquatted .net domains?

All three elements of Paragraph 4(a) of the UDRP must be satisfied for a transfer or cancellation order to issue. In typosquat cases, element one is almost never the battleground. Elements two and three are where cases are won or lost.

Element one – Confusing similarity. The complainant must hold trademark rights and show the domain is identical or confusingly similar. In a typosquat, similarity is structural: one or two character deviations from a distinctive mark produce a domain that looks, and sounds, like the brand. Panels apply a straightforward comparison test. The mark does not need to be registered – common-law rights suffice, provided the complainant can document them – but registration evidence is cleaner and faster.

Element two – No legitimate interest. The complainant bears the initial burden of making a prima facie case that the respondent lacks legitimate interests. In practice, a parking page or pay-per-click page linked to the category of goods or services the mark covers – or to the mark owner's competitors – is strong prima facie evidence. The burden then shifts to the respondent to invoke one of the Paragraph 4(c) safe harbors: a bona fide offering of goods or services before notice of the dispute; being commonly known by the domain name; or legitimate noncommercial or fair use without intent to mislead.

Typosquatters rarely have a plausible Paragraph 4(c) defense. A respondent who adopted a misspelling of another's mark is hard-pressed to argue it was "commonly known" by that misspelling. Deliberate deviation from the mark signals awareness of the mark – and therefore forecloses the claim of generic or descriptive adoption.

Element three – Bad faith registration and use. This is the most contested element. Under the UDRP the test is cumulative: registration and use must each be shown to be in bad faith. Panels in typosquat cases apply a well-settled inference: a registrant who deliberately misspells a trademark is unlikely to have done so without knowledge of the mark. Where the domain resolves to a parking page generating revenue from competitor advertisements, the Paragraph 4(b)(iv) circumstance applies – commercial gain through user confusion created by the domain's similarity to the mark. That is treated as both a bad-faith use indicator and, by inference, evidence that the registration was itself made in bad faith.

The cumulative nature of element three is the most important clause in the Policy for .net typosquat cases. Registration intent is assessed at the date of registration; use patterns afterward provide the evidence. A domain registered years before the complainant's mark was adopted presents a harder case – and that is the minority scenario discussed below.

What evidence do panels actually look at in .net typosquat disputes?

The complaint's strength is a function of the evidence package. Four categories of evidence matter most in .net typosquat proceedings.

1. The mark's distinctiveness and priority. A highly distinctive or fanciful mark (coined words, unusual spellings) makes the typosquatter's "innocent adoption" argument implausible. Panels have consistently held that where a mark has no descriptive meaning in the relevant language, it strains credibility to suggest a registrant arrived at the same string, or a near-identical one, independently.

2. The domain's content history. Web archive captures of the domain's resolving page are among the most useful exhibits. A parking page filled with links to the complainant's competitors – or to the complainant's own product category – establishes the use prong of element three directly. A domain that cycled between a parking page and a default "parked for sale" splash page, with no substantive content, is also probative. Panels do not require active harm; passive holding of a famous mark in a typosquat domain, with no plausible legitimate use, can satisfy the use prong in appropriate cases.

3. The registrant's prior conduct. Paragraph 4(b)(ii) of the UDRP lists a pattern of abusive registrations as a bad-faith circumstance. If the respondent holds other domains that are typosquats of third-party marks – and registrar WHOIS/RDDS data or prior panel decisions reflect this – that pattern can be decisive. It removes any credibility from a good-faith defense.

4. Any demand for payment. A communication from the registrant offering to sell the domain for an amount exceeding documented acquisition costs falls squarely within Paragraph 4(b)(i). In typosquat cases that communication sometimes comes unsolicited – the registrant has preemptively approached the brand owner. That approach is powerful evidence. We have seen cases where a registrant's opening email to a brand owner contained enough language to satisfy all three Paragraph 4(b) circumstances simultaneously.

Where does panel consensus hold, and where does it break?

The consensus view, reflected consistently across WIPO and the Forum, is that deliberate character-deviation typosquats of well-known marks in the .net zone are strong candidates for transfer. When a complainant holds a registered trademark, presents web archive evidence of parking-page use, and can show the registrant has no plausible claim to the name, panels order transfer without extended analysis of the individual elements.

The minority view – and the scenario where cases are genuinely contested – arises in three situations. First, where the complainant's rights are junior to the registration date. If a brand owner adopted and registered a mark after the domain was created, the bad-faith-at-the-moment-of-registration requirement under element three becomes difficult. Panels will look at whether the complainant had unregistered rights predating registration and whether the registrant could plausibly have known of them. Cases in this posture often turn on the registrant's industry and the geographic spread of the mark.

Second, where the deviation is large enough to raise a genuine similarity question. A two-word addition to a common-word mark in .net may not constitute typosquatting at all. Panels have declined to find confusing similarity where the second-level label, though phonetically related, requires significant departure from the mark's spelling or structure. This boundary is fact-intensive.

Third, where the respondent can show a prior business or personal use of the name. This is uncommon in pure typosquat cases, but not unknown. A respondent who registered the domain years before receiving any notice of the dispute and who operated a website with substantive content tied to the domain's literal meaning – not to the complainant's mark – will have a credible Paragraph 4(c) case. In our defense practice we have seen complaints filed against registrants with exactly this profile, and we have successfully opposed transfer on those facts.

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

How do panels treat passive holding in .net typosquat cases?

Passive holding – a domain that resolves to a blank page or an empty registrar default – is one of the more nuanced areas of typosquat panel practice. The Policy requires both registration and use in bad faith. A domain that does nothing, by the literal text, may seem to lack the "use" component. Panels have addressed this by applying an aggregate-circumstances test.

Where the domain is an obvious typosquat of a well-known or distinctive mark, the respondent has provided no evidence of any intended good-faith use, and the registrant's identity or conduct suggests familiarity with the mark, panels regularly find that passive holding constitutes use in bad faith. The reasoning is that it is impossible to conceive of any legitimate use of the domain that would not exploit the complainant's mark. That proposition is easy to sustain when the domain is a single-character deviation of a coined mark.

Where the mark is less distinctive, the deviation is larger, or there is any plausible alternative explanation for the registration, panels have declined to extend the passive-holding inference. The minority position is that the use element should be given independent content and should not be collapsed into the registration analysis by inference alone. Complainants who rely solely on passive holding without supporting evidence of intent should treat that uncertainty seriously.

Is WIPO, the Forum, or another provider the right choice for a .net typosquat case?

The UDRP applies to .net through every accredited provider: WIPO, the Forum, CAC, and ADNDRC. Provider selection matters in practice, though the substantive test is identical across all four.

WIPO handles the largest volume of UDRP cases globally and is the most frequently selected provider for .net disputes. Its filing fee for a single-panel case covering one to five domains is USD 1,500. The Forum's entry-point fee for one to two domains is approximately USD 1,300. The Czech Arbitration Court (CAC) offers the lowest published entry fee – beginning around USD 500–800 – though it is the least frequently used of the four providers. ADNDRC fees begin around USD 1,300 for a single-panel case.

Provider selection can also affect timeline. WIPO offers an expedited procedure for single-panel cases covering up to five domains, targeting a decision within approximately one month. That option can matter when a typosquat is actively diverting traffic or operating a phishing page. The standard procedure at all providers runs approximately two months.

In a matter we handled in spring 2025 – a cluster of .net and .com typosquats targeting a specialty-goods brand, approximately eight domains held by the same registrant – we recommended a consolidated WIPO filing. The case settled at the pre-panel stage, with transfer of all domains, within six weeks of commencement.

What is the cross-zone picture – when is court action needed instead of UDRP?

The UDRP covers .net fully, but it does not cover all situations a brand owner faces. The decision matrix is roughly as follows.

If the domain is a .net typosquat and the only goal is transfer or cancellation, a UDRP complaint at WIPO or the Forum is the correct path. It is faster and far less expensive than litigation. If the registrant is also operating a .de version of the typosquat, neither the UDRP nor any WIPO-administered ccTLD procedure applies to that domain – the .de dispute must proceed through German courts, with a DENIC DISPUTE entry available to block transfer during litigation. A hybrid matter covering .net and .de therefore requires two parallel tracks, one arbitral and one judicial, with local litigation counsel handling the court side.

If the brand owner also wants damages – lost revenue, statutory damages under US anticybersquatting legislation – the UDRP cannot provide them. Transfer or cancellation are the Policy's only remedies. A US federal court action under the applicable anticybersquatting statute is the only path to monetary relief, though that route is substantially more expensive and slower. In our practice, clients who face an actively harmful typosquat in .net often file a UDRP complaint first – to stop the bleeding – and assess court action separately once the domain position is resolved.

For .net disputes where the registrant holds an identically-spelled domain in a ccTLD that operates under a UDRP-variant (for example, .me or .co), those may be bundled with the .net complaint at WIPO if the same registrant controls all domains. This can consolidate timelines and filing costs materially. The threshold question is whether the registrant of record is consistent across all disputed domains.

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

What should a respondent do when facing a .net typosquat complaint?

Not every .net domain that resembles a trademark is a typosquat. Respondents are entitled to assert their legitimate interests, and panels take those assertions seriously when they are supported by evidence. The 20-day response window is not optional. A respondent who defaults – who files nothing – loses the opportunity to present the Paragraph 4(c) safe harbors, and panels may draw adverse inferences from silence.

The strongest respondent positions in .net disputes involve demonstrable pre-dispute use of the domain in connection with goods or services not related to the complainant's mark; a domain name that corresponds to the respondent's own legal name or long-standing trade name; or a mark registration in the respondent's jurisdiction that predates the complaint. These are not hypothetical defenses. We have built successful responses on each of these bases in matters where the complainant either had weak marks or had acquired mark rights after the domain was registered.

Where the complaint is abusive – filed against a registrant with a clear legitimate interest, with the evident aim of obtaining a valuable domain rather than protecting a genuine mark – the respondent can seek a Reverse Domain Name Hijacking (RDNH) finding. An RDNH finding carries no financial penalty under the Policy. Its effect is reputational: the finding is published and reflects adversely on the complainant's conduct. In a recent matter (a .net domain held for legitimate business use, summer 2025), we secured an RDNH finding for a registrant where the complainant's mark was both junior in date and geographically remote from the registrant's market.

Related at COGNOMEN

• UDRP domain recovery – complaint assessment, forum selection, and filing across gTLDs
• How to recover multiple domains in a single UDRP proceeding – strategy and consolidation
• Recovering a typosquatted .mx domain – the governing procedure and evidence requirements