How to defend a .net domain acquired as an investment

How to defend a .net domain acquired as an investment. UDRP and ccTLD domain recovery and defense across .net. Email the firm to assess your case.

A brand owner files a UDRP complaint against a .net domain you acquired years ago as a portfolio investment. The demand is transfer. You have no connection to their company, no intent to profit from their mark, and solid reasons for registering the name. Yet the complaint has landed, and you have 20 days to respond once the case commences.

To defend a .net domain acquired as an investment under the UDRP, you must rebut at least one of the three elements of Paragraph 4(a) – or establish a safe harbor under Paragraph 4(c). The most effective route is almost always demonstrating a legitimate interest in the name as a domain investor, documenting that the registration was not targeting the complainant's mark, and, where the complaint is opportunistic, seeking a finding of Reverse Domain Name Hijacking. WIPO administers the overwhelming majority of .net proceedings; the current WIPO filing fee for a single-member panel defense starts at the same USD 1,500 threshold, allocated to the complainant – your filing cost is nil, though legal preparation is not.

This page covers the governing rules for .net, the safe harbors available to domain investors, how to build a winning record, what decides the outcome, and when an RDNH finding is realistic.

Why .net domains are governed by the UDRP – and what that means for you

The UDRP applies to every accredited registrar for gTLDs, including .net – which means the same three-element test that governs .com disputes governs yours. There is no separate .net policy. A complainant files at WIPO, the Forum, CAC, or ADNDRC; the registrant receives notice; the registrar locks the domain; and a panel of one or three decides transfer, cancellation, or denial within roughly two months.

That timeline is fixed by the Rules, not by the parties. A registrant who defaults – who files no response – loses almost automatically. That single fact is why the 20-day response window matters. A default is not neutral. Panels treat it as an admission of the complainant's factual allegations, which means a complainant with a thin case can still win against a silent respondent.

In our practice, we see .net investment domains challenged with exactly this dynamic: a complainant with a mark that postdates the registration date, a demand letter, and then a complaint when the holder refuses to sell below market. The legal question is whether the registration was abusive at the moment it was made – not whether the name looks similar to a mark that came later.

What are the three UDRP elements a complainant must prove – and where can a domain investor break the chain?

A complainant must satisfy all three elements of Paragraph 4(a): (1) the disputed domain is identical or confusingly similar to a mark in which the complainant has rights; (2) the registrant has no rights or legitimate interests in the domain; and (3) the domain was registered and is being used in bad faith. Each element is cumulative. Defeat any one of them and the complaint fails.

For a domain investor, element (1) is rarely the ground to contest – descriptive or generic strings often match someone's trademark somewhere. The productive battlegrounds are elements (2) and (3).

On element (2), the complainant carries an initial burden of alleging no legitimate interest; the burden then shifts to the respondent to produce evidence supporting one. Three safe harbors appear in Paragraph 4(c): a bona fide offering of goods or services before notice of the dispute; being commonly known by the name; and legitimate noncommercial or fair use without commercial intent to mislead. Domain investment is not listed explicitly, but panels have consistently recognized that holding a domain for resale can constitute a legitimate interest – provided the name was chosen because of its generic or descriptive value, not to exploit a specific mark. That distinction is everything.

On element (3), panels apply the "registered AND used" test cumulatively. A mark that did not exist at the date of registration, or that the registrant demonstrably could not have known about, typically defeats bad-faith registration. Passive holding – a parked page generating generic pay-per-click links – creates a harder argument, but it is not automatically fatal when the remaining record supports good faith.

For an assessment of whether your .net investment record supports a defense on elements (2) and (3), contact info@cognomenlaw.com.

How do you build the legitimate-interest record that wins a UDRP response?

The legitimate-interest defense lives in its documentation. The response is not an argument about fairness; it is a submission of evidence that a panel must weigh. Each piece either supports or undermines the inference that the registration targeted a specific mark.

The most effective records we assemble in respondent defense work share several features. First, they establish the registration date and what the domain investor could reasonably have known on that date – WHOIS history, Wayback Machine captures, and any evidence that the complainant's mark postdates or was obscure at registration. Second, they show the nature of the name itself: is it a common word, a geographic term, a technical abbreviation, or a genuine acronym? Generic and descriptive names have value independent of any one brand. Third, they document the portfolio context – panels look more favorably on a respondent who holds dozens of similar generic names than one whose portfolio happens to be dominated by names confusingly similar to known marks.

Pay-per-click content matters. If the parking page displayed links related to the complainant's products rather than the generic meaning of the string, that works against the respondent. In a recent matter – a .net portfolio dispute, summer 2024 – we successfully defended an investor holding a two-word descriptive domain by showing that the parking links were generic to the industry broadly, not directed at the complainant's specific products, and that the mark in question postdated the registration by over two years. The complaint was denied.

Proactive evidence collection before the response deadline is essential. Panels do not typically accept supplemental filings after the response window closes, and the registrar lock means you cannot alter the record on the live page. Gather screenshots, archive captures, and registration history contemporaneously.

When is an RDNH finding realistic for a domain investor defending a .net?

Reverse Domain Name Hijacking is a formal finding by a panel that the complaint was brought in bad faith – typically to deprive a legitimate registrant of a name the complainant wants but cannot buy at a price it accepts. An RDNH finding carries no monetary penalty; it is a reputational sanction, publicly listed in the panel decision.

Panels have consistently found RDNH where: the complainant knew or should have known at filing that the registrant's registration predated the trademark; where the complaint was filed as a pressure tactic after failed purchase negotiations; or where the complainant's own submissions contained material omissions about the registration timeline. In our experience defending these cases, the clearest RDNH candidates are complaints where the complainant's mark registration came substantially after the domain registration date and the only bad-faith inference rested on speculation.

RDNH is not a claim you file independently. It is a finding the panel may make on its own or at the respondent's request – and requesting it without a well-grounded basis can undercut credibility on the merits. We regularly advise registrants on whether the record supports an RDNH request and how to frame that request without overreaching.

Is RDNH worth pursuing? For a serious domain investor, yes – because a pattern of RDNH findings against a complainant or its counsel can deter future abusive filings across a portfolio.

What evidence actually decides the outcome of a .net UDRP response?

Evidence that decides UDRP respondent cases breaks into four categories: registration history, name characteristics, post-registration conduct, and third-party context.

Registration history is the first thing a panel examines. The date of the registrant's acquisition relative to the complainant's first use or trademark registration is often dispositive. If you acquired the domain before the complainant's mark existed in any form, bad-faith registration is almost impossible to establish. If you acquired it after a well-known mark was in use, the panel will ask what you knew and why you chose that string.

Name characteristics address the generic or descriptive quality of the string. Panels apply a meaningful presumption in favor of registrants who hold names with dictionary definitions, standard abbreviations, or common commercial usage. A five-letter acronym that also matches a complainant's mark may have been chosen entirely for its generic value. Documentation of that independent value – industry usage, search volume data, comparable domain sales in the secondary market – strengthens the response.

Post-registration conduct covers how the domain has been used. Parking with generic links, holding inactive, or using the domain for legitimate content all support the respondent differently. Sending an unsolicited offer to the trademark holder, targeting the holder's employees, or pointing the domain at a competitor's site are the strongest bad-faith markers a complainant can cite.

Third-party context includes correspondence records. If the complainant sent a cease-and-desist or a low purchase offer before filing, and you responded with a market-based counter, that sequence supports a good-faith posture. If you initiated the sale discussion after learning of the mark, the inference runs the other way. Save every communication. Produce them in the response.

In a second matter worth noting – a .net acronym dispute, early 2025 – we built the response around secondary-market pricing data showing the string had traded at four figures for names in the same category, independent of any single brand. The panel denied the complaint, citing the respondent's well-documented investment rationale.

To weigh UDRP defense strategy for your specific .net investment, email info@cognomenlaw.com.

How does defending a .net differ from other gTLD or ccTLD disputes?

The right route depends on the zone and the goal. For .net, the UDRP governs without variation – the same rules, the same forums, the same remedies as .com. There is no .net-specific quirk in the legal test. The practical difference from .com is market perception: panels and complainants alike know that .net domains have traded as investment assets for decades, which means a portfolio-holding argument carries well-established precedent.

Compare that with a ccTLD dispute. A .de investment domain cannot be defended at WIPO under the UDRP – Germany's registry, DENIC, has no equivalent arbitration procedure, and disputes travel to the German courts with a DENIC DISPUTE entry to block transfer during litigation. A .uk investment domain is governed by the Nominet DRS, which uses an "abusive registration" test under a "registered OR used" standard – notably different from the UDRP's cumulative "registered AND used" requirement. That structural difference can work in the respondent's favor or against it, depending on the facts.

For new-gTLD domains – .app, .shop, .io – the URS is an alternative suspension mechanism available to complainants alongside the UDRP. The URS imposes a higher evidentiary threshold ("clear and convincing") and suspends rather than transfers the domain, making it a weaker tool for complainants. As a respondent, a URS proceeding is faster but the response window is correspondingly short.

If a domain investor holds .net and .com variants of the same name, a complainant may file a single complaint covering both under one proceeding – provided the same registrant holds both. That consolidated approach is permissible under the UDRP and can be more efficient for the complainant. It is also more expensive for the respondent to defend, which is one reason portfolio-level defense planning matters.

If you hold .net and a matching ccTLD, confirm the governing procedure for the ccTLD with counsel before assuming the UDRP applies. More than 87 ccTLDs have appointed WIPO as a provider and use the UDRP or a close variant; many others do not.

What does the process look like from complaint to decision?

The UDRP has five stages. First, the complainant files a written complaint with the chosen provider – WIPO, the Forum, CAC, or ADNDRC. Second, the provider performs formal compliance review and notifies the registrant, placing a registrar lock on the domain. Third, the respondent has 20 days from commencement to file a response. Fourth, a panelist (or three, if either party requests it) is appointed and issues a written decision. Fifth, the registrar implements the decision – transfer, cancellation, or denial – unless a court action is filed during the implementation window.

In practice, the response window is where a domain investor's defense is won or lost. Drafting a compelling response means marshaling all four categories of evidence described above, presenting them in the format the provider requires, and making the legal argument on each element clearly and concisely. Panels are not courts; they issue decisions without hearings. The written record is the totality of the case.

WIPO offers an expedited option for a decision within about one month, available for single-panel cases of up to five domains. For a standard case, the process runs roughly 45 to 60 days from filing to decision. If the complainant requested a single panelist but the respondent requests a three-member panel, the parties generally split the higher three-member fee – meaning the respondent's financial exposure rises. That decision should be made deliberately, based on the complexity of the case and the credibility value of a three-member panel's denial finding.

Is a domain investor's defense strategy different from a business registrant's?

Yes – materially. A business registrant defending a domain typically argues that the name describes the business itself, that the registrant is known by the name, or that the domain is used in a bona fide commercial offering predating the dispute. Those arguments ground the defense in the registrant's identity and use.

A domain investor's defense is structurally different. The investor rarely uses the domain actively. The argument is that the name has independent generic or descriptive value, that the registration predated or was ignorant of the complainant's mark, and that holding a domain for resale at market value is a recognized commercial practice that panels have consistently treated as legitimate – provided the registrant was not targeting the complainant specifically.

What counts as "targeting"? Panels look at the distinctiveness of the mark at registration, evidence that the registrant searched or tracked the complainant's brand, the pricing of any resale demand relative to market comparables, and the content of any communications between the parties. An investor who held a name for years and responded to an inbound inquiry with a market-priced counter is in a fundamentally different position from one who registered the name the day after a mark was published and immediately contacted the brand owner with a large-sum demand.

We handle both situations, but the advice differs. The first investor has a strong record to document. The second needs a careful assessment of whether a defense is viable at all – and if so, on what basis.

Related at COGNOMEN

• UDRP and ccTLD respondent defense – all zones and forums
• How to defend a .it domain acquired as an investment
• How to seek an RDNH finding – practitioner guide