Third parties could nonetheless seek enforcement of a registrar’s obligations set forth in the ICANN
Agreement by resort to a grievance process under ICANN’s auspices.
Verio, Inc. is engaged in the business of selling a variety of web site design, development, and operation
services and as such competes with Register’s web site development business. To facilitate its pursuit of
customers, Verio obtained daily updates of WHOIS information from domain name registrars, including
Register.com. Upon acquiring the WHOIS information of new registrants, Verio would send them
marketing solicitations by email, telemarketing, and direct mail. Solicitations sent by email were
inconsistent with the terms of the restrictive legend Register attached to its responses to Verio’s queries;
other solicitations were inconsistent with requests made by domain name registrants not to receive
marketing materials connected to their registration of domain names. To thwart Verio’s use of WHOIS
data gathered from its system, Register.com revised the restrictive legend accompanying downloads of
such data to limit its use for all solicitations, not just email solicitations.
This dispute arose when Register.com sued Verio for unfair competition and breach of contract for
Verio’s use of Register.com’s WHOIS data and trademarks in its marketing campaigns. Verio responded
by claiming that Register.com’s restriction on the use of WHOIS data for all solicitations violated the
ICANN Agreement’s requirement that registrars permit use of such data for any lawful purposes, except
spam. (Note: this case arose before enactment of the CAN-SPAM Act and other laws regulating
unsolicited commercial email.) Relying on the “no third-party beneficiary” language of the ICANN
Agreement Register.com argued that Verio could not enforce the terms of the ICANN Agreement against
it. The trial court agreed with Register.com and enjoined Verio from using Register.com’s WHOIS data
and trademarks in its marketing solicitations.
Issue: Is Verio, Inc. an intended third-party beneficiary of the agreement between Register.com and
ICANN?
Holding: Judgment for Register.com affirmed. Excerpts from the court’s opinion:
Verio’s principal argument is that Register was not authorized to forbid Verio from using the data for
direct mail and telemarketing solicitation because the ICANN Agreement prohibited Register from
imposing any “terms and conditions” on use of WHOIS data, “except as permitted by
ICANN-adopted policy,” which specified that Register was required to permit any lawful purpose,
except unsolicited commercial email. Register does not deny that the restrictions it imposed
contravened this requirement of the ICANN Agreement. Register contends, relying on the “no
third-party beneficiary” provisions of §II.S.2, that the question whether it violated §II.F.5 of its
Agreement with ICANN is a matter between itself and ICANN, and that Verio cannot enforce the
obligations placed on Register by the ICANN Agreement.
ICANN intervened in the district court as an amicus curiae and strongly supported Register’s
position, opposing Verio’s right to invoke Register’s contractual promises to ICANN. ICANN
explained that ICANN has established a remedial process for the resolution of such disputes through
which Verio might have sought satisfaction: “If Verio had concerns regarding Register.com’s
conditions for access to WHOIS data, it should have raised them within the ICANN process rather
[than] simply taking Register.com’s data, violating the conditions [imposed by Register], and then
seeking to justify its violation in this Court.” [Verio’s claim was] intended to be addressed only
within the ICANN process.”
The court agreed with ICANN’s argument that §II.S.2 was “vital to the overall scheme of [its]
various agreements” with domain-name registrars around the world. “In the fast-paced environment
of the Internet, new issues and situations arise quickly, and sometimes the language of contractual
provisions does not perfectly match the underlying policies. For this and other reasons, hard-and-fast
enforcement [by courts] of the letter of every term of every agreement is not always appropriate.”
Assignment and Delegation
After a contract is made, one or both parties may wish to substitute someone else for themselves. A
contracting party may transfer his rights under a contract, which is called an assignment of rights. Or a