How to defend a .group domain against a UDRP complaint

How to defend a .group domain against a UDRP complaint. 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 .group registration you use for a trade association, a professional network, or a community of shared interest. The complainant holds a trademark containing the same word. You have 20 days to respond once the case commences – and if you do nothing, a default transfer is the likely result.

To defend a .group domain against a UDRP complaint, a respondent must address all three elements of Paragraph 4(a) of the Policy and, where the facts support it, affirmatively demonstrate a legitimate interest under Paragraph 4(c). The .group extension is a new gTLD operating under the standard UDRP, administered before WIPO, the Forum, or another ICANN-accredited provider; the same rules that govern .com disputes apply here. The realistic defenses – generic or descriptive use, a bona fide offering before notice, being commonly known by the name, or legitimate noncommercial use – are well-settled in the consensus case law.

This page covers the governing rules, the Paragraph 4(c) safe harbors, the evidence that decides outcomes, how an RDNH finding works, the cost structure, and how to start.

What makes .group disputes different – and what stays the same

The .group extension is a generic top-level domain delegated in the second wave of new gTLDs; its registry operates under a standard ICANN Registry Agreement that incorporates the UDRP by reference. That means a complainant filing against your .group domain has precisely the same procedural path as one filing against a .com: complaint to WIPO or the Forum, a 20-day response window, a single-member or three-member panel, and a decision in roughly two months.

What can differ is the factual framing. The word "group" carries a strong generic and descriptive weight in English and in many other languages. A registrant who chose a .group domain for an industry consortium, a community organization, or an affinity network often has an argument that the name is used in a way that bears no targeted relationship to the complainant's mark. That factual distance matters more in .group than it does in, say, a .brand extension. Panels have consistently held that where the second-level string is the trademark itself but the use is generic or descriptive, a respondent may build a credible legitimate-interest record.

The extension does not insulate a registration, however. A respondent who registered the domain after the complainant's mark became well-known, and who points it at a landing page monetizing the mark's goodwill, will face the same analysis as a .com cybersquatter.

What do the three UDRP elements mean for a respondent?

A complainant must win on all three elements of Paragraph 4(a) to obtain a transfer order; a respondent wins by defeating any one of them. Understanding the architecture of the Policy is the first step in deciding where your defense is strongest.

The first element – confusing similarity – is largely a mechanical comparison between the domain's second-level string and the complainant's trademark. Respondents rarely defeat this element alone, but where the second-level string is a common dictionary word rather than a distinctive mark, the analysis can work in your favor: panels have noted that generic terms create a weaker similarity finding that affects the overall assessment.

The second element – no rights or legitimate interests – is where most defenses are built. The complainant bears the formal burden, but panels have settled on a shifting framework: once the complainant makes a prima facie case, the respondent must come forward with evidence. That evidence lives in the Paragraph 4(c) safe harbors described in the next section.

The third element – bad faith registration AND use – is conjunctive. Both limbs must be satisfied. If you registered the domain before the complainant's mark was filed, or if you had no knowledge of the complainant at the time of registration, the "registered in bad faith" limb often fails. In our practice, we regularly advise respondents to start by documenting precisely when they registered the domain and what they knew then – because a well-documented registration story frequently ends the analysis at the third element.

If you have just received a UDRP complaint against a .group domain and are unsure which element gives you the strongest ground, contact info@cognomenlaw.com for an assessment.

How do the Paragraph 4(c) safe harbors apply to a .group registration?

Paragraph 4(c) of the UDRP lists three circumstances that, if demonstrated, are sufficient to establish a legitimate interest – and each has a specific application to the typical .group use case.

The first safe harbor is a bona fide offering of goods or services before any notice of the dispute. For a .group registrant, this typically means showing that the domain was in active, genuine use – a community platform, a membership directory, a conference organizer, a trade body – before you received any cease-and-desist or the UDRP complaint itself. Panels look for contemporaneous evidence: screenshots with dates, server logs, membership records, emails to members, promotional materials. The earlier and more consistent the evidence, the stronger the argument.

The second safe harbor is being commonly known by the domain name. This applies when the registrant's own name, trade name, or organizational name corresponds to the domain. A professional group that operates as "Vertex Group" and registers vertex.group has a strong argument under this limb, provided it can show the name was actually used in commerce or organizational activity before the dispute.

The third safe harbor is legitimate noncommercial or fair use without intent to mislead or tarnish. Fan communities, advocacy groups, and public-interest organizations have relied on this ground. The critical qualifier is intent: the use must not be designed to divert consumers or damage the mark owner. A community forum that discusses topics adjacent to a brand – rather than imitating the brand's commercial offering – often satisfies this standard.

In practice, we have defended .group registrations by combining two safe harbors: demonstrating a bona fide offering through documented organizational activity while simultaneously showing the registrant's entity had been commonly known by the name before registration. That combination is harder for a panel to dismiss than a single ground alone.

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

Reverse Domain Name Hijacking is a formal finding by a UDRP panel that the complaint was brought in bad faith to deprive a legitimate registrant of a domain. It is available under the Policy itself and requires no separate action by the respondent – a panel may make the finding on its own motion, though a respondent's explicit request and argument substantially increases the likelihood.

An RDNH finding carries no monetary penalty. What it does carry is reputational weight: the decision is published, attributed to the complainant, and permanently searchable in the relevant forum's database. For a brand owner or a law firm that files abusive complaints, a public RDNH finding is a genuine deterrent.

What circumstances justify seeking RDNH? Panels have found RDNH where the complainant filed knowing the respondent had a clear legitimate interest; where the complaint was filed to pressure a sale at below-market price; where the complainant misrepresented material facts in the complaint; or where the trademark rights relied upon were acquired after the domain was registered and the complainant must have known this. The last scenario is particularly relevant to .group registrations: a domain registered years before the complainant's trademark was filed is a strong RDNH signal if the complainant proceeded anyway.

We have sought RDNH findings in matters where the trademark filing post-dated the domain registration by a significant margin and the complaint advanced a confusing-similarity argument that could not survive basic scrutiny. In a recent matter – a .group community domain, spring 2025 – we secured both a denial of the transfer and a formal RDNH finding after demonstrating that the complainant's mark was registered more than three years after our client's domain.

To assess whether the facts of your .group case support an RDNH argument, email info@cognomenlaw.com.

What evidence actually decides the outcome?

The response window is 20 days. That is the time available to locate, organize, and present every piece of evidence that supports the three Paragraph 4(c) grounds. What panels find decisive varies by fact pattern, but certain categories appear repeatedly in well-reasoned defense decisions.

Registration-date documentation is foundational. A registrar-confirmed WHOIS history, a first-seen archive record, or the original registration confirmation email establishes when you took the domain – and whether that date precedes the complainant's trademark filing, first use, or first significant public exposure. This is not optional evidence; it is the base layer of the entire defense.

Contemporaneous use evidence is almost equally important. For .group domains, this means records of organizational activity: founding documents, membership communications, event listings, website snapshots with date metadata, social-media accounts associated with the name, and any external press coverage. The more of this that predates the dispute, the harder it is for a panel to find no legitimate interest.

The complainant's own conduct can also become evidence. If the complainant waited years before filing – during which time you operated openly under the name – that delay is relevant to the bad-faith analysis. Panels have noted that a complainant's long tolerance of a domain registration weighs against a finding that the domain was registered to target the mark. Similarly, if the complainant sent an unsolicited purchase offer before filing the UDRP, that correspondence belongs in the response.

What panels find unhelpful: bare denials without supporting documentation, post-filing website changes designed to construct a use record after the fact, and arguments that are legally correct in the abstract but unsupported by any evidence specific to the registrant. A response that tells a documented story beats one that argues the law.

How do .group UDRP costs split?

The UDRP filing fee is paid by the complainant. For a single-domain case before WIPO with a single-member panel, the current filing fee is USD 1,500. For a three-member panel, the complainant pays USD 4,000. There is no separate filing fee for a respondent who answers before a single-member panel.

If you, as respondent, request a three-member panel, the panel fee increases to USD 4,000 and the parties generally split the difference between the single- and three-member rates. That portion falls on the respondent. A three-member panel may be worth the cost when the case presents a genuinely close legal question or when you believe you need the additional scrutiny of three panelists to defeat a well-resourced complainant.

Legal fees for a UDRP defense are separate from the forum's fees. Market rates for respondent defense on a straightforward case run in a comparable range to complainant-side work; the complexity of the evidence assembly and the strength of the RDNH argument affect the time required. We do not combine our fee with the forum's; both are presented separately and transparently.

The right route depends on the facts. Where the domain is a .group with clear organizational use and a pre-filing registration date, a single-member panel at WIPO or the Forum is often the most efficient path. Where the complainant has aggressive outside counsel or the case involves a genuinely close fair-use question, the broader review of a three-member panel can justify the additional cost. And if the .group domain dispute is connected to a parallel .com or national-extension dispute, coordinating the two proceedings early – rather than letting them run on separate tracks – is usually the more cost-effective approach.

Cross-zone considerations: when a .group dispute runs alongside other extensions

A complainant who is serious about recovering a name rarely files against a single extension in isolation. In our practice, we regularly advise registrants who face parallel UDRP complaints covering both the .group and a legacy extension – typically .com or .net – filed simultaneously or in short sequence. That scenario requires coordinated strategy.

Under the UDRP, a single complaint may cover multiple domains only when the registrant of record is the same holder. A complainant who files two separate complaints, one per extension, creates two separate records and two separate timelines. Evidence assembled for the .group response can and should be used in the parallel proceeding, but the arguments sometimes need to be tailored: a generic-use defense that works for .group may not carry the same weight for a .com where the second-level string is more distinctive.

Where the dispute also implicates a ccTLD – a .uk, .eu, or national extension – the governing rules change entirely. Nominet's DRS for .uk uses a different test: "abusive registration," read as registration or use that takes unfair advantage of the complainant's rights. That conjunctive-versus-disjunctive difference matters. The EURid procedure for .eu has its own eligibility rules. We address those procedures at the links below. If your .group dispute sits alongside a Nominet DRS matter, the two files should be managed in parallel but not conflated; the evidentiary standards differ.

In a recent matter – a coordinated .group and .co complaint, autumn 2024 – we defended both extensions in simultaneous proceedings, using a unified legitimate-interest record but advancing forum-specific arguments on the bad-faith element. Both complaints were denied. The respondent held both domains on the same organizational basis, and the complainant's trademark filing post-dated both registrations.

What happens if you do nothing?

A default – failing to file a response within the 20-day window – does not automatically result in a transfer. A panel in a default case is still required to assess whether the complainant has met its burden on all three elements. Panels do not treat default as admission.

In practice, though, the risk of default is real. Without a response, the panel sees only the complainant's version of the facts. It has no evidence of the registration date, the organizational use, the pre-dispute conduct, or any of the Paragraph 4(c) grounds. A panel making reasonable inferences from the complaint alone will almost always find for the complainant in a well-pleaded cybersquatting case.

What about seeking an extension? Under the standard UDRP Rules, extensions of the response deadline are granted in limited circumstances and require a request to the provider before the deadline expires. A request made on day 19 is not impossible, but panels and administrators scrutinize late extension requests. If there is any prospect of defending the domain, the decision to engage counsel should happen within the first week of commencement – not in the final days.

The AUDIENCE_MYTH we encounter most often is that a UDRP complaint is automatically a trademark enforcement tool that respondents have no real power to contest. That is not accurate. The Policy was designed with the respondent's rights in mind. Paragraph 4(c) exists precisely to protect legitimate registrants. In our experience, respondents who build a documented legitimate-interest record and submit a complete response win at rates that reflect the genuine balance in the Policy's design.

Related at COGNOMEN

• Respondent defense and RDNH across gTLD and ccTLD zones
• Responding within the UDRP deadline in finance-sector disputes
• National dispute procedures: the Nominet DRS for .uk domains analyzed