RDNH Finding in ALO.com UDRP

A three member WIPO UDRP panel ruled in favor of the domain owner in the ALO.com UDRP. In addition, the panel ruled that Reverse Domain Name Hijacking (RDNH) occurred. The domain name owner was represented by ESQWire.com (Jason Schaeffer and Ari Goldberger), and this is the second case in the last couple of weeks for the law firm where a finding of RDNH was made.

This seems like a pretty cut and dry UDRP decision. It doesn’t really make sense that a complainant can win a UDRP when the domain name has been owned longer than the trademark of the company filing the UDRP even existed. In its argument, the complainant cited the “Octogen Case,” which was just discussed in a sponsored post the Internet Commerce Association wrote published on CircleID. Putting the theory of “retroactive bad faith” to rest is important for domain name investors.

I think there are several aspects of the UDRP decision that stand out for domain investor rights, and I want to highlight a few of them.

From the “Rights or Legitimate Interests” section of the decision:

“However, it is relevant to note that (i) the disputed domain name was registered several years before the Complainant’s filing of its trademark in the United States; (ii) the disputed domain name is constituted by a three-letter term which, as such, has an inherent value, as it may have a number of meanings and is used extensively by third parties as an acronym or a generic term; (iii) the disputed domain name has been pointed to a website displaying generic sponsored links that made no reference to the Complainant, its trademark and products; and (iv) the Respondent has demonstrated that it has engaged in the registration of several domain names incorporating common three-letter combinations that it hosts with domain name parking services, thus showing that its registration and use of the disputed domain name is consistent with its business model.”

Here’s why the panel found that this was a case of Reverse Domain Name Hijacking:

“In light of the circumstances of the case, the Panel makes a finding of Reverse Domain Name Hijacking since the Complainant ought to have known that it could not succeed under any fair interpretation of facts reasonably available prior to the filing of the Complaint, as the disputed domain name was registered several years before the Complainant’s existence and there is no evidence of the Respondent’s use of the disputed domain name in connection with the Complainant’s trademark.”

All in all, I think this was a good UDRP decision.

Elliot Silver
Elliot Silver
About The Author: Elliot Silver is an Internet entrepreneur and publisher of DomainInvesting.com. Elliot is also the founder and President of Top Notch Domains, LLC, a company that has closed eight figures in deals. Please read the DomainInvesting.com Terms of Use page for additional information about the publisher, website comment policy, disclosures, and conflicts of interest. Reach out to Elliot: Twitter | Facebook | LinkedIn

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Recent Posts

Spaceship SellerHub to Launch for All on April 29

2
Last week, Spaceship's new SellerHub opened for third party beta testing. Participants were limited to larger portfolio operators. Yesterday, CEO Richard Kirkendall announced the...

Atom.com Brings Expert Review Process in House

1
For as long as I’ve known the platform, Atom.com has relied on an “Expert Review Process” to evaluate domain names submitted by prospective sellers....

Google Change Should Reinforce .com Dominance

2
Google has operated its search engine on many different domain names. Of course, Google.com is the company’s primary domain name and the one that...

Don’t Delay Registering Trending Domain Names

4
I regularly see people discuss the possibility of domain registrar front running. In fact, I've written about this topic before. By and large, I...

ICA Webinar on Transfer Lock Changes

4
Transfer lock policies can differ at each domain registrar. Depending on the situation and domain name status, some locks are required by ICANN and...