Step-by-step: defend a .app domain used for criticism or commentary

Step-by-step: defend a .app domain used for criticism or commentary. UDRP and ccTLD domain recovery and defense across .app. Email the firm to assess your case.

A brand owner files a UDRP complaint targeting your .app domain – a site you built to publish criticism, consumer reviews, or commentary about that very brand. You registered the name in good faith. You have been using it for legitimate speech. And now a 20-day response clock is ticking. Can you keep the domain?

Yes – defending a .app domain used for criticism or commentary is a recognized path under the UDRP. The Paragraph 4(c) safe harbors expressly protect legitimate noncommercial or fair use. A respondent who documents genuine criticism use, avoids commercial diversion, and files a timely, well-structured response can defeat the complaint and, where the filing was abusive, secure a finding of Reverse Domain Name Hijacking (RDNH). The WIPO filing fee for the complainant starts at USD 1,500; your defense costs nothing to the forum unless you elect a three-member panel.

This guide walks through each step of the defense, names the trap hidden in each one, and explains what evidence actually decides the outcome.

What rules govern a .app domain dispute?

The .app registry is a new gTLD operated by Google Registry, and its registrar agreements incorporate the UDRP – the same Policy that governs .com, .net, and hundreds of other generic zones. That means every UDRP-accredited provider can take the case. In practice, WIPO and the Forum handle the overwhelming majority of .app complaints. CAC and ADNDRC are available but rarely selected for .app matters.

The three-element test of Paragraph 4(a) controls entirely. The complainant must prove all three: (1) the domain is identical or confusingly similar to a mark the complainant holds; (2) the registrant has no rights or legitimate interests; and (3) the domain was registered and used in bad faith. That cumulative "registered AND used" standard is the UDRP's – not the Nominet or auDRP variant. For a criticism site, the third element is often conceded to be genuinely contested, but the defense lives most comfortably in the second element: demonstrating rights or legitimate interests under the Paragraph 4(c) safe harbors.

One practical note: because .app forces HTTPS, every .app domain resolves under a secure connection. That technical fact is neutral for the legal analysis, but it does mean your criticism site is unambiguously live and accessible – a factor that can help show genuine use rather than passive holding.

Step 1: Read the complaint the day it arrives – and act within 48 hours

The response deadline is 20 calendar days from the date the provider formally commences the proceeding – not from the date you receive notice by email. Miss that window and the panel decides on the complaint alone, on a record the complainant built without any check from you.

The hidden trap: many registrants read the complaint, feel confident in their position, and spend the first two weeks drafting a moral argument rather than a legal one. Panels do not reward indignation. They reward evidence organized around the three elements.

Within 48 hours of receiving the complaint, do four things. First, confirm the exact commencement date on the provider's case-status page – not the date the email landed in your inbox. Second, preserve all evidence of your site's content: screenshots, web-archive captures, publication dates of posts, visitor analytics if available. Third, identify the mark the complainant is relying on: registration number, jurisdiction, and filing date relative to your domain registration date. Fourth, consult counsel. A UDRP response is a legal brief, filed once, on a closed record. There is no discovery and no amendment.

Step 2: Build the Paragraph 4(c) legitimate-interest record for a criticism domain

Paragraph 4(c) of the UDRP offers three safe harbors. For a criticism or commentary site, the most relevant is Paragraph 4(c)(iii): legitimate noncommercial or fair use of the domain, without intent to mislead consumers or tarnish the mark for commercial gain. Panels have consistently held that genuine criticism sites – those that actually publish criticism, not thin placeholder pages – can qualify.

What does the record need to show? The following elements, documented and exhibited:

• Content authenticity. The site must publish substantive criticism, not a single sentence and a "contact us" form. Save every article, post, review, and comment, with publication timestamps. If the site was active before the complainant contacted you, that timeline is critical.
• No commercial diversion. The domain must not host pay-per-click advertising for competing products, affiliate links for rival services, or any commercial offering that trades on the complainant's mark. This is the single most common reason criticism-domain defenses fail: the registrant added AdSense, a comparison widget, or a referral link that technically monetized the mark owner's traffic.
• Clear identification as a criticism site. Panels look for a prominent disclaimer – visible above the fold – stating that the site is not affiliated with the mark owner. Absence of that disclaimer invites a panel to find that users would be confused, cutting against the legitimate-interest argument.
• Registration predating or independent of the dispute. If you registered the domain before the complainant's mark had any established reputation in the relevant market, that fact goes directly to bad faith. Include the registration date receipt and any contemporaneous records showing why you chose the name.
• Evidence of being commonly known by the name. Less common for criticism domains, but where the registrant operates under a pseudonym or brand that matches the domain, Paragraph 4(c)(ii) may also apply. Do not overlook this if it fits your facts.

The hidden trap in this step: over-documenting legal argument and under-documenting factual evidence. The panel will not take your word for what the site looked like in 2022. Exhibit the screenshots. Attach the web-archive URLs. The record you file is the only record the panel sees.

For a read on whether your site's current content meets the legitimate-interest threshold, reach us at info@cognomenlaw.com.

Step 3: Counter the bad-faith allegation directly

Even a strong legitimate-interest showing will not end the analysis if the panel is troubled by bad-faith indicators. Complainants targeting criticism domains typically allege one or more of the Paragraph 4(b) bad-faith factors: that you registered the domain to sell it to the mark owner at a profit, to disrupt its business, or to attract users for commercial gain by creating confusion as to source or affiliation.

Each allegation needs a direct, evidence-based answer in the response. The standard structure is: restate what the complainant alleges, identify the element it is supposed to satisfy, and then produce the evidence that contradicts it.

Common complainant theories and how to counter them:

• "You registered to sell to us." Counter with evidence that you have never contacted the complainant with an unsolicited offer, never listed the domain on a brokerage, and have maintained an active site throughout. If the complainant contacted you first, preserve that communication – it cuts strongly against a for-profit registration theory.
• "The domain disrupts our business." Legitimate consumer criticism has legal protection in most jurisdictions. Document that the content is factual commentary, clearly labeled as opinion where appropriate, and not a coordinated campaign of false statements. Panels distinguish protected criticism from commercially motivated interference.
• "You are attracting traffic through confusion." This is where the disclaimer visibility matters most. A prominent, above-the-fold disclaimer stating "This site is not affiliated with [Brand]" undercuts the confusion-as-source theory. Panels regularly cite its absence as a bad-faith indicator and its presence as a legitimate-use marker.
• Passive holding. If the site was briefly dormant – under construction, migrating hosts, or awaiting content – the complainant may characterize that as passive bad-faith holding. Explain the gap with documentation: migration logs, hosting invoices, draft content files with metadata timestamps.

In a recent matter (a .app criticism domain, spring 2025), we defended a registrant who had published consumer-safety commentary about a consumer-electronics brand for several years. The complainant alleged the domain was registered primarily to disrupt business. We produced contemporaneous registration records, the original publishing plan, and archived site content showing publication pre-dating any dispute notice. The panel denied the transfer.

Step 4: Decide whether to request a three-member panel

By default, a UDRP case is decided by a single panelist. The respondent may request a three-member panel, but doing so shifts part of the fee burden: if the complainant requested a single-member panel, the parties split the three-member panel cost, meaning the respondent bears half of the difference.

At WIPO, a three-member panel for one to five domains costs USD 4,000 versus USD 1,500 for a single-member panel. The respondent's share of the incremental cost is therefore USD 1,250. That is a real budget question. When does it make sense?

Three-member panels tend to produce more deliberative decisions on genuinely contested legal questions. A criticism-site defense involves contested doctrine – the scope of the fair-use safe harbor, the standard for confusion under Paragraph 4(b)(iv), the weight given to a disclaimer – and where those questions are genuinely close, a three-member panel may reduce variance. They are also more likely to issue a reasoned RDNH finding where one is warranted. If the complaint appears to be a strategic attempt to silence criticism, that argument is often better made to a three-member panel.

The hidden trap: requesting a three-member panel without a genuine reason to do so. If your defense is strong and the complainant's case is weak, a competent single panelist will deny the transfer. Spending on a three-member panel to hedge a case that is already defensible is a budgeting error, not a legal strategy.

If a prior filing or response in a related matter produced an unfavorable outcome, a focused second review can identify the element that was missed. Email info@cognomenlaw.com.

Step 5: Pursue an RDNH finding where the complaint is abusive

Reverse Domain Name Hijacking – defined under the Policy as using the UDRP in bad faith to deprive a legitimate registrant of a domain – is available as an affirmative finding when the complainant's case was clearly untenable. Panels do not make RDNH findings lightly, but the bar is not impossibly high where the abuse is plain.

What makes a complaint RDNH-worthy in the criticism-domain context? The clearest cases are where the complainant knew, or should have known, that a legitimate-use defense was available – that the site published substantive criticism, that the domain name included a pejorative or critical term making confusion implausible, or that the registrant had made no commercial use of the domain – yet filed anyway. A complainant who uses the UDRP primarily to silence speech rather than to redress genuine cybersquatting is presenting exactly the kind of abusive filing the RDNH mechanism addresses.

To make the argument effectively, the response must set out the RDNH request explicitly, identify the specific facts that demonstrate the complainant could not have held a reasonable belief in the merits of each element, and – critically – demonstrate that the complainant had actual or constructive knowledge of those facts before filing. The argument should be proportionate: an RDNH section that occupies a third of the response at the expense of the core legitimate-interest defense is a strategic mistake.

An RDNH finding carries no monetary sanction. Its practical effect is reputational – it is published in the decision database – and it can deter future abusive filings by the same complainant. In our practice, we regularly advise registrants who have received complaints that look designed to pressure a settlement rather than to vindicate a genuine trademark interest.

Step 6: Understand the cross-zone picture before settling

A complainant who loses a UDRP complaint for a .app domain does not necessarily go away. The same mark owner may simultaneously own, or later file for, the corresponding .com, .org, or national ccTLD. How does the cross-zone picture affect your .app defense?

First, a UDRP denial in a .app matter does not legally bind a later panel on a .com filing. Panels may note the prior decision and give it persuasive weight, but each proceeding is decided on its own record. If the complainant files a parallel .com complaint, that is a separate matter requiring a separate response.

Second, where the complainant also operates in a national market with its own ccTLD, it may attempt a parallel filing under that ccTLD's procedure. If the zone is .uk, for instance, the Nominet DRS applies an "abusive registration" test that reads "registered or used" abusively – a lower bar than the UDRP's cumulative standard. A defense that is bulletproof under the UDRP may need recalibration for that zone.

Third, and most practically: if the complainant contacts you with a settlement offer after receiving the response but before the panel issues a decision, the UDRP allows the parties to request a suspension. Evaluate any settlement on its merits. A complainant offering a token payment to drop the complaint may be signaling weakness. A complainant offering a material sum for a domain you intend to keep is presenting a different kind of decision. In our practice, we regularly advise clients on whether a settlement mid-proceeding is strategically preferable to a panel decision – and that analysis turns on the domain's long-term value and the strength of the record already filed.

In a recent matter (a .app commentary domain, autumn 2024), we advised a registrant who received a settlement approach two weeks after filing a response. The response had already established a strong legitimate-interest record and included a well-supported RDNH argument. The complainant's settlement figure was nominal. We recommended proceeding to panel, which denied the transfer and found RDNH.

Related at COGNOMEN

• UDRP respondent defense and RDNH – overview of how we build the record and challenge abusive complaints
• Respond within the deadline – process and what happens if the window closes
• File a UDRP complaint – for brand owners considering the complainant side of the same dispute