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

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

A technology company received a UDRP complaint at WIPO in early 2025. The respondent had held a .dev domain for years – long before the complainant filed for, let alone received, a trademark registration. The complainant's counsel argued confusing similarity and bad faith. The respondent's position was straightforward: the domain was registered before the trademark existed. That fact alone does not end the case. But it heavily shapes every element of the defense.

When a respondent registered a .dev domain before the complainant held trademark rights, the UDRP's bad-faith element becomes extremely difficult for the complainant to sustain. Under Paragraph 4(a)(iii) of the UDRP, bad faith requires registration AND use in bad faith – a cumulative standard. Registration that predates any trademark right is strong evidence that the "registration in bad faith" limb fails entirely. A standard WIPO defense runs about two months from commencement to decision. The WIPO filing fee for the complainant is USD 1,500 for a single-member panel on one domain; the respondent pays nothing to participate.

This analysis covers the governing rules for .dev, the full Paragraph 4(c) safe-harbor toolkit, how panels treat prior-registration evidence, where the contrary view surfaces, what a realistic RDNH finding requires, and the practical steps to build a winning defense record.

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

The .dev registry is operated by Google Registry and has incorporated the UDRP as its mandatory dispute-resolution mechanism, meaning the complete text of the Policy and its supplemental Rules applies without modification. That matters for respondents: the three-element test of Paragraph 4(a) applies verbatim, the Paragraph 4(b) bad-faith factors apply, and crucially the Paragraph 4(c) safe harbors apply. There is no .dev-specific carve-out that weakens registrant rights.

Google Registry also enforces a technical restriction: .dev domains must be served over HTTPS. That means .dev registrations are concentrated heavily in the developer and technology community, which has a bearing on the legitimate-use analysis. A respondent using a .dev domain for a personal project, an open-source repository, or a developer tool occupies a recognized and documented category of use.

Proceedings are filed before an ICANN-accredited UDRP provider. Because .dev is a new generic top-level domain, all four providers are available – WIPO, the Forum, CAC, and ADNDRC. In practice, WIPO and the Forum account for the overwhelming majority of proceedings across all gTLDs. The complainant selects the provider; the respondent cannot move the case once filed. Understanding this from the outset shapes how you prepare the response, because WIPO and the Forum have somewhat different administrative styles even though they apply identical substantive rules.

Does prior registration defeat the bad-faith element under the UDRP?

Prior registration is the single most powerful fact a .dev respondent can bring to a panel, and the consensus view is that it is generally dispositive of the "registration in bad faith" prong when the evidence is clear. The reasoning is elementary: to register a domain in bad faith targeting a mark, the registrant must have known of that mark at the time of registration. If the mark did not exist yet, the registrant could not have targeted it.

Panels have consistently held that a respondent who registers a domain before any trademark rights arise cannot have registered in bad faith for purposes of Paragraph 4(a)(iii). The WIPO Jurisprudential Overview reflects this consensus position. It recognizes an exception – where a complainant can show the respondent anticipated an imminent trademark filing or brand launch and registered the domain specifically to intercept it – but that exception requires the complainant to prove forward-looking bad intent at the moment of registration, not merely speculate about it.

What does "before the trademark" mean in practice? The relevant comparison is between the domain registration date and the earliest date on which the complainant acquired enforceable trademark rights. For a registered mark, that date is normally the filing date in the jurisdiction where the registration was sought, or the date of actual registration, depending on the legal system. For an unregistered or common-law mark, the complainant must demonstrate that it had established sufficient reputation under the name before the domain was registered. Common-law trademark claims require evidence of use in commerce, market recognition, and consumer association – a much harder showing than production of a registration certificate. Respondents defending against common-law assertions should scrutinize the date and the evidence carefully; many such claims rest on thin foundations.

The prior-registration defense works best when the respondent can document the exact registration date and show the complainant's trademark postdates it by a clear margin. A gap of months is meaningful; a gap of years is often decisive.

How do panels handle the "cybersquatting in anticipation" exception?

The anticipatory bad-faith doctrine is the primary weapon a complainant uses when confronted with a prior-registration defense. The argument runs: the respondent knew the complainant's brand was about to launch, or saw early trademark filings, and registered the domain preemptively to profit from the imminent mark. Panels will find bad faith under this theory only where the evidence of forward-looking intent is concrete and specific.

Generic awareness that a company exists, or that its name is commercially attractive, is not enough. The complainant must produce evidence tying the registrant specifically to knowledge of the complainant's imminent trademark rights. Relevant evidence might include: the registrant contacted the mark owner shortly before or after filing to offer the domain for sale; the domain was registered immediately following a public funding announcement or product launch; the registrant had a demonstrable pattern of registering names that correspond to emerging brands; or the registrant's own communications revealed knowledge of the specific mark.

In our practice, we find that complainants overreach this doctrine regularly. A brand owner discovers a .dev domain that matches their name, assumes the registrant must have known about them, and instructs counsel to argue anticipatory bad faith with nothing concrete to point to. That argument inverts the burden of proof. The complainant bears the burden on all three UDRP elements. A respondent who registered a .dev domain two or three years before the complainant's trademark filing has a strong answer: the anticipatory bad-faith theory requires more than temporal proximity to an eventual trademark.

What is the contrary view? A minority of panels have shown willingness to infer bad faith from circumstantial evidence even absent direct proof of knowledge, particularly where the domain precisely replicates a distinctive coined mark and the registration was followed quickly by silence or parking behavior. This minority approach is most likely to surface when the mark is extremely well-known internationally even before formal trademark registration – think a globally recognized technology product that had extensive press coverage before its official launch. The respondent in that scenario faces a harder road. The defense then must shift to demonstrating a credible independent reason for the registration.

Building the Paragraph 4(c) safe-harbor record for a .dev domain

Even if a respondent wins on the bad-faith element, panels often examine the safe harbors of Paragraph 4(c) as well. A strong Paragraph 4(c) showing reinforces the prior-registration defense and provides an independent ground for denial of the complaint. For .dev domains, three safe harbors are particularly relevant.

Bona fide use before notice of the dispute (Paragraph 4(c)(i)) is the workhorse safe harbor. The respondent must show that before receiving notice of the dispute – which panels generally read as the date the complaint was filed or a prior cease-and-desist – the respondent was using the domain in connection with a bona fide offering of goods or services. For a .dev domain, this typically means a developer project, a software application, a technical portfolio, or a commercial offering in the technology space. Because .dev is a developer-oriented zone, a technical use is credible on its face. The key is documentation: screenshots, version-control history, deployment logs, user-facing materials, and any correspondence about the project, all dated before notice.

A common trap: the domain was registered years ago but the respondent has done little with it since. Panels examine whether the use was genuine and ongoing. Passive holding of a .dev domain – pointing it at a parking page or leaving it resolving to nothing – is a fact pattern that weakens the Paragraph 4(c)(i) defense. It does not defeat the prior-registration argument on bad faith, but it gives the panel less to work with on legitimate interest. Respondents in that position should audit the domain's history carefully, produce any evidence of development work or plans, and be prepared to explain the gap.

Commonly known by the name (Paragraph 4(c)(ii)) applies where the registrant is an individual, business, or organization known by the domain name, independently of any trademark registration. A developer who has operated under a trade name matching the .dev domain, or who has a professional identity associated with that name in the relevant community, may satisfy this safe harbor. The evidence is the registrant's own documentation: business registrations, professional profiles, project attributions, and community recognition.

Legitimate noncommercial or fair use (Paragraph 4(c)(iii)) covers uses that are not commercial – criticism sites, community resources, educational tools, or open-source projects that do not generate revenue for the registrant. This safe harbor is available but panels apply it narrowly where the domain is not clearly differentiated from the complainant's mark, or where the content suggests the registrant is trading on the complainant's reputation even without direct commercial intent.

In building the record, we regularly advise registrants who hold .dev domains to compile a timeline: when was the domain registered, what development activity occurred, when was the domain first publicly accessible, and what did it resolve to at each stage? That timeline, supported by exhibits, is what a panel actually reads. Assertions without evidence carry almost no weight.

To weigh UDRP against a court action for your case, email info@cognomenlaw.com. We can assess the three elements and your evidence before any filing deadline passes.

What evidence actually decides the outcome of a prior-registration defense?

Every UDRP panel produces a written decision, and reading those decisions analytically reveals a consistent pattern: the cases that go against respondents despite prior registration almost always share one or more of several features. Understanding those features tells you what evidence to assemble and what vulnerabilities to address.

First, registration date documentation. The panel will check the domain's registration date against the complainant's trademark evidence. If the registrant cannot produce a clear WHOIS historical record or registrar-confirmed creation date, the panel has less certainty about the timeline. Respondents should obtain a certified or registrar-confirmed record of the domain's creation date early in the process, particularly if the domain has changed registrars, which can sometimes obscure the original date in RDDS output.

Second, the complainant's trademark date. The response must dissect the complainant's trademark evidence, exhibit by exhibit. When was each mark applied for, in which jurisdiction, and when was it granted? If the complainant relies on a common-law mark, what evidence supports the claimed date of first use? Respondents frequently discover, on careful analysis, that the complainant's claimed trademark rights are later – sometimes substantially later – than the domain registration. That discrepancy should be stated explicitly and supported with documentary comparison.

Third, the respondent's conduct after registration. Panels look at what the registrant has done with the domain since registering it. A history of consistent, documented use in a direction unrelated to the complainant's business is very strong. A history of contacting the complainant to offer the domain for sale is very damaging – it can establish the "use in bad faith" limb even where registration preceded the trademark. In a recent matter involving a .dev domain in the technology sector (spring 2025), we secured denial of the complaint because the respondent produced three years of development commit history and had never contacted the complainant. The complainant's trademark postdated the registration by approximately twenty-two months. The panel denied the complaint on both bad faith and legitimate interest grounds.

Fourth, the distinctiveness of the mark. If the complainant's mark is descriptive or generic in the technology context – words like "stack," "core," "deploy," or similar developer vocabulary – the prior-registration defense is reinforced by the argument that the registrant had a plausible independent reason to choose the name. Coined or highly distinctive marks make the independent-reason argument harder, though the timeline analysis remains equally important.

Fifth, consistency of the record. Panels are alert to respondents who construct a post-hoc narrative. If the respondent claims a legitimate project but the project's digital footprint only materialized after the complaint was filed, that inconsistency undermines the defense. The value of documented pre-complaint use is that it cannot be fabricated retroactively.

When is a Reverse Domain Name Hijacking finding realistic on a .dev domain?

Reverse Domain Name Hijacking (RDNH) is a finding that the complainant brought the UDRP case in bad faith, knowing it lacked the facts to meet the three-element test. An RDNH finding is reputational, not monetary – the UDRP provides no damages, costs award, or injunction in any direction. But an RDNH finding is on the record. It is public. It signals that the complainant's legal team filed an abusive complaint, and brand owners in some industries care about that signal.

Panels find RDNH where a complainant, represented by counsel, knew or should have known that the registration predated its trademark rights and filed anyway. The prior-registration scenario is among the most fertile grounds for RDNH because the date evidence is typically straightforward. If the complaint itself acknowledges or reveals the registration date, and the complainant's trademark evidence on its face postdates that registration, a panel can infer that the complainant's counsel failed to analyze the timeline before filing.

For an RDNH finding, the respondent's submission should do three things. It should set out the timeline clearly, with exhibits, showing the gap between the domain creation date and the earliest trademark right. It should identify what the complainant's own submissions reveal about the registration date – complainants often include WHOIS data that contains the answer. And it should characterize the complaint as an attempt to use the UDRP as a commercial tool to acquire a domain the complainant cannot purchase or is unwilling to pay market price for.

A realistic RDNH scenario on a .dev domain: the domain was registered four years before the complainant's trademark application date; the complainant has been developing its brand during those four years but applied for the mark only recently; the complainant now wants the domain and has sent a low-ball offer that was rejected; and the complainant's UDRP complaint essentially re-presents the same offer in procedural form. That pattern, documented, supports an RDNH request.

The contrary view is that panels do not routinely find RDNH and generally require more than a timeline showing to conclude the complaint was filed in bad faith. Some panels limit RDNH to cases where the complainant's conduct was egregious – threatening communications, procedural abuse, or a pattern of filing against the same registrant. The consensus standard, however, is simply that a represented complainant knew or should have known it could not succeed, and that is a standard the timeline analysis often satisfies.

Choosing the right strategy: defense posture and the cross-forum dimension

The choice of strategy in a .dev defense turns on several variables that the respondent and counsel should assess before filing the response.

If the prior-registration gap is large and documented – several years, with a clear creation date record – the defense can be built primarily on that foundation. The response lays out the timeline, attacks the complainant's trademark dates, documents any pre-complaint use, and requests denial on all three elements. If the evidence warrants it, an RDNH finding is requested as well.

If the gap is narrower – months rather than years – the defense requires more layering. The Paragraph 4(c)(i) safe harbor becomes more critical. The respondent needs to demonstrate that any use of the name was genuinely for an independent project, not in anticipation of the complainant's brand. Evidence of the registration's purpose – emails, project plans, GitHub history, business correspondence – is what closes that gap.

If the complainant is in the technology sector and the mark is widely recognized internationally, even without a registration date that predates the domain, the respondent should consider whether the independent-purpose evidence is strong enough to withstand a circumstantial anticipatory-bad-faith argument. A developer who registered a .dev domain that matches a globally recognized technology product faces a different landscape than one who registered a domain matching a small regional software vendor.

The cross-zone dimension matters when the complainant also holds or threatens a dispute over related domains in other zones – a .com, a .io, or a ccTLD. A UDRP decision on one domain does not bind a panel on another, but a favorable prior decision is persuasive. We have defended registrants where the .dev dispute was the first filing, and the strategy adopted there set the frame for later disputes in other zones. Coordinating that response from the outset avoids inconsistency.

Where arbitration under the UDRP cannot fully address the situation – for example, where the respondent seeks damages or a declaratory judgment on trademark rights – US anticybersquatting litigation in court is the path that reaches money and injunctive relief, handled with local litigation counsel in the relevant jurisdiction. The registrar lock escalation and court recovery service addresses situations where domain ownership is contested beyond what the UDRP's limited remedies can resolve.

If you have received a complaint or a cease-and-desist targeting a .dev domain you registered before the complainant's trademark, contact info@cognomenlaw.com for an assessment of the three elements and your evidence before the 20-day response deadline runs.

The realistic next step for a .dev respondent

The respondent's single most important action is to start before the deadline. Under the UDRP, the respondent has 20 days from the date the case commences to file a response. Missing that deadline does not automatically mean losing, but defaulting deprives the panel of the respondent's evidence and almost always results in transfer. The complainant's uncontested submissions become the panel's only record.

A response in a prior-registration defense should be built in four layers. First, a clean timeline exhibit: domain creation date, complainant's earliest trademark date, any interim use by the respondent, and date of notice of dispute. Second, a trademark-date analysis: what the complainant filed, when, in which jurisdiction, and when rights were actually established. Third, a use-and-purpose section: what the respondent has done with the domain, with exhibits, in chronological order. Fourth, where the evidence supports it, an RDNH request: why the complainant knew or should have known the complaint was untenable on the facts.

In our practice, we have defended registrants who arrived within 48 hours of the response deadline and still produced a complete record. The legal analysis moves fast when the prior-registration gap is clear and the registrant can locate the relevant documents quickly. Earlier is better, but the window, while short, is workable if the evidence exists.

The AUDIENCE_MYTH version of this situation is that prior registration is a complete answer and the registrant can simply assert it without proof. It is not, and they cannot. Prior registration is a powerful defense, but it is a legal argument that requires exhibits, analysis, and a response structured to address all three UDRP elements. A bare assertion that the domain predates the trademark, submitted without supporting documentation, rarely prevails against a well-briefed complainant.

See also the broader analysis of respondent rights and defensive strategy at COGNOMEN's respondent defense and RDNH service, and the deadline management guide at responding within the UDRP deadline.

Related at COGNOMEN

• Respondent defense and RDNH – protecting your domain at WIPO, the Forum, and CAC
• Responding within the UDRP deadline – what to file and when
• Registrar lock escalation and domain recovery where arbitration is insufficient