Step-by-step: defend a .dev domain acquired as an investment

You registered a .dev domain as an investment – perhaps a clean generic term, a developer-relevant keyword, or a short brandable string. Now a trademark holder has filed a UDRP complaint, and you have 20 days to respond before the case proceeds without you. The right answer is not to panic, and it is not to transfer the name in the hope of avoiding a fight. The right answer is to understand exactly what the complainant must prove and to build a response that meets each element directly.

A .dev domain is a gTLD administered by Google Registry and subject to the Uniform Domain Name Dispute Resolution Policy (UDRP), with WIPO as the predominant dispute provider. To succeed, the complainant must prove all three elements of Paragraph 4(a): confusing similarity to a mark, your lack of rights or legitimate interests, and registration and use in bad faith. If any element fails, the complaint fails – and where the complaint was brought opportunistically, a panel may add a finding of Reverse Domain Name Hijacking (RDNH).

This guide walks through each step in sequence, flags the trap each one conceals, and identifies the evidence that decides the outcome.

What rules govern a .dev dispute, and why does the zone matter?

A .dev domain is a generic top-level domain, so the UDRP – not a national ccTLD procedure – controls any complaint. WIPO is the dominant forum; the Forum and CAC also accept .dev cases, but WIPO handled the large majority of disputes in this zone since the registry's opening. Understanding which rulebook applies is the starting point, because the defenses available to a respondent differ sharply between the UDRP and country-code procedures such as the Nominet DRS for .uk or the DENIC-block system for .de.

Under the UDRP, the only remedies a panel can order are transfer or cancellation. No monetary award can follow you out of the proceeding. That asymmetry matters tactically: a complainant who spends USD 1,500 or more on a WIPO filing fee – plus legal fees – is investing real money for a binary outcome. A weak complainant may settle or withdraw once you file a substantive response. In our practice, we have seen withdrawal shortly after a respondent's response landed, when the complainant recognized the record did not support bad faith.

The .dev registry also enforces HTTPS. Every live .dev site must present a valid certificate. That technical requirement has a subtle evidentiary consequence: a parking page on .dev is still a live page. Panels have evaluated parking-page revenue as potentially passive bad-faith use, though the analysis is fact-specific and does not automatically doom an investor's position.

If you have just received a UDRP complaint over a .dev domain you acquired as an investment, contact info@cognomenlaw.com for an assessment of the three elements before your response deadline runs.

Step 1: Read the complaint carefully – and map each element to your facts

The single most common respondent error is drafting a response that argues generally rather than arguing element by element. The UDRP complaint is structured around Paragraph 4(a)(i), (ii), and (iii). Your response must match that structure. A response that rebuts bad faith but ignores the complainant's trademark rights argument leaves the panel with an unanswered record on the first element.

Read the complaint as an analyst, not as the party being accused. For each element, ask: what evidence did the complainant actually produce, and what is missing? Trademark registration certificates speak for themselves; assertions about your knowledge or intent require evidence. Mark every assertion the complainant made without support. Those gaps become your response's foundation.

The trap hidden in Step 1 is assuming the complaint is strong because it looks long. Complainants sometimes bulk out a filing with trademark history that is not actually relevant to the domain's registration date. A senior trademark right acquired after the domain's registration date raises serious questions about whether Paragraph 4(a)(iii) can be met – because a registrant cannot have targeted a mark that did not yet exist. Check the dates of every right cited against the WHOIS (or RDDS) registration timestamp for the domain.

Step 2: Establish whether you have rights or legitimate interests under Paragraph 4(c)

Paragraph 4(c) of the UDRP lists three non-exhaustive safe harbors. The most relevant for a domain investor are: (i) demonstrable preparations to use the domain in connection with a bona fide offering before receiving notice of the dispute; and (iii) legitimate noncommercial or fair use. A second safe harbor – being commonly known by the domain name – applies mainly where the respondent's own name or brand matches the domain.

For investors, the bona fide-use harbor and the legitimate-investment doctrine are the practical terrain. Panels have long recognized that domain investing is a legitimate business activity provided the registrant selected the domain for its inherent value – a dictionary word, a common abbreviation, a developer-relevant generic – rather than to exploit a specific complainant's mark. The burden of proof on this element shifts after the complainant makes a prima facie showing: you must then produce actual evidence of legitimate interest, not a bare assertion.

What evidence works? Development plans – even preliminary ones documented before the complaint arrived – are valuable. Email threads discussing potential use, mockups, screenshots of build environments, a GitHub repository or domain-linked project sketch, correspondence with a developer about the site: all of these pre-dispute documents are more persuasive than post-complaint declarations made in the response itself. Panels discount evidence that appears to have been manufactured in reaction to the filing.

The trap in Step 2 is conflating generic value with non-infringing intent. A domain with obvious keyword value in the developer community can still be found to lack legitimate interest if panels conclude that the specific registration targeted the complainant's mark. If the complainant's brand is suggestive rather than descriptive – a coined word that happens to look like a dictionary term – the investor defense requires sharper analysis.

Step 3: Undercut the bad-faith allegation with a complete registration-intent record

Paragraph 4(a)(iii) requires the complainant to prove the domain was registered and is being used in bad faith. Both limbs must be established. Registration intent is assessed at the date of registration – not at the date of the complaint. Use in bad faith is assessed at the time of the proceeding.

Assembling the registration-intent record means answering: what did you know about the complainant at the moment you registered this domain? If the complainant's mark was obscure, regional, or post-dates your registration, that evidence goes directly to negating the first limb. Purchase confirmation emails, domain portfolio records, portfolio acquisition strategy documents (even a spreadsheet listing the criteria you apply), and contemporaneous market data on comparable sales all help reconstruct your state of mind at the relevant moment.

On the use limb, panels evaluate what the domain resolves to. A parking page that displays pay-per-click links in categories competitive with the complainant's business is the fact pattern complainants most frequently cite as bad-faith use. If your parking page is generic – links to broadly relevant developer content – or if the domain simply returned a blank page, those facts are more defensible. Documentation of what the domain resolved to on the complaint date and in the period leading up to it can be obtained through archive services; gather that evidence early.

The trap in Step 3 is passive holding. Panels have held that passive holding – leaving a domain unused for a long period – can in certain circumstances constitute bad-faith use, particularly where the domain is an exact match of a well-known mark and the registrant offers no credible explanation for the non-use. If your domain has sat parked and unbuilt for years, your response needs to address that directly, not avoid it.

In a recent matter – a .com developer-keyword domain, spring 2025 – we assembled a portfolio acquisition record that showed the domain had been acquired alongside a dozen similar single-keyword developer terms, with no targeting of any specific brand. The complainant withdrew before the panel appointment, declining to proceed on a record that clearly supported legitimate investment intent.

Step 4: Build the counter-record and prepare your response document

A UDRP response is a short brief, not a court pleading. WIPO's rules set an annex page limit that most experienced respondents reach. Every word must earn its place. The structure that works: open with a concise statement of why the complaint fails on each element; then address each Paragraph 4(a) element in order; then, if appropriate, make the case for RDNH.

Organize your evidence as numbered annexes keyed to the argument. Screenshots are effective; RDDS/WHOIS printouts showing registration date and registrant name are standard exhibits. Trademark registration printouts from the relevant office support your analysis of whether the complainant's rights pre-date your registration. Comparable domain sales data – showing that names like this one trade for legitimate consideration among investors – contextualizes your investment intent.

The trap in Step 4 is over-length and under-focus. Panels are experienced adjudicators who read hundreds of these filings each year. A 40-page response that buries the strongest point in discursive background does less work than a 12-page response that opens with "the domain was registered four months before the complainant's trademark application and resolves to a generic parking page unrelated to the complainant's category."

We regularly advise respondents on the evidence hierarchy: which exhibits move the needle and which produce volume without effect. The final response document should be reviewed against the complaint point by point before submission to ensure no assertion goes unanswered.

Step 5: Assess whether an RDNH finding is realistic – and request one if the facts support it

Reverse Domain Name Hijacking is a panel's finding that a complainant brought the UDRP in bad faith – typically, where the complaint was filed with knowledge that it could not succeed. RDNH carries no financial penalty under the UDRP, but it is a matter of public record in the WIPO case database. For serial complainants, a pattern of RDNH findings creates reputational and practical consequences.

When should you request RDNH? The conditions that most frequently support such a finding are: the complainant's trademark rights post-date the domain registration by a significant margin; the complainant was aware of that timeline and filed anyway; the domain is a dictionary term or generic expression that self-evidently did not target the complainant; or the complaint relies on fabricated or implausible bad-faith theories. None of these individually guarantees an RDNH finding – panels retain discretion – but together they frame a compelling argument.

The trap in Step 5 is requesting RDNH reflexively. A panel that denies the transfer but declines to make an RDNH finding is still a win for the respondent. Overclaiming RDNH in a case where the complainant had a colorable (if ultimately failing) argument can read as unsympathetic to the panel. Request RDNH where the factual case for it is affirmatively strong; do not append it as boilerplate.

In a matter involving a short three-letter .dev domain, winter 2024, we pursued an RDNH finding alongside the substantive defense on the grounds that the complainant's mark was a stylized logo without independent text rights over the letter combination at issue. The panel denied the transfer and noted the weakness of the rights element – a publicly recorded outcome that served the registrant's long-term portfolio reputation.

If you believe the complaint against your .dev domain was brought opportunistically, we can assess the RDNH argument alongside the full respondent defense. Email info@cognomenlaw.com to discuss the record.

How does .dev compare to other zones for respondent-side disputes?

The choice of zone shapes the defense, even when the underlying UDRP rules are identical on paper. A .dev dispute is a pure UDRP proceeding – same rules as .com – but several zone-specific facts color the analysis. Google Registry's operation of .dev means the registry is closely associated with the technology and developer community. Panels aware of that context may be more receptive to arguments that a domain was acquired for its value to that community, not to target a business mark.

Contrast that with a .uk dispute, which proceeds under the Nominet DRS – a distinct set of rules with a different test ("abusive registration" rather than "registered and used in bad faith") and a mandatory mediation stage before a formal decision. Or a .de dispute, which has no UDRP equivalent at all and requires proceedings in German courts, with a DENIC DISPUTE entry to freeze the domain during litigation. Those zones present different strategic calculations entirely.

Within the gTLD family, the UDRP applies equally to .dev, .com, .net, .org, and the new gTLDs. But new gTLDs like .dev also see URS (Uniform Rapid Suspension) proceedings, which operate at a "clear and convincing" standard – higher than the UDRP's preponderance standard – and result only in suspension, not transfer. A complainant who cannot meet the UDRP standard is even less likely to succeed under URS, which is useful background when assessing a threat letter that cites both routes.

The practical cross-zone scenario that arises for .dev investors: a complainant holds a .com of the same name and files over the .dev. The complainant's own .com registration does not itself constitute a trademark right – only a registered or well-established common-law mark does. Panels have rejected arguments that domain ownership creates trademark rights that can anchor a UDRP complaint.

What evidence actually decides the outcome?

At the end of a UDRP proceeding, three categories of evidence disproportionately influence the panel's decision. Understanding the hierarchy helps you invest time in what matters.

Registration-date evidence is the most powerful in the investor's toolkit. A domain registered before the complainant's trademark – or a domain generic enough that no targeting was plausible at the date of registration – goes to the heart of Paragraph 4(a)(iii). Chain-of-title records showing consistent investor ownership without any approach to or communication with the complainant reinforce this. Panels have consistently held that a domain investor who acquired a name for its keyword or investment value, with no contemporaneous awareness of the complainant's brand, cannot be found to have registered it in bad faith toward that complainant.

Use evidence – what the domain does at the time of the proceeding – shapes the bad-faith use limb. A domain that generates pay-per-click revenue in the complainant's product category is harder to defend than one parked generically or developing toward a legitimate build. Screenshots, archive records, and traffic reports give the panel a concrete picture rather than a contested narrative.

Portfolio context is underused by respondents. A domain investor who can show that the disputed name was acquired as part of a coherent, documented investment strategy – alongside similar keyword terms, at market prices, without any specific targeting – presents a very different profile from a registrant who holds a single exact-match domain for a known brand name. Panels are experienced in distinguishing the two. Bring the portfolio into the record.

Related reading at COGNOMEN

• Respondent defense and RDNH services – how COGNOMEN builds the record for registrants
• Seeking an RDNH finding – when and how to bring the argument
• Domain due diligence – what to check before acquiring a domain with dispute exposure

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.