How to respond to a UDRP complaint within the deadline for a .app dom…

How to respond to a UDRP complaint within the deadline for a .app dom. UDRP and ccTLD domain recovery and defense across .app. Email the firm to assess your ca…

A UDRP complaint lands in your inbox naming a .app domain you registered legitimately, built around, or acquired through an open market purchase. The clock is already running. Miss the deadline, and a panel will decide on the complainant's version of events alone.

To respond to a UDRP complaint within the deadline for a .app domain, you have 20 days from the date the case commences to file a written response with the administering forum – typically WIPO for .app disputes. The response must address all three elements of Paragraph 4(a), document any Paragraph 4(c) safe harbor, and be filed with the proper formal elements or the forum will reject it. A default is not a neutral outcome; it is effectively a concession.

This page covers the procedural clock, the legal test, the evidence that decides the outcome, when an RDNH finding is realistic, and the right next step for a .app registrant who has just received a complaint.

Why .app Domains Draw UDRP Complaints – and What That Means for Your Defense

.app is a new-gTLD operated by Google Registry. Because ICANN-accredited registrars manage .app registrations, the Uniform Domain Name Dispute Resolution Policy applies in full. A complainant files with a WIPO, the Forum, or another approved provider; the same three-element test governs as for a .com.

That matters because .app carries a tech-sector signal. Complainants frequently allege that a .app domain targets a software brand, a SaaS product, or an app-store presence. The registration date and how the domain is actually used – a live application, a portfolio hold, a developer project – are therefore central facts from the first day of a dispute.

We regularly advise registrants who built real .app projects only to find a late-arriving brand owner claiming exclusive rights to the underlying term. The keyword in that sentence is "late-arriving." Timing – both the registration date and the date the complainant acquired trademark rights – is often the first thing we examine in a .app defense.

What Is the Response Deadline and How Is It Calculated?

The respondent has 20 days to file a response after the case formally commences, a date set by the administering forum and communicated in the commencement notice. Commencement is not the same as the date you receive the complaint. The forum triggers commencement after verifying that the registrant contact details are accurate and proper service has been completed. That verification step typically takes a few days, but it is not guaranteed, and the window to prepare a substantive response is therefore shorter than it appears.

Extensions are available but not automatic. WIPO's Supplemental Rules permit a respondent to request a brief extension for good cause. The forum must receive that request before the original deadline expires. Waiting until day 19 to file the extension request is risky; waiting until day 21 is fatal. In practice, the moment you receive a commencement notice, the preparation timeline should begin immediately.

What happens if you miss the deadline? The panel proceeds on the complaint alone. It may still review the file and deny transfer if the complaint is facially deficient – but that is a low-probability path. A default registrant cannot introduce new evidence, cannot correct the record, and forfeits the ability to seek a reverse domain name hijacking finding, regardless of how strong that argument might have been.

How Do the Three UDRP Elements Apply to a .app Defense?

Under Paragraph 4(a) of the UDRP, a complainant must establish all three elements. A respondent defeats the complaint by negating any one of them. In our practice, element two – rights or legitimate interests – and element three – bad faith in registration and use – are where most .app defenses are won or lost.

Element one: confusing similarity. The panel compares the domain to the complainant's trademark. For .app, the TLD extension is generally disregarded in the comparison, consistent with the consensus view across thousands of UDRP decisions. If the second-level label is identical or confusingly similar to a registered mark, element one is usually conceded and the defense focuses on elements two and three.

Element two: rights or legitimate interests. Paragraph 4(c) provides three explicit safe harbors: a bona fide offering of goods or services before notice of the dispute; being commonly known by the domain name; or legitimate noncommercial or fair use without intent to mislead or divert for commercial gain. A registrant with a live .app product – even a beta or a small commercial operation – who registered before the complainant's mark existed presents a strong element-two defense. The evidence here is concrete: domain registration WHOIS/RDDS history, GitHub commits, app store records, business registrations, investor materials, and any public reference to the project predating the complaint.

Element three: bad faith. Under Paragraph 4(b), bad faith requires that the domain was registered and is used in bad faith. That cumulative requirement is the UDRP's fundamental structure – and it is frequently misapplied by complainants who can show only one limb. A registrant who registered a .app domain before the complainant's trademark existed cannot have registered in bad faith with that mark in mind. Panels have consistently held that a complainant cannot bootstrap a later-acquired mark onto a registration that predates it.

Building the Legitimate-Interest Record Before You File the Response

A credible legitimate-interest defense is built on contemporaneous, dated evidence – materials that existed before the complaint arrived and that show the domain's purpose was independent of the complainant's brand. Evidence gathered after commencement is not worthless, but panels scrutinize post-dispute materials carefully for signs of retrofitting.

The evidence that performs best in .app disputes includes: the WHOIS/RDDS registration history showing the date the domain was acquired; any app-store submissions (Google Play, Apple App Store) that reference the domain; product documentation, screenshots, or code-repository records with timestamped commits; third-party communications – investor emails, partnership inquiries, developer community posts – that use the domain name naturally; and any business records (incorporation, VAT registration, domain purchase receipts) tying the registrant to the project predating the trademark claim.

What weakens the record? A domain that was registered, then parked with pay-per-click advertising matching the complainant's industry, then developed only after the complaint arrived. Or a pattern of owning multiple near-identical domains across different TLDs, particularly where the .com is also disputed. Panels look at the totality of the record. Building your response means assembling every piece of that totality, not only the favorable parts – because the panel will see the unfavorable parts anyway.

If you have just received a commencement notice for a .app domain, the time to assess the evidence is now, not after the deadline passes. To begin your defense assessment, contact info@cognomenlaw.com.

When Is a Reverse Domain Name Hijacking Finding Realistic?

Reverse domain name hijacking (RDNH) is a finding that the complainant brought the proceeding in bad faith – specifically, to deprive a legitimate registrant of a domain it was entitled to hold. The finding carries no monetary penalty under the UDRP, but it is publicly published in the forum's case database. For a corporate complainant, an RDNH finding is a reputational event that affects future filings before the same panels and forums.

When do panels find RDNH? The consensus view identifies several recurring patterns: a complainant with a trademark registered after the domain; a complainant who knew the registration predated its rights and filed anyway; an attempt to use the UDRP as a cost-effective substitute for a trademark infringement action that would require actual evidence; and cases where the complaint's factual assertions are demonstrably false or exaggerated.

For .app domains, RDNH is realistic where the complainant is a well-resourced brand owner who identified the domain in a monitoring sweep, found a registration date that predates its mark, and filed regardless – calculating that a default was likely. Panels have noted that the UDRP was not designed to recover domains from registrants who had a legitimate purpose when they registered. Where we see that pattern, we will raise RDNH affirmatively in the response, because a filed claim, not a merely defensive posture, is what motivates a panel to address it.

For a deeper examination of when RDNH findings are granted and how to argue for one, see our guide to seeking an RDNH finding.

If the complaint names a .app domain you registered before the complainant's trademark existed, an RDNH argument may be available. Email info@cognomenlaw.com to weigh whether the facts support it.

What Evidence Decides the Outcome in a .app UDRP Defense?

The single most important variable in a .app UDRP defense is the relationship between the domain's registration date and the complainant's trademark rights. Everything else – use, parked content, communications about the domain – is read through that temporal lens. A registrant who cannot show a plausible, pre-dispute purpose that is independent of the complainant's brand will struggle even if the domain was never used for anything abusive.

Panels also weigh the following: whether the registrant responded at all (a filed response, even an imperfect one, puts evidence in front of the panel); whether the domain is passively held or actively used for something unrelated to the trademark; whether the complainant's rights are narrow or broad (a mark limited to a specific geographic market may not support a finding of bad faith targeting); and whether the complainant attempted to purchase the domain before filing and, if so, what the registrant said in response.

In a recent matter – a .app dispute filed in spring 2025 – we defended a developer-registrant who had built a small productivity application under the disputed name for approximately three years. The complainant was a software company that had registered a mark after the domain was created. We documented the development history, assembled app-store records and code-repository timestamps, and argued that the registration predated any trademark rights the complainant could demonstrate. The case ended with the complaint denied and an RDNH finding recorded.

A second matter – a .app portfolio holding, autumn 2024 – presented a harder set of facts. The registrant had not developed the domain and held it alongside a number of similar registrations. We built the response around the registrant's established history in the secondary domain market, the generic character of the second-level label, and the absence of any targeting conduct. The complaint was denied on element three, without transfer.

How Does a .app UDRP Compare to Other Routes the Complainant Might Use?

The right route depends on what a complainant is actually entitled to pursue. If the domain is a .app and the complainant holds a registered trademark with a plausible similarity argument, UDRP at WIPO is the standard path. The filing fee for a single-panel WIPO case starts at USD 1,500, the procedure runs roughly two months, and the only remedies are transfer or cancellation.

If the complainant wants money – damages, attorney's fees, a permanent injunction – the UDRP cannot provide any of those. US anticybersquatting litigation in federal court is the only route that reaches monetary relief, and it is substantially more expensive and slower for both sides. A complainant who threatened a lawsuit but filed a UDRP instead may simply be cost-managing. That calculation can be worth addressing in the response.

What about URS? The Uniform Rapid Suspension procedure applies to new gTLDs and .app qualifies. URS has a higher evidentiary threshold – "clear and convincing" evidence – and the remedy is suspension, not transfer. A complainant who wants the domain transferred to itself cannot get that through URS alone. URS is used more commonly where the complainant's goal is rapid disablement of an infringing use, not acquisition of the asset. If the complainant filed UDRP, it wants the domain.

For a broader look at COGNOMEN's respondent-defense work across all zones, see our respondent defense and RDNH service overview.

Cost Structure: Forum Fees and Legal Fees Separated

The forum filing fee is borne by the complainant. A respondent does not pay a filing fee to participate. The cost of mounting a defense is therefore the cost of legal preparation, not of forum access. That is a meaningful difference from court litigation, where both sides face filing fees and procedural costs from the outset.

Legal fees for a UDRP respondent defense are fact-dependent. For a straightforward single-domain .app case with clear legitimate-interest evidence and no RDNH component, a flat-fee engagement in the market typically falls in the USD 3,000–7,000 range, covering response drafting, evidence assembly, and panel submission. More complex matters – a three-member panel request, an RDNH component, a parallel URS filing, or a dispute that also involves a .com – attract higher fees.

If the respondent requests a three-member panel, the parties generally split the incremental cost. At WIPO, a three-member panel on a single-domain case costs USD 4,000 in total filing fees; the split mechanism means the respondent picks up approximately half of the difference above the single-member fee. That cost is sometimes worth bearing where the case is close and a single panelist's idiosyncratic view of, say, passive holding in the tech sector could decide the outcome.

For .de domains, note that the UDRP does not apply. Disputes over .de domains proceed through the German courts, with a DENIC DISPUTE entry available to block transfers while the litigation runs. If a registrant holds both a .app and a .de under the same brand and faces complaints on both, the two proceedings are structurally separate with different cost profiles. For the .de procedural route, see our guide to registrar lock escalation for .de domains.

What Happens After the Response Is Filed?

Once WIPO receives the response, it proceeds to panel appointment. For a single-member panel at WIPO, the panel is typically appointed within a few days of the response deadline passing. The panel then reviews the full record – complaint, annexes, response, and any annexes the respondent filed – and issues a decision. Supplemental filings are not a matter of right; panels may accept them in limited circumstances (new facts arising after the response, for instance), but submitting additional materials without leave is usually disregarded.

The panel's decision is published in WIPO's online case database, regardless of which side prevails. If the panel orders transfer, the registrar implements it after a brief waiting period during which the registrant may commence a court proceeding in the relevant jurisdiction to halt implementation. That window is short, and relying on it as a fallback is not a strategy – it is an emergency option for extreme cases.

A denial of the complaint leaves the registrant in possession of the domain. A finding of RDNH is appended to the published decision. In either outcome, the complainant retains the right to bring a court action – the UDRP does not preclude that – but a published denial makes the subsequent litigation path more difficult for the complainant to navigate.

Related at COGNOMEN

• Respondent defense and RDNH across gTLDs and ccTLDs – service overview
• How to seek a reverse domain name hijacking finding – step-by-step guide
• Registrar lock escalation for .de domains – procedural guide