Step-by-step: defend a .group domain registered before the complainan…

Step-by-step: defend a .group domain registered before the complainan. UDRP and ccTLD domain recovery and defense across .group. Email the firm to assess your…

A trademark application is filed. The mark owner then discovers that someone else registered a matching .group domain months – or years – earlier. They file a UDRP complaint anyway. That sequence happens more often than brand owners admit, and it lands in front of a panel that must decide whether the registration predated any cognizable trademark rights at all.

To defend a .group domain registered before the complainant's trademark, a respondent must demonstrate that the complainant cannot satisfy all three elements of Paragraph 4(a) of the UDRP – specifically that no trademark rights existed at the time of registration, or that the respondent holds a legitimate interest under Paragraph 4(c). The response window is 20 days from commencement. A well-documented prior-registration defense regularly collapses the third element and, in clear cases, supports a finding of Reverse Domain Name Hijacking.

This guide walks each step of that defense in the .group context, flags the trap hidden in each one, and explains what evidence decides the outcome.

Why .group domains fall under the UDRP – and what that means for your defense

The .group new gTLD is administered under ICANN's standard accreditation framework, which means all three UDRP elements of Paragraph 4(a) bind any complaint filed against it. There is no separate zone-specific rulebook. The complainant must prove identity or confusing similarity, absence of legitimate interest, and – critically – that the domain was registered and is being used in bad faith. That cumulative "and" is the structural foundation of a pre-registration defense.

Panels do not rewrite that conjunctive standard. Where registration predated any filed trademark application, the complaint faces a fundamental evidentiary gap on the third element. The complainant cannot logically allege that a registrant targeted a mark that did not yet exist. That does not mean the complaint will always fail on that ground alone – panels have credited common-law or unregistered mark rights established before the registration date – but a purely post-registration mark is a strong starting point.

The forum for .group complaints is typically WIPO or the Forum, with WIPO accounting for the overwhelming share of new-gTLD disputes. WIPO's published filing fee for a single-member panel covering one to five domains is USD 1,500. If the complainant elected a single panelist and you request a three-member panel, the parties generally split the higher fee of USD 4,000. Knowing that cost dynamic matters: a respondent who is confident in the timeline evidence may decline to pay the upcharge and rely on a well-prepared response before a single panelist.

For a rapid read on whether the timeline evidence is sufficient to support this defense, email info@cognomenlaw.com.

Step 1: confirm the registration date and the complainant's earliest trademark rights

The first step is verifying exactly when the .group domain was created and when the complainant's trademark rights first attached. These two dates determine whether a pre-registration defense is available at all – and panels scrutinize the gap with care.

Pull the WHOIS/RDDS creation date for the domain. Then source the complainant's earliest trademark filing date, its registration date, and – where relevant – any evidence of prior commercial use that could support a claim to unregistered or common-law rights. Brand owners filing UDRP complaints sometimes rely not on a registered mark but on a long-established trade name, which panels have recognized as a qualifying "trademark or service mark" under Paragraph 4(a)(i).

The trap here is complacency. A registrant who sees a post-registration trademark assumes the case is won. It is not. Panels ask whether the complainant had de facto brand recognition before your registration – through commercial activity, press coverage, or a pending application that later ripened into registration. If that evidence exists, the complainant can argue the respondent knew, or constructively should have known, of the mark. Counter that now, not at the supplemental-filing stage.

Gather contemporaneous evidence of what you knew – or could not have known – at the moment of registration. Search history, business plans, correspondence, domain portfolio strategies, and any public record of why you chose the string are all relevant. The cleaner and earlier the paper trail, the stronger this step becomes.

Step 2: build the Paragraph 4(c) legitimate-interest record

Even when the pre-registration timeline is airtight, a panel will look at all three elements of Paragraph 4(a). A respondent should not rest on element three alone. The Paragraph 4(c) safe harbors give you affirmative ground to stand on alongside the timeline defense.

Three non-exhaustive circumstances establish legitimate interest. First, a bona fide offering of goods or services before you received notice of the dispute. Second, being commonly known by the domain name. Third, legitimate noncommercial or fair use without intent to mislead commercially. In the .group context, the first and third safe harbors are most commonly engaged.

What does "bona fide offering before notice" look like in practice? A respondent running a membership platform, an industry collective, a community site, or any commercial venture under the .group domain since before the complaint was filed stands on comparatively solid footing. Document that use: wayback-machine captures, invoices, subscriber records, contracts, or correspondence with group members are all admissible. The volume of that use is less important than its authenticity and its pre-notice timing.

The trap in this step is underdocumentation. Many registrants use their domain genuinely but maintain no archive. By the time a complaint arrives, the only evidence is a current live site. That is far weaker than a chain of historical screenshots and business records showing continuous use from registration. Start building that record the moment you learn of the dispute.

In a matter we handled in late 2024 – a .group domain registered by a trade association approximately eighteen months before the complainant filed any trademark application – we assembled contemporaneous membership correspondence and a series of archived event announcements as the core of the legitimate-interest record. The panel found for the respondent on all three elements without reaching the RDNH question.

How strong is the pre-registration defense, and when is RDNH realistic?

A pre-registration defense is at its strongest when three conditions align: the domain was registered well before any trademark filing; no common-law rights of the complainant predate registration; and the respondent can show a plausible, documented reason for choosing the string. All three together make it difficult for a panel to find bad faith, because the intent to target a non-existent mark is logically incoherent.

Reverse Domain Name Hijacking is a panel finding that the complaint was brought in bad faith to deprive a legitimate registrant of the domain. It carries no monetary penalty, but it does carry reputational consequence for the complainant and their counsel. Panels have found RDNH where the complainant knew – or must have known – that the registration predated the mark and filed anyway. The clearest RDNH scenarios involve a complainant who conducted trademark clearance, saw the registration date, and filed without acknowledging the gap in the complaint itself.

RDNH is not guaranteed and not automatic. A panel may decline to make the finding even where the complainant lost, because good-faith filing on a close issue is not abusive. But where the date gap is large, the complainant's mark is post-registration by a meaningful margin, and the complaint omits any mention of common-law rights, the conditions for an RDNH request are present and worth pleading in the response.

We regularly advise respondents to request RDNH explicitly in the response when the timeline evidence is compelling. A generic or cursory RDNH request without argument will almost never succeed. The request must walk the panel through the complainant's evident knowledge of the timeline and explain why filing was unreasonable – not merely unsuccessful.

If you have already received a complaint and are weighing whether to seek an RDNH finding alongside your substantive defense, email info@cognomenlaw.com for an assessment.

Step 3: structure the response before the 20-day deadline

The UDRP response is due 20 days from formal commencement of the case – not from the date you learned of the complaint. Missing this deadline does not end the case; a panel may still consider late submissions, but most will proceed to a decision on the complaint alone if no response is filed. Default decisions in respondent cases are disproportionately unfavorable.

A well-structured response for a pre-registration defense follows a clear order. Open by establishing the timeline precisely – date of registration, date of any complainant trademark filing, and the gap between them. Then address each Paragraph 4(a) element in turn. Do not skip element one (similarity) even if it looks conceded; the framing there can affect how a panel reads the bad-faith analysis.

On element two, articulate which Paragraph 4(c) safe harbor applies and attach the supporting exhibits. On element three, walk the panel through why registration before a mark existed is inconsistent with the UDRP's bad-faith requirement, which demands intent to target a specific trademark. Close with the RDNH argument if the facts support it, and make it specific.

The trap in this step is treating the response as a letter rather than a legal submission. Panels read hundreds of responses. A response that mirrors the structural discipline of the complaint – element by element, with numbered exhibits and precise date references – is easier to follow and harder to dismiss. Length does not substitute for precision.

Step 4: choose your panel composition and manage the forum dynamic

The complainant nominates the forum – typically WIPO or the Forum for a .group domain. You cannot change that. What you can control is whether the case proceeds before a single panelist or a three-member panel.

If the complainant requested a single panelist, you may request a three-member panel. The cost of doing so is sharing the higher three-member fee – approximately USD 4,000 at WIPO – while the complainant covers the remaining portion above the single-member fee already paid. That cost calculus is relevant. For a domain with significant commercial value, the additional outlay for three panelists is often justified: three-member panels are more likely to reach an RDNH finding where appropriate, and minority dissents can become useful public record.

Where the timeline evidence is overwhelming and the RDNH argument is strong, a three-member panel also signals that the respondent is prepared to contest fully. Complainants sometimes reassess a borderline case when the respondent demonstrates it will absorb the cost of escalation. We have seen cases settle – or complaints withdrawn – after a respondent's request for a three-member panel in circumstances where the pre-registration gap was undeniable.

What evidence actually decides the outcome

Documentary precision decides most pre-registration UDRP defenses. Panels weigh evidence, not argument. The following categories are the most consistently determinative in our practice.

Registration-date evidence is primary: the authoritative WHOIS/RDDS creation timestamp, confirmed through the registrar's records where available. Panels give weight to registrar-verified creation dates over self-reported claims.

Trademark-history evidence is equally critical. Pull the full prosecution history of the complainant's mark from the relevant registry – filing date, publication date, registration date, and any prior applications that were abandoned. If the complainant relies on common-law rights, the burden is on the complainant to establish them; your response can scrutinize that showing directly.

Evidence of legitimate use should be as chronologically dense as possible. Screenshots should carry visible timestamps – native Wayback Machine captures include both the crawl date and the live URL. Business records – contracts, invoices, board resolutions naming the domain, correspondence – carry high evidentiary weight because they are harder to manufacture after the fact.

Evidence of registrant intent at the time of registration is often underestimated. A contemporaneous business plan, an email chain discussing domain strategy, or a portfolio acquisition record that shows the registrant evaluated the string on descriptive or generic grounds – independent of any brand association – directly counters an inference of bad faith.

Finally, evidence addressing the complainant's knowledge of the timeline strengthens any RDNH request. If the complaint itself contains the complainant's registration date and omits any response to the gap, that omission is worth highlighting. A complainant who ignores the problem in pleadings is in a weaker position before a panel that notices the same problem.

In a second matter we advised on, a .group domain registered in early 2023 became the subject of a complaint in summer 2025 from a complainant whose trademark registration issued in late 2023. The complaint argued common-law rights predating our client's registration but offered no contemporaneous commercial-use evidence – only the trademark certificate. We identified that gap, assembled a counter-chronology of publicly available press records showing the complainant had no market presence before 2024, and the panel denied the complaint, leaving the domain with the registrant.

Cross-zone considerations: when a .group defense intersects with other domains

The right strategy for a .group defense does not exist in isolation if the respondent also holds the matching .com, .net, or a ccTLD variant. A UDRP complaint may cover multiple domains simultaneously only if they share the same registrant. If the complainant files across several zones in a single complaint or parallel complaints, the respondent's litigation posture must account for each zone's procedural rules.

For a .com complaint filed in parallel, the UDRP analysis is identical – the same three elements, the same safe harbors, and the same pre-registration logic applies. A coordinated response covering both domains before a single forum is usually more efficient than sequential responses. For a ccTLD variant, the governing procedure changes. A .de analog, for example, involves German court proceedings rather than the UDRP, and a DENIC DISPUTE entry blocks transfer during litigation. A .uk domain is governed by the Nominet DRS, which applies an "abusive registration" test and reads abusiveness as "registered or used" – a meaningfully different standard from the UDRP's cumulative conjunctive.

Where a respondent holds a portfolio of domains using the same contested string across zones, a coordinated defense strategy is essential. The outcome in one forum can be cited – though it is not binding – in another. A transfer order in the .com proceeding can prejudice the .group defense if the panel reasoning addresses facts common to both registrations. Conversely, a successful RDNH finding in the .group case is a useful document when opposing the .com complaint.

Related at COGNOMEN

• Respondent defense and RDNH services – full scope of how COGNOMEN defends registrants
• Analysis: defending a .mx domain registered before the complainant's trademark
• How complainants prove bad faith on .org – the evidence standard your defense must meet