Step-by-step: defend a generic-word .group domain

Step-by-step: defend a generic-word .group domain. UDRP and ccTLD domain recovery and defense across .group. Email the firm to assess your case.

A UDRP complaint lands in your inbox. The domain is a single common English word followed by .group – a term that describes an industry sector, a business category, or a commercial concept that dozens of entities share. The complainant owns a trademark. You registered the name because it matched your business, your investment thesis, or your legitimate commercial use. Now you have 20 days to respond or default.

Defending a generic-word .group domain under the UDRP requires satisfying the safe harbors in Paragraph 4(c) of the Policy: demonstrating a bona fide offering of goods or services before notice of the dispute, being commonly known by the name, or establishing legitimate noncommercial or fair use. The WIPO filing fee for a single-member panel begins at USD 1,500. Where a complaint is filed in bad faith against a clearly defensible registration, panels may issue a Reverse Domain Name Hijacking (RDNH) finding. This guide follows the five steps a registrant must take to mount a credible defense in a .group UDRP proceeding.

The five steps below trace the decision a respondent makes at each stage – and the trap concealed inside it.

Step 1: What rules govern a .group domain dispute, and why does that matter?

The .group extension is a new generic top-level domain operated under ICANN's second expansion program. Like all new gTLDs, .group is subject to the UDRP and ICANN's Rules for Uniform Domain Name Dispute Resolution Policy – the same Policy that applies to .com, .net, and .org. The forum of first resort is typically WIPO or the Forum; both are ICANN-accredited providers for new gTLDs.

Why does this procedural baseline matter? Because the applicable zone determines which rules, which forum fee schedule, and which filing infrastructure apply. A .group complaint proceeds identically to a .com complaint in structure: all three UDRP elements under Paragraph 4(a) must be proved by the complainant. The complainant must show (1) confusing similarity to a mark, (2) absence of respondent rights or legitimate interests, and (3) registration and use in bad faith – both limbs, cumulatively.

The trap in Step 1: some registrants assume that because .group is a newer, less mainstream zone, the complaint carries less weight or fewer procedural resources. That assumption is wrong. WIPO administers .group disputes under identical procedural rules to .com. The respondent's deadline, filing requirements, and evidence obligations are the same. Miss the 20-day response window and a default occurs – meaning the panel decides on the complainant's submissions alone.

The zone choice does, however, carry one practical implication. Generic-word .group domains often attract complaints from complainants whose marks are descriptive or weak – precisely because the registrant's legitimate use of a common term is more credible in a zone that signals a sector or group affiliation. That dynamic is a defense asset, discussed in Step 3.

If you have received a UDRP complaint on a .group domain, the response deadline is firm and cannot be extended by inaction. For an assessment of your domain dispute, contact info@cognomenlaw.com.

Step 2: What are the Paragraph 4(c) safe harbors, and how do you build the legitimate-interest record?

The most decisive element in a generic-word .group defense is typically the second UDRP element: whether the respondent has rights or legitimate interests in the domain. Because the complainant must prove absence of such rights, the respondent's task is to raise a credible case that at least one of the Paragraph 4(c) safe harbors applies. The panel then shifts the burden back to the complainant.

Three safe harbors are available under Paragraph 4(c):

• Bona fide offering – Before notice of the dispute, the respondent used or demonstrably prepared to use the domain in connection with a genuine offering of goods or services that is not itself an attempt to profit from the complainant's mark.
• Commonly known by the name – The respondent is an individual, business, or entity commonly known by the domain name, regardless of trademark rights.
• Legitimate noncommercial or fair use – The respondent uses the domain without intent for commercial gain by misleadingly diverting consumers or tarnishing the complainant's mark.

For a generic-word .group domain, the first and third safe harbors are usually the most relevant. Common English words – "capital," "alliance," "venture," "media," "legal," and similar terms – appear routinely in business names. A registrant who registered alliance.group to anchor a network of allied businesses, or capital.group to identify a holding vehicle, operates in a conceptual space that is plainly not the exclusive property of any single trademark owner.

Building the record is the hard work. Evidence that consistently supports a legitimate-interest finding includes: a business registration predating the complaint, a website or landing page operational before the respondent received notice of the dispute, correspondence showing the domain was offered internally as a business address, invoices or contracts using the name, or documented preparation steps such as wireframes, hosting records, or registered business names. The key word is before: the timing of each piece of evidence relative to notice of the dispute is scrutinized closely.

The trap in Step 2: registrants frequently underestimate what "before notice" means. Notice is deemed to occur when the registrar formally notifies the respondent of the complaint commencement – not when the complainant sends a cease-and-desist, but not necessarily later than that either. A registration followed immediately by a parking page with pay-per-click links connected to the complainant's industry will undermine even a genuinely generic-word defense. The parking configuration matters as much as the dictionary definition of the word.

How do you assess the strength of your generic-word defense before drafting the response?

Strength assessment comes before drafting. A weak response filed in haste can concede points that a carefully constructed filing would have held. In our practice, we conduct a structured pre-response audit covering four dimensions: the trademark record, the domain's history, the content history, and the complainant's conduct.

On the trademark record: how old is the complainant's mark? Is it registered or only asserted at common law? Does it cover only one jurisdiction? A mark registered after the domain was created cannot form the basis for a bad-faith registration finding – panels have consistently held that a respondent cannot have acted in bad faith toward a mark that did not exist at the point of registration. For a generic word, the complainant may hold a trademark of the same term but that does not displace all others' rights to use the ordinary word commercially.

On domain history: when was the domain registered? By whom – the current registrant, or a prior holder? What was the resolution record? WHOIS/RDDS history and the Wayback Machine are the first sources. A prior period of passive holding may raise a question; a history of clear legitimate use resolves it.

On content: what does the domain resolve to today, and what did it resolve to during the registration history? Screenshots, cached pages, and hosting records give the panel the content timeline it needs. Pay-per-click links that generate revenue from clicks connected to the complainant's sector are a recurring bad-faith indicator – even where the underlying word is generic.

On complainant conduct: did the complainant send a demand letter before filing? What did they offer or threaten? In a small number of matters in our respondent practice, the demand letter itself reveals overreach – an attempt to acquire a domain for below-market value by threatening litigation – which is relevant to a potential RDNH claim.

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

Step 3: When is a Reverse Domain Name Hijacking finding realistic in a .group case?

Reverse Domain Name Hijacking – a panel finding that the complainant brought the complaint in bad faith to deprive a legitimate registrant of the domain – is available in any UDRP proceeding. It carries no monetary penalty but produces a published, public finding of abuse against the complainant's name. In our respondent-side practice, we regularly advise registrants who hold defensible generic-word domains and face complaints that are, on analysis, driven by acquisition strategy rather than genuine trademark injury.

Panels have consistently held that RDNH is most warranted where the complainant: (a) knew or should have known it could not succeed on the merits; (b) brought the complaint primarily to use the UDRP as a tool to obtain a domain it could not afford to purchase; or (c) filed without adequate investigation of the respondent's legitimate use. A complainant who holds a descriptive or geographically limited trademark for a word that functions as a common commercial descriptor, yet files a UDRP against a registrant with visible legitimate use, is in a structurally precarious position.

For generic-word .group domains specifically, the argument is frequently available. The .group extension itself signals a category or organizational concept, not a brand. A trademark owner who claims exclusive rights over a common word in a zone that by design connotes sector identity is, at minimum, overreaching. That overreach is the foundation of a credible RDNH argument.

The trap in Step 3: RDNH is not automatic. It requires an affirmative request in the response and a factual record that supports the conclusion. Panels rarely grant RDNH where the complainant's case, even if unsuccessful, was colorable. The request must be grounded in the specific conduct – the strength (or weakness) of the trademark, the pre-filing investigation, and the evident purpose of the filing. Generic assertions of bad faith in the response will not move a panel.

In a recent matter – a new-gTLD generic-word dispute, summer 2025 – we secured an RDNH finding for a respondent who had held a single-word .group domain since early in the zone's availability, used it consistently as a business identifier, and faced a complaint filed by a mark holder whose registration postdated the domain by more than a year. The panel found the complainant knew of the registration timeline before filing.

Step 4: What evidence decides the outcome, and how do you present it?

Evidence in a UDRP proceeding is filed as annexes to the response, without live testimony or cross-examination. The panel reads the written record only. Presentation clarity directly affects persuasion. Each annex should be labeled, paginated, and cross-referenced to the specific paragraph of the response where it is relied upon.

The evidence that most frequently decides a generic-word defense in favor of the respondent includes:

• Business registration or incorporation documents predating the complaint – ideally predating the complainant's trademark filing date as well.
• Operational records for the domain: hosting invoices, DNS configuration history, screenshots of a working website with dated metadata, email headers showing the domain in active commercial use.
• Communications predating the dispute that reference the domain as a business identifier – internal emails, proposals, or client contracts.
• Evidence of the generic nature of the word: dictionary definitions, third-party registrations of similar strings in other zones, evidence of industry-wide use of the term.
• Evidence of the complainant's trademark scope and limitations: narrow geographic scope, limited goods or services specification, registration dates.

On the complainant's side, the evidence that harms the respondent most is: a parking page history with pay-per-click links on the complainant's terms, a WHOIS history showing multiple registrant changes in a short period (suggesting trading), and any prior demand or offer by the respondent to sell the domain at an above-cost price to someone who appears to be a brand owner.

The trap in Step 4: respondents sometimes include too much evidence without prioritizing. A panel working through a large annex set without clear cross-referencing may simply miss the decisive exhibit. One clean screenshot, properly dated and labeled, outweighs ten undated PDF downloads. Quality of presentation is a competency signal.

We have defended .group and other new-gTLD registrations by building the evidence record before drafting the response – not simultaneously. In a mid-2025 matter involving a descriptive-term .group domain in the professional services sector, the response annex set ran to eleven exhibits, each cross-referenced to the specific UDRP element it addressed. The transfer was denied.

Step 5: What is the realistic next step after filing the response?

After the respondent files the response within the 20-day window, the case moves to panel appointment. For a single-member panel at WIPO, the appointment and decision phase typically results in a case concluded within approximately two months of filing. Either party may request a three-member panel; if only the respondent requests three members, the respondent generally pays the cost difference – meaning the panel fee rises to USD 4,000 at WIPO for a three-member tribunal.

When should the respondent request a three-member panel? In a high-stakes generic-word dispute where the trademark is genuinely arguable and the respondent has invested significantly in the domain, the broader deliberation of a three-person panel may reduce variance. In a case where the respondent's legitimate-interest record is very strong and an RDNH finding is being sought, a single panelist may be equally appropriate. The decision should be made on the facts, not on principle.

After the decision: if the panel denies the complaint, the domain remains with the registrant and the registrar lock imposed at the outset of the proceeding is removed. There is no further appeal within the UDRP system. The complainant may, however, seek review in a court of competent jurisdiction within a statutory period. If that risk is material – for example, if the complainant is a sophisticated brand owner with deep resources – the respondent should consider what further protective steps are appropriate.

If the panel orders transfer: the registrar implements the transfer after a 10-business-day waiting period, during which the respondent can seek a court stay of the transfer. That window is narrow. Any intention to seek judicial review must be acted on immediately.

One cross-zone note: if the same complainant also holds a .com or ccTLD claim on the same name, a separate proceeding in each zone is required. A UDRP decision on a .group domain does not bind a subsequent panel on a .com complaint covering the same mark and registrant. We regularly advise clients on coordinated multi-zone defense strategy where the exposure extends beyond a single extension.

Related at COGNOMEN

• UDRP respondent defense and RDNH – services and process overview
• How to defend an investment domain in an online UDRP proceeding
• Recovering a lapsed domain: strategy and analysis in the .tv zone