What is Reverse Domain Name Hijacking (RDNH)?
Reverse domain name hijacking (RDNH) is a finding by a UDRP panel that a complaint was brought in bad faith – typically to wrest a legitimately held domain from its rightful registrant rather than to remedy genuine cybersquatting.
An RDNH finding is the Policy's formal sanction against complainant abuse. It does not award damages or costs; the remedy is reputational. Panels issue it when the record shows that the complainant knew – or should have known – it could not satisfy one or more of the three UDRP elements yet pressed the complaint forward anyway. The finding is published in the decision and remains permanently searchable in the WIPO and Forum case databases.
This page defines the term precisely, distinguishes it from concepts readers often confuse it with, traces its source in the Policy, and describes the patterns that most reliably attract a finding.
What RDNH is – and what it is not
RDNH is not a separate claim or a counter-complaint. It is a discretionary finding available under the UDRP Rules, entered at the panel's own initiative or on the registrant's request, at the close of the same proceeding in which the complainant sought a transfer. It is equally available in the Nominet DRS for .uk domains, where the procedure expressly recognizes it.
The term readers most commonly confuse RDNH with is cybersquatting – the registrant-side abuse that the UDRP was designed to address. Cybersquatting is the wrongful registration of a domain corresponding to someone else's mark for bad-faith commercial gain. RDNH is the mirror image: it is the complainant's bad faith, not the registrant's. A proceeding can result in a denial of the complaint (the registrant wins) without any RDNH finding, because most denied complaints represent genuine but unsuccessful attempts to satisfy the three elements – not abuse of the process.
A second term sometimes confused with RDNH is reverse trademark hijacking, a concept from trademark law referring to an attempt to cancel a legitimately held mark. The two share a structural logic, but only RDNH lives within UDRP procedure. Confusing the two can lead a registrant to pursue the wrong remedy entirely.
Where RDNH comes from in the UDRP rules
The UDRP Rules define reverse domain name hijacking as "using the Policy in bad faith to attempt to deprive a registered domain-name holder of a domain name." The definition is short. Its application by panels over more than two decades has built a detailed body of practice.
The bad-faith standard for RDNH is assessed from the complainant's conduct, not from the domain's registration history. Panels examine whether the complainant filed despite knowing – or being unable plausibly to argue otherwise – that one or more elements plainly could not be met. Common triggers include: a complainant whose trademark post-dates the domain's registration; a complainant who relied on a mark too descriptive or weak to support a similarity finding; or a complainant whose evidence of bad faith was demonstrably thin while the registrant's record of good-faith use was clear.
Importantly, an RDNH finding is not available simply because the complaint failed. A well-intentioned complaint that misjudges the facts does not necessarily cross the line. The panel must find the complainant went forward in the knowledge, or with constructive knowledge, that it lacked a sustainable case. That distinction matters because it sets a high bar – one that keeps the RDNH finding meaningful rather than routine.
How does RDNH play out in practice?
Three patterns recur in matters we have defended. Each illustrates a different trigger for a finding.
Pattern one: the post-dating problem. A complainant holds a trademark registered years after the domain was acquired by the registrant. The registrant acquired the domain for legitimate reasons – a geographic identifier, a common dictionary word, an abbreviation with obvious generic utility. The complainant files, hoping the panel will treat the mark's fame as sufficient to bridge the chronological gap. Panels regularly decline to do so, and where the post-dating is obvious from the public record, a finding of abuse has consistently followed. The complainant's own evidence establishes the timeline that defeats the complaint.
Pattern two: the weak-mark gamble. A complainant asserts rights in a term that is descriptive or generic – one that a range of parties might legitimately use. The registrant holds the domain for a bona fide business purpose and can point to commercial use predating the complaint. The complainant offers little evidence that the registrant even knew of the mark, let alone targeted it. Panels treat the filing of such a complaint, without more, as an attempt to use the Policy to secure a domain the complainant simply wants rather than one to which it has a legitimate claim. This is the pattern that most often draws a finding when the complainant is a larger entity with counsel who should have recognized the weakness of the claim.
Pattern three: recycled litigation pressure. A complainant who has failed to acquire the domain through negotiation, or who has lost an earlier arbitration, files a fresh complaint on materially the same facts. Panels treat the re-litigation of a previously settled controversy – particularly where no new evidence is offered – as an indicator of bad faith. The UDRP is not a second-chance forum for a complainant who lost a prior round or walked away from a reasonable resolution.
Why RDNH matters to a domain registrant
Receiving a UDRP complaint is alarming. The domain is placed under a registrar lock the moment the case commences, and the registrant has only 20 days to file a response or face a default. A default does not guarantee transfer – the three UDRP elements still apply – but in practice an uncontested complaint filed by a reasonably organized complainant often results in transfer. Filing a well-constructed response is therefore the single most consequential act a registrant can take.
Within that response, raising RDNH is both a substantive argument and a signal to the panel. It asks the panel to evaluate not just whether the complaint is correct but whether it should have been brought at all. A well-supported RDNH submission changes the dynamic: the panel must address the registrant's position on complainant conduct, and a finding in the registrant's favor creates a searchable precedent that follows the complainant into any future proceedings against other registrants.
The reputational effect matters. A published RDNH finding against a brand owner signals to the community – investors, other registrants, future panels – that the entity has used the UDRP as a commercial acquisition tool rather than a rights-protection mechanism. For repeat complainants, a pattern of such findings can itself be evidence of abuse in later cases. There is no monetary penalty, but the public record is permanent.
The AUDIENCE_MYTH worth correcting directly: receiving a complaint does not mean losing the domain. Many registrants assume that a well-resourced complainant, or a big brand name on the other side, makes the outcome a foregone conclusion. It does not. Where the registrant can demonstrate legitimate interest – through use in commerce, a plausible non-mark reason for registration, or a clear timeline that pre-dates the mark – a panel applying the three elements correctly will deny the complaint. And where the complainant's filing was abusive, the registrant can seek something more: the formal finding that the Policy itself was misused against them.
For an assessment of whether your domain dispute warrants a full response or an RDNH submission, contact info@cognomenlaw.com.
Related terms: confusing similarity and the first UDRP element
RDNH most often arises at the intersection of the first and third elements of Paragraph 4(a). The first element – What is Confusing similarity? Definition and meaning – determines whether the domain is identical or confusingly similar to a mark the complainant holds. A complainant with a trademark that is clearly distinct from the domain, or one whose mark post-dates the registration, typically cannot satisfy this threshold. When a panel finds that threshold was plainly unmet from the outset, the RDNH analysis follows naturally.
Understanding the confusing-similarity standard is therefore a precondition for evaluating both the merits of a complaint and the likelihood of an RDNH finding. A mark that differs materially from the domain in all but a generic word, or one that could not have been in the registrant's contemplation at the time of registration, is the profile that most reliably leads to both a denial and a finding of abuse.
COGNOMEN is an independent boutique focused exclusively on domain-name disputes. We recover, defend, and transact internet domains across generic and country-code zones, before WIPO, the Forum, CAC, ADNDRC, and national procedures, and in court where arbitration cannot reach. We act for brand owners, domain investors, and registrants – including respondent-side defense and reverse domain name hijacking. COGNOMEN focuses only on domain-name disputes – recovery, defense, and transactions. To discuss a domain dispute or an RDNH submission, contact info@cognomenlaw.com.
Related at COGNOMEN
Frequently asked questions
What is reverse domain name hijacking (rdnh)?
Reverse domain name hijacking is a formal UDRP panel finding that a complaint was filed in bad faith – meaning the complainant sought to use the Policy to take a legitimately held domain rather than to remedy genuine cybersquatting. It is a reputational sanction only; no monetary penalty attaches. The finding is published and permanently searchable in the case database.
How is reverse domain name hijacking (rdnh) proven or established?
A panel may find RDNH on its own initiative or on the registrant's request. The registrant must show that the complainant knew, or could not plausibly have believed otherwise, that at least one of the three UDRP elements was plainly absent – for example, because the mark post-dates the domain's registration, the mark is too weak to support a claim, or the registrant's good-faith use was obvious from public records before the complaint was filed.
Why does reverse domain name hijacking (rdnh) matter to my domain?
If you receive a UDRP complaint against a domain you hold legitimately, raising RDNH in your response serves two purposes. First, it asks the panel to scrutinize complainant conduct and deny the complaint on abuse grounds as well as on the merits. Second, a published finding follows the complainant permanently, deterring future abusive filings and creating precedent that may protect other registrants from the same complainant.
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
This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.