The Publisher’s Shield: Section 230

Work in progress

This case is under active development. All pages are being written, expanded, and fact-checked on an ongoing basis — content and coverage are subject to change.

The statute

Documented

Section 230 of the Communications Decency Act (CDA), codified at 47 U.S.C. § 230, was enacted as part of the Telecommunications Act of 1996. Its central operative provision is subsection (c)(1):

“No provider or user of an interactive computer service shall be treated as the publisher or speaker of any information provided by another information content provider.”

Subsection (c)(2) adds a “Good Samaritan” immunity for content-moderation decisions. It has two subparts:

“(A) No provider or user of an interactive computer service shall be held liable on account of any action voluntarily taken in good faith to restrict access to or availability of material that the provider or user considers to be obscene, lewd, lascivious, filthy, excessively violent, harassing, or otherwise objectionable, whether or not such material is constitutionally protected; or (B) any action taken to enable or make available to information content providers or others the technical means to restrict access to material described in paragraph (1).”

Section 230 explicitly does not limit federal criminal liability, intellectual-property law, or certain communications-law provisions. 47 U.S.C. § 230(e).

Why it was enacted: the publisher/distributor distinction

Documented

The legislative history of Section 230 responds directly to two cases that produced contradictory results under existing common-law defamation doctrine:

• Cubby, Inc. v. CompuServe Inc., 776 F. Supp. 135 (S.D.N.Y. 1991). CompuServe provided access to a third-party online forum without reviewing the content. The court held that CompuServe was a distributor, not a publisher, and could only be held liable for defamatory content if it had actual knowledge of the content’s defamatory character. CompuServe had no such knowledge and was not liable.
• Stratton Oakmont, Inc. v. Prodigy Services Co., 1995 WL 323710 (N.Y. Sup. Ct. 1995). Prodigy, unlike CompuServe, moderated its forums and had a policy of removing offensive content. Because Prodigy exercised editorial control, the court held it was a publisher, not a distributor — and therefore liable for defamatory content posted by third parties even without specific knowledge. The exercise of any content moderation triggered full publisher liability.

Congress found this outcome perverse: Stratton Oakmont penalised platforms that tried to moderate content by treating moderation as an assumption of publisher liability, while platforms that moderated nothing (like CompuServe) escaped liability entirely. Section 230 eliminated this penalty by decoupling moderation decisions from publisher status: a platform can moderate content under (c)(2)’s Good Samaritan protection without thereby becoming a publisher liable for everything else on the service.

What immunity is actually claimed in practice

Documented

Courts have interpreted Section 230(c)(1) broadly. Under the dominant reading, a platform is immune from any claim that would treat it as a publisher of third-party content — which encompasses not just defamation but negligence claims, product-liability theories, and many state-law tort claims. Zeran v. America Online, Inc., 129 F.3d 327 (4th Cir. 1997), was the first influential circuit decision articulating this broad interpretation.

The immunity applies when: (1) the defendant is a provider or user of an interactive computer service; (2) the claim treats the defendant as the publisher or speaker; and (3) the information at issue was provided by another information content provider.

The structural tension

Contested

The internal tension in how platforms invoke Section 230 alongside First Amendment editorial-discretion claims has been identified by legal scholars on both sides of the regulatory debate. The argument is:

• When facing liability claims, platforms invoke Section 230(c)(1): they are not the publisher of third-party content. They are neutral conduits. The content is not theirs.
• When facing must-carry legislation (requirements to host content they would prefer to remove), platforms invoke the First Amendment: they are publishers exercising editorial discretion over curated speech. The content decisions are theirs.

These positions are in tension. A pure conduit — a telephone company transmitting calls without reviewing their content — is precisely the entity historically subjected to common-carrier obligations. A newspaper exercising editorial discretion — deciding what to print and why — has the strongest First Amendment claim against compelled carriage. Platforms simultaneously claim aspects of both statuses. Whether both claims can be simultaneously valid, and under what circumstances each applies, is a question courts are still working through.

Some legal commentators argue that the tension is not a paradox but a feature: platforms exercise editorial discretion at the system level (algorithmic ranking, community standards) while being non-discriminatory conduits at the individual-post level. Others argue that the scale and opacity of algorithmic curation mean the “conduit” description no longer fits even at the individual-post level.

Section 230 and common-carrier status

Documented

Section 230(f)(2) defines “interactive computer service” to include “any information service, system, or access software provider that provides or enables computer access by multiple users to a computer server, including specifically a service or system that provides access to the Internet and such systems operated or services offered by libraries or educational institutions.” This is not the same as the Title II Communications Act definition of a common carrier, and Congress did not classify interactive computer services as common carriers in the 1996 Act.

The Telecommunications Act of 1996 (of which the CDA containing Section 230 was a part) simultaneously classified broadband as an information service (not a Title II common carrier) and enacted Section 230’s publisher immunity. The two provisions are consistent: both place internet services in a non-common-carrier category. Whether that classification was correct, and whether Congress can or should revise it for platforms that have reached infrastructure scale, is the legislative question addressed in the remedy framework.