U.S. Lawmakers Rush to Tackle Online Piracy: A Comparative Breakdown of the ACPA and DEFEND IP Act

Executive Overview

For over a decade following the ferocious public outcry and legislative collapse of the Stop Online Piracy Act (SOPA) and the Protect IP Act (PIPA), pirate site blocking remained radioactive in Washington. U.S. lawmakers largely avoided the topic, wary of igniting a fresh culture war with digital rights advocates, major technology companies, and everyday internet users.

That long-standing political taboo shattered when Congress saw the introduction of two distinct pirate site-blocking bills within a ten-day window. This legislative surge signals a profound shift in U.S. copyright policy, driven by intense lobbying from major rightsholder coalitions and growing frustration over the global reach of offshore copyright infringement.

The first legislative vehicle, the American Copyright Protection Act (ACPA) (H.R. 10364), was introduced by Rep. Darrell Issa. It establishes a broad framework empowering federal courts to compel Internet Service Providers (ISPs), Domain Name System (DNS) resolvers, and Virtual Private Networks (VPNs) to block foreign pirate domains.

Shortly thereafter, a bipartisan coalition introduced the DEFEND IP Act (H.R. 10575) in the House—led by Reps. Zoe Lofgren and Ben Cline—alongside a companion effort in the Senate spearheaded by Senators Thom Tillis, Chris Coons, Marsha Blackburn, and Adam Schiff. This unified measure merges Lofgren’s earlier FADPA proposal with the Senate’s Block BEARD initiative.

While both bills share the foundational goal of using the federal court system to suppress foreign commercial piracy operations while leaving technical execution to intermediaries, they diverge significantly under the hood. Their differences span critical policy areas: which intermediaries are captured, how a "pirate site" is legally defined, whether ISPs receive retroactive or prospective liability shields, how compliance costs are reimbursed, and what protections exist against overblocking.

As Congress races against a tight legislative clock—compounded by the impending departure of key bill sponsors—the debate over site blocking has officially re-entered the American legislative mainstream.

Detailed Chronology: From the Ashes of SOPA to the Dual-Bill Clash

To understand how Washington arrived at two competing site-blocking bills, one must trace the evolutionary arc of recent copyright lobbying and congressional compromise.

The Post-SOPA Chill and the Resurgence of Negotiations

Following the historic 2012 internet blackouts that forced the shelving of SOPA and PIPA, legislative efforts targeting website infrastructure became politically toxic. For years, copyright industries argued that rampant piracy was gutting American creative economies, while civil liberties groups and tech platforms warned that court-ordered site blocking represented a slippery slope toward internet censorship, infrastructure destabilization, and the erosion of network neutrality.

By early 2024, however, behind-the-scenes negotiations began to thaw. Rightsholders intensified pressure on lawmakers, pointing to the widespread adoption of court-ordered site-blocking regimes across Europe, the United Kingdom, and Australia as proof that administrative and judicial blocking could be executed without catastrophic technical failures.

Early Drafts and the Evolution of the ACPA

The path to the ACPA began with discussion drafts circulated late last year. Initially, Rep. Issa’s proposed framework included protective carve-outs for smaller entities, suggesting that any ISP controlling 1% or less of the U.S. broadband market—effectively exempting every provider with fewer than 1.2 million customers—should be spared from blocking mandates.

However, when the ACPA was officially introduced as H.R. 10364, that broad exemption was severely pruned. The final text dropped the market-share threshold down to a mere 100,000 monthly users or subscribers, sweeping a vast array of smaller regional ISPs and commercial VPN services directly into the regulatory crosshairs.

The Birth of the DEFEND IP Act

Concurrently, a parallel effort was brewing across both chambers of Congress. Recognizing that fragmented approaches would stall in committee, Senator Chris Coons, Senator Thom Tillis, and Representative Zoe Lofgren worked to reconcile disparate proposals—specifically Lofgren’s Framework for Accountability and Designation of Pirate Assets (FADPA) and the Senate’s Block BEARD initiative.

The resulting DEFEND IP Act (H.R. 10575) represents a more moderate, highly structured compromise designed to appease consumer advocates and tech platforms while still offering rightsholders a functional tool to sever access to blatant, foreign-based copyright infringers.

Supporting Context & Metrics: A Comparative Analysis of Intermediary Obligations

A granular comparison of the ACPA and the DEFEND IP Act reveals stark contrasts in scope, liability, financial mechanics, and due process protections.

Side-by-Side Legislative Comparison

Intermediary Scope: Who Must Block?

The most immediate friction point between the two bills lies in which internet intermediaries can be hauled into federal court and ordered to disrupt traffic.

• Broadband Providers: Under the ACPA, fixed and mobile broadband providers servicing 100,000 or more monthly users or subscribers in the U.S. are vulnerable to orders. The DEFEND IP Act lowers this subscriber floor to 50,000 subscribers, capturing a wider net of smaller regional and municipal broadband operators.
• Virtual Private Networks (VPNs): This represents a glaring divergence. The ACPA explicitly includes VPN services within its definition of a "service provider," meaning that a commercial VPN boasting 100,000 American users could face a court order forcing them to block specific foreign domains. Conversely, the DEFEND IP Act explicitly excludes entities that exclusively provide VPN services or encrypted routing, as well as encrypted DNS protocols like DNS-over-HTTPS (DoH).
• DNS Resolvers: The ACPA includes all non-exempt DNS resolvers meeting the user threshold. The DEFEND IP Act narrows this focus strictly to public resolvers generating more than $100 million in annual revenue, shielding smaller, private, or non-commercial name resolution services.

Legal Thresholds: What Constitutes a "Pirate Site"?

Both legislative frameworks establish a tripartite test to determine whether a foreign online location qualifies for a blocking order—evaluating whether the site is primarily designed for infringement, marketed to promote infringement, or possesses little legitimate commercial utility. However, the linguistic nuance creates a significant variance in legal standards:

• The DEFEND IP Act sets a stringent bar, requiring rightsholders to prove that the target site has “no commercially significant purpose or use” beyond copyright infringement.
• The ACPA applies a more plaintiff-friendly standard, targeting sites that possess “only limited commercially significant purpose or use” beyond providing access to infringing works.

Furthermore, the ACPA explicitly captures indexing, referencing, and deep-linking services alongside direct host sites by targeting platforms that "provide access to material." The DEFEND IP Act focuses more narrowly on sites designed for the purpose of violating exclusive rights, leaving some ambiguity regarding passive indexers.

The Liability Shield Battleground

For ISPs and technology platforms, the ultimate dealbreaker in any site-blocking regime is legal liability. If an intermediary complies with a blocking order—or fails to catch every instance of infringement—can they be sued for monetary damages by copyright holders?

The ACPA offers a sweeping, proactive liability shield. Under Section 1610(b), any qualifying service provider—regardless of whether they were specifically named in a blocking order—is completely shielded from monetary relief for direct or secondary copyright infringement arising from enabling access to a declared pirate site. The sole exception is if the provider actively conspires with the infringing operators. Crucially, this liability protection takes effect the day the bill is signed, months before the broader regulatory framework becomes operational.

The DEFEND IP Act takes the opposite approach. It contains no piracy-damages shield. Instead, it explicitly clarifies that nothing within the act modifies existing Digital Millennium Copyright Act (DMCA) safe harbors or long-standing principles of secondary liability.

This directly reflects historic negotiations. In prior Senate hearings, major ISP representatives and trade groups demanded retrospective and prospective immunity, arguing that forcing them to act as auxiliary copyright enforcers exposed them to catastrophic litigation. Conversely, major content syndicates like the Motion Picture Association (MPA) argued that such immunity was entirely unnecessary, pointing to foreign jurisdictions where site-blocking laws have not triggered systematic litigation against compliant ISPs.

Financial Mechanics and Cost Recovery

Executing technical blockades—whether via DNS poisoning, IP blacklisting, or SNI filtering—demands operational expenditures. The bills handle this financial burden very differently:

• The DEFEND IP Act leaves cost recovery entirely to judicial discretion. Courts may order petitioners to pay reasonable, direct compliance costs, but the statute explicitly bars reimbursement for capital expenditures, infrastructure upgrades, general overhead, and attorneys’ fees. Furthermore, providers must file itemized cost motions within 60 days.
• The ACPA mandates that courts shall order copyright owners to reimburse providers for commercially reasonable compliance costs. Critically, this reimbursement can include proportionate overhead expenses, such as the salary costs of specialized engineering personnel dedicated to executing the specific blocking order. Additionally, the ACPA requires rightsholders to post a financial bond to protect intermediaries and provides up to $250,000 in statutory compensation for legitimate operators who suffer losses due to erroneous overblocking.

Official Statements and Industry Perspectives

The introduction of the ACPA and the DEFEND IP Act has galvanized lobbying efforts across Capitol Hill, drawing sharp commentary from content creators, internet infrastructure providers, and civil society organizations.

Proponents of the legislation—including major Hollywood studios, record labels, and sports leagues—argue that current enforcement mechanisms are woefully inadequate against sophisticated offshore pirate syndicates that routinely ignore U.S. subpoenas and court judgments.

"Piracy has evolved into a multi-billion-dollar enterprise operated by sophisticated actors operating beyond our immediate jurisdiction," noted representatives from major creative trade associations during recent congressional briefings. "Site blocking is not an extreme measure; it is a proven, necessary tool that has successfully mitigated domestic consumption of pirated live sports, cinema, and television across democratic allies worldwide."

Conversely, internet freedom advocates, cryptographic researchers, and small-ISP trade bodies have raised profound alarms regarding mission creep, collateral censorship, and technical integrity.

Critics emphasize that DNS and network-level blocking are inherently blunt instruments prone to overblocking—where legitimate websites sharing IP addresses or server spaces with targeted pirate domains are inadvertently rendered inaccessible to millions of users.

Furthermore, civil liberties groups have fiercely attacked the ACPA’s inclusion of VPNs, arguing that forcing privacy-centric routing services to log, inspect, or disrupt user traffic fundamentally undermines cybersecurity architecture and compromises the digital privacy of millions of lawful citizens relying on virtual private networks for secure communications.

Future Outlook: The Legislative Horizon

As autumn turns to winter, the immediate fate of both bills hangs in a precarious political balance. The legislative timeline is exceptionally narrow, complicated by the political realities of the current congressional session.

Most notably, primary bill sponsor Rep. Darrell Issa is retiring at the end of the year, and Senator Thom Tillis faces a looming conclusion to his current term in January. For either the ACPA or the DEFEND IP Act to cross the finish line, congressional leadership must rapidly decide whether to forge a compromise text that bridges the stark chasm between the two bills—particularly regarding VPN inclusion, ISP liability shields, and cost-reimbursement mandates—or allow the measures to lapse, forcing a total restart in the next Congress.

If a unified compromise can be struck, the U.S. will cross a major regulatory Rubicon, officially joining the global community of nations enforcing judicial site-blocking regimes. However, if the legislative battle stalls under the weight of industry lobbying and civil liberties opposition, online copyright enforcement will remain tethered to traditional, protracted civil litigation and DMCA notice-and-takedown frameworks—leaving rightsholders searching for alternative avenues to combat foreign digital piracy.