How to suspend a .app domain through URS

How to suspend a .app domain through URS. UDRP and ccTLD domain recovery and defense across .app. Email the firm to assess your case. Transparent fees, respond…

A malicious actor registers [yourbrand].app, points it at a phishing page or a counterfeit storefront, and your customers start receiving fraudulent emails from an address that carries your name. You want the domain offline. Fast. The Uniform Rapid Suspension system – URS – was built exactly for this situation, and .app is among the new generic top-level domains where it applies.

To suspend a .app domain through URS, a complainant must satisfy a clear and convincing standard across all three elements of the Policy: that the domain is identical or confusingly similar to a mark the complainant holds, that the registrant has no rights or legitimate interests, and that the domain was registered and is being used in bad faith. The remedy is suspension for the remainder of the registration term – not transfer of ownership. WIPO is the primary URS provider for .app disputes.

This page covers how the URS test works in .app, what evidence decides a case, why URS and UDRP serve different needs, and how to start a filing.

Why does URS apply to .app domains?

The .app registry, operated by Google, launched in 2018 as one of the new generic top-level domains introduced through ICANN's new gTLD program. Every new gTLD registry that joined that program is contractually bound to offer URS as a dispute-resolution mechanism alongside the UDRP. .app is no exception. When Google entered the registry agreement, URS became part of the mandatory rights-protection framework for the zone.

What does that mean in practice? It means that a brand owner whose mark is being abused in a .app registration has two distinct paths available: URS for a rapid suspension, or UDRP for a transfer of ownership. Both paths are open. The choice between them is a strategic one, and it is the first decision that a practitioner handling a .app dispute must make.

WIPO administers URS cases for the overwhelming majority of new gTLD registries, including .app. Filing goes through WIPO's Center. The published procedure, the fee schedule, and the panelist pool are all WIPO infrastructure, even though the underlying URS rules are ICANN's.

The distinction from classic .com disputes matters to brand owners who think of domain recovery as a single category. In .com, UDRP is the standard tool and transfer is the standard remedy. In .app – and across new gTLDs generally – URS adds a faster, cheaper route, but one that stops short of returning the domain to the mark owner.

What is the URS standard, and how does it differ from the UDRP?

The URS applies a clear and convincing evidence standard – materially higher than the UDRP's preponderance-of-the-evidence approach. A complainant who could win a UDRP case may still fall short in URS if the evidence leaves any genuine factual ambiguity about the registrant's intent or the scope of the complainant's mark rights. Panels have consistently held that close or nuanced cases belong in UDRP, not URS.

The three elements are structurally identical to the UDRP's Paragraph 4(a) requirements. The complainant must show: first, that the domain is identical or confusingly similar to a mark in which the complainant has rights; second, that the registrant has no rights or legitimate interests; and third, that the domain was registered and is being used in bad faith. The cumulative "registered AND used" requirement is the same as in UDRP – it is not relaxed for URS.

Where URS diverges is in the remedy and the speed. The only URS remedy is suspension of the domain for the remainder of its registration term. The domain resolves to a UDRP lock page for that period. It does not transfer to the complainant. If the complainant wants ownership, UDRP is the right vehicle. URS is the right vehicle when the overriding goal is to take the domain offline immediately – stopping a phishing campaign, neutralizing a counterfeit site, or protecting consumers from confusion during a product launch.

There is also a timing difference. URS is designed to be resolved in a matter of weeks rather than the standard UDRP arc of roughly two months. That speed premium is the core commercial reason to file URS rather than UDRP when suspension – not transfer – is the immediate priority.

If you are weighing URS against UDRP for a .app domain and need to decide quickly, reach us at info@cognomenlaw.com. We assess the three elements, evaluate the evidentiary record, and advise on the forum and the filing strategy.

What evidence does a URS panel look for in a .app case?

Because the evidentiary bar is higher, the quality of the complaint record matters more in URS than in a standard UDRP filing. Panels reviewing .app URS cases expect the complainant to arrive with a clean, well-documented file – not one that relies on the panel to draw inferences that the evidence only partially supports.

On the first element – identity or confusing similarity – the complainant must show a registered trademark or, in some cases, an established unregistered mark. A live trademark registration in at least one major jurisdiction, ideally predating the .app registration, is the strongest foundation. The comparison is between the mark and the second-level label of the domain; the .app suffix is generally disregarded for this element because it is the required TLD extension.

On the second element – absence of rights or legitimate interests – the complainant presents negative evidence: the registrant is not commonly known by the name, has no license from the complainant, and made no bona fide use before notice of the dispute. In .app specifically, the all-HTTPS requirement that Google built into the zone means the domain must resolve over a secure connection – and where a .app domain resolves to a phishing page, a parked page, or an error, the absence of any legitimate use is typically evident from a screenshots-and-resolver check.

Bad faith – the third element – is where URS cases turn. The Paragraph 4(b) factors apply: registration to sell at a premium to the mark owner, registration to disrupt a competitor, intentional attraction of users by confusion for commercial gain, or a pattern of abusive registrations. In .app cases, panels have been attentive to the combination of the zone's app-ecosystem context (suggesting the registrant intended to target the complainant's mobile-app brand or customer base) and the HTTPS-only nature of the zone (suggesting the operator had technical capacity and intent). A phishing use, a counterfeit site, or a pay-per-click page exploiting brand recognition are each strong bad-faith indicators under the standard list of factors.

One fact pattern that recurs in our practice: a brand owner launches or announces a new mobile app; within days, a third party registers [brandname].app or [brandname-app].app; the domain goes to a parked page or a competitor's site. That sequence – registration immediately following a brand announcement or product launch – is powerful circumstantial evidence of bad faith and tends to clear the URS's higher evidentiary threshold.

URS or UDRP: which route fits a .app dispute?

The right route depends on what the complainant actually needs. The two procedures are not interchangeable.

If the immediate goal is suspension – getting the domain offline to stop ongoing consumer harm, halt a phishing campaign, or protect a product launch – and the evidence of abuse is unambiguous, URS is the faster and less expensive path. The filing fee is lower than the UDRP equivalent, and a decision typically arrives sooner. The trade-off is the remedy ceiling: URS will not hand the domain to the complainant.

If the goal is ownership – actually acquiring the .app domain and using it commercially – UDRP is the right vehicle. The WIPO filing fee for a UDRP single-member panel covering one to five domains is USD 1,500, and a standard case resolves in roughly two months. The UDRP's preponderance standard is also easier to meet where the evidence is solid but not airtight.

If the facts are genuinely ambiguous – for example, where the registrant has some colorable claim to the name, or where the mark is descriptive and the registration predates any consumer recognition – URS is likely to fail. Panels have consistently sent close cases back to UDRP. Filing URS in a borderline case risks a denial without a second chance at suspension under that procedure.

A third scenario arises where the complainant has both an urgent need for suspension and a longer-term interest in ownership. In that situation, filing URS now to neutralize the harm and then pursuing UDRP for the transfer is a sequenced approach that the procedures technically permit. Whether the cost and effort of two proceedings is justified turns on the facts – particularly whether the UDRP could be filed and decided before the URS suspension term expires.

There is also a cross-zone dimension. A brand facing abuse in .app may simultaneously face squatting in the .com equivalent, a .shop variant, or a country-code domain. URS applies only to new gTLDs; it is not available for .com, and it does not reach ccTLDs. Where the abuse spans both new-gTLD and classic zones, a combined strategy – URS for the .app, UDRP for the .com, and the applicable national procedure for any ccTLD – may be necessary. We regularly advise brand owners running parallel actions across multiple zones, coordinating filings and evidence to maximize consistency.

To weigh URS against UDRP for your .app domain, or to plan a multi-zone filing strategy, email us at info@cognomenlaw.com. We handle the full route-selection analysis before any filing fees are committed.

How does the URS filing process work at WIPO for .app?

WIPO's URS process for .app follows a defined sequence, designed to be faster than the standard UDRP pipeline. Here is how each stage runs.

The complainant prepares and submits the URS complaint through WIPO's online system. The complaint must identify the domain, the trademark basis, the three URS elements (with evidence attached), and the relief sought. WIPO conducts an administrative completeness review before the case formally commences – typically within a few business days of filing.

Once the case commences, the registrant receives formal notification and has a defined window to file a response. The window is shorter than in UDRP. If no response is filed, the case proceeds as a default – and the higher evidentiary threshold still applies; URS default is not automatic suspension. WIPO appoints a single examiner (URS uses "examiner" rather than "panelist"), who reviews the record on the papers. No in-person hearing takes place.

If the examiner grants the complaint, the .app domain is placed in a suspended state. It resolves to a WIPO-branded lock page for the balance of the registration term. The registrant cannot transfer, delete, or modify the domain during that period. At the expiration of the registration term, the complainant may choose to extend the suspension by paying the renewal fee – effectively keeping the domain in limbo – or allow it to expire and then register it through normal channels, subject to any priority claim.

If the examiner denies the complaint, the domain is released back to normal status. A denial in URS does not legally prevent the complainant from filing a UDRP complaint, though the factual record of the URS denial will be visible and a UDRP panel may consider it when assessing whether the complainant's evidence meets the UDRP standard.

In a recent matter – a .app domain used for a phishing campaign against a fintech brand, spring 2025 – we assembled the complaint record in under a week and the suspension order arrived before the end of the following month. The brand's customer-service team confirmed that fraudulent transaction attempts linked to the domain had stopped immediately after the suspension took effect.

What does a URS filing actually cost for a .app domain?

URS filing fees are lower than UDRP fees, and that is by design. The procedure was introduced partly to offer a cost-accessible option for clear-cut cases. At WIPO, URS fees are published and are notably below the UDRP equivalent; treat the current fee as a modest official fee compared to the WIPO UDRP single-panel rate of USD 1,500. Check the current schedule with us or directly on WIPO's site before budgeting, as fees may be updated periodically.

Legal preparation fees are separate from the official filing fee. A URS complaint for a single .app domain, where the evidence is clear and the trademark record is clean, typically falls at the lower end of the market range for UDRP work. A realistic budget for attorney preparation of a straightforward URS complaint – mark research, evidence compilation, complaint drafting, and WIPO submission – runs in a range that is meaningfully below the cost of a defended UDRP proceeding. We provide specific estimates after reviewing the mark and the domain in question.

How do fees split if the case escalates? If a URS case proceeds and the respondent appeals an adverse URS decision, additional fees and preparation time follow. Appeal in URS goes to a three-member panel. We address this in more detail in the FAQ section below.

What are the limits of a URS win, and what should a complainant do next?

A URS suspension order is a real result. The domain goes offline, consumer harm stops, and the registration is frozen. But it is not permanent ownership, and brand owners who secure a URS suspension should think clearly about what comes next.

The suspension lasts for the remainder of the current registration term. If the registrant registered a one-year .app domain six months ago and you win URS today, you have roughly six months of suspension. At the end of that term, the complainant may pay the renewal fee to extend the suspension – this right is explicitly recognized in the URS rules – or allow expiry and attempt to register the domain through normal channels.

Allowing expiry creates risk. The domain enters the deletion and drop cycle, and without a backorder or priority mechanism in place, a bad actor could re-register it. The extension-of-suspension right is valuable precisely because it sidesteps that race.

If the long-term goal is to own and use the .app domain – which it often is for brand owners whose names align with mobile-app branding – then a UDRP complaint, filed either in parallel with or following the URS, is the route to actual transfer. We have handled sequences where URS suspends the domain quickly, giving the brand's counsel time to build a cleaner UDRP record, and the UDRP then produces the transfer order. The two procedures work together when the strategy is designed from the outset.

A myth worth addressing: some brand owners assume that winning a URS case automatically resolves any related domain dispute across other zones or that it creates a permanent priority claim. It does not. A URS order in .app has no formal effect on a parallel .com or ccTLD registration carrying the same second-level label. Each zone is governed by its own dispute procedure, and each complaint stands on its own record.

What URS does create is a useful factual record. An examiner's finding of bad faith in a .app URS is evidence – admissible in a subsequent UDRP – that the registrant engaged in abusive registration conduct. Panels in UDRP proceedings have treated prior adverse URS findings as relevant to the Paragraph 4(b) pattern-of-conduct analysis, though the outcome in the UDRP turns on the UDRP record, not on the URS decision alone.

Related at COGNOMEN

• URS and new gTLD disputes – full practice overview across all zones
• How to suspend a .shop domain through URS – procedure and evidence guide
• FAQ: defending a generic domain name – respondent-side strategy