Twitter, Inc. v. sad asdaa
Claim Number: FA2204001991695
Complainant is Twitter, Inc. (“Complainant”), represented by James F. Struthers of Richard Law Group, Inc., Texas, USA. Respondent is sad asdaa (“Respondent”), Turkey.
REGISTRAR AND DISPUTED DOMAIN NAME
The domain name at issue is <twitter-verification.com>, registered with Google LLC.
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.
Richard Hill as Panelist.
Complainant submitted a Complaint to the Forum electronically on April 8, 2022; the Forum received payment on April 8, 2022. The Complaint was received in English.
On April 10, 2022, Google LLC confirmed by e-mail to the Forum that the <twitter-verification.com> domain name is registered with Google LLC and that Respondent is the current registrant of the name. Google LLC has verified that Respondent is bound by the Google LLC 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 April 12, 2022, the Forum served the English language Complaint and all Annexes, including a Turkish and English language Written Notice of the Complaint, setting a deadline of May 2, 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@twitter-verification.com. Also on April 12, 2022, the Turkish and English language 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 May 6, 2022, pursuant to Complainant's request to have the dispute decided by a single-member Panel, the Forum appointed Richard Hill 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 any response from Respondent.
Complainant requests that the domain name be transferred from Respondent to Complainant.
Preliminary Issue: Language of Proceeding
Prior to discussing the three elements of the Policy, the Panel must decide on the language of the proceedings. The Registration Agreement is written in Turkish, thereby making the language of the proceedings Turkish.
Pursuant to UDRP Rule 11(a), the Panel has the authority to determine a different language for the proceedings, having regard to the circumstances of the case. It is established practice to take UDRP Rules 10(b) and (c) into consideration for the purpose of determining the language of the proceeding to ensure fairness and justice to both parties. Pursuant to Rule 10(b), Respondent must be given a fair opportunity to present its case. Pursuant to Rule 10(c), the Panel may weigh the relative time and expense in enforcing the Turkish language agreement, which would result in prejudice toward either party. See Finter Bank Zurich v. Shumin Peng, D2006-0432 (WIPO June 12, 2006) (deciding that the proceeding should be in English, stating, “It is important that the language finally decided by the Panel for the proceeding is not prejudicial to either one of the parties in his or her ability to articulate the arguments for the case.”).
In the present case, Respondent has received the Notice of Complaint and Commencement Notification in Turkish and has chosen not to respond to the Complaint. The disputed domain name contains the English word “verification” and the fraudulent phishing emails sent by Respondent are in English, thus Respondent is conversant in English. Pursuant to Rule 11(a), having regard to the circumstances of the case, the Panel determines that fairness and justice to both parties, and due expedition, are best satisfied by conducting the remainder of the proceedings in English. See H-D U.S.A., LLC v. Yoshihiro Nakazawa, FA 1736477 (Forum July 21, 2017); see also UBS AG v. ratzel laura, FA 1735687 (Forum July 14, 2017).
A. Complainant
Complainant states that it operates a real-time global information network that allows the public to discover what is happening in the world and what people are talking about, share information and news, and connect to anyone, anywhere in real time. The Twitter service allows users to consume, create, distribute, and discover content via short messages popularly known as “Tweets.” Each Tweet can contain text and rich media, including pictures, videos, and applications. The Twitter service can be accessed at <twitter.com> and on a variety of mobile devices. As of October 2021, Twitter had more than 200 million daily active users. According to Alexa, <twitter.com> website traffic ranks in the top 20 for the US and globally. Complainant has rights in the TWITTER mark based on its registration of the mark in the United States in 2009. The mark is registered elsewhere around the world and it is famous.
Complainant alleges that the disputed domain name is confusingly similar to its TWITTER mark as it incorporates in the entire mark and simply adds a hyphen, the term “verification,” and the “.com” generic top level domain (“gTLD”). Complainant cites UDRP precedents to support its position.
According to Complainant, Respondent does not have rights or legitimate interests in the disputed domain name. Respondent is not commonly known by the disputed domain name and Complainant has not licensed nor authorized Respondent to use the TWITTER mark. Additionally, Respondent does not use the disputed domain for any bona fide offering of goods or services or legitimate noncommercial or fair use as Respondent uses the disputed domain name to pass off as Complainant and phish for users’ information via email. Complainant cites UDRP precedents to support its position.
Further, says Complainant, Respondent registered and uses the disputed domain name in bad faith. Respondent uses the disputed domain name to pass off as Complainant and phish for users’ information via email. Additionally, Respondent had actual knowledge of Complainant’s rights in the TWITTER mark based on the fame of the mark and Respondent’s efforts to pass off as Complainant in fraudulent emails. Complainant cites UDRP precedents to support its position.
B. Respondent
Respondent failed to submit a Response in this proceeding.
Complainant owns the mark TWITTER and uses it to operate a social networking service. The mark is famous.
Complainant’s rights in its mark date back to at least 2009.
The disputed domain name was registered in 2022.
Complainant has not licensed or otherwise authorized Respondent to use its mark.
Respondent uses the disputed domain name in furtherance of an email phishing scheme; the fraudulent emails display Complainant’s famous mark.
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 that Complainant must prove each of the following three elements to obtain an order that a domain name should be cancelled or transferred:
(1) the domain name registered by Respondent is identical or confusingly similar to a trademark or service mark in which Complainant has rights; and
(2) 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, the Panel shall decide this administrative proceeding on the basis of Complainant's undisputed representations pursuant to paragraphs 5(f), 14(a) and 15(a) of the Rules 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; however, the Panel may deny relief where a complaint contains mere conclusory or unsubstantiated arguments. See WIPO Jurisprudential Overview 3.0 at ¶ 4.3; see also 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”).
The disputed domain name incorporates Complainant’s TWITTER mark in its entirety and merely adds a hyphen, the generic term “verification,” and the “.com” gTLD. The addition of a hyphen, generic term, and gTLD to a mark may not sufficiently distinguish the disputed domain name from the mark it incorporates under Policy ¶ 4(a)(i). See Skechers U.S.A., Inc. and Skechers U.S.A., Inc. II v. Svensson Viljae, FA 1784650 (Forum June 1, 2018) (finding confusing similarity where “[t]he disputed domain name <skechers-outlet.com> adds a hyphen and the generic term ‘outlet’ to Complainant's registered SKECHERS mark, and appends the ‘.com’ top-level domain.”); see also Bloomberg Finance L.P. v. Nexperian Holding Limited, FA 1782013 (Forum June 4, 2018) (“Where a relevant trademark is recognisable within a disputed domain name, the addition of other terms (whether descriptive, geographical, pejorative, meaningless, or otherwise) does not prevent a finding of confusing similarity under the first element.”). Thus the Panel finds that the <twitter-verification.com> domain name is confusingly similar to Complainant’s TWITTER mark under Policy ¶ 4(a)(i).
Complainant has not licensed or otherwise authorized Respondent to use its TWITTER mark. Respondent is not commonly known by the disputed domain name: when no response is submitted, WHOIS information can be used to show that a respondent is not commonly known by the disputed domain name under Policy ¶ 4(c)(ii). See State Farm Mutual Automobile Insurance Company v. Dale Anderson, FA1504001613011 (Forum May 21, 2015) (concluding that because the WHOIS record lists “Dale Anderson” as the registrant of the disputed domain name, the respondent was not commonly known by the <statefarmforum.com> domain name pursuant to Policy ¶ 4(c)(ii)). Here, the WHOIS information identifies “sad asdaa” as the registrant. Thus the Panel finds that Respondent is not commonly known by the domain name under Policy ¶ 4(c)(ii).
Respondent uses the disputed domain name in emails to pass off as Complainant and phish for users’ information. Use of a disputed domain name to pass off as a complainant in emails as part of a phishing scheme does not constitute a bona fide offering of goods or services or legitimate noncommercial or fair use. See Microsoft Corporation v. Terrence Green / Whois Agent / Whois Privacy Protection Service, Inc., FA 1661030 (Forum Apr. 4, 2016) (finding the respondent’s use of the disputed domain names to send fraudulent emails purportedly from agents of complainant to be neither a bona fide offering of goods or services under Policy ¶ 4(c)(i), nor a legitimate noncommercial or fair use under Policy ¶ 4(c)(iii)); see also Enterprise Holdings, Inc. v. I S / Internet Consulting Services Inc., FA 1785242 (Forum June 5, 2018) (“On its face, the use of a domain name that is confusingly similar to the mark of another in order to facilitate a phishing scheme cannot be described as either a bona fide offering of goods or services under Policy ¶ 4(c)(i) or a legitimate noncommercial or fair use under Policy ¶ 4(c)(iii).”). Thus the Panel finds that Respondent fails to use the disputed domain name to make a bona fide offering of goods or services under Policy ¶ 4(c)(i) or a legitimate noncommercial or fair use under Policy ¶ 4(c)(iii). And the Panel finds that Respondent does not have rights or legitimate interests in the disputed domain name.
Respondent (who did not reply to Complainant’s contentions) has not presented any plausible explanation for its use of Complainant’s mark. In accordance with paragraph 14(b) of the Rules, the Panel shall draw such inferences from Respondent’s failure to reply as it considers appropriate. Accordingly, the Panel finds that Respondent did not have a legitimate use in mind when registering the disputed domain name.
Indeed, as already noted, Respondent uses the disputed domain name to pass off as Complainant and phish for users’ information. Use of a disputed domain name to pass off as a complainant and engage in phishing is evidence of bad faith disruption of a complainant’s business under Policy ¶ 4(b)(iii) and an attempt to attract users for commercial gain under Policy ¶ 4(b)(iv), as well as bad faith under Policy ¶ 4(a)(iii). See Eastman Chemical Company v. Lukas Moris, FA 1956649 (Forum Aug. 23, 2021) (“Complainant first argues Respondent registered and uses the disputed domain name in bad faith because Respondent uses the disputed domain name to impersonate Complainant in furtherance of a phishing scheme. A domain name that is used in connection with a phishing scheme over email may be evidence of a domain name registered and used in bad faith under Policy ¶¶ 4(b)(iii) and (iv).”); see also Qatalyst Partners LP v. Devimore, FA 1393436 (Forum July 13, 2011) (finding that using the disputed domain name as an e-mail address to pass itself off as the complainant in a phishing scheme is evidence of bad faith registration and use); see also Google Inc. v. Domain Admin / Whois Privacy Corp., FA1506001622862 (Forum Aug. 10, 2015) (finding that the respondent’s apparent use of the disputed domain name in furtherance of a ‘phishing’ scheme further established its bad faith registration and use of the disputed domain name under Policy ¶ 4(a)(iii)). Therefore the Panel finds bad faith registration and use under Policy ¶¶ 4(b)(iii) and (iv), and 4(a)(iii).
Further, Respondent registered the disputed domain name with actual knowledge of Complainant’s mark: the fraudulent phishing emails display Complainant’s famous mark. While constructive notice is insufficient to demonstrate bad faith, actual knowledge of a complainant’s rights in a mark prior to registration may be evidence of bad faith per Policy ¶ 4(a)(iii). See Custom Modular Direct LLC v. Custom Modular Homes Inc., FA 1140580 (Forum Apr. 8, 2008) (“There is no place for constructive notice under the Policy.”); see also Orbitz Worldwide, LLC v. Domain Librarian, FA 1535826 (Forum Feb. 6, 2014) (“The Panel notes that although the UDRP does not recognize ‘constructive notice’ as sufficient grounds for finding Policy ¶ 4(a)(iii) bad faith, the Panel here finds actual knowledge through the name used for the domain and the use made of it.”); see also Univision Comm'cns Inc. v. Norte, FA 1000079 (Forum Aug. 16, 2007) (rejecting the respondent's contention that it did not register the disputed domain name in bad faith since the panel found that the respondent had knowledge of the complainant's rights in the UNIVISION mark when registering the disputed domain name). The Panel finds that Respondent had actual knowledge of Complainant’s rights in the mark prior to Respondent’s registration of the disputed domain name and that this constitutes bad faith under Policy ¶ 4(a)(iii).
Having established all three elements required under the ICANN Policy, the Panel concludes that relief shall be GRANTED.
Accordingly, it is Ordered that the <twitter-verification.com> domain name be TRANSFERRED from Respondent to Complainant.
Richard Hill, Panelist
Dated: May 6, 2022
Click Here to return to the main Domain Decisions Page.
Click Here to return to our Home Page