Webroot Inc. v. Singh

CourtDistrict Court, D. Colorado
DecidedAugust 27, 2019
Docket1:18-cv-01909
StatusUnknown

This text of Webroot Inc. v. Singh (Webroot Inc. v. Singh) is published on Counsel Stack Legal Research, covering District Court, D. Colorado primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Webroot Inc. v. Singh, (D. Colo. 2019).

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF COLORADO Judge Raymond P. Moore

Civil Action No. 18-cv-01909-RM-STV

WEBROOT INC.,

Plaintiff,

v.

CHITRANSHU SINGH, POLISHSYS TECHNOLOGIES, and CHANDRESH SINGH,

Defendants. ______________________________________________________________________________

ORDER ______________________________________________________________________________

This matter is before the Court on the February 15, 2019 Recommendation of United States Magistrate Judge Scott T. Varholak (the “Recommendation”) (ECF No. 38) to grant in part and deny in part Plaintiff’s Motion for Judgment by Default (the “Motion”) (ECF No. 35). The Recommendation is incorporated herein by reference. See 28 U.S.C. § 636(b)(1)(B); FED. R. CIV. P. 72(b). The Recommendation advised the parties that specific written objections were due within fourteen days after being served with a copy of the Recommendation. (ECF No. 38 at pages 35- 36.) Despite this advisement, no objections to the Recommendation have to date been filed by any party and the time to do so has expired. (See generally Dkt.) “When no timely objection is filed, the court need only satisfy itself that there is no clear error on the face of the record in order to accept the recommendation.” FED. R. CIV. P. 72(b) advisory committee’s note; see also Summers v. Utah, 927 F.2d 1165, 1167 (10th Cir. 1991) (“In the absence of timely objection, the district court may review a magistrate’s report under any standard it deems appropriate.”). As shown below, the Court has conducted more than a clear error review of the matter. The Court does so in light of the fact that Defendants are citizens of India and alternate service was allowed. Upon such review, as set forth below, the Court accepts in part and rejects in part the Recommendation.1

I. THE RECOMMENDATION The Factual Background. As the Magistrate Judge aptly stated, this trademark dispute arises from Defendants’ alleged use of various domain names which Plaintiff alleged infringes on its WEBROOT trademark. There are seven domain names at issue: webrootcomsafe.org, installwebroot.org, web--root.org, webroot-support.org, webroot-com-safe.net, web-root.org, and webrootcom-safe.org. The domain name “webrootcom-safe.org” is identified in the Amended Complaint as the “Domain Name” and in the Recommendation as the “Remaining Domain.” For consistency, the Court will refer to webrootcom-safe.org as the Remaining Domain. Plaintiff contends Defendants have engaged in a pattern of registering domain names that include its WEBROOT marks2 and, through these websites, offered unauthorized customer

support services in connection with the WEBROOT marks. Plaintiff further alleges Defendants misled consumers into believing that their services are authorized, sponsored, or endorsed by Plaintiff. In addition, Defendants allegedly collect product keys from unsuspecting customers who believe they are interacting with Plaintiff when, in fact, they are interacting with Defendants.

1 The Court finds Plaintiff has, on more than one occasion, combined Defendants in its conclusion even though its factual allegations and supporting papers did not address all Defendants. For example, Plaintiff alleges the NAF panel “found that Defendants’ use of that Domain Name was fair use.” (ECF No. 9, ¶ 53.) The NAF’s findings, however, related only to Defendants Chitranshu Singh and Polishsys Technologies. (ECF No. 9-12 at pp. 2, 3, 22, 23.) 2 As defined in the Recommendation as the “Webroot family of trademarks.” (ECF No. 38, p. 2.) Plaintiff filed two Uniform Dispute Resolution Procedure (“UDRP”) proceedings involving the domain names. The first UDRP proceeding was filed against Defendant Chandresh Singh (“Chandresh”) regarding domain name webrootcomsafe.org; the National Arbitration Forum (“NAF”) found in favor of Plaintiff and transferred that domain name to Plaintiff. The second UDRP was filed against Defendants Chitranshu Singh (“Chitranshu”) and

Polishsys Technologies3 – not all Defendants – and addressed the remaining six domain names (hereafter “Six Domain Names”). The NAF found in favor of Plaintiff on five domain names and against Plaintiff on the sixth, the Remaining Domain. The NAF transferred those five domain names to Plaintiff. To the extent the Recommendation stated otherwise as to such findings, e.g., that the second UDRP was against all Defendants, it is rejected. The Procedural Background. Plaintiff was granted leave to serve Defendants via email and did so. After the Court’s initial review of the Recommendation, it questioned whether the service afforded Defendants was sufficient and, ultimately, directed further service upon Defendants which Plaintiff effected. (ECF Nos. 40-44.) The Court finds the service, as

supplemented, is sufficient. Personal Jurisdiction. The Court agrees with the Recommendation that personal jurisdiction may be had against those Defendants who registered the Remaining Domain with Name.com as the Domain Name Registration Agreement (“Agreement”) for Name.com requires registrants to submit to personal jurisdiction in Colorado federal courts. The question, however, is who registered the Remaining Domain, and is therefore is subject to personal jurisdiction in this

3 Plaintiff’s documents show that Chandresh was named in the second UDRP complaint, but the NAF findings and decision were directed only against Chitranshu and Polishsys. Moreover, Plaintiff’s Motion states this second UDRP was only against Chitranshu and Polishsys and that these domain names were registered by Chitranshu and Polishsys (Motion, p. 5). Accordingly, the Court finds the second UDRP was only against Chitranshu and Polishsys. court, as “[e]ach defendant’s contacts with the forum State must be assessed individually.” Calder v. Jones, 465 U.S. 783, 790 (1984). The Motion asserts that “Defendants” registered the Remaining Domain (along with the five others in the second UDRP), referring the Court to paragraph 42 of the Amended Complaint. (Motion, p. 5.) Paragraph 42 of the Amended Complaint, however, alleges that “Plaintiff became

aware of six additional domains associated with the Defendants.” (ECF No. 9, ¶ 42 (emphasis added)). Plaintiff, who bears the burden of showing personal jurisdiction may be had, fails to show that a person “associated” with a domain name that is registered on Name.com would subject that person to personal jurisdiction in Colorado. Plaintiff also asserts the Six Domain Names were registered by Polishsys and Chitranshu, referring the Court generally to ECF No. 9-10 which consists of Plaintiff’s amended complaint with exhibits filed on May 24, 2018 in the second UDRP. The Court’s review of these documents, however, shows that, as of May 2, 2018, the Remaining Domain was registered to Polishsys (ECF No. 9-10, p. 81) on GoDaddy.com. The Amended Complaint’s allegations,

however, show there were changes in the registration. In paragraph 1 of the Amended Complaint, Plaintiff alleges the Remaining Domain was registered by Chitranshu and was then “currently” registered on Name.com. Paragraphs 7 and 8 of the Amended Complaint alleges that on June 25, 2018, the date of the NAF’s second decision, the registrant at that time was Polishsys but, at some point in time, the registrant was changed to Chitranshu. Regardless, the NAF’s decision stated that Name.com confirmed the Remaining Domain was registered on Name.com. (ECF No. 9-12, p.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Cite This Page — Counsel Stack

Bluebook (online)
Webroot Inc. v. Singh, Counsel Stack Legal Research, https://law.counselstack.com/opinion/webroot-inc-v-singh-cod-2019.