Prove a legitimate interest in your .net domain: what panels actually…

Prove a legitimate interest in your .net domain: what panels actually. UDRP and ccTLD domain recovery and defense across .net. Email the firm to assess your ca…

A UDRP complaint lands in your inbox. The complainant is a trademark holder. You registered the domain years ago, you have used it commercially, and you believe the registration was entirely legitimate. The question is not whether you think you have a right to the name. The question is whether a panel, applying the specific tests under the Policy, will agree.

To prove a legitimate interest in your .net domain under the UDRP, a respondent must satisfy at least 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 a legitimate noncommercial or fair use. The complainant carries the initial burden, but once a prima facie case is made, the respondent must come forward with concrete evidence. A standard case is decided within roughly two months of filing; the respondent has 20 days from commencement to file a response.

This article examines what the safe harbors actually require in .net disputes, how panels weigh the evidence respondents put forward, where the consensus view ends and the genuine splits begin, and when a finding of Reverse Domain Name Hijacking becomes a realistic outcome.

Why .net is governed by the UDRP and what that means for respondents

.net is an accredited gTLD subject to the UDRP in full. Every .net registrar is contractually bound by ICANN to apply the Policy. That means the same three-element test applies to your .net name as applies to a .com or .org dispute. The respondent cannot point to a separate .net-specific rule set; the framework is identical.

This matters because some registrants assume that .net — traditionally associated with network operators and infrastructure providers — carries a presumption of technical legitimacy. Panels do not apply that presumption. What panels apply is the text of Paragraph 4(a) and the Paragraph 4(c) safe harbors, without any TLD-level softening for .net. A respondent holding a .net name for infrastructure purposes, ISP services, or technology development is no better positioned at the outset than a respondent holding the equivalent .com — unless the respondent builds an affirmative record. Building that record is the work.

The burden structure is worth understanding precisely. The complainant must first establish a prima facie case that the respondent has no rights or legitimate interests. Once that showing is made, the evidentiary burden shifts: the respondent must affirmatively demonstrate a right or legitimate interest. The shift is informal in the UDRP sense — panels call it a "burden of production" rather than a full persuasion burden — but the practical consequence is that a respondent who files a bare denial will almost certainly lose the second element.

In our practice, respondents who contact us after receiving a complaint frequently underestimate this shift. They focus on what they believe to be true about their own registration, rather than on what they can document in a way that persuades a panelist reading the submission cold. The distinction is everything.

For an assessment of your domain dispute, contact info@cognomenlaw.com.

What are the Paragraph 4(c) safe harbors, and what does each require?

Paragraph 4(c) of the UDRP identifies three non-exhaustive circumstances that, if demonstrated by the respondent, establish a legitimate interest. Each safe harbor has a distinct factual profile and carries distinct evidentiary demands.

Safe harbor one: bona fide offering before notice

The first safe harbor — a bona fide offering of goods or services before notice of the dispute — is the most commonly invoked and the most thoroughly analyzed in panel decisions. The key phrase is "bona fide." Panels do not treat all commercial use as equivalent.

What does "bona fide" exclude? It excludes use that is designed to exploit the complainant's trademark. A respondent operating a pay-per-click parking page that serves ads competing directly with the trademark holder's products is unlikely to succeed under this safe harbor, even if the page existed before the complaint was filed. The question is whether the commercial activity is genuinely directed at a space the respondent developed independently, or whether the domain's value derives from the trademark association itself.

What does "bona fide" include? A respondent operating a legitimate business under the domain — an actual service, a product line, a subscriber base, verifiable revenue — and who can document that operation with invoices, screenshots, contracts, or customer communications, stands on solid ground. The temporal requirement matters too: the offering must predate notice of the dispute, which panels typically read as the date the complaint was filed, not the date the registrant first became aware of the trademark.

In a recent matter involving a .net domain held by a small-business technology operator (spring 2025), we assembled invoices, server logs, and client agreements spanning approximately four years before the complaint date. The panel found a bona fide offering and denied the transfer. The complainant had registered its mark after the respondent's domain registration — a fact that also bore on the bad-faith element.

Safe harbor two: commonly known by the name

The second safe harbor — being commonly known by the domain name — requires more than a self-serving declaration. Panels look for external corroboration: business registrations, trade name filings, press coverage, customer invoices issued under the name, or other documentation showing that the respondent's business or personal identity is associated with the term prior to the dispute.

This safe harbor is frequently invoked by respondents who operate under the domain as a trade name but who have not registered a trademark. That is not fatal. Panels have consistently held that a registered trademark is not required; what is required is that the respondent is genuinely known by that name in commerce or to a relevant audience. Unregistered or common-law rights in the name — demonstrated through use, not assertion — satisfy the safe harbor.

Where respondents fail here is in offering the panel nothing but a claim. A declaration saying "I have been known by this name since 2017" is not evidence. It is an assertion. What turns the assertion into evidence is the attached exhibit: the business license issued in that name, the domain registration history, the website screenshots archived over time through third-party crawlers, the customer correspondence using the name.

Safe harbor three: legitimate noncommercial or fair use

The third safe harbor — legitimate noncommercial or fair use — covers a narrower factual category but is directly relevant to respondents operating commentary sites, fan sites, criticism pages, or genuinely noncommercial community projects. The critical word is "legitimate." Use that misleads consumers as to the source or sponsorship of the site does not qualify, even if the respondent generates no revenue.

For .net domains, this safe harbor is most relevant in contexts where the domain name corresponds to a descriptive or generic term that the complainant has trademarked. A respondent operating an informational or community site about, for example, a type of technology protocol, a geographic feature, or a common noun does not require permission from a trademark holder who later registered the phrase. The respondent must demonstrate the noncommercial character of the use and the absence of misleading suggestion — and must do so with evidence of the site's actual content and history.

How do panels weigh the respondent's evidence in practice?

Understanding the safe harbors is necessary. Knowing how panels actually evaluate the evidence respondents submit is what decides cases. The consensus view across panels is that the quality of evidence matters more than its volume, and that contemporaneous documentation — records that existed at the relevant time, not assembled for litigation — carries the highest weight.

Panels have consistently held that a respondent's own declaration, without supporting exhibits, carries little weight. Conversely, a modest submission supported by bank records, registration certificates, archived web pages, and third-party communications can be decisive even against a large complainant. The asymmetry of credibility between third-party documentation and self-serving assertion is the single most important practical reality for respondents to internalize.

What do panels treat with skepticism? Website screenshots taken after the complaint was filed and not independently verified. Domain use that begins only after the respondent receives the complaint. Claims of business plans or intended uses that were never documented before the dispute. Registration of a domain containing a well-known mark with no plausible generic or descriptive rationale. Passive holding without any demonstrated use — combined with an implausible account of future plans.

What do panels credit? Archived web pages from third-party services showing consistent use before the dispute. Revenue records, even modest ones, tied to the domain. A business entity registration predating the complainant's trademark. Customer testimonials or third-party references to the respondent under the domain name. Correspondence showing the respondent was conducting its business through the domain in the normal course.

The minority view — and it is a genuine minority — holds that passive holding of a domain incorporating a descriptive or generic term can, in certain circumstances, constitute a legitimate interest in its own right, on the theory that a registrant need not actively develop every name it holds. The consensus position rejects that argument for domains that overlap with a registered trademark; panels require some demonstrable connection between the respondent and the name.

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

Building the legitimate-interest record: what to include in a respondent submission

A respondent submission that succeeds in a .net UDRP defense is not a narrative. It is an organized evidentiary record with a clear legal argument. The structure that works consistently has three components: the factual chronology, the legal analysis, and the exhibit package.

The factual chronology establishes the timeline: when the domain was registered, when any business or project associated with it was started, when commercial use began, and when the complainant's trademark rights came into existence. Where the respondent's registration predates the trademark, this alone can be decisive — it is difficult, though not impossible, to argue that a registrant targeted a mark that did not yet exist. Where the trademark predates the registration, the chronology must instead demonstrate what the respondent's purpose was at the moment of registration and why it was not directed at the trademark.

The legal analysis applies the Paragraph 4(c) safe harbors to the respondent's facts. It identifies which safe harbor applies, explains the factual basis for that safe harbor, and addresses — rather than ignores — the complainant's strongest arguments. A submission that does not engage with the complainant's evidence signals to the panel that the respondent cannot answer it.

The exhibit package is the foundation. We advise respondents to include, at minimum: the domain registration record; any business entity documents issued under the relevant name; screenshots from the Wayback Machine or equivalent archived sources showing the domain's use at intervals before the dispute; any commercial documentation — invoices, contracts, terms of service — issued under the domain; and, where relevant, correspondence showing the respondent's name or business predating the trademark.

One common error: respondents submit a large exhibit package without explanation, assuming the panel will find the relevant material. Panels have limited time. The submission should direct the panel specifically to each exhibit and explain its relevance in a sentence or two. Evidence that is not explained is evidence that may not be weighed.

When is an RDNH finding realistic, and what does it achieve?

Reverse Domain Name Hijacking — a panel finding that the complaint was brought in bad faith to deprive a legitimate registrant of a name — is a genuine outcome in cases where the complainant's conduct reflects an abuse of the UDRP process. It is not, however, a routine finding, and respondents who expect it automatically when they win are regularly disappointed.

Panels have consistently found RDNH where: the complainant knew or should have known it could not succeed, typically because the respondent's registration clearly predated the trademark; the complaint was filed with a coercive motive — particularly after an offer to purchase the domain was refused; or the complainant's submission contained demonstrably false factual claims about the respondent's registration or use.

What RDNH achieves is reputational, not financial. The UDRP provides no monetary penalty, no costs award. A finding of RDNH appears in the decision record, which is public. For large brand owners with active enforcement programs, an RDNH finding carries real consequences: it signals to future panels and to the industry that the complainant has used the system abusively. For respondents who are domain investors or industry participants, an RDNH finding on the record can matter defensively in future proceedings.

In a matter we handled involving a .net domain held by a domain investor (autumn 2024), the complainant had offered a modest acquisition price, been declined, and then filed a UDRP complaint approximately three weeks later. The investor had held the name for over a decade, with a clear registration predating the complainant's trademark by years. The panel denied the transfer and found RDNH — identifying the post-rejection filing as the decisive indicator of bad faith. The investor's prior documentation of the offer and rejection was critical evidence.

When is RDNH not realistic? Where the complainant had a plausible, good-faith case even if it lost on the merits. A complainant who files on a close call — a domain that genuinely might be confusingly similar to a mark, with ambiguous use evidence — is not filing in bad faith merely because it fails. Panels require more than a loss to find RDNH; they require an inference that the complainant knew it had no case or filed for an improper purpose.

How does the .net analysis compare across zones and forum choices?

Because .net is a UDRP-governed gTLD, the legal test is the same regardless of whether the respondent files at WIPO, the Forum, CAC, or ADNDRC. The procedural and evidentiary rules are set by the UDRP and the UDRP Rules, not by the forum. The choice of forum affects case management style and potentially the pool of panelists, but not the applicable standard.

The contrast with ccTLD procedures is significant. For a .uk domain, the Nominet DRS applies a different standard: the complainant must show an "abusive registration," reading "registered OR used" abusively — a lower cumulative bar than the UDRP's "registered AND used in bad faith." A respondent defending a .uk name who loses on the UDRP standard might still succeed under the Nominet test if the original registration was in good faith, even if subsequent use became problematic. The distinction is not academic; we regularly advise clients holding parallel .net and .uk names who face complaints on both fronts simultaneously.

For .eu domains, the procedure is administered through the Czech Arbitration Court's ADR.eu platform. The complainant may rely on a broader set of "rights" than registered trademarks alone, and the remedy may be revocation rather than transfer where the complainant lacks EU eligibility. A respondent who might succeed in a .net UDRP defense on legitimate-interest grounds could face a different analysis in a parallel .eu proceeding.

For .de, there is no administrative dispute procedure. Disputes proceed through the German courts. DENIC offers a DISPUTE entry — a registration block preventing transfer — while a court action proceeds, but the dispute resolution itself requires litigation. Respondents with .net and .de registrations in parallel should anticipate entirely separate proceedings, different legal standards, and different costs.

The practical choice for a .net respondent is almost always among the four UDRP-accredited forums. WIPO and the Forum together account for roughly 97% of all UDRP proceedings. Forum selection is worth considering, but the decisive variable is the strength of the respondent's evidentiary record — not the forum.

What the objection about "sophistication" misses

A persistent myth among respondents — particularly domain investors — is that holding a domain with commercial purpose automatically exposes them to a bad-faith finding, or that panels are structurally hostile to portfolio registrations. Neither is accurate.

Panels have consistently recognized that domain investing is a legitimate commercial activity. Buying and holding generic or descriptive domain names for resale is not inherently bad faith. What panels examine is the specific purpose of the specific registration: was this domain registered because it corresponds to a generic or descriptive term the respondent values commercially, or because it corresponds to a trademark the respondent was targeting? The answer to that question is in the evidence — or its absence.

The objection that "panels always favor complainants" conflates the outcome distribution with structural bias. A significant proportion of UDRP cases settle or result in default before a decision is reached, which skews published outcomes. Among contested cases, respondents who file a substantive, evidence-backed submission succeed at rates that reflect the genuine merits of their position. The Policy is not the complainant's automatic ally — it is a test, and respondents who meet it win it.

Where the objection has some basis is in cases where respondents default — filing no response at all. A default does not automatically result in transfer, but panels examining an unanswered complaint are limited to the complainant's record. Substantive rights that are never asserted are not found by panels acting on limited information.

Related reading on legitimate-interest strategy across national procedures: Proving legitimate interest in a .fr domain: the SYRELI and PARL EXPERT analysis.

Related at COGNOMEN

• UDRP respondent defense and RDNH: keep your domain and pursue a hijacking finding
• Legitimate interest in a .fr domain: how SYRELI and PARL EXPERT differ from the UDRP
• Domain acquisition with escrow: a worked example from a .pl cross-border transaction