FAQ: defend a .app domain registered before the complainant's tradema…

What does it mean to defend a .app domain registered before the complainant's trademark?

Defending a .app domain in this context means contesting a UDRP complaint on the ground that the complainant's trademark rights did not exist when you registered the domain – and that you therefore could not have registered it in bad faith toward those rights. The .app zone is a new gTLD managed by Google Registry; it operates under standard UDRP rules administered by WIPO, the Forum, CAC, or ADNDRC. The legal test is the same three-element test that applies to .com: the complainant must prove (1) confusing similarity to a mark it holds, (2) your lack of rights or legitimate interests, and (3) registration and use in bad faith. A successful respondent defense breaks that chain at element three, element two, or both.

We regularly advise registrants who received a UDRP complaint years after registration, only to find the complainant's trademark application postdates the registration by months or years. That gap matters. It does not end the inquiry – panels will also examine your use of the domain, your conduct after registration, and whether the complainant had common-law rights that predate your registration – but it is often the decisive fact.

What does it mean when a .app domain is governed by UDRP via WIPO?

Because .app is a generic top-level domain, ICANN-accredited registrars apply the UDRP as a condition of registration. WIPO is the leading forum for .app disputes, handling the large majority of new-gTLD UDRP proceedings. Filing a complaint at WIPO triggers the five-stage procedure: complaint, commencement, response, panel appointment, and decision. As a respondent, you have 20 days from formal commencement to file your response. Missing that window results in a default – the panel proceeds on the complaint alone, which almost always means transfer. The registrar implementing a transfer decision is similarly bound by the UDRP Rules.

One procedural nuance specific to new gTLDs like .app: the URS (Uniform Rapid Suspension) is an alternative remedy available to complainants. URS results in suspension, not transfer, and applies a higher "clear and convincing" standard. If you receive a URS notice rather than a UDRP complaint, the response window is shorter still – verify the deadline with counsel immediately. In our practice, the majority of well-funded complainants pursuing a .app domain choose the full UDRP rather than URS precisely because transfer is the remedy they want.

What does it cost to defend a .app domain registered before the complainant's trademark at WIPO?

The WIPO filing fee for a UDRP complaint is paid by the complainant, not the respondent. As a respondent, your direct forum fee is zero unless you request a three-member panel. If the complainant filed for a single panelist and you want three panelists, you request the upgrade and share the difference in cost: the three-member WIPO fee for one to five domains is USD 4,000, split between the parties under the Rules. For most respondents in a straightforward pre-trademark-registration case, a single-member panel is adequate.

Legal fees for respondent defense are separate. Market rates for UDRP defense work – document review, response drafting, evidence assembly – typically run in the USD 3,000–7,000 range for a single-domain case, depending on factual complexity and the volume of prior correspondence. Where the registration date gap is clear and contemporaneous evidence of your use is strong, the matter is more contained. Where the complainant alleges common-law rights predating your registration, the analysis is more involved. We present our fee ranges transparently before engagement.

How long does it take to defend a .app domain registered before the complainant's trademark?

A standard UDRP defense runs about two months from the date the complaint is filed to the panel's decision, assuming no procedural extensions. The respondent's window is fixed at 20 days from formal commencement – that clock starts, not from the date you first see the email, but from the date WIPO formally commences the proceeding. Panels rarely grant extension requests without a compelling reason. The practical implication: if you discover a complaint has been filed, do not wait.

Timeline pressure is real. A default – failing to file a response at all – is treated by panels as an admission of the factual record in the complaint. We have defended matters where the registrant's only contact was a panicked call four days before the deadline; workable, but avoidable. Where WIPO's expedited option applies (single-panel cases of up to five domains), a decision can arrive in about one month. Most .app respondent matters we handle produce a decision within the standard two-month window.

What evidence is needed to defend a .app domain registered before the complainant's trademark?

The most persuasive evidence package combines registration date proof, contemporaneous use evidence, and documentation of your purpose at the time of registration. Specifically: the original WHOIS or registration confirmation showing the registration date; any correspondence, business plans, code repositories, invoices, or screenshots showing you were actively building toward a legitimate use before you received notice of this dispute; and, where applicable, evidence that you were commonly known by the name or were making a bona fide offering. The Paragraph 4(c) safe harbors are not abstract – they require a factual record.

The registration-date gap alone is not enough. Panels also ask: what did you do with the domain after registering it? Passive holding – parking a domain on a revenue page with no development – weakens the defense even where registration predates the mark, because panels examine use as well as registration under element three. Ideally, you have contemporaneous artifacts: a commit history, a beta launch, a business registration, client emails referencing the name. In a recent matter (a .app domain, spring 2025), we built a legitimate-interest record from archived developer documentation and early user-registration logs; the panel denied the complaint and declined to transfer the domain.

If you cannot show contemporaneous use, focus on the complainant's burden. Under the UDRP, the complainant must prove bad faith; it is not enough to show the domain is similar to the mark. Where the trademark registration date clearly postdates the domain registration, the complainant faces a structural problem that no amount of reframing resolves – provided the respondent presents the timeline clearly.

Can I defend a .app domain registered before the complainant's trademark for more than one domain at once?

A single UDRP complaint may cover multiple domains only if they share the same registrant of record. If you hold several .app domains – or a .app alongside a .com, .net, or other gTLD – the complainant may consolidate them in one proceeding. You respond to all of them together in a single filing. That consolidation can work in your favor: a consistent record across multiple domains showing legitimate use and a coherent registration purpose reinforces the defense. It can also expose you to a single adverse decision that strips several assets at once.

Where you hold domains across multiple zones – say, a .app and a .com with similar facts – the UDRP complaint may cover both if the registrant is the same, even though the zones differ. Cross-zone defense requires coordinating the legitimate-interest narrative across all of them simultaneously. If a companion ccTLD is at issue, a separate procedure under the applicable national rules may also be necessary; those run on independent timelines. We regularly handle multi-domain and multi-zone respondent matters where the pre-trademark-registration argument applies across the portfolio.

What are the possible outcomes when you defend a .app domain registered before the complainant's trademark?

The panel can reach one of three outcomes: transfer of the domain to the complainant, cancellation of the domain, or denial of the complaint (meaning you keep the domain). Transfer and cancellation are the only affirmative remedies available under the UDRP – no monetary damages, no costs award. Denial leaves the domain in your hands with no further UDRP remedy available to the complainant (absent new facts or a separate court action). There is also the possibility of a Reverse Domain Name Hijacking finding.

RDNH – a panel determination that the complaint was filed in bad faith to deprive a legitimate registrant – is available where the complainant knew or should have known it could not succeed, typically because the registration predated the mark. An RDNH finding carries no monetary penalty, but it is a published reputational mark against the complainant and its legal team. In our practice, we pursue RDNH arguments whenever the pre-trademark registration gap is clear, the complainant is commercially sophisticated, and the record shows a deliberate attempt to use the UDRP as leverage rather than as a genuine dispute mechanism.

Outcomes are always fact-specific. A strong registration-date gap, combined with contemporaneous use evidence and a well-constructed response, produces the best conditions for denial and, potentially, an RDNH finding. A registration date gap without supporting use evidence leaves more room for the panel to find the domain was acquired opportunistically.

When is an RDNH finding realistic in a .app domain defense?

RDNH is realistic when three conditions align: the complainant's trademark application or registration clearly postdates the domain's registration date, the complainant is legally represented (putting it on constructive notice of the Policy's limits), and the complaint relies on weak or demonstrably incorrect facts. Panels are more willing to find RDNH in new-gTLD matters where the complainant filed knowing the registration predated the mark but chose to proceed anyway – treating the UDRP as a low-cost shakedown tool.

RDNH does not follow automatically from a denied complaint. Panels apply it sparingly. The strongest RDNH records we build include: a side-by-side comparison of registration dates and trademark filing dates; evidence that the complainant conducted (or could easily have conducted) a WHOIS search before filing; and a showing that the complaint's bad-faith theory is internally inconsistent with publicly available facts. If those elements are present, we include a dedicated RDNH section in the response.