Defend a .store domain registered before the complainant's trademark:…

Defend a .store domain registered before the complainant's trademark:. UDRP and ccTLD domain recovery and defense across .store. Email the firm to assess your…

A brand owner files a UDRP complaint against your .store domain. Their trademark registration, it turns out, postdates your registration by two or more years. You registered the name to build an e-commerce project. Now a panel will decide whether you had the right to hold it all along.

When a registrant holds a .store domain registered before the complainant's trademark existed, the UDRP's own mechanics work in the respondent's favor. Paragraph 4(a)(iii) requires the complainant to prove that the domain was registered and used in bad faith – a cumulative standard. A respondent who registered before the mark was filed can, as a matter of UDRP doctrine, challenge the logical foundation of the bad-faith element. Combined with a properly built Paragraph 4(c) legitimate-interest record, that prior-registration defense is one of the strongest positions in the Policy. A 20-day response window from commencement is the only procedural deadline that matters immediately.

This analysis covers the doctrinal basis for the defense, how panels read the pre-trademark chronology, how to build the legitimate-interest record under Paragraph 4(c), when a Reverse Domain Name Hijacking finding is realistic, and what evidence decides the outcome in a .store dispute before WIPO or the Forum.

What governs .store domains under the UDRP?

The .store new gTLD is fully subject to the UDRP, the same Policy that covers .com and other accredited gTLDs. Disputes are heard at WIPO, the Forum, CAC, or ADNDRC – the respondent's choice of forum does not change the governing rules, though the complainant files first and picks the provider. WIPO handles the substantial majority of .store cases, and its three-element test under Paragraph 4(a) is identical to the test applied to any other UDRP-accredited zone.

There is no separate .store registry procedure that offers an alternative path. Unlike .uk – where Nominet's DRS has its own "abusive registration" test and a free mediation stage – .store disputes go directly under the UDRP. That means the complainant must satisfy all three Paragraph 4(a) elements, and the respondent may rely on all of the Paragraph 4(c) safe harbors. No shortcuts exist on either side.

In our practice, registrants in new-gTLD zones sometimes assume that the novelty of the extension creates procedural uncertainty. It does not. The URS – a suspension remedy used in some new-gTLD disputes – is an alternative that complainants may choose, but it carries a higher evidentiary threshold and delivers only suspension, not transfer. A complainant seeking outright transfer of a .store domain will normally file under the UDRP, and the respondent's defense is prepared on that basis.

Does registration before the trademark eliminate the bad-faith element?

Prior registration is not an automatic win, but it is a structurally powerful defense because it attacks the logical coherence of the bad-faith element. Paragraph 4(a)(iii) requires the complainant to prove that the domain was registered and used in bad faith – both limbs must be satisfied. Panels have consistently held that a registrant cannot have registered a domain in bad faith with respect to a trademark that did not yet exist at registration. The intent to target a mark requires knowledge of, or a reasonable expectation of, that mark at the moment of registration.

The consensus view in UDRP jurisprudence is that where the domain was registered clearly before the trademark right arose, the bad-faith registration limb fails and the complaint cannot succeed on that element alone. This is not a minority position. It is the orthodox reading of the Policy that panels worldwide apply with regularity.

There is, however, a contrary view that panels apply in a narrow set of circumstances. Where the complainant can show that the respondent registered the domain in anticipation of a trademark that was publicly announced but not yet registered – a pre-launch product, a well-publicized brand rollout, or a company going public – some panels have found that the "registration in bad faith" requirement can be met even before the formal trademark date. This line of reasoning is applied cautiously and requires concrete evidence of the respondent's awareness of the mark-in-formation. Absent that showing, the prior-registration defense holds.

Practically, the chronology the respondent must document is: (1) the date the domain was registered; (2) the earliest date the complainant acquired trademark rights (whether through registration or, in some panels' reading, through substantial common-law use); and (3) any evidence that the complainant's brand had commercial visibility in the respondent's market before the domain was registered. A two-year gap – domain registered well before any trademark application was filed – gives the respondent a strong factual platform. A six-month gap invites scrutiny of whether unregistered rights existed at the time.

How do panels apply Paragraph 4(c) safe harbors to a .store registrant?

Paragraph 4(c) of the UDRP lists three circumstances that, if demonstrated, establish the respondent's rights or legitimate interests in the domain. For a .store registrant defending a pre-trademark registration, two of the three are directly relevant.

The first is Paragraph 4(c)(i): a bona fide offering of goods or services before notice of the dispute. For an e-commerce-oriented domain like a .store name, this safe harbor is particularly natural. A respondent who was actually building or operating a store – product listings, shopping cart infrastructure, supplier relationships, an email newsletter, or archived website versions – has exactly the type of pre-notice commercial use the Policy envisions. The key is that the offering must be genuinely commercial and not constructed after the complainant's complaint arrived. Panels are alert to websites that spring up suddenly between the registrar's lock notice and the response deadline.

The second relevant safe harbor is Paragraph 4(c)(iii): legitimate noncommercial or fair use of the domain, without intent to mislead consumers or tarnish the mark. This is harder to invoke in a .store context – the extension signals commercial intent – but it remains available where the use is genuinely non-deceptive. A product review site, a community forum, or a fan page under a .store address would need careful construction of the argument.

The third safe harbor – Paragraph 4(c)(ii), being commonly known by the domain name – is rarely dispositive for individual registrants who do not hold a corresponding trademark. It applies most naturally to a person or company whose name matches the domain. If the respondent's entity name or trading name predates the complainant's mark and matches the domain, that coincidence strengthens the whole defense.

We regularly advise respondents who have extensive pre-dispute use evidence but have not organized it for a UDRP response. The practical task is assembling screenshots with metadata, web archive captures, payment records, correspondence with suppliers or customers, and any business registration showing the name predates the complaint. Evidence of use is not self-organizing; it requires active curation in the 20-day response window.

For a read on whether the three UDRP elements are met in your situation, reach us at info@cognomenlaw.com.

What is Reverse Domain Name Hijacking and when is it realistic in a .store case?

Reverse Domain Name Hijacking – RDNH – is a panel finding that the complaint was brought in bad faith to deprive a legitimate registrant of their domain. It carries no monetary penalty, but it is a reputational finding against the complainant and their counsel, and it appears in the published record. For a respondent in a pre-trademark .store dispute, an RDNH finding is a realistic second objective alongside defeating the complaint.

Panels find RDNH where the complainant knew, or should have known, that the complaint could not succeed. The clearest trigger for that conclusion is a registration date that clearly predates the complainant's trademark, combined with publicly documented evidence of the respondent's pre-notice use. If a brand owner files a UDRP complaint against a .store domain that was registered two years before the brand owner even applied for its mark, and the respondent's use of the domain was apparent from the public archive, the complaint looks opportunistic. Panels have found RDNH in precisely that pattern.

RDNH is not automatic. Panels require the complainant to have been in a position to know the case would fail before filing. Factors that support an RDNH finding include: the prior-registration chronology was objectively verifiable from WHOIS/RDDS data before the complaint was drafted; the respondent had documented use of the domain predating the mark; the complainant is a sophisticated party with legal counsel; and the complaint made no attempt to address the obvious chronological problem. Factors that cut against RDNH include a genuinely close chronological call or a plausible – even if ultimately losing – argument that common-law trademark rights predated registration.

In a matter we handled (a .store domain for a specialty goods retailer, summer 2025), the respondent had registered the name roughly eighteen months before the complainant's trademark application. The complainant's complaint made no reference to unregistered rights and cited only the registration date. The panel denied the transfer and entered an RDNH finding. The result required careful documentation of registration history, web archive evidence of pre-complaint use, and a structured argument on the chronological impossibility of bad-faith registration.

For a deeper treatment of when an RDNH finding is worth pursuing, see our discussion at seeking an RDNH finding.

What evidence decides the outcome in a .store UDRP defense?

The evidentiary burden in a UDRP defense is on the respondent to produce evidence of legitimate interests; the complainant carries the broader burden on all three Paragraph 4(a) elements. In a pre-trademark .store case, the outcome typically turns on four evidentiary categories.

First, the registration chronology. The date the domain was registered, compared with the earliest date the complainant can claim trademark rights, is the foundational fact. The respondent must produce the registration confirmation, the WHOIS/RDDS historical record, and – critically – any evidence of what the complainant's brand looked like in the marketplace at the time of registration. If the complainant's mark was not in use or was confined to a different geographic or product market, that context matters.

Second, the pre-notice use record. Web archive screenshots showing active use before the complaint was sent, dated correspondence with customers or suppliers, e-commerce platform data, payment processor records, and any business registration in the registrant's name matching the domain string all contribute. The Wayback Machine is a standard reference point, but it is not always complete. Respondents who have operated under a domain for years often discover that their archive coverage has gaps; filling those gaps with internal records becomes essential.

Third, the absence of targeting conduct. Panels look for evidence that the registrant chose the name for independent reasons unrelated to the complainant's brand – a personal name, a descriptive or generic term, a dictionary word relevant to the product category. A .store domain that describes the type of goods being sold carries an inherently plausible independent-origin story. A domain that is an exact match for the complainant's brand name without any descriptive or generic quality is harder to defend, even with good chronology.

Fourth, the complainant's awareness before filing. If the complainant corresponds with the registrant before filing – offering to buy the domain, sending a cease-and-desist, or acknowledging the registrant's business – that correspondence can cut both ways. For the RDNH argument, it is useful if it shows the complainant knew of the legitimate use and filed anyway.

In a second matter we defended (a .store domain for a craft goods marketplace, early 2026), the respondent had three years of archived commercial use, supplier invoices predating the complaint by more than two years, and a company registration under the same trading name. The panel found legitimate interest under Paragraph 4(c)(i) and did not reach the bad-faith element. No RDNH finding was sought; the transfer denial was the objective and it was achieved on the evidence alone.

How does the .store defense compare across WIPO and the Forum?

The choice of forum is made by the complainant, not the respondent. Still, respondents benefit from understanding how WIPO and the Forum differ in practice, because the approach to the response may be calibrated to the provider's procedural norms.

WIPO handles the substantial majority of .store cases and publishes all decisions in its online database. Its panelists tend to produce detailed written decisions that address the RDNH question with care. The Forum – formerly the National Arbitration Forum – operates with slightly less published analytical depth in some decisions but processes cases efficiently. WIPO's filing fee starts at USD 1,500 for a single-member panel covering one to five domains; the Forum begins at approximately USD 1,300. If the complainant chose WIPO, the respondent's panel-selection request (for a three-member panel) would generally require splitting the higher three-member fee of USD 4,000.

When does a three-member panel make sense for a respondent? Where the pre-trademark chronology is strong but not airtight, and where an RDNH finding is a realistic objective, a three-member panel provides a more deliberate process and a published dissenting opinion if the panel is divided. The additional cost is material but can be justified where the domain has substantial commercial value or where the RDNH finding serves a broader strategic purpose – for instance, where the same complainant has a pattern of filing against registrants with prior rights.

CAC is an option if the complainant chose that forum. Its fees are the lowest entry point among the UDRP providers, and its published decisions are fully recognized under the Policy. ADNDRC serves primarily Asia-Pacific parties. For a .store domain held by a European or North American registrant, WIPO or the Forum is the almost certain venue.

For a comprehensive overview of respondent-side strategy, including how to build the legitimacy record and when to seek an RDNH finding, see our respondent defense and RDNH practice.

What are the realistic next steps if you receive a UDRP complaint on a .store domain?

The procedural clock starts on the date the provider formally commences the case – not the date you first receive an email about it. From commencement, the respondent has 20 days to file a response. Missing that deadline results in a default. A default is not an automatic loss, but it removes the respondent's voice from the proceeding and forces the panel to decide on the complainant's evidence alone. Panels in default proceedings do sometimes deny complaints where the complaint itself is obviously deficient – but that is not a position a respondent with a strong case should accept.

The immediate priorities on receipt of a complaint notice are: verify the commencement date, preserve all evidence of pre-registration use and business activity, pull the web archive for the domain, and retrieve the registration confirmation and any WHOIS/RDDS historical data. None of that is recoverable if the response deadline passes.

The decision matrix for how to proceed looks like this. If the domain was clearly registered before the complainant's trademark existed, and there is documented commercial use of the .store address predating the complaint, a full UDRP response on the merits is the standard path – aimed at defeating the transfer and, where the chronology is stark and the complainant's conduct is opportunistic, at an RDNH finding alongside. If the chronology is close – within months rather than years – and unregistered rights are arguable on the complainant's side, the response strategy becomes more nuanced, focusing on the use evidence and the absence of any targeting conduct. If the domain was registered before the trademark but has been held passively without any commercial use, the defense is harder; passive holding is not itself bad faith, but it deprives the respondent of the Paragraph 4(c)(i) safe harbor, and the whole weight of the defense shifts to the chronological argument alone.

Court action is not unavailable. A respondent who prevails in a UDRP proceeding retains the domain, and no further action is normally required. Where a complainant fails in a UDRP and then pursues litigation – which is rare but not unknown – the respondent's position is strengthened by the published panel decision. For a .store domain that is also subject to potential US anticybersquatting litigation, the strategic calculation changes; that path involves a court process handled with local litigation counsel and carries substantially different cost and risk parameters than the administrative UDRP procedure.

To weigh UDRP defense options for your .store domain, email info@cognomenlaw.com.

Related at COGNOMEN

• Respondent defense and RDNH – strategy, safe harbors, and how to pursue a hijacking finding
• When to seek an RDNH finding – the factors panels weigh and how to make the argument
• UDRP recovery in cross-border phishing cases – complainant-side procedure and evidence