SailPoint Technologies, Inc. v. Kiran Gurram
Claim Number: FA2107001957059
Complainant is SailPoint Technologies, Inc. (“Complainant”), represented by Dwayne K. Goetzel, Texas, USA. Respondent is Kiran Gurram (“Respondent”), Georgia, USA.
REGISTRAR AND DISPUTED DOMAIN NAME
The domain name at issue is <sailpoint.dev>, registered with Blue Razor Domains, LLC.
The undersigned certifies that has acted independently and impartially and to the best of his knowledge has no known conflict in serving as Panelist in this proceeding.
Paul M. DeCicco, as Panelist.
Complainant submitted a Complaint to the Forum electronically on July 28, 2021; the Forum received payment on July 28, 2021.
On July 29, 2021, Blue Razor Domains, LLC confirmed by e-mail to the Forum that the <sailpoint.dev> domain name is registered with Blue Razor Domains, LLC and that Respondent is the current registrant of the name. Blue Razor Domains, LLC has verified that Respondent is bound by the Blue Razor Domains, 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 August 2, 2021, the Forum served the Complaint and all Annexes, including a Written Notice of the Complaint, setting a deadline of August 23, 2021 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@sailpoint.dev. Also on August 2, 2021, 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 August 26, 2021, pursuant to Complainant's request to have the dispute decided by a single-member Panel, the Forum appointed Paul M. DeCicco 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 contends as follows:
Complainant has rights in the SAILPOINT mark through its registration of the mark with the United States Patent and Trademark Office (“USPTO”). Additionally, Complainant has used the SAILPOINT mark since at least as early as 2007.
Respondent’s <sailpoint.dev> domain name is identical or confusingly similar to Complainant’s mark, as Respondent incorporates Complainant’s mark in its entirety.
Respondent has no rights or legitimate interests in the <sailpoint.dev> domain name as Respondent is not commonly known by the at-issue domain name nor has Respondent been licensed, authorized, or otherwise permitted by Complainant to use Complainant’s mark. Furthermore, Respondent’s use is not a bona fide offering of goods or services, nor a legitimate noncommercial or fair use, as Respondent is merely passively holding the disputed domain name.
Respondent registered and uses the <sailpoint.dev> domain name in bad faith. Specifically, Respondent is a creating a false affiliation with Complainant by diverting Internet users to an inactive webpage. Additionally, Respondent had actual or constructive knowledge of Complainant’s mark at the time of registration.
B. Respondent
Respondent failed to submit a Response in this proceeding.
Complainant has rights in the SAILPOINT mark through its registration of such mark with the USPTO.
Respondent is not affiliated with Complainant and had not been authorized to use Complainant’s trademark in any capacity.
Respondent registered the at‑issue domain names after Complainant acquired rights in the SAILPOINT trademark.
Respondent holds the at-issue domain name passively.
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 at-issue domain name is confusingly similar to a trademark in which Complainant has rights.
Complainant’s registration of the SAILPOINT mark with the USPTO demonstrates Complainant’s rights in a mark under Policy ¶ 4(a)(i). 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).”).
Respondent’s <sailpoint.dev> domain name consists of Complainant’s SAILPOINT trademark followed by the top-level domain name “.dev.” Under the Policy, the differences between Respondent’s domain name and Complainant’s trademark do nothing to distinguish the domain name from the mark. Therefore, the Panel concludes that Respondent’s <sailpoint.dev> domain name is confusingly similar to Complainant’s SAILPOINT trademark pursuant to Policy ¶ 4(a)(i). See Tupelo Honey Hospitality Corporation v. King, Reggie, FA 1732247 (Forum July 19, 2017) (“Addition of a gTLD is irrelevant where a mark has been fully incorporated into a domain name and the gTLD is the sole difference.”).
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. See Hanna-Barbera Prods., Inc. v. Entm’t Commentaries, FA 741828 (Forum Aug. 18, 2006). Since Respondent failed to respond, absent evidence of Policy ¶ 4(c) circumstances Complainant’s prima facie showing acts conclusively.
Respondent lacks both rights and legitimate interests in respect of the at-issue domain name. Respondent is not authorized to use Complainant’s trademark in any capacity and, as discussed below, there are no Policy ¶ 4(c) circumstances from which the Panel might find that Respondent has rights or interests in respect of the at-issue domain name.
The WHOIS information for <sailpoint.dev> indicates that “Kiran Gurram” is the domain name’s registrant. There is nothing in the record before the Panel that indicates that Respondent is otherwise known by the <sailpoint.dev> domain name. As such, the Panel finds that Respondent is not commonly known by the at-issue domain name under Policy ¶ 4(c)(ii). See Coppertown Drive-Thru Sys., LLC v. Snowden, FA 715089 (Forum July 17, 2006) (concluding that the respondent was not commonly known by the <coppertown.com> domain name where there was no evidence in the record, including the WHOIS information, suggesting that the respondent was commonly known by the disputed domain name).
Respondent holds the at-issue domain name passively. Browsing to the domain name returns an error message. Respondent’s passive holding of <sailpoint.dev> in this manner is not indicative of a bona fide offering of goods or services under Policy ¶ 4(c)(i), nor of a non-commercial or fair use under Policy ¶ 4(c)(iii). See CrossFirst Bankshares, Inc. v Yu-Hsien Huang, FA 1785415 (Forum June 6, 2018) (“Complainant demonstrates that Respondent fails to actively use the disputed domain name as it resolves to an inactive website. Therefore, the Panel finds that Respondent fails to actively 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).”).
Given the forgoing, Complainant satisfies its initial burden under Policy ¶ 4(a)(ii) and conclusively demonstrates Respondent’s lack of rights and lack of interests in respect of the at-issue domain name.
Respondent’s <sailpoint.dev> domain name was registered and used in bad faith. As discussed below without limitation, bad faith circumstances are present that compel the Panel to conclude that Respondent acted in bad faith pursuant to paragraph 4(a)(iii) of the Policy.
First and as mentioned above regarding rights and legitimate interests, Respondent’s holds the at-issue domain name passively. Doing so demonstrates Respondent’s bad faith. See Phat Fashions, LLC v. Kruger, FA 96193 (Forum Dec. 29, 2000) (finding bad faith under Policy ¶ 4(b)(iv) even though the respondent has not used the domain name because “it makes no sense whatever to wait until it actually ‘uses’ the name, when inevitably, when there is such use, it will create the confusion described in the Policy”).
Moreover, the Panel finds that Respondent registered its <sailpoint.dev> domain name knowing that Complainant had trademark rights in SAILPOINT. Respondent’s prior knowledge is evident from the Complainant’s long term use its SAILPOINT trademark. Respondent’s prior knowledge of Complainant's trademark shows that Respondent registered and used its <sailpoint.dev> domain name in bad faith pursuant to Policy ¶ 4(a)(iii). See Minicards Vennootschap Onder FIrma Amsterdam v. Moscow Studios, FA 1031703 (Forum Sept. 5, 2007) (holding that respondent registered a domain name in bad faith under Policy ¶ 4(a)(iii) after concluding that respondent had "actual knowledge of Complainant's mark when registering the disputed domain name"); see also Victoria’s Secret Stores Brand Mgmt., Inc. v. Michael Bach, FA 1426668 (Forum Mar. 2, 2012) (“Although Complainant has not submitted evidence indicating actual knowledge by Respondent of its rights in the trademark, the Panel finds that, due to the fame of Complainant’s [VICTORIA’S SECRET] mark, Respondent had actual notice at the time of the domain name registration and therefore registered the domain name in 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 <sailpoint.dev> domain name be TRANSFERRED from Respondent to Complainant.
Paul M. DeCicco, Panelist
Dated: August 27, 2021
Click Here to return to the main Domain Decisions Page.
Click Here to return to our Home Page