Reverse Domain Name Hijacking: Test the Complaint Before Filing
A trademark registration and a similar domain name do not make a UDRP complaint automatically safe or successful. The complainant must prove all three policy elements, including that the respondent registered and used the domain in bad faith. If the available chronology or known facts make that case untenable, a rushed filing can lead to a finding of Reverse Domain Name Hijacking.
The UDRP Rules define RDNH as using the procedure in bad faith to attempt to deprive a registered domain-name holder of a domain name. A denied complaint is not automatically abusive. The risk rises when the complainant knew or should have known an essential element could not be proved, withheld material facts, mischaracterised evidence, ignored an obvious legitimate-interest case, or used the procedure as leverage after an unsuccessful purchase attempt.
1. Compare the dates
When were the domain, trademark rights, respondent business, and relevant use established? Later-acquired rights can create a decisive bad-faith problem.
2. Stress-test the defence
Descriptive meaning, surname, prior business, reseller use, criticism, investment, acquisition history, or another bona fide explanation must be examined fairly.
3. Prove targeting
Build a supported chronology showing why the respondent selected the domain because of the complainant’s mark, not merely why the brand wants the name now.
A panel may deny a complaint because the evidence does not establish one element without finding that the filing itself was abusive. RDNH addresses complainant bad faith and abuse of the administrative proceeding. Under Rule 15(e), a panel that finds the complaint was brought in bad faith, for example to attempt RDNH or primarily to harass the holder, declares that in the decision.
Weak but arguable case
The complainant loses after a genuine dispute over evidence or policy application. Failure alone is not sufficient for RDNH.
Known fatal defect
Available facts show an essential element cannot fairly be proved, yet the complaint presents the case as straightforward.
Procedural leverage
The filing is used to pressure a legitimate holder, obscure a failed acquisition strategy, harass, or obtain a domain beyond the policy’s purpose.
Use the current ICANN UDRP Rules and section 4.16 of the WIPO Overview 3.1 for the operative framework.
Did the respondent register or acquire the domain before the complainant had relevant trademark rights?
Establish the actual acquisition history, changes in control, earlier rights if any, and whether an exceptional fact can support targeting.
Does the string have a dictionary, surname, acronym, geographic, product, criticism, reseller, or existing-business explanation?
Review the respondent’s identity, historic content, business records, usage pattern, domain portfolio, disclosures, and commercial context.
Did the brand approach the holder, negotiate, reject a price, threaten UDRP, or omit those events from the complaint?
Preserve the complete communications and explain the sequence honestly. A high asking price alone does not replace proof of bad-faith registration.
Are assertions based on verified facts, reasonable inference, or unsupported labels such as fraud, cybersquatting, or impersonation?
Identify the source for every material allegation, disclose contrary facts, and remove claims the record cannot fairly support.
Confirm trademark filing, registration and first-use dates, ownership chain, licences, territories, and unregistered-rights evidence.
Confirm creation, acquisition, registrant changes, registrar history, archived use, sale history, and evidence of a new registration event where relevant.
Investigate name, business, descriptive use, investment, criticism, reseller conduct, authorisation, historic pages, and plausible good-faith purpose.
Connect the mark to registration through content, communications, portfolio pattern, redirects, offers, location, industry, timing, or other supported facts.
Collect facts that weaken the complaint and explain them. Do not omit prior negotiations, older respondent use, or known dates.
Assess negotiation, operational takedown, trademark or contract action, court, monitoring, or no action when UDRP does not fit.
Confirm why transfer or cancellation is needed and whether UDRP can lawfully provide it.
Place trademark rights and domain registration, acquisition, use, and communications on one timeline.
State the strongest plausible respondent case before drafting the complaint’s rebuttal.
Identify the evidence, counterevidence, inference, and unresolved gap for all three UDRP elements.
Proceed, pause, gather evidence, select another route, or stop, and preserve the reasons.
Review the trademark dates, domain acquisition, respondent interest, targeting record, negotiations, contrary facts, and alternative remedies before filing.
Proceed with UDRP
All three elements have a supported record, contrary facts are addressed, the respondent-interest case is weak, and transfer or cancellation is the required remedy.
Pause and investigate
Ownership dates, acquisition history, respondent identity, archived use, negotiations, or targeting evidence remain incomplete or contradictory.
Choose another route
The dispute is mainly contractual, commercial, infringement-focused, urgent operational abuse, or a domain acquisition problem outside the UDRP test.
What the finding does not do
- It does not award damages under the UDRP.
- It does not automatically decide a national-law claim.
- It does not mean every failed argument was dishonest.
- It does not transfer the domain to the complainant.
- It does not replace advice on court or settlement options.
Practical impact
- The published decision records abuse of the procedure.
- Investigation, drafting, and provider spend is lost.
- Negotiating credibility and leverage may weaken.
- Internal approval and governance failures become visible.
- Future filings may receive closer scrutiny from respondents and advisers.
Primary references
Review the ICANN UDRP Rules, the WIPO Overview 3.1, and the WIPO UDRP Guide before relying on any general checklist.