How to defend a .app domain registered before the complainant's trade…

How to defend a .app domain registered before the complainant's trade. UDRP and ccTLD domain recovery and defense across .app. Email the firm to assess your ca…

A brand launches its product, files a trademark, and then discovers a .app domain registered months or years before the filing date — by someone with a different purpose entirely. The complainant sees the domain as a threat. The registrant sees it as theirs, fairly acquired. When the UDRP complaint lands, the registrant has 20 days to respond, and the case turns on a single analytical question: does a registration that predates the trademark itself constitute bad faith?

To defend a .app domain registered before the complainant's trademark, the respondent must demonstrate that the domain could not have been registered in bad faith because the trademark rights did not yet exist at the date of registration. This pre-registration timeline is the foundational defense under Paragraph 4(a)(iii) of the UDRP. Panels have consistently held that a registrant cannot have targeted a mark that did not exist — and where the complainant pressed the claim anyway, a finding of Reverse Domain Name Hijacking (RDNH) is a realistic and achievable outcome.

This page covers the legal test as it applies to .app domains, the evidence that builds a winning defense, the safe harbors under Paragraph 4(c), and how to position an RDNH argument — with a candid read on where panels draw the line.

Why .app Domains Are Filed Under UDRP Rules at WIPO

.app is a new generic top-level domain (new gTLD) operated by Google Registry, and it is subject to the UDRP in the same way .com and .net are. A complainant files the complaint before one of the ICANN-accredited dispute-resolution providers — most commonly WIPO or the Forum — and the three-element test of Paragraph 4(a) applies without modification. There is no separate national procedure for .app. The UDRP is the exclusive administrative route; a complainant who wants the domain transferred must win all three elements before a UDRP panel.

What sets new-gTLD disputes apart, in practice, is the registration date. Because .app opened to the general public in May 2018, many registrants hold domains that pre-date trademarks filed by companies that only emerged or rebranded after that date. The gap between the domain registration date and the trademark priority date is frequently decisive — and it is where the defense anchors.

For respondents before WIPO, the forum filing fee on the complainant's side starts at USD 1,500 for a single-member panel. If the respondent requests a three-member panel, the parties generally split the higher panel fee of USD 4,000. The case is normally decided within about two months of filing. That window is tight, but it is enough time to build a thorough, well-documented defense if work begins immediately on receipt of the complaint.

The Three UDRP Elements — and Where the Pre-Registration Defense Lives

A complainant must satisfy all three elements of Paragraph 4(a) to obtain a transfer order. Defeating any one element defeats the complaint. The pre-registration defense speaks most directly to the third element — bad faith registration and use — but it intersects with the second as well.

The first element asks whether the domain is identical or confusingly similar to a trademark in which the complainant has rights. Respondents rarely win here: the comparison is mechanical, and panels generally give the complainant the benefit of the doubt on similarity. Do not build the defense on this element alone.

The second element asks whether the respondent has rights or legitimate interests in the domain. This is where Paragraph 4(c) safe harbors become the respondent's affirmative tool. The complainant carries the initial burden, but in practice a respondent must come forward with a credible case. Relevant safe harbors include: a bona fide offering of goods or services before any notice of the dispute; being commonly known by the domain name; and legitimate noncommercial or fair use. For a domain registered well before the complainant's trademark filing, the bona fide offering safe harbor is often accessible — particularly if the registrant used the domain for a project, a service, or a portfolio purpose that predates the complaint.

The third element is where the pre-registration argument is most powerful. Panels have consistently held that, as a general rule, a registrant who acquires a domain before the complainant's trademark existed — and without knowledge of any pending mark — cannot have registered the domain with the specific intent to target that mark. Bad faith requires a target. No mark, no target. That reasoning is well-settled in the UDRP consensus view, set out in the WIPO Jurisprudential Overview, and it is the cornerstone of a pre-registration defense.

If you have received a UDRP complaint against a .app domain you registered before the complainant's trademark priority date, contact info@cognomenlaw.com immediately. The 20-day response window starts on the day the case commences — not the day you notice the email.

How Do Panels Assess Bad Faith When the Domain Pre-Dates the Trademark?

The consensus position is clear: a domain registered before a trademark was filed cannot ordinarily be found to have been registered in bad faith targeting that mark. But panels do not stop at the registration date. They examine the full picture, including whether the trademark had acquired unregistered — common law — recognition before registration, whether the domain was acquired in a secondary market after the mark emerged, and whether the registrant's conduct after registration suggests a later predatory purpose.

Three fact patterns tend to undercut the pre-registration defense even when the timeline looks favorable. First, if the complainant can demonstrate that it had substantial common-law or unregistered rights before the domain was registered — a well-known startup brand, for example, that achieved significant press coverage before its formal trademark filing — panels will look past the filing date. The relevant question is the date of the complainant's rights, not the date of their registration certificate. Second, if the respondent acquired the domain in the aftermarket at a date when the trademark already existed, the original registration date is irrelevant; the acquisition date controls. Third, if the domain has been used in a way that targets the complainant post-registration — redirecting to a competitor, sending phishing traffic, or demanding a price far above registration cost — those acts can establish bad faith in use even where registration was innocent.

In a matter we handled in the .app space (late 2024), a complainant filed against a registrant who had held the domain since the year .app opened publicly. The complainant's trademark filing postdated registration by more than a year. We documented the registration timeline, produced evidence of the registrant's pre-dispute use for a legitimate software project, and demonstrated that the complainant had filed knowing the domain predated its mark. The panel denied the transfer and found RDNH.

The obverse case also appears in our practice. Where a registrant had originally registered a .app domain legitimately before the mark, but then in mid-2025 redirected the domain to a PPC landing page featuring the complainant's brand after the complainant became prominent, the later use created a bad-faith-in-use finding. Pre-registration timing alone did not save the domain when subsequent conduct was plainly targeting.

Building the Legitimate-Interest Record: What Evidence Moves Panels

Winning the second element requires more than asserting a safe harbor. Panels expect documentary proof. The defense record should be assembled as soon as the complaint arrives — many of the most useful documents are dated materials that must be retrieved promptly before links rot, accounts are closed, or logs are lost.

For a pre-registration .app domain, the following categories of evidence are typically the most persuasive.

• Registration history: WHOIS or RDDS records showing the original registration date, and the registrant's identity at that date. If the domain was registered close to the date .app opened, a screenshot of the registration confirmation email with its timestamp is particularly strong.
• Use before notice: Any evidence that the domain was used — even in development or beta form — for a genuine purpose before the complainant's complaint or cease-and-desist. This includes git commits referencing the domain, developer screenshots, app-store submissions, API documentation, or marketing materials dated before the dispute.
• Business rationale: A clear, credible explanation for why this particular domain was chosen. Generic or descriptive terms are easier to explain; coined terms require more. If the term is descriptive of a technology function — common in .app registrations — that context matters.
• The complainant's trademark timeline: The complainant's own trademark application and registration data, drawn from the relevant national office or WIPO Madrid, proving that the priority date is later than the registration date. This is the backbone of the bad-faith defense.
• Absence of targeting: Evidence that the registrant had no knowledge of the complainant at the time of registration — no mention of the complainant in the registrant's prior communications, no contemporaneous news coverage of the complainant's brand in the registrant's market.

We regularly advise registrants who have strong chronological facts but weak documentary records. If your domain pre-dates the trademark but you have no contemporaneous evidence of your intended use, the defense is harder — though not impossible. The panel will weigh the plausibility of the registrant's account against the complainant's claims. A clear, coherent narrative, supported by even limited corroboration, is more persuasive than a bare assertion.

When Is a Reverse Domain Name Hijacking Finding Realistic?

RDNH is a finding that a complainant brought or maintained a UDRP complaint in bad faith — typically, knowing it could not succeed, or using the UDRP to harass a legitimate registrant. The finding is reputational; the UDRP provides no monetary penalties. But an RDNH finding is published alongside the decision and becomes part of the complainant's record before panels.

In a .app pre-registration case, RDNH becomes realistic where several factors converge. The complainant must have known — or should plainly have known — that the domain predated its trademark rights. The complainant must have been represented by counsel or have had access to basic WHOIS data that disclosed the registration date. And the complainant must have filed anyway, typically because it wanted the domain and calculated that the registrant would not respond.

Panels apply RDNH sparingly. A complaint that presents a weak but colorable claim will not attract the finding. Panels look for something more: a claim that was objectively unfounded from the outset. A complainant that filed with full knowledge that its trademark postdates the domain, combined with no plausible basis for arguing common-law priority at an earlier date, is the paradigm case. In our experience, requesting a three-member panel — at the cost of splitting the higher fee — meaningfully increases the likelihood of a formal RDNH finding, because three panelists applying collective scrutiny are more likely to articulate the full deficiency than a single arbitrator under time pressure.

RDNH is also available in cases where the complainant's first element argument fails on its face — for example, a mark that is so different from the domain that the claim was never credible — but in .app pre-registration matters, the timeline argument is usually cleaner and more decisive.

If the complaint against your .app domain relies on a trademark filed after your registration date, we can assess whether an RDNH finding is a realistic objective. Email info@cognomenlaw.com with the complaint and your registration details.

Choosing Between a Single-Member and Three-Member Panel

The complainant selects the panel size at filing. A single-member panel costs the complainant USD 1,500 at WIPO; a three-member panel costs USD 4,000. If the complainant selected a single panelist and the respondent believes the case is strong enough for a three-member panel, the respondent may request the upgrade. The cost difference — roughly USD 2,500 — is split between the parties, meaning the respondent pays approximately USD 1,250 to secure the three-member composition.

When is that upgrade worth it? In a pre-registration case with a clear RDNH angle, we typically advise requesting a three-member panel for three reasons. First, a three-member panel is more likely to issue a detailed, reasoned RDNH finding, which carries greater deterrent value for the complainant and its counsel. Second, the collegial deliberation of three panelists reduces the variance in outcome that a single panelist can introduce. Third, the published decision from a three-member panel carries more weight in any subsequent proceedings — including a court action or a future UDRP involving the same domain.

Against that: if the registrant is resource-constrained, the additional cost may not be justified where the single-element bad-faith defense is airtight and RDNH is a secondary objective. Each case turns on its facts.

Cross-Zone Considerations: What If the Complainant Also Holds the .com?

A common pattern in .app domain disputes is that the complainant already controls the .com equivalent and files to consolidate under the .app. The existence of the complainant's .com does not change the UDRP analysis, but it changes the litigation posture in several ways worth understanding.

If the complainant controls the .com and has actively used it in commerce before the .app was registered, that use may support a common-law trademark claim at a date earlier than the formal registration. The respondent should examine not just the registered trademark filing date but also the date the complainant began publicly using its brand — in press releases, app-store listings, and commercial agreements. A brand that launched publicly in, say, spring 2018 and filed its trademark in autumn 2018 may have common-law rights dating to the spring, which could pre-date a .app registration from summer 2018. The analysis is fact-specific; the defense cannot assume that the formal filing date is the only relevant date.

If the complainant holds both the .com and a .org or regional ccTLD equivalent, and files complaints across all of them simultaneously, the UDRP permits consolidation only where the respondent is the same registrant across all domains. A respondent who holds only the .app has no procedural exposure from complaints against other domains held by different registrants. However, a concurrent .app filing and a court action — for example, a US anticybersquatting action — is possible, and the respondent's litigation posture in the UDRP will be visible to any court that later reviews the case. We regularly advise clients on coordinating UDRP and court-level strategy where both are in play.

For disputes involving ccTLDs in addition to .app, the governing procedure differs zone by zone. A .app dispute runs under the UDRP; a parallel .uk dispute would run under the Nominet DRS, which applies a different test — "abusive registration" under a "registered or used" standard, a lower bar than the UDRP's cumulative "registered and used in bad faith." A .de dispute has no UDRP equivalent at all and proceeds through the German courts. Where a brand attack spans multiple zones, the defense strategy must be calibrated to each forum's rules independently.

What Happens If the Respondent Does Not File a Response?

Default — failing to respond within the 20-day window — does not automatically mean the complainant wins. A panel must still assess the complaint on its merits. But in practice, default dramatically weakens the respondent's position. The panel draws reasonable inferences from the available record, and without a response, the bad-faith and legitimate-interest elements are evaluated on the complainant's evidence alone.

In a pre-registration .app case, default is particularly costly. The registration-date defense requires the respondent to present the timeline, to point the panel to the trademark's priority date, and to document any pre-dispute use. None of that happens automatically from a WHOIS record. A panel reviewing a default complaint will generally give the complainant reasonable favorable inferences — including on the question of whether the respondent had prior knowledge of the mark — even where the timeline on its face looks favorable to the registrant.

We have stepped into a number of matters as late-stage respondent counsel — after a client received a default decision or discovered the complaint only after the response deadline had passed. In those situations, the procedural options are narrow: a request to re-open the case on grounds of extraordinary circumstances, or a court challenge to the UDRP decision under the registrar's agreement. Neither is straightforward. The far better outcome is to respond within the 20-day window, with a complete and well-documented submission. If you have received a complaint and the deadline is close, contact us immediately.

Related at COGNOMEN

• UDRP Respondent Defense and RDNH — full service overview for registrants facing a complaint
• Case Study: defending a .co domain registered before the complainant's trademark priority date
• Case Study: URS vs. UDRP in a new-gTLD tech domain dispute — choosing the right defense forum