Bring a court action when UDRP cannot reach a .store domain: what pan…

Bring a court action when UDRP cannot reach a .store domain: what pan. UDRP and ccTLD domain recovery and defense across .store. Email the firm to assess your…

A brand owner finds its trademark registered as a .store domain by an unknown party. The domain resolves to a competing storefront, or to nothing at all — a passive hold waiting for a buy-back demand. The instinct is to file a UDRP complaint. But what happens when the UDRP process stalls, produces the wrong outcome, or simply cannot reach the conduct at issue? That is when a court action enters the picture.

To bring a court action when UDRP cannot reach a .store domain, the complainant must identify the governing national statute in the relevant jurisdiction — most commonly US anticybersquatting legislation for .store domains registered by parties with US connections — and demonstrate bad-faith registration or use of a mark-identical or confusingly similar name. The UDRP at WIPO remains available for .store, with a USD 1,500 filing fee for a single-member panel and a standard decision window of roughly two months; but where the UDRP remedy of transfer or cancellation is insufficient, or where the registrant's identity or conduct falls outside the Policy's reach, a court action is the only path to damages, injunctive relief, or compelled disclosure.

This analysis covers the UDRP's scope as applied to .store, the fact patterns where arbitration falls short, the mechanics of shifting to court, the evidence that decides the outcome, and the cross-zone considerations that affect strategy when the same brand is at risk across multiple zones simultaneously.

How does the UDRP apply to .store domains, and where does it stop?

The UDRP applies to .store as a generic top-level domain in the same way it applies to .com and .net — the registry operates under ICANN's accreditation framework and all registrars for the zone are bound by the Policy. A complainant may file before WIPO, the Forum, or the Czech Arbitration Court (CAC); WIPO and the Forum together account for roughly 97% of all UDRP proceedings. The three-element test under Paragraph 4(a) of the Policy applies without modification: the domain must be confusingly similar to a mark the complainant holds, the registrant must lack rights or legitimate interests, and the domain must have been registered and used in bad faith.

That cumulative standard is where the Policy's boundary becomes visible. A registrant who acquired the .store domain in good faith, then pivoted to using it in a way that now conflicts with a mark, may defeat the bad-faith registration limb. A registrant operating under a name with a plausible non-infringing purpose can assert the Paragraph 4(c) safe harbors. Panels cannot award monetary damages — the only UDRP remedies are transfer or cancellation. And the Policy reaches only the domain name itself; it cannot compel discovery, freeze assets, or restrain conduct occurring on the associated website.

Where does that leave the brand owner? When the registrant's conduct involves fraud, passing off, tortious interference, or conduct rising to the level of a statutory anticybersquatting violation, the UDRP produces a result that is legally correct but commercially incomplete. Transfer of the domain name is achieved, but the underlying harm — diverted customers, counterfeit sales, reputational damage — goes uncompensated. In those situations, a court action either supplements the UDRP or replaces it entirely.

If you are weighing whether a UDRP complaint or a court action is the right path for your .store domain, contact info@cognomenlaw.com for an assessment of the three UDRP elements and the realistic litigation alternatives.

What fact patterns make a court action the better choice for a .store dispute?

The choice between UDRP arbitration and court is a strategic decision, not a formality. Four patterns in our practice reliably point toward court.

Pattern 1: damages are the goal. The UDRP cannot award money. If the registrant's conduct caused measurable harm — lost sales, costs of a recall campaign, customer confusion resulting in chargebacks — only a court can make the complainant financially whole. US anticybersquatting legislation, for example, provides for statutory and actual damages in qualifying cases. That possibility changes the calculus for any brand owner who suffered quantifiable losses before discovering the registration.

Pattern 2: the registrant's identity is unknown or deliberately obscured. Privacy and proxy registrations are routine in the .store zone. The UDRP requires the complainant to name a respondent and serve the complaint; if the registrar's privacy shield does not lift voluntarily, the formal notice may land at a proxy address with little practical effect. A court, by contrast, can issue pre-judgment discovery orders compelling the registrar to disclose the underlying registrant's identity. That disclosure may itself be the relief the brand owner needs before any further action.

Pattern 3: the UDRP produced an adverse decision or an RDNH finding. Panels occasionally find for the respondent — sometimes correctly, sometimes on a close reading of the bad-faith element that a court would weigh differently. A court is not bound by a prior panel decision, though the decision may be admitted as evidence. Similarly, if the respondent won a panel finding of Reverse Domain Name Hijacking against the complainant, the brand owner may wish to pursue the matter in a forum that can actually sanction the abusive registrant rather than merely note the complaint's failure.

Pattern 4: the conduct spans multiple domains and requires injunctive relief. A UDRP complaint covers only domains with the same registrant. A coordinated cybersquatting campaign using dozens of .store, .com, and ccTLD variants — different registrars, different registrant names — cannot be solved in a single arbitration. A court action can name multiple defendants, seek a broad injunction, and address the pattern as a whole.

In a recent matter (a .store and .com dual-registration cybersquatting campaign, autumn 2025), we advised a brand owner whose UDRP transfer order resolved the .com but left a separately registered .store untouched because the registrant of record differed. A court action consolidating both claims, and adding a demand for statutory damages, was the only mechanism that addressed the full scope of harm. The outcome depended on the court's view of the evidence — no result is guaranteed — but the court route was demonstrably the only path to complete relief.

Can a court action run alongside or after a UDRP, and what are the timing risks?

A court action may be filed before, during, or after a UDRP proceeding for the same domain — the Policy does not prohibit it. However, the interaction between the two creates timing risks that a practitioner must manage carefully.

If a court action is pending when the UDRP decision issues, the registrar is required to delay implementing a transfer for ten business days after notification of the panel's decision. During that window, the registrant may file in court specifically to stay the transfer. That filing does not automatically block implementation, but it creates a litigation record that the registrar will take seriously. A brand owner who wants the transfer to proceed cleanly should therefore time the court filing — if both routes are pursued — so that it does not inadvertently arm the respondent with a mechanism to delay a favorable UDRP outcome.

The reverse situation is equally important. If the brand owner files in court first, the UDRP complaint filed later proceeds in parallel unless one forum stays the other. WIPO panels are not courts and have no power to stay a court action; a court, on the other hand, may issue an order that effectively supersedes the UDRP proceeding. In practice, parties who initiate court proceedings for a .store domain and simultaneously file a UDRP complaint should coordinate both tracks carefully, because inconsistent positions in the two forums can damage credibility in each.

One zone-specific wrinkle: because .store is a new-style gTLD and not a national ccTLD, there is no separate ccTLD procedure sitting between the UDRP and the courts. The only administrative route is the UDRP (or, for a suspension-only remedy, the URS). That simplifies the procedural map but places greater pressure on getting the court strategy right when the UDRP's limits are reached.

If a prior UDRP filing produced an unsatisfactory outcome, or if a respondent has filed in court to block a transfer, email info@cognomenlaw.com to assess the litigation options for your .store domain.

What evidence does a court require that differs from UDRP practice?

UDRP panels work on paper and apply a balance-of-probabilities standard, constrained by a limited evidentiary record — the complaint, the response, and any supplemental filings the panel admits. Courts operate differently, and the evidentiary demands are substantially higher.

At the threshold, a court will require the brand owner to establish standing under the applicable statute. For US anticybersquatting litigation, that means demonstrating a valid trademark registration or sufficiently distinctive unregistered mark, registered or having acquired distinctiveness before the domain was registered. The timing of trademark rights relative to domain registration is scrutinized more carefully in court than in many UDRP proceedings, because courts consider the full factual record rather than the parties' competing written submissions.

Bad faith in a court context is assessed against a non-exhaustive statutory list that broadly mirrors the UDRP's Paragraph 4(b) factors but is applied with greater rigor. The registrant's intent at the time of registration — not merely subsequent use — is central. Documentary evidence of the registration process (WHOIS/RDDS history, registrar records, correspondence), the domain's configuration history (DNS records, hosting changes, archived website content), and any communications between the parties (buy-back demands, email exchanges, social media messages) become the factual spine of the claim.

What a brand owner must assemble before filing in court includes: a full chain of trademark ownership and registration history; a complete WHOIS/RDDS history for the .store domain from registration to the present; screenshots and archived copies of the domain's content at material dates; any monetization or redirection records (parking platform data, revenue records if obtainable); and a record of prior communications. If privacy registration was used, the registrar's response to any pre-litigation disclosure request should also be documented.

In a recent matter (a .store passive-hold case, spring 2025), the brand owner's court filing succeeded in part because we had assembled a contemporaneous archive of the domain's DNS records over an 18-month period, showing a pattern of pointed redirection that coincided with the trademark holder's product launches. That timeline evidence would have been difficult to present in a UDRP's condensed evidentiary format.

How do registrar-lock mechanics and transfer-reversal procedures interact with a court action?

When a .store domain is at risk — whether through cybersquatting, unauthorized transfer, or account compromise — the immediate practical step is a registrar lock: a status flag preventing the domain from being transferred to another registrar or registrant while the dispute is resolved. Understanding how that lock interacts with a court proceeding is critical.

A registrar lock can be obtained through two routes. The first is administrative: the brand owner or its counsel contacts the registrar directly and requests a hold pending dispute resolution, often citing the relevant ICANN transfer policy. Registrars are not obligated to grant this request in the absence of a formal proceeding, but many will hold the domain when a credible dispute is documented. The second route is judicial: a court can issue a temporary restraining order or preliminary injunction specifically directing the registrar to impose or maintain a lock while the case proceeds. That order travels from the court to the registrar and is not contingent on the registrar's voluntary cooperation.

Transfer-reversal mechanics matter most in domain theft and hijacking situations — cases where a domain was moved without the owner's authorization through account compromise or social engineering. The UDRP is not designed for domain theft; it addresses bad-faith registration, not unauthorized transfer. For a stolen .store domain, the correct first step is registrar escalation using the documented account-compromise evidence, combined with a UDRP or court action depending on whether the domain ended up with an identifiable bad-faith registrant or with a privacy shield obscuring the new holder.

Where a court action is the chosen route, the registrar-lock obtained by court order serves a dual purpose: it preserves the domain as an asset pending judgment and prevents the registrant from transferring the domain to defeat enforcement. The lock does not itself return the domain to the brand owner — that requires either a UDRP transfer order or a court judgment directing transfer — but it prevents the situation from worsening while the proceeding runs its course.

For more detail on the mechanics of recovering a stolen or hijacked domain and the registrar escalation process, see our service overview at COGNOMEN's court recovery services.

What is the consensus panel view on .store bad-faith patterns, and where does the minority sit?

UDRP panels hearing .store disputes apply the same jurisprudence developed across gTLDs since 1999. The consensus view is well-settled on several points. First, the generic nature of the word "store" in the TLD string is disregarded when assessing confusing similarity — panels compare the second-level domain to the complainant's mark, not the full domain string. A registration of brand.store is therefore assessed the same way as brand.com for the first UDRP element. Second, registration of a mark-identical second-level domain under .store, combined with use in commerce competitive with or impersonating the mark holder, satisfies both the confusing-similarity and bad-faith elements in the absence of a credible legitimate-interest defense.

Where panels diverge is at the edges of passive holding. The consensus position — established across thousands of decisions — is that passive holding of a domain confusingly similar to a mark can constitute bad-faith use under Paragraph 4(b), depending on the totality of circumstances: the distinctiveness of the mark, the absence of any plausible legitimate use, the respondent's concealment of identity, and prior conduct. The minority view, expressed in some decisions, is that passive holding alone is insufficient absent some positive act, particularly where the mark is descriptive or where the domain was registered before the mark achieved wide recognition.

That divergence matters practically. A brand owner whose mark is highly distinctive and globally known will almost certainly succeed on a passive-holding theory before most UDRP panels. A complainant with a weaker mark, or one that was not well-known at the time the .store domain was registered, faces a real risk of a denial — and, in egregious cases, an RDNH finding. Understanding where the panel consensus sits, and where the minority view might give a respondent traction, is essential before deciding whether to file a UDRP complaint or move directly to court.

A court, unlike a UDRP panel, can receive full testimonial and documentary evidence bearing on the registrant's knowledge and intent. That broader record often resolves the ambiguity that passive-holding cases generate in UDRP panels. The trade-off is cost and time: court litigation takes longer and costs more than a UDRP proceeding. The strategic question is whether the evidentiary advantage and the broader remedies justify the additional investment.

How do cross-zone considerations affect strategy when .store is one of several disputed domains?

The right route depends on the zone and the goal. If the domain is a .store gTLD and transfer is the sole objective, the UDRP at WIPO or the Forum is usually fastest and least expensive — the WIPO filing fee starts at USD 1,500 for a single-member panel covering up to five domains, and a standard case resolves in roughly two months. If the same registrant also holds a matching .com, both can be joined in a single UDRP complaint because they share a registrant of record. But if the .store and the .com have different registrants — even acting in concert — separate proceedings are required, and the coordination cost rises sharply.

If the same brand is at risk under a ccTLD as well — say, a .de or a .uk domain — the procedural map becomes more complex. For a .de domain, there is no UDRP equivalent; that dispute belongs in the German courts, and a DENIC DISPUTE entry can be filed to block transfer while the claim proceeds. For a .uk domain, the Nominet DRS applies an "abusive registration" test with a free mediation stage before any expert decision, and it reads "registered or used" abusively — a materially lower threshold than the UDRP's cumulative "registered and used in bad faith." A brand owner managing registrations across .store, .de, and .uk is therefore managing three distinct legal standards simultaneously.

Where the conduct spans multiple zones and the registrant is identifiable, a US court action under anticybersquatting legislation can address .store and other gTLDs in a single proceeding if the court has jurisdiction — it cannot directly order the transfer of a .de or .uk domain, but a judgment on the underlying claim may support parallel national proceedings. The practical implication: a court action is sometimes the coordinating spine of a multi-zone campaign, with the UDRP handling the gTLD domains quickly and court proceedings addressing the ccTLDs through local litigation counsel in the relevant jurisdiction.

For guidance on recovering a hijacked domain across multiple zones and the interaction between registrar-level escalation and formal dispute proceedings, see the analysis at recovering a hijacked domain: a case study.

What practical steps should a brand owner take before filing in court?

The pre-filing phase for a court action is more demanding than filing a UDRP complaint. Five steps are essential.

Step 1: establish and document trademark rights. Confirm the registration status, registration date, and scope of the mark in the relevant jurisdiction. Identify any unregistered-mark arguments that might supplement a registration. Courts apply stricter scrutiny to trademark standing than most UDRP panels.

Step 2: assemble the domain's history. WHOIS/RDDS records from registration through the present, DNS configuration changes, archived content at material dates, and any monetization or redirection data. The domain's history is the factual spine of the bad-faith claim.

Step 3: identify and serve the correct defendant. A privacy or proxy registration obscures the real registrant. If the registrar will not lift the privacy shield voluntarily, a pre-litigation discovery application — available in several jurisdictions — may be required before the court action itself is filed.

Step 4: assess the jurisdictional options. For .store domains, the applicable court jurisdiction depends on the registrant's location, the complainant's location, and the registry's terms of service. Many registries specify a dispute-resolution forum in their registration agreement. Those terms do not prevent a court action, but they shape the jurisdictional analysis.

Step 5: consider whether a parallel UDRP complaint should be filed. If transfer is achievable through the UDRP and the court action is pursued primarily for damages, filing both in parallel is often the right approach — the UDRP secures the domain quickly, and the court proceeding continues for the monetary claim. Coordination between the two tracks is essential; a position taken in the UDRP record will be available to the court.

For questions about domain assignment agreements and the structuring of transfers agreed outside of formal proceedings, see our FAQ at domain assignment agreements: frequently asked questions.

Related at COGNOMEN

• Court recovery and domain theft: COGNOMEN's litigation and registrar-escalation service for brand owners and registrants
• Recovering a hijacked domain: anonymized case study covering registrar escalation and cross-zone strategy
• Domain assignment agreements online: FAQ on transfer structuring and due diligence for agreed dispositions