The domain LionsHead.com was lost via the UDRP process, as the Respondent did not file a response to counter the Complainant’s allegations.
Registered in 2002, LionsHead.com has been in the possession of a domain portfolio holder. The Complainant, Lionshead Specialty Tire & Wheel LLC, have registered the mark LIONSHEAD with the USPTO. That registration took place in 2021, a full 19 years after the domain was registered!
The sole panelist at the Forum (NAF,) Charles A. Kuechenmeister, supported the Complainant’s claim that the domain is not being used:
Complaint Exhibit B is a screenshot of the web page resolving from the Domain Name. It is a blank page containing only the name ”Lions Head.” This is not an active use of the Domain Name. As such it is neither a bona fide offering of goods or services as contemplated by Policy ¶ 4(c)(i) nor a legitimate noncommercial or fair use as contemplated by Policy ¶ 4(c)(iii).
Unfortunately, this UDRP decision demonstrates the potential loss that a Respondent can incur if they fail to respond via a qualified counsel.
Final decision: Transfer the domain LionsHead.com to the Complainant.
Copyright © 2024 DomainGang.com · All Rights Reserved.Lionshead Specialty Tire & Wheel, LLC v. Domain Vault / Domain Vault LLC
Claim Number: FA2202001984051
PARTIES
Complainant is Lionshead Specialty Tire & Wheel, LLC (“Complainant”), represented by Daniel Tychonievich of Krieg DeVault LLP, Indiana, USA. Respondent is Domain Vault / Domain Vault LLC (“Respondent”), Colorado, USA.
REGISTRAR AND DISPUTED DOMAIN NAME
The domain name at issue is , registered with Name.com, Inc.
PANEL
The undersigned certifies that he has acted independently and impartially and to the best of his knowledge has no known conflict in serving as Panelist in this proceeding.
Charles A. Kuechenmeister, Panelist.
PROCEDURAL HISTORY
Complainant submitted a Complaint to the Forum electronically on February 11, 2022; the Forum received payment on February 11, 2022.
On February 15, 2022, Name.com, Inc. confirmed by e-mail to the Forum that the domain name (the Domain Name) is registered with Name.com, Inc. and that Respondent is the current registrant of the name. Name.com, Inc. has verified that Respondent is bound by the Name.com, Inc. registration agreement and has thereby agreed to resolve domain disputes brought by third parties in accordance with ICANN’s Uniform Domain Name Dispute Resolution Policy (the “Policy”).
On February 17, 2022, the Forum served the Complaint and all Annexes, including a Written Notice of the Complaint setting a deadline of March 9, 2022 by which Respondent could file a Response to the Complaint, via e-mail to all entities and persons listed on Respondent’s registration as technical, administrative, and billing contacts, and to postmaster@lionshead.com. Also on February 17, 2022, the Written Notice of the Complaint, notifying Respondent of the e-mail addresses served and the deadline for a Response, was transmitted to Respondent via post and fax to all entities and persons listed on Respondent’s registration as technical, administrative and billing contacts.
Having received no Response from Respondent, the Forum transmitted to the parties a Notification of Respondent Default.
On March 15, 2022, pursuant to Complainant’s request to have the dispute decided by a single-member Panel, the Forum appointed Charles A. Kuechenmeister as Panelist.
Having reviewed the communications records, the Administrative Panel (the “Panel”) finds that the Forum has discharged its responsibility under Paragraph 2(a) of the Rules for Uniform Domain Name Dispute Resolution Policy (the “Rules”) “to employ reasonably available means calculated to achieve actual notice to Respondent” through submission of Electronic and Written Notices, as defined in Rule 1 and Rule 2. Therefore, the Panel may issue its decision based on the documents submitted and in accordance with the ICANN Policy, ICANN Rules, the Forum’s Supplemental Rules and any rules and principles of law that the Panel deems applicable, without the benefit of a Response from Respondent.
RELIEF SOUGHT
Complainant requests that the Domain Name be transferred from Respondent to Complainant.
PARTIES’ CONTENTIONS
A. Complainant
Complainant has rights in the LIONSHEAD mark through its registration of the mark with the United States Patent and Trademark Office (“USPTO”). Respondent’s Domain Name is confusingly similar to Complainant’s LIONSHEAD mark. It incorporates the mark in its entirety and adds the “.com” generic top-level domain (“gTLD”).
Respondent has no rights or legitimate interests in the Domain Name, as it resolves to a generic, parked webpage.
Respondent registered and used the domain name in bad faith. It fails to make any active use of the Domain Name.
B. Respondent
Respondent did not submit a Response in this proceeding.
FINDINGS
Paragraph 15(a) of the Rules instructs this Panel to “decide a complaint on the basis of the statements and documents submitted in accordance with the Policy, these Rules and any rules and principles of law that it deems applicable.”
Paragraph 4(a) of the Policy requires a complainant to prove each of the following three elements to obtain an order cancelling or transferring a domain name:
(1) the domain name registered by the respondent is identical or confusingly similar to a trademark or service mark in which the complainant has rights; and
(2) the respondent has no rights or legitimate interests in respect of the domain name; and
(3) the domain name has been registered and is being used in bad faith.
In view of Respondent’s failure to submit a Response, pursuant to paragraphs 5(f), 14(a) and 15(a) of the Rules the Panel will decide this administrative proceeding on the basis of Complainant’s undisputed representations and draw such inferences it considers appropriate pursuant to paragraph 14(b) of the Rules. The Panel is entitled to accept all reasonable allegations set forth in a complaint. Nevertheless, the Panel may deny relief where a complaint contains mere conclusory or unsubstantiated arguments. eGalaxy Multimedia Inc. v. ON HOLD By Owner Ready To Expire, FA 157287 (Forum June 26, 2003) (“Because Complainant did not produce clear evidence to support its subjective allegations [. . .] the Panel finds it appropriate to dismiss the Complaint”), WIPO Overview of WIPO Panel Views on Selected UDRP Questions, Third Edition (WIPO Overview 3.0), at ¶ 4.3 (“In cases involving wholly unsupported and conclusory allegations advanced by the complainant, . . . panels may find that—despite a respondent’s default—a complainant has failed to prove its case.”).
The Panel finds as follows with respect to the matters at issue in this proceeding:
Identical and/or Confusingly Similar
The LIONSHEAD mark was registered to Complainant with the USPTO (Reg. No. 6,534,553) on October 26, 2021 (USPTO registration certificate submitted as Complaint Annex A). Complainant’s registration of its mark with the USPTO establishes its rights in that mark for the purposes of Policy ¶ 4(a)(i). BGK Trademark Holdings, LLC & Beyoncé Giselle Knowles-Carter v. Chanphut / Beyonce Shop, FA 1626334 (Forum Aug. 3, 2015) (Complainant’s registration with the USPTO (or any other governmental authority) adequately proves its rights under Policy ¶ 4(a)(i)).
Respondent’s Domain Name is confusingly similar to Complainant’s LIONSHEAD mark. It incorporates the mark in its entirety, merely adding the “.com” gTLD. This change does not distinguish the Domain Name from Complainant’s mark for the purposes of Policy ¶ 4(a)(i). MTD Products Inc v. Mike Kernea / Skyline, FA 1775278 (Forum Apr. 19, 2018) (“The mere addition of a gTLD is inconsequential and does not avoid a finding of identity.”). Dell Inc. v. Protection of Private Person / Privacy Protection, FA 1681432 (Forum Aug. 1, 2016) (“A TLD (whether a gTLD, sTLD or ccTLD) is disregarded under a Policy ¶ 4(a)(i) analysis because domain name syntax requires TLDs. Likewise, the absence of spaces must be disregarded under a Policy ¶ 4(a)(i) analysis because domain name syntax prohibits them.”). The WIPO Overview 3.0, at ¶ 1.7, states that the test for confusing similarity “typically involves a side-by-side comparison of the domain name and the relevant trademark to assess whether the mark is recognizable within the domain name.” Notwithstanding the changes described above, Complainant’s mark is clearly recognizable within the Domain Name.
For the reasons set forth above, the Panel finds that the Domain Name is identical or confusingly similar to the LIONSHEAD mark, in which Complainant has rights.
Rights or Legitimate Interests
If a complainant makes a prima facie case that the respondent lacks rights or legitimate interests in the domain name under Policy ¶ 4(a)(ii), the burden of production shifts to respondent to come forward with evidence that it has rights or legitimate interests in it. Neal & Massey Holdings Limited v. Gregory Ricks, FA 1549327 (Forum Apr. 12, 2014) (“Under Policy ¶ 4(a)(ii), Complainant must first make out a prima facie case showing that Respondent lacks rights and legitimate interests in respect of an at-issue domain name and then the burden, in effect, shifts to Respondent to come forward with evidence of its rights or legitimate interests”). If a respondent fails to come forward with such evidence, the complainant’s prima facie evidence will be sufficient to establish that respondent lacks such rights or legitimate interests. If the respondent does come forward with such evidence, the Panel must assess the evidence in its entirety. At all times, the burden of proof remains on the complainant. WIPO Overview 3.0, at ¶ 2.1.
Policy ¶ 4(c) lists the following three nonexclusive circumstances, any one of which if proven can demonstrate a respondent’s rights or legitimate interests in a domain name for the purposes of Policy ¶ 4(a)(ii):
(i) Before any notice to the respondent of the dispute, the respondent’s use of, or demonstrable preparations to use, the domain name or a name corresponding to the domain name in connection with a bona fide offering of goods or services;
(ii) The respondent (as an individual, business or other organization) has been commonly known by the domain name, even if the respondent has acquired no trademark or service mark rights; or
(iii) The respondent is making a legitimate noncommercial or fair use of the domain name, without intent for commercial gain to misleadingly divert consumers or to tarnish the trademark or service mark at issue.
Complainant asserts that Respondent has no rights or legitimate interests in the Domain Name, as it is not using the Domain Name in connection with a bona fide offering of goods or services or for a legitimate non-commercial or fair use. It resolves to an inactive web site. This allegation is addressed as follows:
Complaint Exhibit B is a screenshot of the web page resolving from the Domain Name. It is a blank page containing only the name ”Lions Head.” This is not an active use of the Domain Name. As such it is neither a bona fide offering of goods or services as contemplated by Policy ¶ 4(c)(i) nor a legitimate noncommercial or fair use as contemplated by Policy ¶ 4(c)(iii). Morgan Stanley v. Francis Mccarthy / Baltec Marine Llc, FA 1785347 (Forum June 8, 2018) (“both Domain Names resolve to a web site that shows the words, ‘Not Found, The requested URL / was not found on this server.’ ’ Inactive holding of a domain name does not qualify as a bona fide offering of goods or services within the meaning of Policy ¶ 4(c)(i), or a legitimate non-commercial or fair use within the meaning of Policy ¶ 4(c)(iii).”), 3M Company v. Kabir S Rawat, FA 1725052 (Forum May 9, 2017) (holding that “a general offer for sale… provides additional evidence that Respondent lacks rights and legitimate interests” in a disputed domain name).
Complainant did not address the Policy 4(c)(ii) issue, but the WHOIS information furnished to the Forum by the registrar lists “Domain Vault / Domain Vault LLC” as the registrant of the Domain Name. Neither of these names bears any resemblance to the Domain Name. Evidence could, of course, in a given case demonstrate that the respondent is commonly known by a domain name different from the name in which it registered the domain name, e.g., the case of a domain name incorporating the brand name of a specific product offered by and associated with the respondent. In the absence of any such evidence, however, and in cases where no Response has been filed, UDRP panels have consistently held that WHOIS evidence of a registrant name which does not correspond with the domain name is sufficient to prove that the respondent is not commonly known by the domain name. Amazon Technologies, Inc. v. Suzen Khan / Nancy Jain / Andrew Stanzy, FA 1741129 (Forum Aug. 16, 2017) (finding that respondent had no rights or legitimate interests in the disputed domain names when the identifying information provided by WHOIS was unrelated to the domain names or respondent’s use of the same), Alaska Air Group, Inc. and its subsidiary, Alaska Airlines v. Song Bin, FA1408001574905 (Forum Sept. 17, 2014) (holding that the respondent was not commonly known by the disputed domain name as demonstrated by the WHOIS information and based on the fact that the complainant had not licensed or authorized the respondent to use its ALASKA AIRLINES mark). The Panel is satisfied that Respondent has not been commonly known by the Domain Name for the purposes of Policy ¶ 4(c)(ii).
The evidence furnished by Complainant establishes the required prima facie case. On that evidence, and in the absence of any evidence from Respondent, the Panel finds that Respondent has no rights or legitimate interests in the Domain Name.
Registration and Use in Bad Faith
Policy ¶ 4(b) sets forth a nonexclusive list of four circumstances, any one of which if proven would be evidence of bad faith use and registration of a domain name. They are as follows:
(i) circumstances indicating that the respondent has registered or acquired the domain name primarily for the purpose of selling, renting, or otherwise transferring the domain name registration to the complainant which is the owner of the trademark or service mark or to a competitor of that complainant, for valuable consideration in excess of the respondent’s documented out-of-pocket costs directly related to the domain name; or
(ii) the respondent has registered the domain name in order to prevent the owner of the trademark or service mark from reflecting the mark in a corresponding domain name, provided that the respondent has engaged in a pattern of such conduct; or
(iii) the respondent has registered the domain name primarily for the purpose of disrupting the business of a competitor; or
(iv) by using the domain name, the respondent has intentionally attempted to attract, for commercial gain, Internet users to the respondent’s web site or other on-line location, by creating a likelihood of confusion with the complainant’s mark as to the source, sponsorship, affiliation or endorsement of the respondent’s web site or location or of a product of service on the respondent‘s web site or location.
The evidence of Respondent’s conduct discussed above in the rights or legitimate interests analysis also supports a finding of bad faith registration and use. As discussed above, the Domain Name resolves to an inactive web site. Passive holding of a domain name is evidence of bad faith. This may not fit within any of the circumstances described in Policy ¶ 4(b) but that paragraph recognizes that mischief can assume many different forms and takes an open-ended approach to bad faith, listing some examples without attempting to enumerate all its varieties. Worldcom Exchange, Inc. v. Wei.com, Inc., WIPO Case No. D-2004-0955 (January 5, 2005), Bloomberg Finance L.P. v. Domain Admin – This Domain is For Sale on GoDaddy.com / Trnames Premium Name Services, FA 1714157 (Forum Mar. 8, 2017) (determining that Policy ¶ 4(b) provisions are merely illustrative of bad faith, and that the respondent’s bad faith may be demonstrated by other allegations of bad faith under the totality of the circumstances). Given the non-exclusive nature of Policy ¶ 4(b), failure to make active use of a confusingly similar domain name is evidence of bad faith. Caravan Club v. Mrgsale, FA 95314 (Forum Aug. 30, 2000) (finding that the respondent made no use of the domain name or website that connects with the domain name, and that [failure to make an active use] of a domain name permits an inference of registration and use in bad faith).
DECISION
Complainant having established all three elements required under the ICANN Policy, the Panel concludes that relief shall be GRANTED.
Accordingly, it is Ordered that the Domain Name be TRANSFERRED from Respondent to Complainant.
Charles A. Kuechenmeister, Panelist
Dated: March 17, 2022
The domain owner may have been instructed to just let this particular UDRP panelist hang himself and the Complainant. The moment the domain was placed on a UDRP hold, the Lanham Act gave rise to $100,000+ liability. This Panelist, Kuchenmeister, is over 80yo. People that age aren’t aware that prior to market competition for dotcoms, a chore borne by speculators, the web was an unusable sea of porn mousetraps and fraud spoofs. Study up or stand down.
The ACPA “entitles a proper domain name owner to obtain from a trademark owner up to $100,000 in damages, plus attorneys’ fees, when the purported trademark owner improperly attempts to obtain a domain name rightfully owned by someone else. Being deemed a RDNH also puts a trademark registration in jeopardy of being canceled due to the bad faith. One fact pattern that regularly leads to a party being deemed a RDNH is when one party acquires the domain name before the complaining party adopts the trademark; if the complaining party’s trademark did not first exist, then the domain name owner could not have taken the domain name in bad faith.”