Defend a generic-word .dev domain: what panels actually decide

Defend a generic-word .dev domain: what panels actually decide. UDRP and ccTLD domain recovery and defense across .dev. Email the firm to assess your case.

A developer tools company files a UDRP complaint claiming your registered .dev name – a common English word like "deploy," "stack," or "forge" – infringes its brand. You registered the name before the complainant obtained any trademark. Or you registered it at the same time as a mark existed, but in a completely different sector. The question is whether a UDRP panel will order the domain transferred and, if not, whether the panel will go further and call the complaint an abuse of the process.

When you defend a generic-word .dev domain, the applicable procedure is the UDRP administered at WIPO or another accredited provider, because .dev is a new gTLD governed by the standard Policy. The outcome turns on Paragraph 4(c) safe harbors – principally whether you had a legitimate interest in the generic term before the complainant's notice of the dispute – and on whether the complainant can actually prove that the domain was registered AND used in bad faith, both limbs of which must be satisfied simultaneously. A single-member WIPO case costs the complainant USD 1,500 to file; the respondent pays no separate filing fee but carries its own legal costs.

This analysis covers the governing rules, the evidence that decides outcomes, the realistic scenarios in which an RDNH finding can be obtained, and the practical steps a respondent should take from the moment a complaint arrives.

What governs .dev disputes and why the UDRP applies in full

.dev is a new generic top-level domain operated by Google Registry under an ICANN delegation, and like all new gTLDs it is subject to the standard UDRP rather than any national ccTLD procedure. That means the full text of the Policy, the UDRP Rules, and the WIPO Supplemental Rules apply without modification. There is no separate .dev dispute mechanism, no national eligibility requirement, and no alternative "abusive registration" test of the kind used under the Nominet DRS for .uk.

The three elements of Paragraph 4(a) are therefore the only test a panel applies. The complainant must prove: (1) the domain is identical or confusingly similar to a trademark in which the complainant has rights; (2) the registrant has no rights or legitimate interests in the domain; and (3) the domain was registered and is being used in bad faith. Each element is essential. A complainant who proves two of three will still lose. That cumulative structure is the respondent's structural advantage in a generic-word case, because both the second and the third elements are ordinarily contestable when the domain is a common term.

One procedural point matters immediately: if the complainant requests a single-member panel, the respondent may request a three-member panel within the response period. The parties then split the incremental cost of the three-member fee. In a genuinely close case on a generic term, three members often produce more deliberative reasoning and occasionally produce a split decision that is itself informative. We regularly advise respondents on that election in the first week after a complaint commences.

How do panels analyze generic-word domains under Paragraph 4(a)(i)?

The first element is almost always conceded in a generic-word .dev case: if the complainant holds a registered trademark for, say, "Deploy," and the disputed domain is deploy.dev, the domain is identical or confusingly similar to the mark. Panels do not use the first element to filter out generic-term cases. The comparison is a largely mechanical side-by-side of the dominant textual element and the mark. The .dev suffix is treated as a generic top-level domain designator and is typically disregarded in the comparison, just as .com is.

What a respondent should not do is waste response space arguing that Element 1 is not met when it plainly is. That concession frees the response to concentrate on Elements 2 and 3, where the respondent has far stronger ground. Panels reading a response that misallocates space to a losing element on Element 1 sometimes infer that the stronger arguments on Elements 2 and 3 are thin. The response should acknowledge Element 1 briefly and pivot fast.

Building the legitimate-interest record under Paragraph 4(c)

Paragraph 4(c) lists three safe harbors that, if demonstrated, establish a right or legitimate interest. In a generic-word .dev case the most significant are: (c)(i) bona fide use of, or demonstrable preparations to use, the domain in connection with a bona fide offering of goods or services before notice of the dispute; and (c)(iii) legitimate noncommercial or fair use of the domain without intent to mislead consumers or tarnish the mark.

What does "demonstrable preparations" actually require? Panels have consistently held that a respondent must produce contemporaneous evidence – not a retroactive narrative. Registration receipts are not enough. Useful evidence includes: design mockups or wireframes with creation-date metadata; early commits to a code repository under a project name matching the domain; email threads discussing the domain's intended use; invoices or receipts for development tools, hosting, or related services paid at the time of or shortly after registration; and any public announcement, even informal, of the project. A developer registering forge.dev for a metalworking API side project in 2022 should be able to produce GitHub history, a Figma file, or a Notion workspace dated to that period.

The consensus view in the panel community is that genuinely generic or descriptive terms carry an inherent likelihood of legitimate registration. The shorter and more common the word, the more plausible it is that an independent party registered it for a reason unconnected to the complainant's brand. Panels have repeatedly said that the mere registration of a generic word as a domain does not itself constitute bad faith. A contrary minority view does exist: some panels have held that where a complainant's mark is well-known and the respondent offers no actual use at all – not even a placeholder site – the silence can tip the scales. That view is not dominant, but it is the reason passive holding analysis matters.

If you have just received a UDRP complaint on your .dev domain, the response window is 20 days from commencement. For an early read on whether your registration facts support a legitimate-interest defense, contact info@cognomenlaw.com.

What evidence actually decides the bad-faith question in .dev cases?

Bad faith under Paragraph 4(b) is a conjunctive test: the domain must have been registered in bad faith AND used in bad faith. A panel that finds one limb but not the other must deny the complaint. That structure is especially favorable to respondents in the generic-word .dev space, where most registrants have a plausible development or technology rationale for the name.

Registration-stage bad faith turns on what the respondent knew at the moment of registration. The key questions are: Was the complainant's mark in existence? Was it well-known in the developer community specifically? Did the respondent have any prior contact with the complainant, receive a cease-and-desist, or make an explicit offer to sell to the mark owner? A generic word registered before any trademark issued – or registered without knowledge of an obscure junior mark – rarely meets the registration bad-faith standard. Panels look at the timing with precision, and the respondent's affidavit attesting to the state of their knowledge at registration carries genuine weight.

Use-stage bad faith is where passive holding becomes a contested issue. The UDRP doctrine on passive holding holds that, in limited circumstances, a respondent's failure to make active use of a domain can still constitute use in bad faith, particularly where the mark is famous, the respondent has no plausible good-faith use, and the respondent cannot identify any genuine plan. For generic terms in the .dev zone, passive holding arguments are harder for complainants to sustain than in pure brand-squatting cases, because the very genericity of the word undermines the inference that the only conceivable purpose was to target the mark owner.

In a recent matter – a .dev domain comprising a single common technology verb, summer 2025 – we built the legitimate-interest record around a six-month-old code repository and internal project documentation. The complainant's mark post-dated the registration by approximately ten months. The panel found no bad faith at either stage and denied the complaint in full, declining to make an RDNH finding only because the complainant's mark, while junior, was not nonexistent.

When is an RDNH finding realistic, and how do you pursue one?

Reverse Domain Name Hijacking is a finding that the complainant brought the complaint in bad faith or without a plausible legal basis – in effect, to weaponize the UDRP against a legitimate registrant. An RDNH finding carries no monetary penalty: it is reputational and on-record at WIPO, but it matters to brand-protection professionals who track panel outcomes. For a persistent or serial filer, accumulated RDNH findings create real institutional exposure.

What makes an RDNH finding realistic in a generic-word .dev case? Several factors tend to appear in the decisions where panels have made the finding. First, the complainant's mark clearly post-dated the domain registration by a meaningful margin, so any good-faith counsel review should have revealed the absence of registration bad faith. Second, the complainant's trademark is narrow in scope – a descriptive or weakly distinctive mark that should not have been asserted against a term that predates or equals it. Third, the response produces strong affirmative evidence of legitimate interest that the complainant either ignored or should have found through basic pre-filing due diligence. Fourth, the complainant relies on overbroad trademark claims unsupported by evidence of fame or secondary meaning in the relevant market.

RDNH is not awarded merely because the complainant loses. Panels require something more: a showing that the complaint was brought knowingly without a tenable legal basis or with the purpose of dispossessing a legitimate registrant. We have defended .dev and other new-gTLD domains where RDNH was the right argument; in each case, the request was framed not as a fallback but as a standalone claim supported by its own section of the response.

The contrary view also deserves attention. Some panels decline RDNH even in cases where the complaint was very weak, reasoning that a complainant has a right to test an uncertain area of law and that the absence of a monetary sanction means the bar for an RDNH finding should remain meaningful. Respondents should understand that RDNH is earned, not assumed from a win.

If the complaint against your .dev domain appears to lack any credible legal basis, we can assess whether an RDNH argument is warranted. Email info@cognomenlaw.com with the complaint and your registration history.

The decision matrix: which route fits your situation?

The right approach depends on the specific facts of the registration and the complainant's trademark. Consider four common .dev dispute scenarios.

If your domain is a common dictionary or technology term, your registration predates any trademark from the complainant, and you have contemporaneous evidence of intended use, the UDRP response is almost certainly the right tool. You file the response within the 20-day window, lead with Paragraph 4(c)(i), and argue that registration bad faith cannot coexist with a domain registered before the mark existed. The complaint is likely to fail, and RDNH is at least arguable. Cost basis: your legal fee, no forum filing fee as respondent.

If the trademark predates your registration but is in a wholly different field – say, the complainant is a food company and you are building a developer tool under a shared common word – the analysis shifts to the question of whether you could plausibly have been targeting the mark owner. If your use is in a clearly distinct industry, panels will generally reject the targeting inference. The Paragraph 4(c)(i) defense remains available if your use is genuine. The risk is higher if the complainant can argue the word is strongly associated with their brand globally, but for generic terms that association argument is usually weak.

If the domain is genuinely parked with pay-per-click advertising and the ads target the complainant's industry, you are in a substantially harder position. That pattern is one of the clearest signals of use-stage bad faith. In that scenario, the realistic path is either to negotiate a transfer on commercial terms before the decision issues, or to take the domain live with genuine content immediately – though the latter carries its own credibility risk if done after a complaint is filed. We regularly advise on whether to defend or to negotiate, and the answer is always fact-specific.

If the dispute involves both a .com and a .dev registration by the same complainant or respondent, the outcomes are procedurally linked if a single complaint covers both – permissible where the registrant is the same holder. Evidence and arguments cross-apply, which is efficient, but an adverse finding on one domain may color panel reasoning on the other. In a cross-zone scenario we structure the response to treat each domain's specific evidence separately, even within a single filing.

What the minority and the consensus positions actually mean for your strategy

The consensus position in UDRP panels, reflected across WIPO and the Forum, is that generic and descriptive terms present a significant evidentiary burden for complainants, because the Policy was not designed to allow trademark holders to commandeer common vocabulary. Panels have consistently held that a complainant seeking to transfer a generic-word domain must demonstrate something beyond mere similarity: they must show targeting of the specific mark, not just shared use of a common term.

The minority position – reflected in a smaller number of decisions – is that a respondent's complete silence on use, combined with a famous mark and a domain that has no plausible use outside the trademark context, can justify transfer even for relatively short common words. This position is more likely to appear where the complainant's mark is globally recognized and the word, while technically generic, is so firmly associated with the brand that independent registration strains credulity.

What does this mean for strategy? Do not assume a generic-word defense is automatic. Build the affirmative case. Produce your evidence. Explain in the response why you registered the domain when you did, what you intended to do with it, and what steps – however preliminary – you took toward that use. A respondent who says "this word is generic and the complainant should lose" without more is not in the same position as a respondent who says "this word is generic, here is my GitHub repository, here is the commit history, and here is the internal email where I named the project." The difference between those two responses can be the difference between a transfer order and a denial.

In a second recent matter – a .dev domain comprising a two-word technology phrase, spring 2025 – the respondent had made no active use and offered only a bare assertion of generic legitimacy. The panel transferred the domain. The complainant's mark, while not ancient, had modest industry recognition. The respondent's failure to produce a single piece of contemporaneous evidence on intended use was fatal. That outcome illustrates exactly why the defensive record must be built from the registration date forward, not reconstructed in response to a complaint.

How to structure a .dev defense response from day one

A response to a UDRP complaint on a generic-word .dev domain should follow a disciplined architecture. The following sequence reflects how we approach the filing in our practice.

First: acknowledge the undisputed element. If Element 1 is met – the domain and the mark share the same term – concede it in a single paragraph and move on. This signals to the panel that the response is precise rather than obstructive.

Second: lead the legitimate-interest section with your strongest contemporaneous evidence. The affidavit or declaration should be specific: dates, file names, platform names, project descriptions. Exhibits attached to the response carry far more weight than assertions in the narrative. If you have a GitHub repository, attach a printout of the commit log with the earliest commit date visible. If you have wireframes, attach them with the file creation metadata.

Third: address bad faith directly. Explain when you registered the domain and what you knew about the complainant's mark at that time. If the mark post-dates your registration, say so plainly and attach the trademark registration details as an exhibit. If the mark predates your registration but covers a different sector, explain why you had no reason to associate your project with the complainant's brand.

Fourth: if you are seeking an RDNH finding, devote a separate section to it. Do not fold the RDNH argument into the bad-faith defense. An RDNH finding requires the panel to affirmatively conclude that the complainant acted in bad faith in bringing the complaint. That argument should stand on its own feet: identify the specific facts that rendered the complaint meritless from the outset – the timing of the mark, the weakness of the trademark, the absence of any evidence that you targeted the complainant.

Fifth: consider the panel-election question. A three-member panel costs more – the parties split the incremental fee – but in a close generic-word case the deliberative benefit of three panelists often outweighs the cost. We assess that election on the specific facts of each matter.

Related at COGNOMEN

• Respondent defense and RDNH services: protecting your domain against abusive complaints
• Domain registered before the trademark existed: how panels handle the timing defense
• Registrar lock escalation: recovering a domain after theft or unauthorized transfer