Request a three-member panel to defend a .app domain: what panels act…

Request a three-member panel to defend a .app domain: what panels act. UDRP and ccTLD domain recovery and defense across .app. Email the firm to assess your ca…

A complainant files against your .app domain. The notice arrives, the clock starts running, and the first real decision you face is not about evidence — it is about who decides. Do you accept the default single panelist, or do you request a three-member panel to defend a .app domain and shift the adjudication to a broader bench? That choice shapes the entire proceeding.

A respondent in a UDRP proceeding over a .app domain has an explicit right to request a three-member panel, regardless of whether the complainant requested one. Under the UDRP Rules, that election triggers a cost-sharing mechanism: if the complainant chose a single panelist, the parties generally split the three-member fee, which at WIPO runs to USD 4,000 for a case covering one to five domains. The strategic logic is clear — a minority of one cannot outvote the other two members, and a divided decision carries less precedential weight against you.

This analysis covers the procedural mechanics of the election, how three-member panels have reasoned through contested .app registrations, the safe harbors under Paragraph 4(c), how to build a legitimate-interest record that survives scrutiny, and when an RDNH finding is a realistic objective — not just a theoretical one.

What does the .app zone change about a UDRP proceeding?

The .app top-level domain is a sponsored new gTLD operated under registry agreement with ICANN, and its registrars are accredited in the standard ICANN pool — meaning the UDRP applies to .app in full, without modification. A complainant pursuing transfer of a .app domain must satisfy all three elements of Paragraph 4(a) of the Policy, in exactly the same form as for a .com: (1) the domain is identical or confusingly similar to a trademark; (2) the respondent has no rights or legitimate interests; and (3) the domain was registered and is being used in bad faith. Both elements of the third prong are cumulative — registration in bad faith alone does not carry the claim.

What the .app zone does change is the forensic texture of a dispute. The .app extension signals, to many panels, that the registrant operates or intends to operate a software application or digital service. That signal cuts both ways. A complainant may argue that the domain targets the brand in the app economy — an increasingly common framing as mobile distribution grows. A respondent may counter that descriptive or generic terms that form part of the second-level label are entirely at home in the .app namespace, regardless of whether someone holds a trademark in the same string.

The URS (Uniform Rapid Suspension) is also technically available for .app as a new gTLD. But URS results only in suspension for the registration term, not transfer. If a complainant wants the name, UDRP is the route. If you are a respondent, the UDRP is where the real fight happens.

How does the three-member panel election work in practice?

The respondent's right to elect a three-member panel is set out in the UDRP Rules: if the complaint named a single-panelist case, the respondent may elect, in the response, that the matter be decided by three arbitrators. The respondent must pay its share of the additional fee at that point. Under WIPO's schedule, a three-member panel for one to five domains costs USD 4,000, compared with USD 1,500 for a single member. If the respondent elects the larger bench, the additional USD 2,500 is typically split between the parties — so the respondent contributes roughly half the difference beyond the single-panel fee already paid by the complainant.

Is that expense justified? In our practice, we recommend the three-member election in four specific situations. First, when the complainant is a sophisticated brand owner with a documented litigation history — a single panelist who tilts toward complainants may be dispositive. Second, when the mark at issue is weak, descriptive, or geographically limited, so that a careful second and third read is worth the price. Third, when the respondent's legitimate-interest argument is strong but factually complex — three sets of eyes parse a long evidentiary record better than one. Fourth, when an RDNH finding is the primary objective, because a three-member panel's RDNH declaration carries noticeably more reputational weight.

The election must appear in the response itself. A respondent cannot make the request after filing a timely response. That interlock means the decision about composition must be made, in writing, within the 20-day response window after commencement — often the same 20 days you spend assembling the substantive case.

For an early-stage read on whether three-member election strengthens your position in a .app dispute, contact info@cognomenlaw.com.

What safe harbors under Paragraph 4(c) apply to a .app respondent?

Paragraph 4(c) of the UDRP provides three non-exhaustive circumstances that, if established, demonstrate the respondent's rights or legitimate interests. They are: (a) before notice of the dispute, the respondent made a bona fide offering of goods or services using the domain; (b) the respondent has been commonly known by the domain name; and (c) the respondent made a legitimate noncommercial or fair use of the domain without intent to mislead consumers or tarnish the mark. In a .app context, each safe harbor operates differently — and each attracts a distinct panel approach.

The bona fide offering safe harbor is the one most commonly invoked and most frequently contested. Panels have consistently held that a parking page generating pay-per-click revenue from trademark-relevant terms is not a bona fide offering. But panels have also recognized that a respondent who registered a descriptive or generic string before the complainant's trademark rights crystallized, and who has since operated a genuine app or digital product from the domain, presents a fundamentally different picture. The key inquiry is timing and genuineness: did the respondent's use predate notice of the dispute, and does it reflect a real commercial activity unrelated to exploiting the complainant's mark?

The "commonly known by" safe harbor is less frequently applicable in .app disputes, because it typically requires something approaching documentary proof — business registrations, consistent use of the name in commerce, or trade press coverage. It is the narrowest of the three.

The legitimate noncommercial or fair use safe harbor applies most naturally to commentary, criticism, and fan sites. In a .app environment, a respondent who hosts a review platform or consumer-advocacy resource may invoke this ground, but panels examine whether the site's actual content matches the fair-use framing or whether it is a pretext for commercial exploitation.

What this means for case preparation: a respondent cannot simply assert a safe harbor in a conclusory way. The response must exhibit the evidence — development records, app-store submissions, communications predating the dispute, registration logs — that places the conduct within the harbor's terms. We regularly advise registrants in this situation to begin that evidence assembly on day one, not after the response is filed.

How do panels analyze bad faith in a contested .app registration?

The bad-faith prong requires both registration and use to have occurred in bad faith — the two elements are conjunctive, not disjunctive. That structure is the respondent's structural ally: a complainant who can show bad-faith use but cannot show the domain was registered in bad faith at the moment of acquisition has not met the UDRP test. Three-member panels have been more exacting on this point than some solo panelists, and that is one reason the election matters.

Paragraph 4(b) lists non-exhaustive bad-faith factors: the offer to sell the domain to the mark owner for more than out-of-pocket costs; a pattern of abusive registrations; registration to disrupt a competitor; and registration to attract users to a website for commercial gain by creating confusion with the mark. Each factor carries implied defenses.

On the first factor — a demand to sell — the critical distinction is between a speculative asking price and a targeted extortionate demand. Panels have found that a registrant who acquired a domain in the open aftermarket, for legitimate business purposes, and later received an unsolicited offer from the complainant, does not become a bad-faith registrant simply because a response to that offer named a high price. The motive at registration governs, not the motive at negotiation.

On the disruption factor, panels examine whether the second-level string is so exclusively associated with the complainant's brand that no legitimate reading of the domain is available. Generic or descriptive strings fail that test — "cloud.app", "pay.app", "track.app" are obvious examples where complainant-brand-disruption framing would face resistance. By contrast, a string that is a coined term uniquely associated with a single mark invites harder scrutiny of why the respondent chose it.

Passive holding — owning the domain without any active use — is not automatically good faith. The consensus view under the Policy is that passive holding can constitute bad faith use where the surrounding circumstances make it implausible that the domain could ever be put to a good-faith use. But that analysis is fact-intensive, and a well-documented development plan, or evidence of the domain's prior use history, can shift the inference.

What evidence decides a .app respondent's case?

Evidence is the operative variable in a contested .app dispute. Panels decide on the written record — there is no oral hearing, no cross-examination, no deposition. Every inference a panel draws must be grounded in something in the submission. That constraint rewards preparation.

The highest-value exhibits for a respondent are: (1) registration records showing when and how the domain was acquired — aftermarket purchase receipts, auction records, or direct-registration confirmation with a date that predates the complainant's trademark filing or use; (2) communications with potential buyers, partners, or developers that predate the notice of the dispute; (3) app-store submissions, developer agreements, or wire-frame records showing genuine development activity; and (4) any prior correspondence with the complainant, including any unsolicited offer the complainant made to purchase the domain.

On the complainant's side, the evidentiary package typically includes trademark registration certificates, brand-awareness evidence, and screenshots of the respondent's site (or its absence). Three-member panels tend to weigh the complainant's trademark evidence carefully — they ask not just whether the mark exists, but how strong it is, how long it has been in use, and whether it was registered before or after the domain.

In a recent matter — a contested .app registration, spring 2025 — we assembled a respondent record showing the domain had been registered through a public auction, development discussions had begun within weeks, and no contact from the complainant's brand had occurred until two years after registration. The panel found that the cumulative record did not establish registration in bad faith. The case illustrates a point panels have confirmed repeatedly: a well-documented timeline is more persuasive than a well-written legal argument without it.

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

Reverse Domain Name Hijacking — the finding that a complainant brought a UDRP complaint "in bad faith to deprive a legitimate registrant" — is available under the Policy and the UDRP Rules. The finding carries no monetary penalty. It is reputational: it is published in the case decision, indexed by WIPO, and may be cited against the same complainant in future proceedings. For a brand owner with a litigation history, multiple RDNH findings constitute a pattern that panels notice.

RDNH is not a consolation prize for simply winning a defense. Panels require affirmative evidence that the complaint was brought abusively — typically where the complainant knew, or should have known, that it could not succeed on the facts. The clearest RDNH scenarios in our practice share a common structure: the complainant held a trademark that postdated the registration; the complainant had previously made an unsolicited offer to purchase the domain; or the complaint relied on factual characterizations of the respondent's conduct that were demonstrably false on the record.

A three-member panel is the preferred bench for an RDNH objective. A single panelist who finds for the respondent may decline to make an RDNH finding on the ground that it was not affirmatively argued, or may simply allow the defense without the additional step. Three panelists — especially where one is nominated by the respondent from the provider's roster — are more likely to engage with the RDNH question if the evidence justifies it.

The contrary view deserves acknowledgment. A minority of panels have taken a restrictive approach to RDNH, reserving it for egregious cases where the complainant had no colorable argument at all. If the complaint raised a genuine trademark question — even one ultimately resolved in the respondent's favor — some panelists will not reach RDNH. That internal tension in the case law is a reason to argue RDNH explicitly in the response, rather than hoping the panel raises it sua sponte.

If you have received a complaint on a .app domain and believe the filing is abusive, email info@cognomenlaw.com to assess the RDNH argument alongside the defense.

How do WIPO and a national court compare for .app disputes?

WIPO handles .app UDRP proceedings in the same procedural format as any other gTLD dispute. The timeline is roughly two months from filing to decision for a standard single-panel case. A three-member panel may add two to four weeks. The remedies are limited: transfer or cancellation. WIPO cannot award damages, issue injunctions, or impose costs on either party.

A national court — most commonly a US court for .app matters, given the registry's US base — can reach outcomes WIPO cannot. Damages under US anticybersquatting legislation are available where the statutory elements are met. A court can also issue a preliminary injunction to lock the domain pending trial, order disclosure of registrant identity, and award attorney's fees in exceptional cases. Those are substantial additions to the UDRP toolkit.

But the trade-offs are significant. Court proceedings are measured in months to years, not weeks. Legal fees are substantially higher and typically hourly rather than flat. And for a respondent, a court action in an unfavorable jurisdiction — particularly where the complainant is a well-resourced brand owner and litigation is a pressure tactic rather than a good-faith legal claim — can be more burdensome than the original UDRP complaint.

The practical decision matrix looks like this. If you are a respondent seeking to keep a .app domain, WIPO UDRP is the faster, lower-cost battlefield — and the one where respondent-side procedural tools, including the three-member election and the RDNH finding, are available. If the complainant has parallel claims that include trademark infringement beyond the domain, court becomes relevant and you will need local litigation counsel in the relevant jurisdiction working alongside domain-dispute counsel. If the zone were .de rather than .app, neither WIPO UDRP nor the Forum would apply at all — the dispute would proceed through the German courts, with a DENIC DISPUTE entry as a provisional measure. The .app zone's status as a gTLD keeps the UDRP in play and keeps the timeline manageable.

What is the consensus view, and where do panels divide?

The consensus view under the Policy — reflected across WIPO decisions over more than two decades — is that the UDRP is not designed to give trademark holders rights in every domain containing their mark. Descriptive and generic strings, legitimate aftermarket acquisitions, and documented development activity can all rebut a transfer claim. That consensus position is what makes a well-prepared respondent defense viable in a .app proceeding.

Where panels divide is on the margin: cases where the second-level label is distinctive enough to raise a genuine trademark question, but the respondent's use evidence is thin or ambiguous. In those cases, single panelists have reached divergent results on identical-seeming facts. A three-member panel, applying the consensus standard, is more likely to produce a reasoned outcome that accounts for the complexity — and less likely to result in a transfer by default of the analysis rather than the merits.

The second division point is passive holding. The consensus permits an inference of bad faith from passive holding where the circumstances are sufficiently suspicious. But what counts as "sufficiently suspicious" varies. Some panels treat an unresolved parking page as near-dispositive against the respondent; others treat it as one factor in a multi-element analysis. Three-member panels tend toward the multi-factor approach, which gives the respondent more room to address the inference directly.

In a second matter we handled — a .app domain held by a domain investor, summer 2025 — the complainant's trademark was valid but comparatively recent, and the domain had been acquired through a documented aftermarket transaction two years before the mark was filed. A three-member panel declined to find bad faith at registration, noting that the chronology alone precluded the inference. No RDNH finding issued, because the complainant's error was one of timing rather than bad faith in filing. The outcome illustrates that a defensive strategy does not always end in RDNH — it sometimes ends simply in a clean win.

Related at COGNOMEN

• UDRP respondent defense and RDNH: full-service representation across gTLD and ccTLD zones
• Proving legitimate interest: how to build the Paragraph 4(c) record for a UDRP defense
• Case study: defeating a bad-faith claim and protecting a domain investor's portfolio