Step-by-step: seek a reverse domain name hijacking finding for a .dev…

Step-by-step: seek a reverse domain name hijacking finding for a .dev. UDRP and ccTLD domain recovery and defense across .dev. Email the firm to assess your ca…

A brand owner files a UDRP complaint against a developer who has held a .dev domain since the registry opened to general registration. The complaint names a trademark registered years after the domain was created. The panel reviews the record, finds the complainant knew of the registration date, and proceeds anyway. That is reverse domain name hijacking – and a finding to that effect is available to you if the record supports it.

To seek a reverse domain name hijacking finding for a .dev domain, a registrant must demonstrate in its UDRP response that the complainant brought the complaint in bad faith – typically by showing the complaint was filed despite the complainant's knowledge that it could not succeed on at least one of all three UDRP elements. The .dev zone is a gTLD operated by Google Registry and governed by the UDRP, making WIPO the most common forum; the standard 20-day response window applies from the date of commencement. An RDNH finding carries no monetary award, but it is a formal, published reputational sanction.

This guide walks each step in sequence, flags the trap each step conceals, and explains what evidence actually shifts a panel toward an RDNH finding.

What is reverse domain name hijacking, and does it apply to .dev?

Reverse domain name hijacking (RDNH) is a finding by a UDRP panel that a complaint was brought in bad faith, in an attempt to deprive a legitimate registrant of a domain it was entitled to hold. It applies wherever the UDRP applies – and .dev is a gTLD, so the UDRP governs every .dev dispute. WIPO handles the large majority of .dev cases; the Forum and CAC are alternatives.

The RDNH finding is authorized by the UDRP Rules. A panel makes the finding when the complainant used the Policy "as a tool of harassment" or filed knowing the complaint could not succeed. That standard sounds stringent. In our practice we see it applied in a recognizable cluster of situations: a complainant whose trademark postdates the domain by years; a complainant who ignores clear Paragraph 4(c) safe-harbor evidence on the record; or a complainant whose true motive was commercial pressure rather than trademark protection.

The .dev extension adds a wrinkle worth flagging. Google requires all .dev domains to be served over HTTPS, giving the zone a technical credibility signal. Some complainants cite a registrant's live development site as evidence of bad faith while ignoring that the registrant built real content there. A panel reading that argument carefully will often see through it – and that recognition can become part of the RDNH record.

Step 1: Confirm the UDRP governs your .dev dispute and identify the right forum

Before filing a response, verify that your registrar has actually initiated a UDRP proceeding under one of the four accredited providers – WIPO, the Forum, CAC, or ADNDRC. The complaint documents will name the provider. For .dev disputes, WIPO is the dominant choice, accounting for the large majority of gTLD proceedings.

The trap at this step: assuming the proceeding was filed at WIPO when it was filed at the Forum, or vice versa. Each provider has its own online case-management portal, its own commencement notice format, and its own deadline calculation rules. Missing the correct portal means missing the 20-day response window – and a default decision, rendered without your submission, forfeits the RDNH argument entirely.

Practical action: locate the formal commencement notice from the provider (not just the complaint forwarded by your registrar). Note the precise commencement date. Count 20 calendar days forward. That is your hard deadline. File your request for a three-member panel at the same time as your response if you want one – the request cannot come later.

Step 2: Read the complaint for the specific RDNH triggers it reveals

The response that wins an RDNH finding starts with a forensic read of the complaint. You are not reading to rebut every factual assertion. You are reading to find the element the complainant cannot prove – and to identify evidence the complainant had or should have had that it either omitted or mischaracterized.

The most reliable RDNH triggers are these. First, a trademark registration date that postdates the domain's creation date: if the complainant's mark issued after you registered the domain, bad faith at the time of registration is structurally impossible, and any competent practitioner reviewing the WHOIS before filing should have known that. Second, a complaint that cites your domain as "confusingly similar" to a mark but relies on a mark that is purely descriptive, generic, or geographically limited – and where the domain term is a common dictionary word or a common developer term. Third, a complaint that recites no actual evidence of use targeting the complainant's mark, yet asserts bad faith based only on the fact of registration.

We regularly advise registrants who discover mid-read that the complaint they received omits the registration date from the WHOIS record entirely – substituting the "updated date" or ignoring the creation date field. That omission is not accidental. Flag it explicitly in your response.

If you have received a UDRP complaint for a .dev domain and want an assessment of the RDNH argument before drafting a response, contact info@cognomenlaw.com.

Step 3: Build your Paragraph 4(c) legitimate-interest record

RDNH and legitimate interest are not the same argument, but they reinforce each other. A panel cannot find RDNH without also finding at least one of the three UDRP elements unproven. In practice, the weakest element for complainants in abusive .dev complaints is almost always the second: the registrant's lack of rights or legitimate interests. Paragraph 4(c) of the UDRP lists the safe harbors, and the strongest three are: a bona fide offering of goods or services before notice of the dispute; being commonly known by the name; and legitimate noncommercial or fair use without intent to mislead.

For a .dev domain, the bona fide-use safe harbor is particularly accessible. Developers register .dev names for projects, repositories, tools, and communities – and the HTTPS requirement means most live .dev sites have real content. Your record should document: the date you first registered the domain; the date you first deployed content; screenshots, server logs, or archived pages showing active development or use; any commercial or non-commercial project associated with the name; and the absence of any targeting of the complainant's brand in that use.

The trap here: submitting screenshots taken after the complaint was filed and arguing they show pre-dispute use. Panels weight contemporaneous evidence. If your site has been live for years, the Wayback Machine (web.archive.org) is your first documentary source. Pull archived captures going back to the earliest crawl. If the domain was on a development server without public indexing, look for GitHub commits, domain registration invoices, project documentation, or correspondence predating the dispute. Gaps in the timeline hurt; explain any gap directly rather than leaving the panel to speculate.

Step 4: Assemble the bad-faith-complaint evidence and make the RDNH argument explicitly

Panels do not make RDNH findings unless the respondent asks for one. That request must be explicit in the response. A vague complaint that the proceeding is "unfair" will not generate the finding. You must identify the specific conduct that constitutes bad faith on the complainant's part.

The strongest RDNH arguments are documentary. Consider what the complainant should have known before filing. A WHOIS lookup conducted any time before filing would have shown the domain registration date. A basic trademark registry search would have shown the complainant's mark issuance date. If those two dates make bad faith at registration impossible – and if the complainant filed anyway, with counsel, as a sophisticated trademark owner – panels have consistently held that the filing itself was reckless or in bad faith.

Additional evidence that supports an RDNH argument: pre-complaint correspondence in which the complainant or its agent demanded purchase of the domain at a price reflecting the complainant's market position rather than good-faith acquisition; a pattern in the same complaint or across other filings of targeting generic or descriptive domains; complainant's trademark registrations limited to specific goods and services that have no overlap with your domain's use; or a complainant who is a known corporate acquirer of domains using the UDRP as a cheaper alternative to market purchase.

In a recent matter (a .dev registration, spring 2025), we represented a respondent whose domain matched a common software tooling term. The complainant held a trademark in a narrowly defined financial-services subclass, issued two years after the domain was created. The complaint cited no evidence of targeting, no evidence of competitive harm, and no evidence the respondent had ever contacted the complainant. We filed a response documenting the registration date discrepancy, submitted archived development-site captures from the year of registration, and expressly requested an RDNH finding. The panel transferred nothing and issued the RDNH finding the same session.

Step 5: Choose between a single-member and a three-member panel

Panel composition matters more for RDNH than for most other arguments. A single panelist deciding alone may be more conservative about RDNH findings than a three-member panel, which requires a majority. In our practice, we frequently recommend requesting a three-member panel for any respondent case where RDNH is a central argument – the additional scrutiny benefits the registrant when the complainant's conduct is the subject.

The cost of that choice: if the complainant requested a single panelist, the respondent who requests a three-member panel generally bears half the incremental cost difference, with the complainant covering the other half. At WIPO, a three-member panel for one to five domains costs USD 4,000 in total forum fees versus USD 1,500 for a single-member panel. The respondent's share of the additional cost is typically around USD 1,250. That is not a small amount. Weigh it against the value of the domain and the strength of the RDNH record.

The trap: requesting a three-member panel without having a strong RDNH record to support the decision. A three-member panel that finds against you on all elements and declines RDNH is not a better outcome than a single panelist who reaches the same result. Request the three-member panel when the record is genuinely strong; accept the single-member composition when the budget does not support the upgrade and the record will speak for itself.

Step 6: Draft the response with the panel as the audience, not the complainant

A UDRP response is addressed to the panel. Write it the way a panel decision reads: organize by element, state the conclusion first in each section, then support it with the evidence on the record. Panels read hundreds of submissions. A response that buries the RDNH argument in a general protest against the complainant's conduct will not receive the weight it deserves.

Structure the response in three parts. First, address the three elements of Paragraph 4(a) in order, beginning with the one the complainant is weakest on. Second, present the Paragraph 4(c) safe-harbor analysis in its own section, tied to specific exhibits. Third, in a distinct section – not a footnote, not a parenthetical – present the RDNH argument: the rule, the conduct, the evidence that the complainant knew or should have known the complaint could not succeed, and the explicit request for the finding.

What to exclude from the response: grievances that are not on the three UDRP elements; threats of court action that are not supported by a realistic litigation position; allegations about the complainant's character that are not supported by documentary evidence in the record. Panels are not moved by rhetoric. They are moved by a well-ordered record.

If you are evaluating whether your .dev response record is strong enough to support an RDNH finding, reach us at info@cognomenlaw.com before the 20-day window closes.

Step 7: Understand the realistic outcome and what follows an RDNH finding

An RDNH finding is a published record that the complainant misused the UDRP. It carries no monetary penalty. The domain remains with you; the complainant cannot refile the same complaint at a different provider on the same facts – that would compound the bad-faith record. The practical consequence for the complainant is reputational: the decision is indexed in the WIPO database, the Forum's case archive, and legal commentary, and it attaches to the complainant's trademark enforcement history.

For you as registrant, the RDNH finding strengthens your position in any subsequent dispute over the same domain. If the complainant later initiates court action, the published RDNH decision is material evidence of prior abusive conduct. It also removes the administrative pressure of a re-filed complaint on the same facts, because refiling after an RDNH finding at a different provider is widely regarded as itself grounds for a further RDNH finding.

What the RDNH finding does not do: it does not award attorney fees or filing costs. It does not preclude the complainant from filing a new complaint based on genuinely new facts – for example, a subsequent change in how you use the domain. And it does not prevent court action in a jurisdiction where the complainant holds trademark rights. If court action is a realistic threat in a particular jurisdiction, work with local litigation counsel in the relevant jurisdiction to assess the anticybersquatting or trademark-infringement exposure separately.

In a second matter we handled (a .dev domain in the developer-tools space, autumn 2024), the complainant had previously obtained an RDNH finding against it in an unrelated domain dispute. We cited that prior finding as pattern evidence of bad-faith UDRP use. The panel expressly referenced it in the RDNH analysis. The domain was retained and the finding issued. Prior RDNH history, when it exists, is fair game for the record.

Cross-zone considerations: what if the dispute spans .dev and another zone?

UDRP complaints can cover multiple domains in a single filing only if the registrant of record is the same. If you hold a .dev domain and the complainant also targets your .com or a ccTLD in the same filing, your response must address each domain's registration date, each zone's evidence of use, and each domain's RDNH argument separately – or collectively where the facts are common.

The choice of forum is the same across zones in a single UDRP complaint: WIPO, the Forum, or CAC, whichever the complainant selected. You cannot redirect a gTLD dispute to a ccTLD procedure, and you cannot consolidate a .de complaint (which goes to the German courts) into a UDRP proceeding.

Where the same complainant sends cease-and-desist letters for multiple zones, watch for a filing in the zone where the complainant's case is strongest as a vehicle to establish a factual record that then feeds into a stronger filing in a zone where its mark is weaker. That sequencing strategy is a recognized pattern; flag it in your .dev response if you see it.

For .dev specifically, the UDRP applies uniformly regardless of whether the domain is registered through Google Domains, any ICANN-accredited third-party registrar, or another channel. The registry operator's HTTPS requirement and its policies for .dev are separate from the dispute resolution layer.

Related at COGNOMEN

• UDRP respondent defense and RDNH findings – full service overview
• Case study: defending a generic domain name against a US trademark complaint
• Guide: how to prove legitimate interest in a .xyz domain UDRP response