How to prove a legitimate interest in your .group domain

A complaint lands in your inbox. A trademark owner claims your .group domain and demands a transfer under the UDRP. You registered the name because it describes your community, your consortium, or your business category – not to trade on anyone else's brand. The question is not whether you feel entitled to the domain. The question is whether you can prove a legitimate interest in a way a UDRP panel will accept.

To defend a .group domain under the UDRP, the 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 name, or a legitimate noncommercial or fair use without intent to mislead. The standard case runs about two months from filing to decision. Filing fees start at USD 1,500 at WIPO for a single-member panel, paid by the complainant – the respondent's cost is defense counsel only.

This page explains how the Paragraph 4(c) analysis applies in the .group zone, what evidence builds a winning legitimate-interest record, when an RDNH finding is realistic, and what the next step looks like.

Why .group disputes follow the UDRP – and why that matters for your defense

The .group new gTLD operates under standard ICANN-accredited registrar agreements, which means the UDRP governs all disputes, administered through WIPO, the Forum, CAC, or ADNDRC. A complainant who files against your .group domain must satisfy all three elements of Paragraph 4(a): confusing similarity to a mark, your lack of rights or legitimate interests, and bad-faith registration and use. All three must be proven. If any one element fails, the complaint fails.

That structure is the respondent's first line of defense. The burden of proving no legitimate interest is unusual: the complainant makes a prima facie showing, and the burden then shifts to the respondent to rebut. In practice, that means your evidence is what decides the case. A well-documented legitimate-interest record can stop the complaint at element two, without the panel ever reaching bad faith.

What makes .group a distinctive zone? The word "group" is inherently descriptive. It describes an organizational form – a consortium, a club, a professional association, a user community. Panels have consistently noted that generic or descriptive terms carry a weaker scope of trademark protection, and that a registrant who chose the term for its ordinary meaning rather than to target a specific brand stands on stronger ground. That does not mean the safe harbor is automatic. It means the factual record matters enormously.

If you have received a UDRP complaint against your .group domain, the 20-day response window begins the moment the case commences. To assess whether your registration supports a legitimate-interest defense, contact info@cognomenlaw.com now.

What are the three Paragraph 4(c) safe harbors, and which applies to your .group?

Paragraph 4(c) of the UDRP offers three non-exhaustive routes to establishing a legitimate interest; satisfying any one defeats element two of the complaint. Each has a different evidentiary profile, and the right one for your .group domain depends on how you have used the name.

Safe harbor one: bona fide offering before notice. If, before you received notice of the dispute, you were using the domain in connection with a genuine offering of goods or services – or demonstrably preparing to do so – that use qualifies. The critical word is "before." Panels look at the timing carefully. Evidence that you built a website, corresponded with customers, issued invoices, or published content under the domain name before the complaint was filed carries significant weight. Evidence assembled after the complaint arrives does not. We regularly advise registrants to pull together contemporaneous records: hosting logs, archived web pages, emails, contracts, and any other timestamped documentation of use prior to notice.

Safe harbor two: commonly known by the name. If your organization, community, or business is known by the term that forms the domain, you can rely on this safe harbor regardless of whether you hold a registered trademark. An incorporated association, a conference series, a consortium agreement, or even consistent online branding can establish that the registrant is "commonly known" by the name. This is particularly powerful for .group registrations, where the domain often serves as the online home of an actual group entity.

Safe harbor three: legitimate noncommercial or fair use. This route covers fan communities, commentary sites, nonprofit organizations, and similar uses where there is no intent to mislead consumers or tarnish the mark. The key caveat is that the use must not create a false commercial impression. A .group domain used for a genuine hobbyist or community forum, with no pay-per-click monetization and no attempt to impersonate the complainant, fits here.

Which safe harbor applies? In our practice, .group registrations most often fall under the first or second safe harbor. A descriptive-term .group used for an actual organization tends to combine both: the organization is known by the name, and it has been offering something under the domain before the dispute arose. A weak case is one where the domain was parked, the complainant's mark is widely known, and the registrant has no prior use or organizational connection to the term.

How do you build the legitimate-interest evidence record?

Building the legitimate-interest record is not about quantity of documents. It is about timing, consistency, and credibility. Panels assess whether the claimed use is genuine or constructed. The following categories of evidence carry the most weight in .group disputes.

Pre-notice use documentation. Web archive captures (Wayback Machine screenshots with dates), hosting provider invoices, domain registration history showing the date and the context of registration – these establish that the domain was put to use before the complaint. If you registered the .group for a membership organization, the founding documents of that organization, meeting minutes, and membership correspondence all belong in the record.

Commercial or organizational activity. Contracts, invoices, vendor agreements, social media accounts, press mentions, and event listings that reference the domain name show that real commercial or community activity is occurring under the name. The more external and independently verifiable these are, the better.

The registration rationale. A short, coherent account of why you chose this .group domain – the ordinary meaning of the term, the organizational function it serves, the absence of any knowledge of the complainant's mark at registration – is part of every strong response. Panels are not mind readers. Explain the intent in plain language, supported by whatever circumstantial evidence exists: industry publications, generic-term usage by others, comparable domain registrations.

Absence of trademark knowledge. If the complainant's mark is geographically remote, recently established, or used in a sector unrelated to yours, documenting that absence of knowledge is part of the legitimate-interest case and overlaps with the bad-faith rebuttal at element three.

In a recent matter (a .group domain dispute, spring 2025), we assembled a record of founding documents, archived newsletters, and pre-registration planning emails for a professional consortium. The complainant withdrew before the panel's decision, citing the strength of the respondent's evidence. That is a common outcome when the record is genuinely credible – a complaint that looked strong on paper collapses when the respondent's use is real and documented.

When is an RDNH finding realistic in a .group complaint?

Reverse Domain Name Hijacking – an RDNH finding – is the panel's conclusion that a complaint was brought in bad faith to deprive a legitimate registrant of a domain. The finding is reputational, not financial: there is no monetary award. But it is publicly recorded, and it matters, particularly to corporate complainants.

An RDNH finding is realistic in .group disputes when one or more of the following conditions exist. The complainant's trademark postdates the domain registration, making bad faith at registration impossible. The complainant knew or should have known that the respondent had a legitimate interest before filing. The complainant filed despite clear evidence of the domain's descriptive or organizational use. Or the complaint relies on a mark that is geographically or sectorally remote from the respondent's use, with no plausible argument for confusing similarity that a reasonable practitioner would endorse.

Panels do not make RDNH findings lightly. A complainant that had a colorable argument – even one that ultimately fails – generally avoids an RDNH finding. The standard requires something more: a complainant that knew or clearly should have known the complaint could not succeed. We have defended .group registrants in situations where the complainant's own trademark registration date told the whole story. If your .group was registered before the complainant's trademark was filed, that chronology is your strongest card, and an RDNH request belongs in the response.

If you believe the complaint against your .group domain is abusive – or if you want a read on whether an RDNH finding is realistic – email info@cognomenlaw.com for an assessment.

What evidence actually decides the outcome in .group UDRP panels?

The panel's decision in any .group case turns on a single question: does the overall record, viewed as a whole, show that the respondent has a plausible legitimate claim to the name? Evidence that answers yes to that question decisively wins element two. Evidence that leaves the panel guessing loses it.

Several fact patterns consistently decide cases in the respondent's favor. First, pre-dispute use that predates the complainant's mark. If the respondent began using the .group domain commercially or organizationally before the complainant's trademark was even registered, the bad-faith element cannot stand – and that same timeline often supports legitimate interest. Second, use consistent with the ordinary meaning of the term. A .group domain used by an actual group, consortium, or community carries a natural fit that panels recognize. Third, no monetization linked to the complainant's goods or services. Pay-per-click revenue streams that happen to generate links to the complainant's competitors – or, worse, directly to the complainant's category – are the most common evidence point that turns a marginal complaint into a successful one.

Conversely, evidence that tends to hurt the respondent: a domain that has been parked without genuine use; an offer to sell the domain at a price that exceeds registration costs, made early in the dispute; prior registration disputes on file; or a registration date that closely follows the complainant's trademark launch or product announcement in a way that looks opportunistic.

In a second matter we handled (a .group dispute in a European professional services context, autumn 2024), the respondent had registered the domain to serve a trade association whose name included the disputed term. The panel dismissed the complaint on element two alone, noting that the association's formation documents provided clear evidence of a bona fide use predating the complainant's notice by over a year.

How does the choice of forum affect your .group defense?

Because .group is a gTLD governed by ICANN-accredited registrars, the UDRP applies regardless of which forum the complainant chooses. The complainant selects the forum – WIPO, the Forum, CAC, or ADNDRC – and the respondent cannot change that selection. However, the choice of forum affects certain procedural features that matter in practice.

If the complainant chose WIPO and you as respondent prefer a three-member panel, you may request one. In that scenario, the parties generally split the higher three-member fee, with the respondent's share being the difference between the single-member and three-member panel fees. At WIPO, that means a single-member fee of USD 1,500 rises to USD 4,000 for a three-member panel; the respondent's contribution covers part of the difference. A three-member panel is worth requesting when the case is close, the amount at stake is substantial, or RDNH is a realistic outcome worth pursuing before a larger bench.

What if the complainant files the same underlying grievance in multiple zones – say, a .group domain and a national ccTLD? Those are separate proceedings under separate rules. A UDRP decision on the .group domain does not bind a ccTLD panel and does not automatically resolve a parallel .de or .uk dispute. In our practice, we handle these parallel-zone situations by coordinating the legitimate-interest record across filings so that the evidence in each proceeding reinforces rather than contradicts the other. This is one reason why early engagement matters: a response deadline is typically 20 days from commencement, and building a cross-zone record takes time.

The URS – a faster, cheaper remedy available for new-gTLD domains – is also theoretically applicable to .group. However, the URS standard is "clear and convincing" evidence of abuse, a deliberately higher bar than the UDRP's balance-of-probabilities approach. A complainant who expects a close fight on legitimate interest is unlikely to choose URS, because the higher standard favors the respondent. If you receive a URS filing rather than a UDRP complaint, the defense posture is similar but the timeline is compressed. For a detailed comparison of the two procedures, see our FAQ on URS versus UDRP.

Common myths about UDRP respondent defense – and the reality

The most persistent myth is that defaulting – not filing a response – is a viable strategy. It is not. When a respondent defaults, the panel decides on the complainant's papers alone. Default is not a neutral act; panels regularly note default as a factor, and the practical rate of transfer in default cases is substantially higher than in contested ones. Filing a response is almost always the right decision, even when the case feels difficult.

A second myth is that a generic or descriptive domain is automatically safe. Panels do not grant descriptive-term registrants a free pass. The complainant still gets to run the confusing-similarity argument – and in the .group zone, the second-level label is the key. If that label matches a well-known trademark, the first UDRP element will likely be satisfied regardless of the dictionary meaning of the word. The defense then shifts entirely to element two and element three.

A third myth is that RDNH findings are rare and not worth pursuing. The finding appears more often than practitioners once believed, particularly in cases where the complainant's trademark postdates the registration. It is worth requesting in any response where the factual predicate is present. The only cost is a paragraph or two in the response document – the upside is a permanent public record that the complaint was abusive.

For a broader look at how respondent defense and RDNH strategy work across gTLD disputes, see our respondent defense and RDNH practice page, and our alert on defending UDRP complaints in the era of AI-assisted filings.

Related at COGNOMEN

• Respondent Defense & RDNH – full practice overview, strategy, and RDNH pursuit across gTLDs
• Alert: defending a UDRP complaint when the complainant uses AI-assisted filings
• FAQ: URS vs. UDRP – which procedure applies to your new-gTLD domain?

Author: Anton Grant — Respondent defense and reverse domain name hijacking (RDNH). Meet the team.

Speak with Cognomen Law

For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter

Domain in disputeYour sideI want to recover a nameI received a complaint — I need a defensePortfolio / brand protectionWhat happenedEmailI agree to the processing of my enquiry as described in the privacy policy.Assess my case

No obligation. Confidential. We reply within two hours in business hours.

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.