How to seek a reverse domain name hijacking finding for a .store doma…

How to seek a reverse domain name hijacking finding for a .store doma. UDRP and ccTLD domain recovery and defense across .store. Email the firm to assess your…

You registered a .store domain legitimately – perhaps years before a complainant's trademark application was even filed – and now a UDRP complaint sits in your inbox demanding transfer. The complaint may be thin, opportunistic, or filed by a party that knew perfectly well you had a legitimate claim to the name. The question is not only how to defeat that complaint. It is whether the panel should go one step further and declare that the complainant engaged in reverse domain name hijacking.

Reverse domain name hijacking – commonly abbreviated RDNH – is a finding that a complainant brought a UDRP complaint in bad faith, primarily to strip a legitimate registrant of a domain. Under the UDRP, all three elements of Paragraph 4(a) must fail or the panel must conclude the complaint was filed with knowledge it could not succeed. The .store zone operates under the standard UDRP, administered at WIPO and other accredited providers, so the same rules that govern .com apply here. A standard case is decided within roughly two months; the WIPO filing fee for a single-member panel starts at USD 1,500 – paid by the complainant, not you.

This page explains how the RDNH standard works in practice for .store registrants, what evidence builds the strongest record, when a finding is realistic, and what the next step looks like.

What Is Reverse Domain Name Hijacking and When Does It Apply to .store?

RDNH is the UDRP's procedural sanction against complainants who abuse the Policy. A panel issues an RDNH finding when it concludes that the complaint was brought primarily to deprive a legitimate registrant of a domain they had a genuine right to hold. The remedy is reputational, not monetary – there are no damages, no cost awards, and no injunction available under the UDRP – but an RDNH finding is a public record and attaches to the complainant's name permanently in the WIPO or Forum decision database.

The .store generic top-level domain is subject to full UDRP jurisdiction. Its registry delegates domain registrations through ICANN-accredited registrars, and every such registrar is bound by the Policy. When a complaint is filed against a .store domain, it proceeds exactly as a .com complaint would – through WIPO, the Forum, the Czech Arbitration Court, or another accredited provider – under Paragraph 4(a)'s three-element test. That means the RDNH mechanism is equally available. There is nothing about the .store zone that narrows or expands the complainant's obligations or the panel's remedial powers.

In our respondent practice, we regularly advise .store registrants who face complaints that were never viable to begin with. A complainant may own a trademark that postdates the domain registration by months or years. Or the trademark may be registered in one country for one class of goods, while the .store domain was registered and used by a merchant in a completely unrelated sector. Or the complaint may recycle boilerplate bad-faith allegations without engaging the actual registration history. Each of those patterns can support an RDNH finding, but the bar is not trivial.

When Is an RDNH Finding Realistically Available?

An RDNH finding is available when the panel concludes the complainant either knew the complaint could not succeed or recklessly chose to file anyway. That conclusion does not follow automatically from losing on the merits. Most denied complaints do not produce an RDNH finding. The panel must affirmatively find that the filing crossed from an unsuccessful claim into an abusive one.

The circumstances that most reliably support an RDNH finding in practice are these. First, the complainant's trademark postdates the domain registration by a material period – a complainant who seeks to take a domain that predates any rights they hold has no legitimate basis to press a bad-faith-registration argument, and panels have found this pattern sufficient to support RDNH. Second, the complainant had actual or constructive knowledge of the registrant's legitimate interest before filing – for instance, where the registrant operated a live e-commerce site on the .store domain and the complaint omits that fact. Third, the complainant filed with the apparent purpose of obtaining a domain at arbitration cost rather than at market price – using the UDRP as a substitute for a purchase negotiation. Fourth, the complainant's legal team should have identified the weakness at the pre-filing stage; filing despite an obvious deficiency amplifies the bad-faith inference.

What does not reliably produce an RDNH finding: a complaint that fails on element three alone, where the first two elements were colorable; a complaint filed on a genuinely borderline set of facts that the panel ultimately resolves for the respondent; or a complaint where the complainant made an arguable, if ultimately unpersuasive, case. The RDNH threshold requires more than a lost case.

How Do the Paragraph 4(c) Safe Harbors Build Your Defense?

Paragraph 4(c) of the UDRP sets out three circumstances that demonstrate a registrant's legitimate interest, any one of which is sufficient to defeat the second element of Paragraph 4(a). They are: (1) use of the domain in connection with a bona fide offering of goods or services before notice of the dispute; (2) the registrant being commonly known by the domain name; and (3) legitimate noncommercial or fair use of the domain, without intent to mislead or divert consumers.

For a .store domain, the first safe harbor is typically the most powerful. A .store extension signals a commercial intent – that is the nature of the zone. If you operated, or demonstrably prepared to operate, a store using the domain name before you received notice of the complaint, that use is strong evidence of a bona fide offering. "Before notice of the dispute" means before the complaint was filed or, in some readings, before the complainant's formal communication asserting rights. Documentation of pre-complaint use – screenshots, server logs, purchase records, social media posts, product listings – is the foundation of the safe-harbor record.

The second safe harbor applies less often to .store domains held by individuals or investment entities, unless your trading name or personal name actually corresponds to the domain. The third safe harbor – legitimate noncommercial or fair use – can apply to commentary, criticism, or fan sites, but a .store domain used commercially will not ordinarily qualify.

Building the legitimate-interest record is not passive. We recommend assembling it in the weeks between receiving the complaint and filing the response. The record should include: a chronological ownership history showing the registration date; evidence of any prior use, whether commercial or preparatory; any correspondence predating the complaint where the complainant or its agents attempted a purchase negotiation (which can also support the RDNH argument); and an analysis of the complainant's trademark registration date relative to the domain registration date. That analysis goes to both the second and third UDRP elements simultaneously.

For a read on whether the three UDRP elements are met in your .store dispute, and whether the facts support an RDNH argument, reach us at info@cognomenlaw.com.

What Evidence Decides the Outcome of an RDNH Argument?

The single most persuasive item in any RDNH argument is a chronology that shows the complainant's trademark rights did not exist – or were not asserted publicly – when the domain was registered. If the .store domain was registered in, say, early 2022 and the complainant's trademark application was filed in late 2023, the bad-faith-registration element collapses on its own timeline. No filing sophistication can rescue that complaint if the chronology is clear and documented.

Beyond the chronology, the following categories of evidence are material. Pre-complaint communications matter enormously. If the complainant sent a cease-and-desist letter, a purchase inquiry, or a broker email before filing, and the registrant declined, that correspondence both defeats bad faith on the registrant's side and demonstrates the complainant's awareness of the obstacle. Internal evidence of intended use is also critical: business plans, supplier agreements, prototype product images, domain development invoices, or any third-party record linking the registrant to the name in a commercial context. A brief written declaration from the registrant explaining the reason for registration – submitted as part of the formal response – is an ordinary and expected component of the record.

One caution: panels occasionally deny RDNH where the complaint was filed pro se or by a brand owner who can plausibly claim it was acting in good faith without professional advice. The RDNH inference is stronger against represented complainants who had counsel review the filing before submission. In our practice, we have defended .store registrants against complaints filed by brand-owner legal teams that, on examination, could not have missed the registration-date problem – and in those matters, the RDNH argument was pressed from the first line of the response.

A practical note on forum selection: where the complainant has already chosen WIPO, the respondent has no ability to redirect the case to another forum. The response must be filed at WIPO. If the complainant filed at the Forum or CAC, the same principle applies. The RDNH mechanism, however, operates identically at all accredited providers – the standard comes from the Policy, not from any individual forum's supplemental rules.

How Does the .store Zone Compare to Other Zones for RDNH Purposes?

The .store zone offers no procedural differences from .com or other standard gTLDs when it comes to RDNH. Both operate under the UDRP. Both use the same Paragraph 4(b) bad-faith factors and Paragraph 4(c) safe harbors. Both allow a panel to issue an RDNH finding on its own initiative, even without a formal request by the respondent – though making the request explicitly in the response is strongly advisable, because it signals the argument and gives the panel a stated basis to address it.

Where the analysis diverges is in the context a .store domain signals. A complainant who targets a .store domain is implicitly asserting that the registrant chose that zone to trade on the complainant's mark in a retail or e-commerce context. If the respondent can show that the .store registration was chosen for an entirely independent commercial purpose – a genuinely separate retail operation with no nexus to the complainant's goods – that undermines the confusion argument and simultaneously supports the bona-fide-use safe harbor. The zone-specific nature of .store can work for the respondent in exactly this way.

Contrast this with a ccTLD dispute. If the same registrant held both a .store domain and, for example, a .uk version of the same name, a complaint against the .uk domain would proceed under Nominet's DRS, not the UDRP. The Nominet DRS uses an "abusive registration" test and reads the standard as "registered or used" abusively – a different bar from the UDRP's cumulative "registered and used in bad faith." The Nominet DRS also recognizes a form of RDNH under its own rules. But the two proceedings are entirely separate; a UDRP RDNH finding on the .store domain has no direct procedural effect on a Nominet proceeding concerning the .uk version, and vice versa. Each zone has its own governing procedure, its own record, and its own outcome. If you hold both, the defensive strategy must be coordinated across the two.

For any ccTLD outside the standard UDRP zone, the governing national or registry procedure applies. We identify that procedure, confirm eligibility, and prepare the filing for that registry – separately from the gTLD work.

What Does a .store RDNH Response Actually Look Like?

A formal UDRP response in a .store matter is a structured legal submission, typically running between ten and twenty pages, that addresses each of Paragraph 4(a)'s three elements in turn and then argues, in a separate section, that the complaint was brought in bad faith. The structure matters because panelists read many responses; one that is organized around the Policy's own framework is easier to evaluate and, in our experience, more persuasive.

The RDNH section is not simply appended at the end as an afterthought. It is built from the record assembled throughout the response. By the time a panel reaches the RDNH argument, it should already have concluded that the complainant's first or second element was deficient on facts the complainant had access to before filing. The RDNH section then identifies those facts, shows that they were knowable at the time of filing, and draws the inference that filing anyway was an abuse of the Policy.

In a matter we handled for a .store registrant in early 2025 – a dispute in which the complainant's trademark postdated the domain registration by roughly three years – we built the chronology in the first section of the response, established the bona-fide-use record in the second, and pressed the RDNH argument squarely in the third. The panel denied the complaint and made an explicit RDNH finding, noting that the trademark postdate was apparent from a basic WHOIS and trademark database search. The complainant's advisors had no reasonable basis to claim they were unaware of it.

The respondent has 20 days to file a response once the case commences. Extensions are possible under the Rules but not automatic. Missing the deadline means defaulting, which in practice removes the RDNH argument from the table entirely – a panel will rarely make an RDNH finding without a reasoned response from the registrant. That 20-day clock is not generous. Acting immediately upon receipt of a complaint is essential.

What Is the Realistic Next Step If You Have Received a .store UDRP Complaint?

The realistic next step is a rapid pre-response assessment covering four questions. First, does the complainant have trademark rights that predate the domain registration? If yes, the first element may be met; if no, the entire case is vulnerable and the RDNH argument is strong from the outset. Second, can you document a legitimate interest under Paragraph 4(c) – a bona-fide offering, being commonly known by the name, or legitimate fair use? If yes, the second element fails for the complainant. Third, is there evidence of bad faith in the registration or use of the domain by you, the registrant? If no credible bad-faith argument exists, the third element fails. And fourth, taken together, was this complaint filed with knowledge it could not succeed?

If the answers to questions one, two, and three all run in your favor, the fourth question becomes the RDNH question: was the filing an abuse? A "yes" answer to all four supports a full defense and an RDNH request.

We assess the three UDRP elements, assemble the legitimate-interest record, document good-faith registration, and where warranted, seek an RDNH finding – all within the 20-day response window. The assessment comes first; the filing strategy follows from the facts.

If you have received a UDRP complaint against a .store domain and want to assess the RDNH argument, contact info@cognomenlaw.com without delay.

What Are the Costs and What Can You Realistically Expect?

Under the UDRP, the complainant pays the forum filing fee. For a single .store domain at WIPO with a single-member panel, that fee is USD 1,500. You, as respondent, pay nothing to the forum. Your cost is legal representation. Respondent defense in a UDRP matter – including a focused RDNH argument – typically runs in a market range of USD 3,000–7,000 for a straightforward single-domain case; cases with a large document record, a three-member panel, or supplemental submissions will fall at the higher end of that range or above.

Three-member panels are available on request. Either party may request one, but the cost differential is substantial: a three-member WIPO panel costs USD 4,000 for a single-member fee of USD 1,500. If the complainant requested a single-member panel and you as respondent request three members, the parties generally split the higher fee. There are situations where a three-member panel is worth requesting – particularly where the case raises a genuinely novel question of law or where the complainant is a large brand with a track record of obtaining favorable single-member decisions. Your counsel should advise that choice on the facts.

What you realistically gain from an RDNH finding: a published decision in your favor, a permanent record in the WIPO or Forum database, and a public reputational consequence for the complainant. What you do not gain: money, legal-fee reimbursement, or any injunctive relief against future complaints. The UDRP simply does not provide those remedies. If the complainant is a recidivist who brings abusive complaints against multiple registrants, that pattern may be relevant to a court action – but that is a separate proceeding, typically handled with local litigation counsel in the relevant jurisdiction.

In a second matter in our practice – a .store domain held by an e-commerce startup, summer 2025 – a complainant with a geographically restricted national trademark attempted to claim global rights over a domain that the startup had used continuously for over two years before the complaint. The RDNH argument was grounded in the complainant's overstated geographic claim and the startup's documented two-year use record. The panel denied the complaint, made the RDNH finding, and the startup retained the domain without paying any forum fee.

One myth to address directly: many registrants believe that if they ignore the complaint, the panel will simply reject it for lack of evidence. That is incorrect and the belief is costly. A default – meaning a failure to respond – does not compel transfer, but it dramatically reduces the probability of a denial, removes the RDNH argument entirely, and allows the panel to draw adverse inferences from the absence of a response. Defaulting when you have a strong case is the single most common avoidable mistake in respondent practice.

Related at COGNOMEN

• UDRP respondent defense and RDNH – full service overview for domain registrants
• How to defend an investment domain in .cn – cross-zone analysis for domain investors
• Checking ccTLD eligibility in .br – case study on national-zone registration requirements