FAQ: defend a .app domain against a UDRP complaint

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

Defending a .app UDRP complaint means filing a formal response within the 20-day response window to contest one or more of the three elements a complainant must prove. The UDRP, adopted by ICANN in 1999, applies to .app because Google Registry, as a gTLD operator, is bound by the standard ICANN registry agreement. That agreement mandates UDRP compliance, so the procedure is identical to a .com or .net dispute. A respondent who files no response does not automatically lose ownership — the panel must still find all three elements met — but default removes the respondent's voice from the record entirely. Filing a reasoned response is almost always the right course.

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

A standard UDRP case runs approximately two months from filing through panel decision, with the respondent's 20-day response window forming the first critical deadline after commencement. Panels are appointed after the response period closes, and the decision typically follows within 14 days of appointment on a single-member panel. A three-member panel adds time. WIPO also offers an expedited track that can reduce the overall period to roughly one month for eligible single-panel cases of up to five domains. Neither party controls the clock once the response is filed — the timeline is set by the procedural rules, not by agreement.

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

The official WIPO forum fees are paid by the complainant, not the respondent — so filing a response at WIPO costs the registrant no WIPO fee at all. If the complainant requested a single panelist but you prefer a three-member panel, the parties generally split the higher three-member fee: USD 4,000 for 1–5 domains, with the respondent's share roughly half. Legal representation is a separate matter. Market rates for a UDRP respondent defense typically run in the USD 3,000–7,000 range for a straightforward single-domain case, depending on the complexity of the legitimate-interest record. Opting for a three-member panel costs more but gives the respondent a second and third read of the record — a meaningful benefit in close cases.

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

Evidence for a respondent defense maps directly to the Paragraph 4(c) safe harbors: a bona fide offering of goods or services before notice of the dispute, being commonly known by the name, or a legitimate noncommercial or fair use without intent to mislead. Concretely, that means gathering registration records showing when the domain was acquired and why, any business formation documents or trading records linked to the name, screenshots of the site in use (or development materials if the site is not yet live), correspondence predating the complaint that shows the registrant's purpose, and WHOIS history. Where the complainant's trademark registration postdates the domain registration, that timing gap is itself significant evidence — panels have consistently held that a respondent cannot register in bad faith a mark that did not yet exist. We regularly advise registrants to treat the evidence-gathering stage as the make-or-break phase of the defense.

When is a Reverse Domain Name Hijacking finding realistic in a .app defense?

Reverse Domain Name Hijacking — commonly abbreviated RDNH — occurs when a panel finds the complaint was brought in bad faith to deprive a legitimate registrant of a domain. The finding carries no monetary penalty, but it is a reputational sanction recorded in the published decision. RDNH is realistic when the complainant filed despite obvious defects: the registrant's domain predates the trademark, the trademark is clearly generic or descriptive, the complainant could not have believed the bad-faith element was met on the facts, or the complaint was timed to pressure a sale rather than to vindicate IP rights. In our practice, the strongest RDNH records combine a clear pre-complaint registration date, evidence of the registrant's independent purpose, and a complainant whose claimed mark is weak or newly acquired. An RDNH finding does not require the respondent to prove every element of misconduct — it requires showing the complaint was filed in circumstances where the complainant knew or should have known it could not succeed.

For a read on whether the three UDRP elements are met in your .app case, reach us at info@cognomenlaw.com.

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

A single UDRP complaint may cover multiple domains, but only where the registrant of record is the same holder across all named domains. If a complainant has consolidated multiple .app names into one proceeding — because WHOIS or RDDS records show common ownership — the respondent files a single consolidated response addressing each domain. The same 20-day window applies regardless of how many names are listed. Where the domains raise distinct factual records (for instance, one domain is in active commercial use and another is parked), the response should address each separately. A respondent in a multi-domain proceeding should also weigh the three-member panel option carefully: with more domains in play, the investment in a fuller panel review can be proportionate.

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

There are three possible outcomes. First, the complaint is denied — the panel finds the complainant has not proved one or more elements, and the domain stays with the registrant, exactly as registered. Second, the panel orders a transfer to the complainant — the registrar implements the transfer after a brief implementation period during which the registrant may seek a court stay. Third, the panel may order cancellation of the domain rather than transfer, though this is the least common result. A fourth outcome — an RDNH finding alongside a denial — is technically appended to the first category but has real-world significance: it discourages repeat complaints and is a matter of public record. There is no middle ground. The UDRP provides no monetary damages, no costs award, and no injunction — only those three remedies. If the respondent believes the complaint is a strategic attempt to acquire the domain at nil cost, a well-built response and an RDNH bid are the tools available within the procedure.