Jump to content

Reverse domain hijacking

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by The Eloquent Peasant (talk | contribs) at 17:26, 24 September 2023 (→top: WP:SHORTDESC). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Reverse domain name hijacking (also known as reverse cybersquatting or commonly abbreviated as 'RDNH'), occurs where a rightful trademark owner attempts to secure a domain name by making cybersquatting claims against a domain name’s "cybersquatter" owner.[1] This often intimidates domain name owners into transferring ownership of their domain names to trademark owners to avoid legal action, particularly when the domain names belong to smaller organizations or individuals.[2] Reverse domain name hijacking is most commonly enacted by larger corporations and famous individuals, in defense of their rightful trademark or to prevent libel or slander.[3]

Reverse domain name "hijacking" is a legal remedy to counter the practice of domain squatting, wherein individuals hold many registered domain names containing famous third party trademarks with the intent of profiting by selling the domain names back to trademark owners.[4] Trademark owners initially responded by filing cybersquatting lawsuits against registrants to enforce their trademark rights.[5] However, as the number of cybersquatting incidents grew, trademark owners noticed that registrants would often settle their cases rather than litigate.[6] Cybersquatting lawsuits are a defensive strategy to combat cybersquatting, however such lawsuits may also be used as a way of strongarming innocent domain name registrants into giving up domain names that the trademark owner is not, in fact, entitled to.[7][8]

UDRP restrictions on reverse domain name hijacking

Paragraph 15(e) of the UDRP Rules defines reverse domain name hijacking as the filing of a complaint in bad faith, resulting in the abuse of the UDRP administrative process.[9] It becomes difficult to objectively quantify what constitutes subjective “bad faith,” resulting in panels often viewing parties’ factual discrepancies as indeterminable or immaterial at best.[10] Therefore, despite its express recognition in the UDRP, reverse domain name hijacking findings are rare and based heavily on the factual circumstances surrounding each case.[11]

Circumstances which have been cited by WIPO panels as justification for a finding of reverse domain name hijacking includes:

  • When the registration of the domain predates any trademark rights of the Complainant.
  • When the complaint has provided no evidence of bad faith registration or use directed towards the Complainant.
  • Where the Complainant has used the UDRP as a Plan "B" option to attempt to secure the domain after commercial negotiations have broken off.
  • Where the Complainant has attempted to deceive the domain owner or makes misrepresentations or fails to disclose material information to the panel.

Examples of such findings include the following WIPO cases: Gregory Ricks vs. RVK, Inc. (Formally RVKuhns and Associates) (2015). RVK,Inc. has also recently been accused of failure to promptly report a significant breach of its network, which resulted in fraud against the Central Bank of Chile. Scott Gratsinger is in charge of network security and was also involved in the reverse domain hijacking scheme. Ron Paul vs. RonPaul.org[12] (2013), Webpass, Inc. v. Paul Breitenbach[13] (2010), Urban Logic, Inc. v. Urban Logic, Peter Holland (2009), David Robinson v. Brendan (2008), Decal v. Gregory Ricks (2008), Hero v. The Heroic Sandwich[14] (2008), Poker Host Inc. v. Russ “Dutch” Boyd (2008), FCC Fomento de Construcciones y Contratas v “FCC.COM” (2007), Liquid Nutrition v. liquidnutrition.com (2007), Rohl, LLC v. ROHL SA (2006), Her Majesty the Queen (Elizabeth II) v. Virtual Countries, Inc.,[15] and Deutsche Welle v. DiamondWare[16] (2000). A list of over one hundred reverse domain name hijacking decisions is available at rdnh.com.[17]

Although UDRP panelists currently have no tools by which to punish abuses such as Reverse Domain Name Hijacking, such a finding might be used in a local jurisdiction where such abuses might constitute a tort such as tortious interference with contract or an unfair business practice.[18]

ACPA restrictions on reverse domain name hijacking

The Anticybersquatting Consumer Protection Act does not expressly recognize reverse domain name hijacking and often only limits defendants’ recovery to retention or transference of the domain name.[19] It also fails to provide any remedies for victims of attempted reverse cybersquatting.[20] However, the statute permits some monetary relief where bad faith, reckless disregard or the willful violation of a court order are involved.[21]

Similarly, a 1975 amendment to the Lanham Act gives courts discretion in awarding reasonable attorneys’ fees to a prevailing party in “exceptional” circumstances.[22] In attempting to define “exceptional,” Circuit courts are split as to what objectively constitutes malicious, fraudulent, or deliberate misconduct.[23] Some courts award such fees where bad faith or baseless litigation is involved while other courts look for economic coercion or failure to reference controlling law.[24] Nevertheless, due to the inherent animosity arising from being sued, courts generally hold prevailing defendants to a higher level of scrutiny, requiring vexatious or harassing conduct to shift attorney’s fees in their favor.

Implications

Neither the UDRP nor the ACPA provides much deterrent to curb trademark owners’ abuse of their rights.[25] To abate reverse domain name hijacking practices, some legal professionals believe Congress should enact laws that are specifically designed to facilitate litigation against reverse cybersquatters.[26] Similarly, some advocates argue for stronger penalties to deter the unlawful deprivation of validly registered domain names,[27] such as fines and precluding offending trademark owners from filing cybersquatting claims for a designated period of time.[28]

References

  1. ^ Sallen v. Corinthians Licenciamentos Ltda., 2002 U.S. Dist. LEXIS 19976 (D. Mass. Dec. 19, 2000), rev’d, 273 F.3d 14, 17 (1st Cir. 2001) [hereinafter Sallen].
  2. ^ Warren B. Chik, Lord of Your Domain, But Master of None: The Need to Harmonize and Recalibrate the Domain Name Regime of Ownership and Control, 16 INT’L J.L. & INFO. TECH. 8, 60 (2008) [hereinafter Chik].
  3. ^ Id.
  4. ^ Sallen, supra note 1.
  5. ^ Id.
  6. ^ Id.
  7. ^ Schmidheiny v. Weber, 164 F.Supp.2d 484, 487 (E.D. Pa. 2001).
  8. ^ Fridman, David. "Domain Hijacking and the Risks it Poses to your Brand". BrandShield. Retrieved 22 October 2014. The smaller rightful domain owners are often intimidated by legal action and much of the time give up the rights to that domain.
  9. ^ Id.
  10. ^ Id.
  11. ^ Int'l Driver Training, Inc. v. Web Integrations, LLC and Comedy Driving Inc., D2009-0129 (WIPO Arbitration and Mediation Center, Apr. 9, 2009).
  12. ^ "WIPO Domain Name Decision: D2013-0371".
  13. ^ "WIPO Domain Name Decision: D2010-1796".
  14. ^ "WIPO Domain Name Decision: D2008-0779".
  15. ^ "New Zealand v. Virtual Countries, Inc". Retrieved 22 October 2014.
  16. ^ "WIPO Domain Name Decision: D2000-1202".
  17. ^ "Home". rdnh.com.
  18. ^ Doug Isenberg (19 October 2016). "What is 'Reverse Domain Name Hijacking'?". Retrieved 17 December 2018.
  19. ^ Anticybersquatting Consumer Protection Act, 15 U.S.C. 1125(d)(2) (2006).
  20. ^ Frayne v. Chicago 2016, 2009 WL 65236 *2 (N.D. Ill. 2009); General Media Comm., Inc. v. Crazy Troll, LLC, 2007 WL 102988 (S.D.N.Y. 2007).
  21. ^ Id. at 1125(d)(2)(ii).
  22. ^ Christopher P. Bussert, Interpreting the “Exceptional Cases” Provision of Section 117(a) of the Lanham Act: When an Award of Attorney’s Fees is Appropriate, 92 TRADEMARK REP. 1118, 1118-19 (2002).
  23. ^ S. Rep. No. 93-1440, at 5 (1974), reprinted in 1974 U.S.C.C.A.N. 7132, 7136.
  24. ^ Anne M. Mellen, Awarding Attorneys’ Fees Under the Lanham Act: Egregious Litigation Conduct in the “Exceptional” Case, 74 U. CIN. L. REV. 1111, 1117 (2006).
  25. ^ Lewis, Brett. "Reverse Domain Hijacking: Extreme Makeover". DNJournal. Retrieved 22 October 2014.
  26. ^ Chik, supra note 2 at 60.
  27. ^ Id.
  28. ^ Id.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Reverse_domain_hijacking&oldid=1176893635"