How to defend a generic-word .app domain

How to defend a generic-word .app domain. UDRP and ccTLD domain recovery and defense across .app. Email the firm to assess your case. Transparent fees, respond…

A trademark owner files a UDRP complaint against your weather.app, track.app, or translate.app. The complaint argues your domain is confusingly similar to a registered mark and that you registered it in bad faith. You know the word is generic. You know you built something with it. The question is whether the UDRP panel will know the same thing – and whether you have assembled the evidence to show it.

To defend a generic-word .app domain under the UDRP you must defeat at least one of the three elements in Paragraph 4(a) – most commonly by proving a legitimate interest in the domain under Paragraph 4(c), or by showing the registration was made in good faith before any notice of the dispute. A successful defense on a strong record can also produce a finding of Reverse Domain Name Hijacking (RDNH), which is the panel's formal conclusion that the complaint was filed in bad faith to strip a legitimate registrant of a domain. WIPO's standard timeline puts the respondent's answer deadline at 20 days after commencement of proceedings.

This page covers the .app zone specifically, the safe harbors that matter most for generic-word registrations, the evidence that decides the outcome, and the realistic path to an RDNH finding.

What rules govern a .app dispute, and why the UDRP applies?

.app is a new generic top-level domain operated by Google Registry. Because it is an ICANN-accredited gTLD, all registrars offering .app registrations are bound by the UDRP – the Uniform Domain Name Dispute Resolution Policy adopted by ICANN in 1999. There is no separate .app arbitration procedure. Every .app domain dispute proceeds exactly as a .com or .net dispute would, before one of the four accredited providers: WIPO, the Forum, CAC, or ADNDRC. WIPO handles the large majority of cases.

The complaint must satisfy all three elements of Paragraph 4(a): (1) the domain is identical or confusingly similar to a mark in which the complainant has rights; (2) the registrant has no rights or legitimate interests in the domain; (3) the domain was registered and is being used in bad faith. That cumulative "registered AND used" standard is the most important structural feature of the UDRP for respondents. A complainant who cannot prove both limbs of element three fails – regardless of how strong its trademark is.

For generic-word domains, element one is often formally satisfied: a complainant may hold a registered mark containing or matching the word. But elements two and three become the real battleground. Panels have consistently held that registration of a common or generic word as a domain name – without more – does not constitute bad faith, particularly where the registrant had a plausible reason for choosing that word unrelated to the complainant's mark.

For an early assessment of whether the three UDRP elements can be defeated in your .app matter, contact info@cognomenlaw.com.

How does Paragraph 4(c) protect a generic-word .app registrant?

Paragraph 4(c) sets out three safe harbors that, if demonstrated, establish a legitimate interest and defeat element two of the complaint. Each applies differently to a generic-word .app domain, and the strength of your record on each one determines the outcome.

Bona fide offering of goods or services before notice of the dispute. If you registered track.app and then built a tracking application on it, the fact that the product launched – or that development was visibly underway – before the complaint was filed is powerful evidence. Panels look for concrete indicia: a live website, a user base, app-store listings, investor materials, beta-test documentation, or a published launch date. Bare registrations with no use, or use that began only after a demand letter arrived, carry far less weight.

Commonly known by the name. If the registrant is an individual, business, or organization known by the domain word prior to the dispute – a company named "Track" that registered track.app – that alignment is independently sufficient. Entity name, registered trading style, and the historical relationship between the name and the business all go into the record. This safe harbor is less common for pure generic words, but it is available where the business genuinely predates the complaint.

Legitimate noncommercial or fair use. A non-monetized informational resource on a generic topic, a fan page, or a community portal can qualify. Panels apply scrutiny here: bare parking pages, pay-per-click links pointed at a competitor's goods, or a domain that has simply sat idle for years will not satisfy this safe harbor. The use must be real and the connection to the generic meaning genuine.

Building the Paragraph 4(c) record is the core of any respondent defense. We regularly advise registrants to gather and organize that evidence as soon as a complaint or demand letter arrives – not after the response deadline. In a recent matter (a .app generic-word registration, spring 2025), the respondent held a domain matching a common software category term, had operated a functioning application under that name for over two years, and had registration invoices, app-store analytics, and user agreements predating the demand letter by eighteen months. The complaint was denied.

What evidence decides whether you win or lose?

Evidence in a UDRP proceeding is submitted as annexes to the written response – there is no hearing, no live witnesses, and no cross-examination. The panel reads what you put in front of it. The quality and specificity of that record almost always determines the outcome.

The most persuasive evidence for a generic-word .app defense falls into four categories.

Registration history and pre-complaint conduct. The WHOIS/RDDS creation date is the floor, not the ceiling. What matters is what happened after registration: screenshots dated by metadata, Wayback Machine captures, development commits, domain invoices, and any published description of the project. Panels look for a continuous thread from registration to the moment of filing.

The generic character of the word itself. Panels take note when a complainant asserts exclusive rights in a term that any dictionary, industry glossary, or major app store treats as descriptive of a category. Showing that the word appears in standard references – and that dozens of other .app, .com, or .io registrations use the same term across different products – supports the proposition that no single mark owner can claim exclusive entitlement to the domain.

Absence of targeting. Did you know about the complainant's mark when you registered? If you did not – and if the word was chosen for its generic meaning – that absence of targeting is central to defeating bad faith. Prior search results, a declaration, and the domain's content history (showing no reference to the complainant's products or trade dress) all bear on this question.

Use, revenue, and user base. Concrete metrics carry weight. App-store downloads, subscription counts, revenue figures, press coverage, and third-party reviews all show that the domain is doing work as a real product – not sitting as a ransom note waiting for a buyer.

What does not help: a response that argues only that the word is generic without supporting that argument with evidence; a declaration from the registrant alone, unsupported by any documentary annexe; or a response filed on the last day with a compressed record because the 20-day window was not managed from the start.

When is an RDNH finding realistic, and why does it matter?

RDNH – Reverse Domain Name Hijacking – is the UDRP panel's formal finding that a complainant brought the case in bad faith or that it knew it could not prevail but filed anyway. The finding carries no monetary penalty. Its significance is reputational: the decision is published, the complainant's conduct is on record, and the finding signals to future registrants that abusive complaints have visible consequences.

For a respondent with a strong legitimate-interest record, pursuing an RDNH finding alongside the defense is worth considering. Panels award RDNH findings where the complainant had actual or constructive knowledge that the respondent's use was legitimate; where the complainant relied on a narrow or weak trademark to attack a well-established generic-word registrant; or where the complaint was filed after a failed private purchase negotiation to use the UDRP as leverage. In our practice, we have defended registrants in exactly these situations and, where the complaint record supports it, we include a specific RDNH request in the response.

An RDNH argument requires care. It should be made only when the evidentiary record genuinely supports it – not as a reflexive retaliatory claim. Panels are skeptical of RDNH assertions made without a factual basis, and an overreaching RDNH request can distract from the core legitimate-interest defense.

If you believe a complaint against your .app domain was filed to leverage a private sale rather than to assert a genuine trademark right, email info@cognomenlaw.com to weigh whether an RDNH request belongs in your response.

How does the .app zone compare to other gTLDs and to ccTLD routes?

The .app zone presents one structural feature that affects complainants more than respondents: all .app domains are HTTPS-only by default, which means every .app registrant has demonstrated at least the minimal technical effort of obtaining a certificate and pointing the domain. That is a thin signal, but it works against a complainant trying to argue that the domain was registered purely as a ransom asset with no intent to use it.

The right route depends on the zone and the goal. If the dispute is over a .app domain and the complainant seeks transfer, the UDRP applies – respondent files a response, panel decides within roughly two months, and the only remedies are transfer or cancellation. If the complainant chose a different forum than WIPO, the rules of that forum apply, but the underlying Policy and its paragraph 4 safe harbors are identical. If a parallel dispute exists over a corresponding .com, .co, or ccTLD version of the same name, those cases can be consolidated only if the respondent is the same holder; otherwise they proceed separately.

A .de version of the same generic word would not be resolved under the UDRP at all – it would require German court proceedings, with a DENIC DISPUTE entry to block any transfer while litigation proceeds. A .uk version of the same dispute would go through the Nominet DRS, which uses a different test – "abusive registration" rather than UDRP's cumulative bad-faith standard – and includes a free mediation stage before any expert decision. The zone determines the rulebook. We handle UDRP defense for .app and all other gTLDs; for ccTLD proceedings in other zones we work with the appropriate national procedure or local litigation counsel.

What does the three-member panel option mean for your defense?

Under the UDRP rules, either party may request a three-member panel. The complainant normally selects a single-member panel to keep costs down; the respondent may request three members and generally must cover the difference in the filing fee – the parties split the higher three-member fee. At WIPO, a single-member panel runs at a USD 1,500 filing fee; a three-member panel costs USD 4,000.

Three-member panels are worth considering in two situations. First, where the complainant has a dominant trademark and a plausible but ultimately weak bad-faith argument – a three-member panel provides an additional check against a single-panelist decision that might tip in the complainant's favor on a close record. Second, where an RDNH finding is the goal – three-member panels are more likely than single members to make formal RDNH findings, partly because the deliberative process tends to encourage more scrutiny of the complaint's merits.

In a recent matter (a .app generic-category domain, autumn 2024), we advised a registrant to request a three-member panel after reviewing the complaint. The complainant held a narrow descriptive-mark registration in a single jurisdiction, and the domain matched a common software industry term with a fifteen-year history of generic usage. The three-member panel denied the complaint and returned an RDNH finding. The cost of the additional fee was a fraction of the domain's commercial value.

What is the realistic cost and timeline for defending your .app domain?

Filing fees and legal fees are separate and worth understanding in that order. The UDRP forum fee – the amount paid to WIPO or the Forum for administering the case – is set by the complainant's filing. As a respondent, you pay nothing to the forum unless you request a three-member panel, in which case you typically pay your share of the fee difference. The forum filing fee does not come out of your pocket for a standard single-panel defense.

Legal fees for a UDRP respondent defense vary by the complexity of the record. A straightforward single-domain generic-word defense – one where the legitimate-interest evidence is already organized, the domain's use history is clear, and the complainant's mark is weak or geographically narrow – typically falls within the market range of USD 3,000–7,000 in legal fees. Matters requiring extensive evidence gathering, an RDNH argument with a detailed record, or a three-member panel selection and strategy discussion may fall higher.

Timeline: the respondent has 20 days from commencement to file the response. That window starts running the moment WIPO or the Forum formally notifies the respondent of the complaint. A standard case reaches a decision in approximately two months from filing. If you receive a complaint or a demand letter today, the clock is already running.

The question "is it worth defending?" almost always resolves in favor of defending when the domain has genuine commercial use, the registrant has a clean registration history, and the complainant's mark is not a famous or highly distinctive one applied to an identical domain. Losing the domain by default – which is what happens if no response is filed – is an irreversible outcome. A defense, even one that ultimately fails, preserves the record and the possibility of appealing an extreme panel decision in a competent court.

Related at COGNOMEN

• Respondent defense and RDNH – the full practice overview across gTLDs and ccTLDs
• How to defend a UDRP complaint filed against a descriptive or category-name domain
• Passive holding and bad-faith arguments – what complainants allege and how respondents answer