Section 230, Explained

Section 230 of the Communications Decency Act is a single federal statute that shapes almost everything about how comment sections, review sites, and social platforms operate. It was enacted in 1996, long before most of today's internet existed, and it has barely been amended since. Understanding it means reading two short subsections, and then understanding one case that decided what they mean in real cases.

What the statute actually says

Section 230(c)(1) is the famous part: "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." Read plainly, that sentence is 26 words, which is why it is sometimes called "the 26 words that created the internet." It means a website is not legally the author of what its users write. If a user posts something defamatory, the user can be sued for it; the hosting site generally cannot be treated as if it wrote the post itself.

Section 230(c)(2) does separate work. It immunizes providers and users for good-faith decisions to restrict access to material they consider obscene, lewd, harassing, or otherwise objectionable, whether or not that material is constitutionally protected, and for actions taken to help others filter that kind of content. In plain terms: a platform that moderates content in good faith, even overzealously, is generally protected from being sued over the moderation decision itself.

Why Zeran matters as much as the text

The statutory language does not, by itself, answer the hard question: does immunity survive once a platform is notified that specific content is false or harmful? In Zeran v. America Online, Inc., the Fourth Circuit said yes. An unknown poster used AOL message boards to advertise, falsely, that Kenneth Zeran was selling shirts glorifying the Oklahoma City bombing, complete with his home phone number. Zeran told AOL repeatedly and it left the posts up. The court held that Section 230 immunity applies regardless of notice: treating a notified platform as a liable "distributor" rather than an immune "publisher" would defeat the point of the statute, which Congress intended to encourage platforms to self-regulate without fear of being sued into caution or silence. Zeran became the template nearly every later court has followed in reading Section 230 broadly, and as of 2026-07-12 no Supreme Court decision has narrowed that central rule.

What Gonzalez v. Google did and did not do

In 2023, the Supreme Court took up Gonzalez v. Google LLC, a case asking whether Section 230 shields YouTube's algorithmic recommendations, not just the underlying videos. It is tempting to describe the outcome as a Section 230 ruling. It was not. The Court issued a short, unsigned opinion that declined to reach the Section 230 question at all, because the companion case decided the same day, Twitter, Inc. v. Taamneh, unanimously held that the plaintiffs' underlying antiterrorism claims failed on their own terms regardless of Section 230. Since the complaint stated little if any claim for relief independent of the statute, the Court vacated the Ninth Circuit's judgment and remanded for further consideration given Taamneh, without deciding whether algorithmic recommendations fall inside or outside Section 230's shield. Section 230 came out of Gonzalez exactly as it went in: no holding altered, narrowed, or expanded it.

That leaves a real, unresolved fault line. Courts still disagree at the margins about claims that try to plead around Section 230 by targeting a platform's own algorithmic conduct or product design, rather than the third-party content itself, and Gonzalez left that precise question open rather than resolving it. Congress has introduced reform bills targeting Section 230 repeatedly since 2020, and none had been enacted as of this writing; the status of any such bill should be checked against congress.gov before relying on it, since it changes often. Section 230 remains one of the most litigated and most politically contested statutes in tech law, defended by some as the rule that makes open, user-generated platforms possible at all, and criticized by others as letting platforms avoid accountability for harm their design choices help cause.