Balsam v. Tucows Inc.
627 F.3d 1158
9th Cir.2010Background
- Balsam received 1,125 unsolicited emails in Oct 2005–May 2006 advertising adultactioncam.com.
- ICANN administers domain-name registrations; Tucows is an ICANN-accredited registrar under the RAA.
- Balsam sued Angeles Technology for California anti-spam violations and obtained a default judgment for $1,125,000 in 2008.
- Angeles used Tucows' Contact Privacy, hindering Balsam from identifying the actual operator of the domain.
- Balsam filed suit against Tucows and officers in 2009 seeking to enforce ¶ 3.7.7.3 as a third-party beneficiary of the RAA, asserting breach, negligence, conspiracy, and declaratory relief.
- The district court dismissed with prejudice; the Ninth Circuit reviews de novo and affirms.”
Issues
| Issue | Plaintiff's Argument | Defendant's Argument | Held |
|---|---|---|---|
| Is Balsam an intended third-party beneficiary of the RAA | Balsam should benefit from 3.7.7.3 as a harmed party | RAA contains a No Third-Party Beneficiaries clause and 3.7.7.3 is not a binding grant to third parties | No; no intent to create third-party rights |
| Does 3.7.7.3 create independent rights overriding the No Third-Party Beneficiaries clause | 3.7.7.3 governs liability for harm and should inure to complainant | 3.7.7.3 is binding only in a separate registrar–registered name holder agreement and not as an independent RAA term | Not; 3.7.7.3 does not create third-party rights under the RAA |
| Does the No Third-Party Beneficiaries clause unambiguously preclude Balsam's claims | Clause should not bar rights arising from specific provisions | Clause explicitly precludes non-parties from rights under the agreement | Yes; clause unambiguously excludes third-party rights |
| Does Tucows' role as registrar versus registered name holder affect the outcome | Tucows’ conduct as registered name holder could impose duties | The clause protects Tucows from third-party suits; Tucows’ obligations under the RAA pertain to registrars | No independent third-party rights created; district court correct |
| Can the complaint be amended to cure any defect | Amendment could cure third-party beneficiary issue | Defect cannot be cured; no rights exist to confer | Dismissing with prejudice was proper |
Key Cases Cited
- Spinks v. Equity Residential Briarwood Apartments, 90 Cal.Rptr.3d 453 (Cal. Ct. App. 2009) (intent required to confer third-party beneficiary rights; class of beneficiaries must be evident)
- Prouty v. Gores Tech. Gr., 18 Cal. Rptr.3d 178 (Cal. Ct. App. 2004) (contract read as a whole; intent governs third-party beneficiary status)
- Kaiser Eng'rs, Inc. v. Grinnell Fire Prot. Sys. Co., 219 Cal. Rptr. 626 (Cal. Ct. App. 1985) (contractual intent matters for third-party beneficiary questions)
- Solid Host, NL v. Namecheap, Inc., 652 F.Supp.2d 1092 (C.D. Cal. 2009) (3.7.7.3 interpreted as not creating independent RAA rights; separate agreement context)
- Roden v. AmerisourceBergen Corp., 186 Cal.App.4th 620 (Cal. Ct. App. 2010) (absence of intended third-party benefit defeats rights under contract)
- Register.com, Inc. v. Verio, Inc., 356 F.3d 393 (2d Cir. 2004) (No Third-Party Beneficiaries clause expressly excludes non-parties from rights)