What reverse domain name hijacking is
Reverse domain name hijacking — RDNH — is the mirror image of cybersquatting. It is a trademark owner using the UDRP in bad faith to try to take a domain name away from a registrant who is entitled to keep it. The Rules for the UDRP define it at Paragraph 1 in those terms: using the Policy in bad faith to attempt to deprive a registered domain-name holder of a domain name.
It is not a claim anyone files. There is no RDNH complaint, no RDNH forum, no RDNH remedy to seek. It is a finding a panel makes inside a case the registrant has already won on the merits, recorded in the text of the decision. That is why I classify it as disputed: the registrant's position is resolved by the failure of the complaint, not by any recovery process, and the RDNH declaration adds nothing to the domain's status.
What it does add is a record. The decision is published, indexed and citable, and it says in terms that the complainant abused the proceeding.
Paragraph 15(e): the declaration is mandatory, the finding is not
The operative provision is Paragraph 15(e) of the Rules. If the panel finds that the complaint was brought in bad faith — for example in an attempt at reverse domain name hijacking, or primarily to harass the domain-name holder — the panel shall declare in its decision that the complaint was brought in bad faith and constitutes an abuse of the administrative proceeding.
The structure of that sentence matters more than it appears. Whether to make the finding is discretionary; panels weigh the complaint and decide. Once the finding is made, the declaration is mandatory — shall declare — and it must use the language of abuse of the administrative proceeding. There is no version where a panel concludes a complaint was brought in bad faith and then quietly declines to say so.
A panel here is the one or three neutrals the provider appoints to decide the case on the documents. There is no hearing, no discovery and no live testimony. Everything the panel knows about the complainant's state of mind, it takes from the complaint itself and from whatever the respondent — the registrant, defending — puts in the record.
The threshold: losing is not enough
The most persistent misconception about RDNH is that a denied complaint produces one. It does not, and panels have consistently held that the mere lack of success of a complaint is not by itself sufficient for a finding of reverse domain name hijacking.
The reason is obvious once stated. The UDRP asks complainants to prove three elements on a paper record, and complaints fail on the evidence all the time without anyone having acted in bad faith. A trademark owner can hold a genuine mark, believe in good faith that a registrant is targeting it, and be wrong. That is an unsuccessful complaint, not an abusive one.
What tips a case over is not the outcome but the complainant's position at the moment of filing: what it knew, what it plainly ought to have known, and what it chose to put in front of the panel.
The grounds panels rely on
Consensus panel guidance collected in the WIPO Jurisprudential Overview 3.0, and applied across published decisions, groups the recurring grounds for an RDNH finding into a short and fairly stable list. Paraphrasing rather than quoting it, panels have found reverse domain name hijacking where:
- the facts show the complainant knew it could not succeed on one of the three required elements — for instance because it lacked relevant trademark rights, or knew the respondent had rights or a legitimate interest, or knew there was no bad faith because the domain was registered well before the mark;
- the complainant clearly ought to have known it could not succeed on any fair reading of facts reasonably available before filing, including what the website itself showed and what public sources such as the Whois record disclosed;
- the complainant unreasonably ignored settled panel precedent, outside the limited situations where advancing an alternative legal argument is prima facie justified;
- the complainant provided false evidence or otherwise attempted to mislead the panel;
- the complainant provided intentionally incomplete material evidence, which the respondent then had to clarify;
- the complainant failed to disclose that the case was a refiling of an earlier one;
- the complaint was filed after an unsuccessful attempt to buy the domain from the respondent, with no plausible legal basis; or
- the complaint rested on the barest allegations with no supporting evidence at all.
That guidance is a synthesis of decided cases rather than binding policy, and panels apply it as such. A respondent does not have to request the finding for it to be made: panels may reach it on their own analysis of the complaint, and decisions exist in which the issue was raised entirely on the panel's initiative — sua sponte, meaning unprompted by either party.
What the finding does not do
An RDNH declaration is text in a decision. That is the whole of it. The UDRP attaches no damages, no costs, no fee-shifting and no sanction to the finding. The complainant is not barred from filing again, is not fined, and does not compensate the registrant for the cost of defending. The consequence is reputational and precedential: a published decision, on the record, saying the complainant abused the process.
The finding also has no effect on the domain, because by definition the complaint failed and the domain was staying put regardless. RDNH is not a mechanism for getting a name back. Where a domain has already been transferred under an adverse decision, the instrument that matters is the ten-business-day hold at Paragraph 4(k) of the Policy — the period after the provider notifies the registrar during which documented court proceedings filed in the mutual jurisdiction suspend implementation — and, after that, a court.
If you assume the declaration comes with compensation, you are working from the wrong document. It does not.
Where consequences actually live: the Lanham Act
Two United States statutory provisions do carry consequences, and both sit in 15 U.S.C. § 1114(2)(D) rather than in the UDRP.
Subparagraph (v) provides that a domain name registrant whose domain has been suspended, disabled or transferred under a policy of the kind described in the statute may, upon notice to the mark owner, file a civil action to establish that the registration or use of the domain name is not unlawful under the chapter. The court may grant injunctive relief, including reactivation of the domain name or its transfer to the registrant.
Subparagraph (iv) addresses misrepresentation. A registrar that acts on a knowing and material misrepresentation by another person is shielded from liability, and the person who made the misrepresentation is liable for any damages, including costs and attorney's fees, incurred by the domain name registrant.
The division is clean and worth stating plainly: the declaration lives in the UDRP Rules, the money lives in the Lanham Act, and the Lanham Act runs only in United States courts. Whether either provision is available on a given set of facts, and within what limitation period, is a matter for counsel — the subsection's own text sets no deadline.
The URS equivalent: counted, and automatic
Uniform Rapid Suspension handles complainant abuse differently, and more mechanically than the UDRP does. Section 11 of the URS Procedure sets a counted schedule rather than a discretionary declaration: two abusive complaints bring a one-year bar on filing; one deliberate material falsehood brings a one-year bar; and two deliberate material falsehoods bring a permanent bar.
Those counts accumulate across proceedings, which is a meaningfully different exposure from a single reputational finding in a single decision. The URS also runs on a shorter clock throughout — a response due within 14 calendar days of the Notice of Complaint, an appeal within 14 days of a Default or Final Determination, and de novo review available for up to six months after a Default notice, extendable by six more.
The combination of a 500-word cap on explanatory text and a counted penalty for material falsehood rewards precision and punishes the temptation to compress an overstated case into the space available.
How complaints tip into RDNH, and why counsel is required
The recurring complainant-side pattern is a failure of chronology: filing without checking the domain's registration date against the mark's first-use and registration dates, when the third UDRP element requires bad faith at registration. Close behind it is the failed-purchase sequence — approaching the registrant, being refused or quoted a price above expectations, and then filing on the strength of that refusal without a plausible legal basis. Filing on bare allegations with no evidence, and ignoring settled panel positions that dispose of the argument being run, complete the set.
The recurring registrant-side mistake is simpler: default. The response deadline is 20 days from commencement, with an automatic four-day extension available on request, and a panel deciding on the complaint alone has far less material from which to see anything wrong with it. The published decisions bear this out — Securus Technologies, LLC v. Domain Administrator, WIPO Case No. D2021-3383 concerning securus.com, denied the complaint and found reverse domain name hijacking on grounds of the second and third kind described above.
None of this is legal advice, and nothing here characterizes what any party ought to do. It is a description of what the Rules say, what panels have done with them, and where the boundaries sit. Both sides of a UDRP need a trademark attorney experienced in domain disputes: complainants because a badly built pleading can end in a published finding of abuse against them, registrants because the response is the only opportunity to put the record in front of the panel and there is no second one.