Step-by-step: act on a .app domain flagged by a Trademark Clearinghou…

Step-by-step: act on a .app domain flagged by a Trademark Clearinghou. UDRP and ccTLD domain recovery and defense across .app. Email the firm to assess your ca…

A Trademark Clearinghouse claims notice arrives in your inbox. The .app domain you want – or the one your brand already holds – has been flagged. What does that mean, and what do you do next? The answer is not obvious, because the notice is a warning, not a ruling. But it sets a legal clock in motion that very few registrants understand until it is too late.

To act on a .app domain flagged by a Trademark Clearinghouse (TMCH) claims notice, you must first determine whether you are the registrant receiving the notice or the brand owner triggering it. For brand owners, the notice opens a narrow window to pursue either a Uniform Rapid Suspension (URS) – which suspends the domain for the registration term but does not transfer it – or a UDRP complaint, which can achieve transfer or cancellation. For registrants, the notice carries legal consequences: acknowledging it in writing may complicate a later legitimate-interest defense. The correct step depends entirely on which side of the dispute you occupy, and on what evidence you already hold.

This guide walks through each step in order – from reading the notice correctly, through choosing the right procedure, to assembling evidence, filing, and understanding what the outcome can and cannot deliver under the .app zone's rules.

What is a Trademark Clearinghouse claims notice in the .app zone?

A TMCH claims notice is an automated pre-registration alert generated when a registrant attempts to register a domain string that matches – or closely matches – a mark recorded in the Trademark Clearinghouse database during a new gTLD's Claims Period. Google Registry operates the .app zone and has incorporated the TMCH mechanism as required under ICANN's new gTLD program. The notice is not a threat of legal action. It is disclosure: ICANN's rules require the registrar to inform the prospective registrant that a matching trademark record exists, and the registrant's acknowledgment is logged.

Why does the acknowledgment matter? Because if the registrant proceeds after seeing the notice – and the domain is later found to infringe the recorded mark – that logged acknowledgment can be used by a panel to support a finding of bad faith. The UDRP's Paragraph 4(b) bad-faith factors do not include notice-acknowledgment by name, but panels have consistently held that registration with actual knowledge of a conflicting mark satisfies the bad-faith element, particularly where no plausible legitimate use is evident. Receiving the notice and proceeding anyway is not inherently bad faith, but it removes the "I did not know" argument entirely.

For the brand owner whose mark is recorded in the TMCH, the notice is evidence of something different: confirmation that a third party has just registered a domain matching your mark. The next question is whether to file a URS or a UDRP complaint – and that choice has consequences that do not reverse.

Step 1: Identify which role you occupy and read the notice carefully

Before taking any action, determine precisely whether you are the brand owner (the complainant side) or the registrant who received the notice (the respondent side). This sounds obvious. It matters because the deadlines, the burdens of proof, and the tactical options run in opposite directions.

If you are the brand owner: confirm that your mark is validly recorded in the TMCH, that the .app domain string is identical or confusingly similar to that mark, and that you are within any applicable filing window. Check whether the registration occurred during the Sunrise period (limited to TMCH-recorded mark holders) or the Claims period or general availability. A Sunrise registration that you did not win may itself signal bad faith if the registrant cannot demonstrate legitimate interest – but the procedural route to remedy that is a UDRP or URS complaint filed after general availability, not a challenge to the Sunrise process itself.

If you are the registrant: review exactly what the notice says and what you acknowledged at registration. Do not send any informal correspondence to the mark owner at this stage. A poorly worded email offering to "work something out" has been treated by panels as evidence of awareness of infringement. Compile your evidence of legitimate interest – prior use of the name in commerce, personal name rights, non-commercial fair use – before any dispute commences.

If you received a TMCH claims notice and are unsure whether your registration is defensible, contact COGNOMEN at info@cognomenlaw.com before responding to any demand letter. The way you respond – or whether you respond at all – shapes the evidentiary record for any later URS or UDRP proceeding.

Step 2: Understand the two available procedures for .app – URS and UDRP

Two procedures apply to .app disputes before WIPO: the Uniform Rapid Suspension system (URS) and the Uniform Domain-Name Dispute-Resolution Policy (UDRP). They share a three-element legal test but differ fundamentally in remedy, evidentiary standard, and cost. Choosing the wrong one at this stage is the most consequential mistake we see brand owners make.

The URS was designed for new gTLDs and offers speed. Under the URS, the only remedy is suspension of the domain for the remainder of its registration term. The domain does not transfer to you. When the term expires, the registrant can renew it. That is not a hypothetical: we have seen URS complainants suspend a domain only to watch the registrant renew it at term end and resume infringing use. The URS applies a higher evidentiary threshold – clear and convincing evidence on all three elements – rather than the UDRP's preponderance-based approach. It is faster and the filing fee is lower, but it leaves the domain in the registrant's name.

The UDRP at WIPO applies to .app domains and can achieve transfer or cancellation. The evidentiary standard is preponderance of the evidence – that is, the more-likely-than-not standard across the three Paragraph 4(a) elements. The filing fee begins at USD 1,500 for a single-member panel on one to five domains. A standard case is normally completed within about two months. The UDRP is the route to choose if you want the domain.

In practice, the decision matrix is straightforward. If the infringement is clear, the domain is recently registered, and you want to hold it long-term, file a UDRP. If you need the domain taken offline within weeks to stop active consumer harm – fake-review sites, phishing, competitor misdirection – and you accept that the domain remains in the registrant's name, URS is faster. If you want both speed and transfer, consider filing a UDRP and requesting WIPO's expedited option, which can deliver a decision within approximately one month for single-panel cases of up to five domains.

See our detailed service overview at URS and new gTLD disputes at COGNOMEN for a fuller comparison of the two procedures across zones.

Step 3: Assess whether the three UDRP elements are met for your .app domain

Every UDRP complaint – and every URS complaint – requires the complainant to satisfy all three elements of Paragraph 4(a). A weak third element defeats the entire complaint, regardless of how strong the first two are. Assess each element honestly before filing, because a failed complaint carries reputational risk and, in clear cases of overreach, a finding of Reverse Domain Name Hijacking (RDNH).

Element one – confusing similarity is usually the strongest in a TMCH scenario, because the TMCH database only records marks that meet ICANN's validation standards. If your mark is recorded and the .app string matches it (ignoring the TLD suffix, which panels treat as generic), this element is typically met. The trap: similarity alone is not enough. A panel will still assess elements two and three rigorously.

Element two – lack of rights or legitimate interests requires the complainant to make a prima facie showing that the registrant has no rights. The respondent can rebut with any of the Paragraph 4(c) safe harbors: bona fide use before notice, being commonly known by the name, or legitimate noncommercial fair use. In a .app TMCH claims-notice scenario, the registrant's acknowledgment of the notice may foreclose the "didn't know" argument, but it does not foreclose a legitimate-interest defense based on independent business use of the same name. A party operating a legitimate app development service under a name that happens to match your mark may have a genuine defense. Do not assume element two is won automatically.

Element three – bad faith registration and use is the most fact-intensive. Panels consider whether the domain was registered primarily to sell it to the mark owner at a price exceeding out-of-pocket costs; to disrupt a competitor; to attract users for commercial gain through confusion; or as part of a pattern of abusive registrations. The TMCH notice acknowledgment is relevant here: a registrant who acknowledges the notice, registers anyway, and then points the domain at a monetized landing page has a weak position. But passive holding – parking the domain with no active content – can also support a bad-faith finding under what panels call the "passive holding" doctrine, particularly where the mark is well-known and no plausible legitimate use is evident.

If you are not certain whether all three elements hold on your facts, email info@cognomenlaw.com for a read on the elements before filing. A complaint that falls short on element three – even with a TMCH notice in hand – will not transfer the domain and may produce an RDNH finding.

Step 4: Assemble the evidence before you file

The evidence you submit with the complaint – or the response – is the record on which the panel decides. Panels do not conduct independent investigations. They decide on what the parties put in front of them. This step is where most self-represented parties underinvest, and where cases are lost.

For brand owners filing a UDRP: the core evidence package for a .app TMCH case should include the TMCH record and validation certificate confirming your mark's registration; trademark registration certificates or other evidence of mark rights (including common-law rights if the mark is unregistered); WHOIS / RDDS records for the .app domain showing registration date and registrant identity; screenshots of the domain's current use – active site, parking page, pay-per-click links, or any ransom demand; any prior communications from the registrant (email, broker communications, offer to sell); and evidence of prior bad-faith registrations by the same registrant if a pattern exists.

For registrants defending a URS or UDRP: the response record should establish when and why you chose this domain name – independently of any awareness of the complainant's mark. Contemporaneous business records from before registration are the most powerful evidence: company registration documents, app store listings, web-development invoices, correspondence with developers, domain purchase receipts. If you acknowledged the TMCH notice, you will need to explain why you proceeded: your defense must show an affirmative reason that is independent of any intent to exploit the mark owner's goodwill.

A practical note: screenshots are timestamped. Do not take them once the dispute commences and present them as evidence of pre-dispute use. Panels are experienced at identifying fabricated timelines. Contemporaneous third-party evidence – invoices, emails, archived web captures from services like the Wayback Machine – carries far more weight.

In a recent matter (a .app domain, spring 2025), we assembled a legitimate-interest record for a registrant who had operated a software testing tool under the disputed name for several years before the TMCH notice was generated. The complainant's complaint relied almost entirely on the TMCH acknowledgment as bad-faith evidence. We countered with timestamped development records and a public app-store listing that predated the complainant's own TMCH registration date. The panel denied the complaint and declined to make an RDNH finding, given that the complaint was not brought in demonstrable bad faith – but the margin was narrow, and it turned on those pre-registration records.

Step 5: Choose the forum and file correctly

For .app URS and UDRP complaints, WIPO is the leading forum. The Forum (formerly the National Arbitration Forum) also accepts UDRP complaints covering .app domains. WIPO and the Forum together handle the overwhelming majority of new-gTLD disputes, and both have well-developed bodies of decisions on TMCH-related bad-faith arguments.

WIPO filing fees for a UDRP are USD 1,500 for a single-member panel on one to five domains. A three-member panel costs USD 4,000 at WIPO. If the complainant requests a single panelist but the respondent requests three, the parties generally split the higher fee. The Forum's entry fee begins at approximately USD 1,300 for one to two domains under a single-member panel. The Czech Arbitration Court (CAC) also accepts new-gTLD complaints at lower entry fees – typically in the range of USD 500–800 – but it is the least-used of the principal forums and has a thinner body of new-gTLD precedent.

Forum selection matters beyond price. WIPO's panel pool has extensive new-gTLD and TMCH experience, and its expedited option can deliver a decision in approximately one month where the case involves a single panel and up to five domains. If your .app infringement is causing active business harm – customer diversion, phishing – that expedited track is worth the administrative coordination it requires.

For URS specifically, WIPO and the Forum both serve as URS examination providers for .app. The URS fee is lower than a UDRP, reflecting the more limited remedy. File through the provider that accepts URS cases for your specific gTLD registry – confirm current provider status with the registry before filing, as registry–provider relationships can change.

Cross-zone note: if the infringing registrant has also registered the same string across other new gTLDs – .dev, .page, .web – a multi-domain UDRP complaint covering all registrations under a single registrant can be filed as one proceeding, as long as the same entity holds them all. That consolidation avoids duplicate filing fees and produces a single decision covering the entire portfolio of infringing names. We regularly advise brand owners with clusters of new-gTLD infringements on how to structure consolidated complaints efficiently. For a broader look at new-gTLD launch protections and portfolio strategy, see our analysis of new-gTLD launch protection mechanisms.

Step 6: Understand what the panel will decide – and what it cannot

The UDRP's remedies are limited to transfer or cancellation. No monetary damages. No injunction. No costs award. No finding of trademark infringement in any legal sense. A UDRP decision is not a court judgment; it does not bind a court in later litigation, and it does not create res judicata. A losing registrant can – and sometimes does – file a court action within ten business days of the transfer order to prevent the registrar from implementing it. That is rare in practice, but it is a real option that well-advised registrants use where the stakes are high.

For URS, the decision is binary: the domain is suspended or the complaint is denied. Suspension lasts for the registration term. Renewal by the registrant at term end restores the domain to active status. For this reason alone, brand owners whose goal is long-term control of a domain should file a UDRP, not a URS.

Can a three-member panel change the outcome? Yes – and not only by adding expertise. A three-member panel in a UDRP case requires the complainant to pay the higher WIPO fee (USD 4,000), unless the respondent requests the three-member panel, in which case the fee is split. Three-member panels are more likely in high-value disputes, cases with genuine competing rights, or cases where either party flags inconsistent decisions in the single-panelist body. The decision of a three-member panel carries greater persuasive weight in later proceedings at the same forum, though neither single- nor three-member decisions bind future panels as legal precedent.

For registrants, an RDNH finding by a three-member panel carries added weight. RDNH has no monetary consequence – the Policy provides none – but it is a public record that the complaint was brought in bad faith to deprive a legitimate registrant. Where a brand owner has a pattern of filing abusive complaints, an RDNH finding in a three-member decision is a meaningful deterrent tool.

In a recent matter (a .app cybersquatting complaint, late 2024), a three-member panel denied transfer after finding that the complainant's trademark rights were narrowly scoped to a specific geographic market and the registrant operated a genuinely distinct business under the same name in a different region. The complainant had filed a UDRP specifically to avoid a negotiated sale at a price it considered too high. The panel's RDNH finding reflected that calculation. Brand owners should calibrate their decision to file against both the strength of the three elements and the appearance of the complaint in a commercially adversarial light.

What to do if you are the registrant – defending a TMCH-triggered .app dispute

Respondent-side strategy in a TMCH claims-notice dispute differs sharply from the complainant's playbook. The registrant has 20 days to file a response after the proceeding commences. That deadline is strict. A failure to respond does not automatically result in transfer – a panel still assesses the three elements – but a default removes all respondent-supplied evidence from the record. Defaulting is almost always the wrong choice where a genuine defense exists.

The respondent's strongest position is a positive case for legitimate interest under one of the Paragraph 4(c) safe harbors. The most effective safe harbor in a .app TMCH context is the first: bona fide use of the domain in connection with a genuine offering of goods or services before notice of the dispute. "Before notice" means before the URS or UDRP complaint was filed, not before the TMCH claims notice was generated – though the claims-notice acknowledgment will be presented as evidence that the registrant had constructive knowledge from the moment of registration.

We regularly advise registrants who received a TMCH claims notice, registered the domain in good faith for a legitimate purpose, and now face a UDRP complaint from a brand owner who assumed the worst. The notice-plus-registration sequence looks bad in isolation. In context – with pre-registration business records, a developed app, a genuine user base – it is entirely defensible. The work is in the evidence.

Where the complainant's conduct overreaches – where the mark rights are thin, the geographic scope is narrow, or the sole apparent purpose is to force a below-market sale – we build the RDNH record as a parallel objective. An RDNH finding will not recover legal fees, but it does something else: it makes the next abusive complaint from the same complainant harder to file without reputational cost.

For domain transaction and pre-acquisition questions that arise after a dispute is resolved – including escrow and due diligence on a domain's dispute history – see our resource at domain escrow and acquisition FAQ.

Related at COGNOMEN

• URS and new gTLD disputes – full service overview for brand owners and registrants
• New gTLD launch protection mechanisms – analysis of Sunrise, TMCH, and EAP
• Domain escrow and acquisition FAQ – due diligence, chain of title, and dispute history