SEESAW LEARNING, INC. v. Ven Rajagopala
Claim Number: FA2204001991932
Complainant is SEESAW LEARNING, INC. (“Complainant”), represented by Josh Gerben of Gerben Perrott PLLC, District of Columbia, USA. Respondent is Ven Rajagopala (“Respondent”), New York, USA.
REGISTRAR AND DISPUTED DOMAIN NAME
The domain name at issue is <getseesaw.app>, registered with GoDaddy.com, 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.
The Honorable Neil Anthony Brown QC as Panelist.
Complainant submitted a Complaint to the Forum electronically on April 12, 2022; the Forum received payment on April 12, 2022.
On April 12, 2022, GoDaddy.com, LLC confirmed by e-mail to the Forum that the <getseesaw.app> domain name is registered with GoDaddy.com, LLC and that Respondent is the current registrant of the name. GoDaddy.com, LLC has verified that Respondent is bound by the GoDaddy.com, 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 13, 2022, the Forum served the Complaint and all Annexes, including a Written Notice of the Complaint, setting a deadline of May 3, 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@getseesaw.app. Also on April 13, 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 May 9, 2022, pursuant to Complainant's request to have the dispute decided by a single-member Panel, the Forum appointed The Honorable Neil Anthony Brown QC 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.
A. Complainant
Complainant made the following contentions.
Complainant has rights in the SEESAW mark through its registration of the mark with the United States Patent and Trademark Office (“USPTO”) (e.g., Reg. No. 4,768,224 registered July 7, 2015). See Compl. Exhibit B. Respondent’s <getseesaw.app> domain name is virtually identical and confusingly similar to Complainant’s mark because it incorporates the SEESAW mark in its entirety and merely adds the term “get” and adds the “.app” generic top-level domain (“gTLD”)
Respondent has no legitimate interests in the <getseesaw.app> domain name. Respondent is not commonly known by the disputed domain name and Complainant has not authorized or licensed Respondent any rights in the SEESAW mark. Additionally, Respondent does not use the disputed domain name for any bona fide offering of goods or services or legitimate noncommercial or fair use. Instead, the disputed domain name resolves to a page offering competing goods and services.
Respondent registered and uses the <getseesaw.app> domain name in bad faith. Respondent registered the disputed domain name in order to disrupt Complainant’s business and divert customers for commercial gain.
B. Respondent
Respondent failed to submit a Response in this proceeding.
1. Complainant is a United States company engaged in the business of providing educational information and computer software for educational purposes.
2. Complainant has established its rights in the SEESAW mark through its registration of the mark with the United States Patent and Trademark Office (“USPTO”) (e.g., Reg. No. 4,768,224 registered July 7, 2015).
3. Respondent registered the <getseesaw.app> domain name on December 30, 2020.
4. Respondent has caused the domain name to resolve to a webpage offering goods and services competing with those of Complainant.
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 first question that arises is whether Complainant has rights in a trademark or service mark on which it may rely. Complainant submits that it has rights in the SEESAW mark based upon the registration of the mark with the USPTO ((e.g., Reg. No. 4,768,224 registered July 7, 2015). See Compl. Exhibit B. Registration of a mark with the USPTO is a valid showing of rights in a mark. See DIRECTV, LLC v. The Pearline Group, FA 1818749 (Forum Dec. 30, 2018) (“Complainant’s ownership of a USPTO registration for DIRECTV demonstrate its rights in such mark for the purposes of Policy ¶ 4(a)(i).”). Since Complainant provides evidence of registration of the SEESAW mark with the USPTO, the Panel finds that the Complainant has rights in the SEESAW mark under Policy 4(a)(i).
The next question that arises is whether the disputed domain name is identical or confusingly similar to Complainant’s SEESAW mark. Complainant argues Respondent’s <getseesaw.app> domain name is identical or confusingly similar to Complainant’s SEESAW mark as it contains the SEESAW mark in its entirety and merely adds the word “get” and the “.app” gTLD. The addition of a generic or descriptive phrase and gTLD fails sufficiently to distinguish a disputed domain name from a mark per Policy ¶ 4(a)(i). See Microsoft Corporation v. Thong Tran Thanh, FA 1653187 (Forum Jan. 21, 2016) (determining that confusing similarity exists where [a disputed domain name] contains Complainant’s entire mark and differs only by the addition of a generic or descriptive phrase and top-level domain, the differences between the domain name and its contained trademark are insufficient to differentiate one from the other for the purposes of the Policy). Therefore, the Panel finds the disputed domain name is confusingly similar to Complainant’s SEESAW mark per Policy ¶ 4(a)(i).
Complainant has thus made out the first of the three elements that it must establish.
It is now well established that Complainant must first make a prima facie case that Respondent lacks rights and legitimate interests in the disputed domain name under Policy ¶ 4(a)(ii), then the burden shifts to Respondent to show it does have rights or legitimate interests. See Advanced International Marketing Corporation v. AA-1 Corp, FA 780200 (Forum Nov. 2, 2011) (finding that a complainant must offer some evidence to make its prima facie case and satisfy Policy ¶ 4(a)(ii)); see also 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”).
(a) Respondent has chosen to take Complainant’s SEESAW mark and to use it in its domain name adding only the word “get “ to the mark;
(b) Respondent registered the <getseesaw.app> domain name on December 30, 2020;
(c) Respondent has caused the domain name to resolve to a webpage offering goods and services competing with those of Complainant;
(d) Respondent has engaged in these activities without the consent or approval of Complainant;
(e) Complainant contends Respondent lacks rights or legitimate interests in the <getseesaw.app> domain name since Respondent is not commonly known by the disputed domain name and Complainant has not authorized or licensed to Respondent any rights in the SEESAW mark. WHOIS information may be used to determine whether a respondent is commonly known by the disputed domain name under Policy ¶ 4(c)(ii). See Amazon Technologies, Inc. v. LY Ta, FA 1789106 (Forum June 21, 2018) (concluding a respondent has no rights or legitimate interests in a disputed domain name where the complainant asserted it did not authorize the respondent to use the mark, and the relevant WHOIS information indicated the respondent is not commonly known by the domain name). Additionally, lack of authorization to use a complainant’s mark may indicate that the respondent is not commonly known by the disputed domain name. See Emerson Electric Co. v. golden humble / golden globals, FA 1787128 (Forum June 11, 2018) (“lack of evidence in the record to indicate a respondent is authorized to use [the] complainant’s mark may support a finding that [the] respondent does not have rights or legitimate interests in the disputed domain name per Policy ¶ 4(c)(ii)”). The WHOIS information for the disputed domain name lists the registrant as “Ven Rajagopala,” and there is no other evidence to suggest that Respondent was authorized to use the SEESAW mark. Therefore, the Panel finds Respondent is not commonly known by the disputed domain name per Policy ¶ 4(c)(ii);
(f) Complainant argues that Respondent fails to use the disputed domain name in connection with a bona fide offering of goods or services or legitimate noncommercial or fair use as the <getseesaw.app> domain name redirects to another site offering competing goods and services. Where the respondent uses a disputed domain name to redirect users to another site offering competing goods and services, the Panel may find the respondent fails to make a bona fide offering of goods or services or a legitimate noncommercial or fair use per Policy ¶¶ 4(c)(i) or (iii). See Summit Group, LLC v. LSO, Ltd., FA 758981 (Forum Sept. 14, 2006) (finding that the respondent’s use of the complainant’s LIFESTYLE LOUNGE mark to redirect Internet users to respondent’s own website for commercial gain does not constitute either a bona fide offering of goods or services pursuant to Policy ¶ 4(c)(i), or a legitimate noncommercial or fair use pursuant to Policy ¶ 4(c)(iii)) Here, Complainant provides screenshots of the disputed domain name resolving to a page offering competing goods and services. See Compl. Exhibit E. Therefore, the Panel finds that Respondent fails to use the disputed domain name for a bona fide offering of goods or services or legitimate noncommercial or fair use under Policy ¶ 4(c)(i) or (iii).
All of these matters go to make out the prima facie case against Respondent.
As Respondent has not filed a Response or attempted by any other means to rebut the prima facie case against it, the Panel finds that Respondent does not have a right or legitimate interest in the disputed domain name.
Complainant has thus made out the second of the three elements that it must establish.
It is clear that to establish bad faith for the purposes of the Policy, Complainant must show that the disputed domain name was registered in bad faith and has been used in bad faith. It is also clear that the criteria set out in Policy ¶ 4(b) for establishing bad faith are not exclusive, but that Complainants in UDRP proceedings may also rely on conduct that is bad faith within the generally accepted meaning of that expression.
Having regard to those principles, the Panel finds that the disputed domain name was registered and used in bad faith. That is so for the following reasons.
First, Complainant argues that Respondent registered and uses the <getseesaw.app> domain name in bad faith because Respondent disrupts Complainant’s business and attempts to attract Internet users to its competing website for commercial gain. Use of a disputed domain name to offer competing goods or services can be 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). See LoanDepot.com, LLC v. Kaolee (Kay) Vang-Thao, FA1762308 (Forum Jan. 9, 2018) (Finding that Respondent’s use of the disputed domain name to offer competing loan services disrupts Complainant’s business under Policy ¶ 4(b)(iii)); See also AT&T Corp. v. RealTime Internet.com Inc., D2001-1487 (WIPO May 1, 2002) (“[U]se of domain names to sell Complainant’s goods and services without Complainant's authority . . . is bad faith use of a confusingly similar domain name.”); See also Am. Univ. v. Cook, FA 208629 (Forum Dec. 22, 2003) (“Registration and use of a domain name that incorporates another's mark with the intent to deceive Internet users in regard to the source or affiliation of the domain name is evidence of bad faith.”). As previously noted, Complainant provides screenshots of the disputed domain name resolving to a page offering competing goods and services. See Compl. Exhibit E. Therefore, the Panel agrees and finds that Respondent registered and used the disputed domain name in bad faith per Policy ¶ 4(b)(iii) or (iv).
Complainant has thus made out the third of the three elements that it must establish.
Having established all three elements required under the ICANN Policy, the Panel concludes that relief shall be GRANTED.
Accordingly, it is Ordered that the <getseesaw.app> domain name be TRANSFERRED from Respondent to Complainant.
The Honorable Neil Anthony Brown QC
Panelist
Dated: May 10, 2022
Click Here to return to the main Domain Decisions Page.
Click Here to return to our Home Page