Step-by-step: prove a registrant has no legitimate interest in a .dev domain

A developer-tools startup discovers its brand name registered as a .dev domain by someone with no connection to the technology sector. The registrant's site is blank. A five-figure buy-back demand arrives by email three days later. The brand owner wants to know one thing: how do you prove the registrant has no legitimate interest — and does the .dev zone change anything?

To prove a registrant has no legitimate interest in a .dev domain under the UDRP, a complainant must show that none of the Paragraph 4(c) safe harbors applies — no bona fide offering before notice of the dispute, no common knowledge under that name, and no legitimate noncommercial or fair use. The burden is light: raise a prima facie case and the burden shifts to the respondent to rebut it. .dev is a generic top-level domain operated by Google Registry and governed by the UDRP, so the standard WIPO or Forum procedure applies, with a 20-day response window and a decision typically within about two months.

This guide walks each step of building the no-legitimate-interest showing for a .dev complaint, flags the trap hidden in each stage, and explains where evidence makes or breaks the case.

Why does .dev follow the UDRP, and what does that mean for your complaint?

.dev is an ICANN-accredited new generic top-level domain, which means all three UDRP elements under Paragraph 4(a) govern a dispute over it, exactly as they govern a .com or .net dispute. The .dev registry's accreditation agreement requires registrars to flow down the UDRP to registrants; there is no separate national procedure to consider. You file a UDRP complaint at WIPO, the Forum, CAC, or ADNDRC — the zone does not restrict forum choice.

The practical difference with .dev is contextual rather than legal. Google Registry restricts .dev to HTTPS-only sites, which means a parking page on a .dev domain requires a valid TLS certificate. Many bad-faith registrants simply let the domain sit unresolved. That passive holding pattern is relevant to bad faith — panels have consistently held that passive holding of a domain incorporating a well-known mark can satisfy the "use" requirement under Paragraph 4(a)(iii) — but it is also directly relevant to the no-legitimate-interest element, because a domain with no active use and no evidence of preparation for bona fide use is a domain the registrant struggles to defend.

One further point on zone selection for forum choice: because .dev disputes are almost exclusively filed at WIPO or the Forum (which together handle roughly 97% of all UDRP proceedings), this guide focuses on those two forums. CAC and ADNDRC are viable, lower-cost alternatives, but WIPO's Jurisprudential Overview is the most widely cited interpretive resource for the no-legitimate-interest element, and panels at all four forums apply it consistently.

Step 1: Confirm your trademark rights before attacking the registrant's interest

The no-legitimate-interest element is the second of the three UDRP elements under Paragraph 4(a) — but you should assess it first in your evidence-gathering, because the strength of your trademark rights under the first element directly shapes what the registrant can plausibly claim under the second.

A complainant who holds a registered trademark in the relevant class and jurisdiction can argue that any commercial use by the registrant would almost certainly infringe. That makes a bona fide-offering defense far harder for the respondent to mount. Conversely, where your rights are unregistered or recent, the registrant has more room to argue that it independently adopted the name before your mark crystallized.

The trap in this step is chronology. Panels scrutinize the registration date of the .dev domain against the earliest date of your trademark rights. If the registrant registered the .dev domain before your mark was filed — or even before your brand was publicly associated with the name — the no-legitimate-interest analysis becomes entangled with the bad-faith element, and a panel may find the second and third elements together insufficient. Assemble a timeline: trademark filing date, date of first commercial use, and the WHOIS registration date of the .dev domain (now held in RDDS/RDAP records). Gaps and overlaps in that timeline predict the difficulty of your case.

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

Step 2: Build the prima facie case — what evidence actually shifts the burden?

Under the consensus view among UDRP panels, a complainant satisfies the no-legitimate-interest element by making a prima facie showing that the respondent lacks rights or legitimate interests. The burden then shifts to the respondent to produce evidence of one of the Paragraph 4(c) safe harbors. That is the operative legal mechanism — and it is lighter than many brand owners expect.

What evidence builds a prima facie case? Courts and panels have identified a repeatable checklist, drawn from the respondent's own conduct and public records:

• No WHOIS/RDDS name match. The registrant's name or organization does not correspond to the disputed .dev domain. This is the most basic indicator and easy to document from registry RDAP output.
• No trademark, business registration, or trade-name record. A search of trademark databases (national and international) and business registries shows no entry for the registrant under the disputed string. Attach the search results as an exhibit.
• No use of the domain before notice of the dispute. Screenshot evidence — captured with a metadata-preserving tool that records the retrieval timestamp — showing the domain resolves to a blank page, a parking page, or an unrelated redirect is powerful. For .dev domains, a TLS handshake failure or a browser "this site can't be reached" message is equally probative.
• No evidence of preparation for a bona fide offering. A registrant who was genuinely building toward a legitimate service would typically have hosting records, development assets, or some form of documented preparation. A WHOIS history showing the domain sat unresolved for months after registration tends to undercut any such claim.
• A buy-back demand directed at the mark owner. A direct offer to sell the domain back to the complainant — particularly where the demand references the complainant's brand — is among the clearest indications of no legitimate interest, and overlaps directly with the Paragraph 4(b)(i) bad-faith factor.

The trap here is assuming that a non-responding registrant is an automatic win. Panels may default a respondent — meaning no response is filed within the 20-day window — but a default does not relieve the complainant of establishing the prima facie case. Panels have denied complaints even in default where the complainant's own evidence failed to show confusing similarity or left the legitimate-interest element bare. Build the full case regardless of whether you expect a response.

Step 3: Anticipate and preempt the Paragraph 4(c) safe-harbor defenses

A well-prepared .dev complainant addresses each of the three Paragraph 4(c) safe harbors in the complaint itself — not as an afterthought, but as a structured rebuttal of defenses the respondent might raise. This approach matters because panels award more weight to a complaint that has already considered and disposed of plausible counterarguments.

The three safe harbors, and how to preempt them in a .dev case:

1. Bona fide offering of goods or services before notice of the dispute. Document that no such offering exists. For a .dev domain, confirm that the domain resolves to nothing, or to a page with no products, no services, and no mechanism for a customer to transact. If the domain previously resolved to something, use archived web captures to trace what was there and when — a .dev site that appeared only after your cease-and-desist letter is not a bona fide prior offering.
2. Commonly known by the domain name. Search for any public record that associates the registrant — as an individual or an entity — with the disputed string. Social media profiles, professional directories, press mentions, and domain portfolio databases are all relevant. Absence of any such association is part of your affirmative record.
3. Legitimate noncommercial or fair use. For .dev domains, this defense rarely succeeds in isolation because the .dev zone is commercially associated with software products and developer tools. A registrant arguing fan-site fair use for a .dev domain faces contextual skepticism. Document that the domain's registered purpose — to the extent you can determine it — does not fit any recognized fair-use pattern.

In our practice, we have seen respondents raise the "commonly known" safe harbor with evidence assembled quickly after a complaint is filed — a social media account created in the month between registration and commencement. Panels distinguish pre-dispute evidence from post-complaint construction, but the distinction requires factual scrutiny. If you can demonstrate that the respondent's purported "known name" evidence postdates your UDRP filing, say so explicitly in the complaint.

How does the no-legitimate-interest element interact with the bad-faith element in a .dev case?

The second and third UDRP elements are analytically distinct, but the same evidence often does double work. A buy-back demand sent to the complainant satisfies the Paragraph 4(b)(i) bad-faith factor — registration to sell to the mark owner above documented costs — and simultaneously undermines any claim of legitimate interest. Passive holding of a .dev domain incorporating a distinctive mark, with no active use, contributes to the bad-faith finding and also removes any basis for a bona fide-offering defense.

Where the interaction becomes a trap: complainants sometimes argue bad faith so persuasively that they neglect the separate framing of the no-legitimate-interest element. Panels expect each element to be addressed on its own terms. A complaint that buries the second element inside the bad-faith analysis risks an adverse inference that the complainant could not make the showing independently. Structure your complaint with a discrete section for each of the three elements — and make the no-legitimate-interest section self-standing.

In a recent matter involving a .dev domain (summer 2025), we advised a technology brand whose mark had been registered as a .dev the same week the brand's product launched publicly. The registrant's only activity was an MX record — an email-routing configuration with no associated website. We documented the absence of any commercial use, confirmed no trademark or business registration existed for the registrant's name, and established the buy-back communication as the registrant's only contact. The panel found all three elements met and ordered transfer. The bad-faith and no-legitimate-interest analyses reinforced each other precisely because they were written as separate, independently complete sections.

Step 4: Select the right forum and file — what changes the timeline and cost?

For a .dev dispute, forum choice is a real decision with cost and timeline consequences. The WIPO filing fee for a single-member panel covering one to five domains is USD 1,500; the Forum's entry-level fee is approximately USD 1,300 for one to two domains on a single-member panel. CAC begins around USD 500–800 and is the lowest-cost option. Legal fees for a straightforward single-domain UDRP complaint — separate from the filing fee — are typically in the USD 3,000–7,000 range in the market, depending on complexity and the forum selected.

Timeline: a standard case at WIPO or the Forum runs about two months from filing to a decision, assuming no procedural complications. WIPO offers an expedited option for single-panel cases of up to five domains, targeting a decision in about one month — useful if the registrant is actively using the domain in a way that causes ongoing harm.

The choice between WIPO and the Forum for a .dev case turns primarily on two factors. First, WIPO's Jurisprudential Overview is the most comprehensive published guidance on the no-legitimate-interest element, and WIPO panelists cite it regularly — so the interpretive environment at WIPO is highly consistent and predictable. Second, if a three-member panel is warranted — for example, because the case involves a high-value domain, a contested prior use defense, or a potential RDNH cross-claim — WIPO's three-member fee is USD 4,000, which the parties typically split if the complainant requested single-member and the respondent upgrades. Budget that possibility when planning the matter.

If the registrant also holds the corresponding .com or another gTLD variant, the UDRP allows a single complaint to cover multiple domains where the registrant is the same holder. That consolidation can reduce per-domain cost significantly and should be evaluated before filing.

To weigh UDRP against a court action for your .dev case, email info@cognomenlaw.com.

Step 5: Handle the response — what happens if the registrant actually defends?

A respondent who files a timely response — within the 20-day window following commencement — resets the dynamic of the case. The panel must now weigh the respondent's evidence of legitimate interest against your prima facie showing. The most common defensive move is to produce evidence of a claimed prior use, a descriptive justification ("dev" as a generic abbreviation for developer), or a portfolio argument that the domain was registered speculatively without knowledge of your mark.

How do you counter? On the prior-use defense, date stamps are decisive. You need web archive records, hosting logs, social media timestamps, or business registration dates — all pre-dating the registrant's claimed use. On the descriptive defense, panels have consistently held that a generic or descriptive component (such as "dev") does not save a registration where the dominant element is the complainant's distinctive mark. A domain incorporating your registered brand plus a generic term like "dev" is not made non-infringing by the presence of the generic component.

On the portfolio defense — the argument that the registrant holds many domains and simply did not know about your mark — the analysis turns on the distinctiveness of your mark at the time of registration. If the mark was well-known in the developer-tools sector, awareness is presumed by many panels. Document the mark's reputation through contemporaneous press coverage, download statistics, GitHub star counts, or other measurable proxies for market recognition.

We regularly advise complainants whose respondents have filed responses raising the legitimate-interest safe harbors with thin evidence. The pattern we encounter most frequently in .dev cases is a respondent who creates a developer-facing landing page — with placeholder content and a generic "coming soon" message — between the complaint filing date and the response deadline. Panels are alert to this tactic. If you monitor the domain's resolution status from the moment you file, any change in content after commencement is documentable and weakens the respondent's good-faith claim.

What remedies are available, and is the UDRP the only route for a .dev dispute?

The UDRP's only remedies are transfer of the domain to the complainant or cancellation. No monetary damages are available. No injunction issues from a UDRP panel. If the registrant has caused commercial harm — diverting revenue, damaging reputation, intercepting email — those losses require a court action for anticybersquatting relief, which is a separate proceeding entirely, handled with local litigation counsel in the relevant jurisdiction.

For a .dev domain, the decision matrix is straightforward. If you want the domain transferred and you have clear trademark rights, the UDRP at WIPO or the Forum is the right route — faster, cheaper, and with a well-developed interpretive record on the no-legitimate-interest element. If you want damages, or if the registrant's identity is genuinely unknown and you need court-ordered discovery, US anticybersquatting litigation is the path that reaches money and compelled disclosure, though at substantially higher cost and a longer timeline.

The URS (Uniform Rapid Suspension) is theoretically available for new gTLDs including .dev, but its remedy is suspension — not transfer — and it requires a "clear and convincing" evidentiary standard, which is higher than the UDRP's preponderance-based approach. For a complainant who wants ownership rather than a suspended domain, the UDRP is almost always the correct choice for a .dev dispute. URS is most useful when speed matters more than ownership — for example, to stop active phishing from a fraudulent .dev address while a parallel UDRP proceeds.

In a matter we handled in early 2025 involving a software company's .dev domain, the registrant had configured the domain with MX records pointed at a mail server with no public-facing site. The client needed both the domain and a record of any mail traffic that had transited through it. We filed the UDRP for transfer and coordinated separately with the client's litigation counsel for a court process to obtain the mail logs. The UDRP resolved in the client's favor within the standard two-month window; the parallel court process took considerably longer but produced the evidence needed for the damages claim. The two remedies served different purposes and ran concurrently.

Related at COGNOMEN

• UDRP Domain Recovery Service – end-to-end complainant representation across all gTLD zones
• Recovering a domain through UDRP: in-depth analysis of the three-element test and panel trends
• URS vs. UDRP for a .io domain – case study on choosing between suspension and transfer

Author: Cordelia Roe — UDRP complainant practice & gTLD recovery; domain transactions and brand protection. 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.