FAQ: defend a .group domain against a UDRP complaint

What does it mean to defend a .group domain against a UDRP complaint?

Defending means contesting the complainant's case by filing a written response within the 20-day window, demonstrating that at least one of the three UDRP elements has not been proved, and marshaling evidence of any legitimate interest in the name.

The UDRP is a mandatory administrative proceeding. Because .group is a new gTLD issued under an ICANN-accredited registrar, the registry agreement incorporates the UDRP and the UDRP Rules. A complainant files before an approved provider – most commonly WIPO or the Forum – and the registrar places the domain on a hold that prevents transfer while the proceeding runs. You do not have to go to court to participate, and you do not have to pay any provider fee simply to respond.

Defense is distinct from doing nothing. If you default, the panel decides on the complaint alone. Panels generally require only that the complainant's case is not facially deficient; a default is not an automatic loss, but it removes every avenue to present your side. In our practice, we advise respondents even where the complaint looks weak: a reasoned response protects the record, and a strong response can produce an RDNH finding – a formal ruling that the complaint was brought in bad faith to deprive a legitimate registrant.

What, precisely, does "defend" require? It means building a factual record that addresses each element the complainant must prove. The panel reads both filings and weighs them. Your response is not a negotiating document; it is evidence.

How long does it take to defend a .group domain against a UDRP complaint?

A standard UDRP defense runs approximately two months from the date of commencement to a decision, with the respondent's window to file closing 20 days after commencement.

The timeline is set by the UDRP Rules, not by the parties. After the provider formally commences the case, you have 20 days to submit a response. Once both filings are in, the provider appoints a panelist – or three, if either side requests a panel of that size. The panelist then issues a decision, typically within 14 days of appointment for a single-member panel. After a decision ordering transfer, the registrar implements it after a short implementation period, during which you may seek a court stay if you choose to litigate.

Extensions to the response deadline are possible but narrow. A respondent may request one extension of time before the deadline, and the provider grants it in limited circumstances – documented illness, for example, or a genuine settlement discussion. Counsel can advise on whether circumstances justify the request. We recommend beginning preparation immediately on receiving notice, because assembling the evidence record reliably takes more time than the 20-day window suggests.

WIPO also offers an expedited procedure, but that option is elected by the complainant at filing, not by the respondent. Under the expedited track, a decision issues in roughly one month. If you receive a complaint filed under the expedited procedure, the timeline is materially compressed and early preparation is even more important.

What does it cost to defend a .group domain against a UDRP complaint at WIPO?

As respondent, you pay no provider fee to WIPO for a standard single-member panel. If you elect a three-member panel, the fee is split with the complainant: the complainant pays their share and you pay yours, together reaching the USD 4,000 three-member rate for one to five domains.

Legal fees are separate. Market rates for respondent defense on a .group UDRP typically fall in the USD 3,000–7,000 range for a single domain, depending on the complexity of the record and whether the facts are straightforward or require extensive evidence assembly. COGNOMEN publishes fee guidance rather than hiding it: for most single-domain .group cases the preparation cost is closer to the lower end of that range when the factual record is organized and the legitimate-interest argument is clear.

The three-member panel question deserves a separate thought. Respondents sometimes request a three-member panel because they believe a more deliberate hearing reduces the risk of an incorrect decision. That choice carries a cost – half of the three-member fee – but it also introduces additional scrutiny if the complainant's case has weaknesses. We discuss panel composition with every respondent before the response deadline.

One cost consideration that brand owners and investors often overlook: an RDNH finding carries no monetary penalty for the complainant, only reputational consequence. If you are weighing whether to invest in a full response versus conceding a domain of modest value, that trade-off is worth working through with counsel before the deadline passes.

What evidence is needed to defend a .group domain against a UDRP complaint?

The core evidence for a UDRP defense falls under Paragraph 4(c) safe harbors: proof of a bona fide offering before notice of the dispute, documentary evidence that the registrant is commonly known by the name, or proof of legitimate noncommercial or fair use.

Concrete evidence that panels find persuasive includes: business registration records or operating agreements showing use of the name before the complaint was filed; screenshots of websites, social media, or correspondence predating the complainant's notice; domain registration records showing the acquisition date and any prior registration history; and communications that demonstrate the purpose of registration was not to target the complainant's mark.

What does not help? Bare assertions. A response that says "I registered this in good faith" without documentary support carries minimal weight. Panels draw inferences from silence on evidentiary points. If you cannot produce evidence of pre-dispute use, the inquiry shifts to whether the registration was opportunistic – and whether the complainant's trademark had priority in the relevant field at the time of registration.

In a recent matter (a .group domain targeted by a complainant in a professional-services sector, spring 2025), we assembled a file of operating records, email correspondence, and a sworn declaration from the registrant demonstrating consistent use of the group name for an internal organization over several years. The panel found legitimate interest and denied the transfer – and issued an RDNH finding because the complainant had filed knowing that prior-use evidence existed.

Evidence of the complainant's conduct also matters. If the complainant sent a cease-and-desist letter before filing, that letter is part of the record. If prior negotiations show the complainant knew of your legitimate use, that supports both the defense and an RDNH argument. Preserve all communications.

Can I defend a .group domain against a UDRP complaint for more than one domain at once?

Yes – a single UDRP proceeding can cover multiple domains, but only if the registrant of record is the same holder for all of them; each additional domain still requires evidence addressing that specific name.

This consolidation rule cuts both ways. A complainant who holds a trademark and pursues a pattern of alleged typosquats across multiple .group domains can file a single complaint covering all of them, which reduces the complainant's cost and concentrates the proceeding against you. The respondent then defends each domain on its own merits within one response. If the evidence of legitimate interest differs across names – which it usually does – the response must address each domain separately.

Consolidation across different registrants is not available under the standard UDRP. If a complainant targets related .group domains held by legally distinct entities – even affiliated ones – those are separate proceedings unless the panel accepts a consolidation request on grounds that the registrants are, in practice, the same actor. That determination is discretionary and fact-specific.

From a defense strategy perspective, a multi-domain complaint is often a sign that the complainant views the matter as a portfolio enforcement action rather than a targeted dispute. That context can affect the RDNH analysis: if the complaint sweeps in names that have distinct, documented uses, an aggressive filing posture may itself support a finding that the complaint was brought without adequate inquiry.

What are the possible outcomes when you defend a .group domain against a UDRP complaint?

A UDRP panel has exactly three possible decisions: order transfer of the domain to the complainant, order cancellation of the domain, or deny the complaint and leave the domain with the registrant – and in the denial scenario, the panel may also issue an RDNH finding.

Transfer is what the complainant seeks in most proceedings. Cancellation is rare in respondent-contested cases but can result if the complainant prefers the domain exist for no one rather than remain with the current registrant. Denial is the defense objective. A straight denial means the panel found that the complainant failed to prove at least one element; the domain stays with you and the proceeding closes.

RDNH is the additional finding available on denial. It requires the panel to conclude that the complaint was brought in bad faith – for example, to harass a legitimate registrant, to obtain a domain the complainant could not buy at a market price, or to file without adequate investigation knowing the registrant had a legitimate interest. RDNH carries no fine or damages award; its weight is reputational and precedential. We pursue RDNH arguments whenever the record supports them, because the finding signals to other potential complainants that the domain is not a soft target.

A fourth practical outcome exists outside the formal decision: settlement. UDRP proceedings can be suspended while the parties negotiate, and many end by agreement – a sale, a license, or a withdrawal of the complaint. Whether settlement is in your interest depends on the strength of your defense and the value of the domain. We help respondents assess that trade-off honestly, without steering toward a particular result.

When is an RDNH finding realistic in a .group domain dispute?

An RDNH finding is realistic when the record shows the complainant knew or should have known the registrant had legitimate interests before filing, and filed regardless – typically where prior-use evidence was available in public records or prior communications.

Panels apply a demanding standard for RDNH. A complaint that simply fails on the merits does not automatically produce an RDNH finding. The panel must find the complainant acted in bad faith – not merely in error. The categories of conduct that most reliably support RDNH include: filing against a registrant with a clearly documented prior business use; filing after being explicitly told of that use during pre-complaint negotiations; and filing a complaint that characterizes the relevant mark rights in a manner the complainant knew to be overstated.

In a second recent matter we handled (a .group domain, autumn 2025, registered by a professional collective sharing a descriptive name for years), the complainant's counsel had received a detailed letter before filing that set out the registrant's prior use and attached supporting records. The panel found that filing in those circumstances was not a good-faith attempt to enforce legitimate trademark rights. RDNH was recorded.

Is RDNH worth pursuing for its own sake? That depends on your goals. If you want a public record that the dispute was abusive, yes. If you simply want to keep the domain and move on, a clean denial is sufficient. We calibrate the response to the client's objective rather than building the most elaborate available filing for its own sake.