How to prove a legitimate interest in your .shop domain

A UDRP complaint arrives. The complainant – a brand owner who spotted your .shop registration – claims the name is theirs and demands a transfer. You registered it in good faith, you use it for a real business, and you have never heard of their mark. Now you have 20 days to respond before the panel proceeds without you. The question is not whether you feel entitled to the domain. The question is whether you can prove it.

To prove a legitimate interest in your .shop domain under the UDRP, you must satisfy at least one of the three safe harbors in Paragraph 4(c) of the Policy: a bona fide offering of goods or services before notice of the dispute, a showing that you are commonly known by the domain name, or demonstrable legitimate noncommercial or fair use. The respondent's burden is a showing – not a full proof – but the evidence must be concrete and document-backed. A standard WIPO case runs approximately two months from filing to decision, and the filing fee for a single-member panel is USD 1,500, payable by the complainant.

This page covers each safe harbor, how to build the legitimate-interest record for a .shop domain, when a reverse domain name hijacking finding is realistic, and what a defense engagement at COGNOMEN involves.

Why .shop matters: what rules govern your domain?

The .shop gTLD is administered under the standard UDRP, which means the same three-element test that governs .com applies here. A complainant must prove all three elements of Paragraph 4(a): confusing similarity to a mark, absence of the registrant's rights or legitimate interests, and registration and use in bad faith. All three must be established. Failure on any one element ends the case in the respondent's favor.

Because .shop is a generic top-level domain, the word "shop" carries obvious descriptive weight. Many registrants of .shop domains are e-commerce operators, retailers, or entrepreneurs who chose the extension precisely because it describes what they do. That commercial relevance is not automatically a safe harbor, but it does sharpen the narrative a well-constructed defense can tell. The zone itself signals commerce – and panels recognize that descriptive or generic terms in new gTLDs attract a wider range of legitimate registrations than, say, a coined-brand .com would.

In our practice, we see .shop complaints fall into two categories. First, brand owners who hold a registered mark that either predates or postdates the domain registration and who assume the zone extension implies confusion. Second, opportunistic complainants who hold a mark in a different class or territory and use the UDRP as a de facto domain acquisition tool rather than a genuine protection action. The second category is where reverse domain name hijacking findings become available.

What does legitimate interest actually mean under Paragraph 4(c)?

Paragraph 4(c) of the UDRP provides three non-exhaustive safe harbors, each of which defeats element two of the complainant's case if the evidence supports it. They are distinct routes, not cumulative requirements. One is enough.

Bona fide offering before notice. The first and most frequently used safe harbor requires that the registrant was using, or making demonstrable preparations to use, the domain for a bona fide offering of goods or services before receiving notice of the dispute. "Notice" in the UDRP context is generally interpreted as the date the complaint was received – not the date a cease-and-desist letter arrived. What does bona fide mean? Panels look for use that is genuinely commercial, not pretextual. A parked page pointing at pay-per-click links anchored to the complainant's trademark will not qualify. A functioning e-commerce site, a restaurant booking page, a service-business landing page, or documented pre-launch preparations – business registration, web-development invoices, supplier contracts, marketing spend – each supports the first safe harbor.

Commonly known by the domain name. The second safe harbor applies where the registrant – whether an individual, company, or other entity – is genuinely known by the domain name, even without a registered trademark of their own. This route matters for smaller businesses operating under a trade name or DBA. Evidence includes business registrations, local advertising, client correspondence using the name, and social media handles predating the dispute.

Legitimate noncommercial or fair use. The third safe harbor covers commentary, criticism, fan sites, and similar non-commercial use. In a .shop context it appears less often than the first two, but it is not impossible. A consumer-advocacy site reviewing products, or a hobby retailer who is not deriving commercial gain, can engage this route if the use is genuinely noncommercial and not misleading as to source.

One structural point matters: the burden of production shifts. The complainant asserts the absence of legitimate interest. Once that assertion is made, the respondent carries the burden of coming forward with evidence. The standard is a prima facie showing – not a balance-of-probabilities proof. But a bare assertion in the response, unsupported by documentation, rarely succeeds before a serious panel.

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

How do you build the legitimate-interest record for a .shop domain?

The legitimate-interest record is a collection of contemporaneous evidence tying the registrant's use to one of the three Paragraph 4(c) routes – assembled before the response deadline, organized by date, and presented so that a panel of one or three members can follow it in a single reading. This is where defense engagements are won or lost.

Start with the registration date and work forward. The critical question is what the registrant was doing with the domain before notice of the dispute, not what they did after. Panels are appropriately skeptical of evidence that postdates the complaint – a suddenly active website, a retroactive business registration, or correspondence manufactured to fill a gap. The response should narrate a timeline supported by documents.

For a .shop domain operated as an e-commerce or retail site, the most persuasive evidence package typically includes: the domain registration confirmation (showing acquisition date and registrant identity); screenshots or archived versions of the live site across time (the Wayback Machine is a starting point, but hosting logs and CMS export files are stronger); business registration documents or a state-issued trade-name filing; invoices, purchase orders, or supplier contracts bearing the business name; payment-processor or bank records showing sales under the brand; and, where available, correspondence with customers or suppliers referencing the domain name.

For a domain in development rather than live use, substitute the above with the evidence of bona fide preparations: development contracts or freelancer invoices for the site build; supplier negotiations or inventory purchase records; social media channel registrations or brand identity materials produced before notice. The standard is demonstrable preparations, not perfection.

A point we stress in every respondent engagement: do not rely on the registrant's subjective explanation alone. Panels give little weight to "I always intended to build a shop." They give weight to a signed web-design contract dated three months before the complaint was filed.

In a recent matter – a .shop dispute, spring 2025 – we assembled a legitimate-interest record for a small retailer whose domain had been targeted by a complainant holding a mark registered after the domain had been in use for over a year. The retailer had a functioning online store, a state business registration, and archived PayPal sales records from before the complaint. The complaint was denied. The panel found bona fide use under the first Paragraph 4(c) safe harbor and noted the complainant's apparent awareness of the prior use when filing.

When is reverse domain name hijacking a realistic outcome?

Reverse domain name hijacking (RDNH) is a panel finding that the complaint was brought in bad faith – to deprive a legitimate registrant of a domain to which the complainant had no genuine entitlement under the Policy. The finding carries no monetary penalty, but it is public, attached to the panel decision, and consequential for complainants who use the UDRP as a commercial acquisition tool rather than a genuine protection mechanism.

Panels have consistently held that RDNH is warranted in specific, recurring fact patterns. A complainant who filed knowing that the respondent had a legitimate interest – because the domain predated the mark, because the complainant's own mark was in a different class or jurisdiction, or because the use was plainly non-infringing – is a candidate for an RDNH finding. So is a complainant whose legal counsel (or the complainant itself, if acting pro se) should have known that element two or element three of the UDRP test was not met.

The .shop zone creates particular RDNH exposure for over-reaching complainants. Because "shop" is a generic descriptive term, a mark that incorporates it is inherently weaker than a coined word. A complainant asserting that a .shop domain infringes a descriptive or weakly distinctive mark – especially where the registrant's use predates the mark or is in a different category of commerce – may be inviting an RDNH finding by filing at all.

RDNH findings are not automatic. The respondent must actively seek the finding in the response, explain why the complaint was abusive rather than merely unsuccessful, and support the argument with evidence. A default – where the registrant simply fails to respond – will never produce an RDNH finding. And a bare assertion of bad faith by the complainant, without substantiation, is unlikely to carry the day.

We regularly advise registrants on whether the specific facts of their situation – the complainant's mark, the filing date, the relationship between the complainant's business and the respondent's – create realistic RDNH exposure for the other side. It is a claim worth making when the evidence supports it. It is a claim that can undermine a defense when the evidence does not.

What evidence decides the outcome?

Panels deciding .shop UDRP cases under the legitimate-interest element weight several factors against each other. No single piece of evidence is determinative. The combination, the chronology, and the consistency of the record matter most.

On the respondent's side, the most persuasive elements – in rough order of weight – are: a registration date that predates the complainant's mark (this attacks element three simultaneously and collapses the entire complaint); a functioning website with genuine commercial activity documented across time; a business registration or trade-name filing in the registrant's jurisdiction; and the absence of any conduct targeting the complainant specifically – no offer to sell to the mark owner, no history of abusive registrations, no monetization through the complainant's trademark terms.

On the complainant's side, panels give weight to: evidence that the respondent's domain was registered shortly after the complainant's mark achieved public recognition; a pattern of similar registrations by the same respondent across other domains; pay-per-click monetization using the complainant's trademark terms; and an offer to sell the domain for a price exceeding out-of-pocket registration costs.

The gap between these two lists is where a defense is built. If the respondent's record is strong on chronology and genuine use, and the complainant's record is thin on mark recognition at the time of registration, the defense position is sound. If the respondent cannot produce pre-complaint use evidence, the analysis shifts – and the realistic question becomes whether to settle, negotiate a transfer at a fair price, or accept the risk of proceeding.

In a second matter – a .shop complaint, late 2024 – a complainant asserted that a domain registered two years before the complainant's trademark application was filed should be transferred because the complainant had "prior rights" based on unregistered use. We built a defense focused on the registration timeline and the absence of any evidence that the respondent had knowledge of the complainant's business at registration. The complaint was denied. The panel declined to reach RDNH, but the three-element test failed at both element two and element three.

How does a .shop dispute compare to a .com or ccTLD dispute?

The right forum and procedure depend on the zone in which the disputed domain lives. For .shop, the path is clear: the UDRP at WIPO, the Forum, or another ICANN-accredited provider. .shop is a new gTLD, and new gTLDs are subject to the full UDRP. There is no separate .shop dispute body and no special-purpose procedure.

How does that compare to other routes? If the contested name also appears in a .uk domain, the Nominet DRS governs that registration separately – and the DRS test is "abusive registration," which reads "registered or used" abusively rather than the UDRP's cumulative "registered and used in bad faith." That lower conjunctive threshold can work in a complainant's favor on .uk while the UDRP respondent wins on .shop. Two proceedings, two outcomes, same name. For a .de domain there is no UDRP at all – disputes go to the German courts with a DENIC dispute entry to block transfer while litigation runs. For any ccTLD not on the confirmed list in APPENDIX A, the governing national procedure applies and should be verified with counsel.

On cost: a .shop UDRP complaint carries a WIPO filing fee of USD 1,500 for a single-member panel on up to five domains. Legal representation for a respondent defense – separate from the forum fee – typically falls in a market range comparable to complainant-side matters. The filing fee is paid by the complainant, not the respondent. Where the complainant selects a single-member panel and the respondent prefers a three-member panel, the parties generally split the higher three-member fee of USD 4,000.

One further comparison: the URS (Uniform Rapid Suspension) is available for new gTLDs including .shop, but it is a complainant-side remedy only. It does not expand the respondent's options. It applies a higher "clear and convincing" standard and its remedy is suspension rather than transfer – relevant context if you are advising a brand owner on whether to file URS or UDRP, but not a defense route for the registrant.

To assess whether your .shop domain defense meets the legitimate-interest standard under Paragraph 4(c), email info@cognomenlaw.com.

What the defense engagement at COGNOMEN involves

A respondent engagement begins with a conflict check and a rapid review of the complaint, the domain's registration date, and the evidence the registrant can produce. That initial read tells us whether element two is genuinely contested, whether element three has weaknesses, and whether RDNH is a realistic claim. From there, the work is to build the legitimate-interest record, draft the response, and submit within the 20-day window.

We build the legitimate-interest record, document good-faith registration, and where the facts warrant it, seek an RDNH finding. The response is a legal submission, not an informal letter – it must meet the procedural requirements of the applicable UDRP rules, address each element the complainant raised, cite the safe harbors supported by evidence, and present the RDNH argument if it is available. A response that fails to address all three elements invites the panel to read the gaps against the respondent.

We advise clients clearly at the outset: outcomes depend on the specific facts, the quality of the record the registrant can produce, and the discretion of the panel assigned to the case. No outcome is guaranteed. What we can offer is a thorough assessment, a well-constructed record, and an honest view of the realistic range of outcomes given what the evidence shows.

For registrants who also face parallel proceedings – a .shop UDRP and a .uk Nominet DRS complaint filed simultaneously – we coordinate both defenses and ensure the record in each is consistent and strategically coherent. Where a complainant has also threatened or filed court action, we work with local litigation counsel in the relevant jurisdiction on the court side.

Related at COGNOMEN

• Respondent Defense & RDNH – full service overview for domain registrants facing UDRP complaints
• How to defend a UDRP complaint – detailed analysis of the three elements and common panel patterns
• Passive holding in finance domains – the bad-faith doctrines and how they apply to dormant registrations

Author: Anton Grant — Respondent defense and reverse domain name hijacking (RDNH). Meet the team.

Speak with Cognomen Law

For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter

Domain in disputeYour sideI want to recover a nameI received a complaint — I need a defensePortfolio / brand protectionWhat happenedEmailI agree to the processing of my enquiry as described in the privacy policy.Assess my case

No obligation. Confidential. We reply within two hours in business hours.

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.