Reverse Domain Name Hijacking (RDNH)
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://tldfyi.com/iframe/glossary/reverse-domain-hijacking/" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>
Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://tldfyi.com/glossary/reverse-domain-hijacking/
Add a dynamic SVG badge to your README or docs.
[](https://tldfyi.com/glossary/reverse-domain-hijacking/)
Use the native HTML custom element.
Reverse Domain Name Hijacking (RDNH) occurs when a trademark owner files a [[udrp]] complaint in bad faith, attempting to deprive a legitimate domain owner of their registration. [[icann]] policy requires [[udrp]] panels to declare RDNH when a complainant knew it could not succeed on the merits — for example, because the [[registrant]] registered the domain before the trademark existed, or because the complainant's trademark rights are weak or generic. An RDNH finding carries no direct financial penalty but is a formal public rebuke that may deter future abusive complaints and is often cited in subsequent proceedings against the same complainant.
Example
A startup that had owned 'nova.com' since 1998 successfully obtained an RDNH ruling after a corporation filed a UDRP complaint based on a trademark registered in 2005.