For more than a decade following the seismic, industry-shaking protests against the Stop Online Piracy Act (SOPA) and the Protect IP Act (PIPA)—which famously triggered coordinated blackouts across major platforms like Wikipedia and Reddit—broadband site blocking remained the third rail of American telecommunications policy. U.S. lawmakers systematically avoided the subject, wary of colliding with Silicon Valley heavyweights, digital rights advocacy groups, and the open-internet coalition.
That political taboo shattered late last year. In a sudden flurry of legislative activity, two distinct pirate site-blocking bills were introduced in the U.S. Congress within a span of just ten days. The introduction of these measures signals a profound, bipartisan shift in Washington’s approach to digital copyright enforcement, aligning the United States more closely with European, Asian, and Commonwealth nations that have long relied on dynamic domain name system (DNS) and Internet Service Provider (ISP) blocking to combat overseas digital piracy.
The first of these legislative vehicles is the American Copyright Protection Act (ACPA), introduced by Representative Darrell Issa (H.R. 10364). The ACPA proposes a comprehensive enforcement mechanism that empowers federal courts to issue injunctions compelling ISPs, public DNS resolvers, and Virtual Private Networks (VPNs) to restrict access to foreign pirate domains.
Ten days later, a formidable bipartisan coalition introduced the DEFEND IP Act (H.R. 10575) in the House and Senate. Spearheaded in the House by Representatives Zoe Lofgren and Ben Cline—and backed in the Senate by Senators Thom Tillis, Chris Coons, Marsha Blackburn, and Adam Schiff—the DEFEND IP Act represents a deliberate consolidation of prior legislative efforts, merging Lofgren’s FADPA (Freedom and Preservation of Digital Access) proposal with the Senate’s Block BEARD initiative into a unified statutory framework.
While both bills share a foundational philosophy—leveraging federal courts to target foreign-operated pirate infrastructure while leaving the technical implementation up to network intermediaries—they diverge dramatically in their mechanics. These disparities touch upon every critical facet of site-blocking governance: the scope of targeted intermediaries, the statutory definition of a pirate destination, liability shields for telecom operators, cost reimbursement formulas, overblocking penalties, and judicial oversight.
As Congress wrestles with these competing models, the outcome will fundamentally reshape the contours of the American internet, defining the obligations of network operators and the boundaries of digital expression for years to come.
Detailed Chronology: From SOPA’s Shadow to the 2025 Legislative Clash
To understand the sudden emergence of the ACPA and the DEFEND IP Act, one must trace the winding legislative path that brought Capitol Hill to this juncture.
The Post-SOPA Chill
In the wake of the 2012 SOPA/PIPA collapse, the copyright industries—principally the Motion Picture Association (MPA), the Recording Industry Association of America (RIAA), and various publishing houses—found themselves politically isolated. Lawmakers internalized the lesson that any broad legislative proposal granting the government or private rightsholders the power to alter the core routing architecture of the internet invited massive public backlash. Consequently, anti-piracy efforts pivoted away from statutory site-blocking mandates toward voluntary initiatives, such as the Trusted Not to Surf (TNS) program, payment processor blacklists, and targeted civil litigation under existing copyright statutes.
The Groundwork: 2024 Discussions and Drafts
As international jurisdictions—including the United Kingdom, Australia, and the European Union—routinely demonstrated the efficacy of structural site-blocking injunctions in reducing domestic piracy rates, U.S. rightsholders renewed their lobbying efforts in Washington.
By early 2024, preliminary legislative discussions began to leak. Early drafting sessions revealed a deep tension between rightsholders, who demanded sweeping enforcement tools, and Internet Service Providers, who feared crushing operational costs and potential secondary copyright liability.
In May 2025, during a high-profile Senate Judiciary Committee hearing, Senator Chris Coons candidly illuminated the primary roadblock preventing a unified legislative breakthrough:
"It finally feels like we’re making some real progress here on site blocking after years. One of the key roadblocks to getting a final deal is whether ISPs should benefit from immunity, both prospectively and retrospectively."
During the same hearings, Karyn Temple, Senior Executive Vice President and Global General Counsel for the MPA, pushed back against the ISPs’ demands for retrospective immunity, arguing that international precedents showed ISPs were rarely, if ever, subjected to predatory litigation for complying with blocking orders:
"ISPs have not routinely been sued for enforcing site blocking regimes. So, you know, I think in our experience, we don’t think that this is a provision that is necessary at all."
The Legislative Eruption
Despite these lingering disagreements, the legislative dam broke late last year. Representative Darrell Issa unveiled the ACPA, featuring a surprisingly expansive scope that included a broad liability shield and mandatory cost reimbursement. Just over a week later, the Lofgren-Tillis coalition countered with the DEFEND IP Act, opting for a more surgically targeted approach that excluded standalone VPNs, preserved traditional secondary liability frameworks, and restricted financial reimbursements.
With key legislative sponsors facing imminent departures—Representative Issa announced his retirement, and Senator Tillis’s term concludes early next year—the pressure on Capitol Hill to reconcile these two bills or advance a single consensus vehicle has reached a critical juncture.
Supporting Context & Metrics: A Comparative Breakdown of the Bills
A granular examination of H.R. 10364 (ACPA) and H.R. 10575 (DEFEND IP Act) reveals stark contrasts across multiple legal and operational dimensions.
Dimension
ACPA (H.R. 10364)
DEFEND IP Act (H.R. 10575)
VPN Intermediaries
Covered (Any VPN with $ge$ 100,000 monthly users)
Excluded (If operating exclusively as a VPN)
ISP User Threshold
$ge$ 100,000 monthly users or subscribers
$ge$ 50,000 subscribers
DNS Resolvers
Covered (Subject to user thresholds)
Limited (Public resolvers with > $100M in annual revenue only)
Yes (Comprehensive shield for all providers from day one)
No (Relies on existing DMCA safe harbors and secondary liability principles)
Cost Reimbursement
Mandatory (Court must order; covers specialized staff overhead)
Discretionary (At court’s discretion; excludes overhead, infrastructure, and legal fees)
Rightsholder Bond
Required (To cover wrongfully enjoined entities)
Not Required
Overblocking Penalty
Up to $250,000 (For rightsholder-induced errors)
None (Provides a mechanism to fix orders, but no statutory damages)
Judiciary Assignment
Dedicated roster of designated district judges
Any appropriate federal district court
1. Who Has to Block? Intermediary Scope
The most polarizing divergence between the two proposals lies in which network intermediaries can be conscripted to enforce a blocking order.
The ACPA Approach: Under Issa’s bill, any broadband access provider, DNS resolver, or Virtual Private Network (VPN) boasting 100,000 or more monthly users or subscribers in the United States can be legally compelled to implement blocking measures. Notably, this represents a significant expansion from early discussion drafts, which had proposed exempting any ISP with 1% or less of the U.S. market share (a threshold that would have shielded virtually every provider with fewer than 1.2 million customers). Root nameservers and top-level domain (TLD) registries remain exempt.
The DEFEND IP Approach: The Lofgren-Cline-Tillis bill lowers the subscriber threshold for traditional broadband providers to 50,000 subscribers, thereby capturing a wider array of regional and smaller-scale ISPs. However, it implements strict limitations on other intermediaries. Public DNS resolvers are only captured if they generate more than $100 million in annual revenue, and services utilizing encrypted DNS protocols (such as DNS-over-HTTPS or DoH) are shielded. Most importantly, the DEFEND IP Act explicitly excludes entities that exclusively provide VPN services or encrypted routing tunnels.
2. The Pirate Site Legal Test
Both bills establish a three-prong statutory test to determine whether a foreign-located online destination meets the threshold of a "pirate site," allowing rightsholders to petition for blocking orders. However, the legal bar for establishing guilt differs subtly but critically:
DEFEND IP Act Standard: Requires rightsholders to prove that the targeted foreign location has "no commercially significant purpose or use" other than copyright infringement. This is an absolute standard.
ACPA Standard: Adopts a lower threshold, targeting sites that possess "only limited commercially significant purpose or use" beyond providing access to infringing materials. Furthermore, the ACPA explicitly targets sites that "provide access to material that violates an exclusive right," encompassing pure linking and indexing directories alongside direct hosting operations. The DEFEND IP Act uses language primarily focused on sites designed for the purpose of violating rights, introducing ambiguity regarding third-party indexing sites.
3. The Liability Shield Controversy
The single most contentious policy battleground is the question of post-blocking legal immunity.
ACPA’s Comprehensive Immunity: The ACPA includes an expansive liability shield. Once a court declares a site to be a foreign piracy site, any service provider—whether specifically named in the blocking order or not—is completely shielded from monetary damages for direct or secondary copyright infringement arising from enabling access to that site. This protection takes effect on the day the bill is signed into law, months ahead of the operational enforcement mechanisms.
DEFEND IP’s Status Quo: The DEFEND IP Act rejects retrospective and sweeping prospective immunity. It explicitly states that nothing in the bill modifies the Digital Millennium Copyright Act’s (DMCA) Section 512 safe harbors or established principles of secondary copyright liability. Providers acting in good faith to comply with an order are shielded from claims brought by the blocked site operator, but they receive no broad blanket protection against copyright holders.
Official Statements and Industry Perspectives
The introduction of these opposing bills has galvanized a diverse coalition of telecommunications companies, tech advocacy groups, and content creators, each mobilizing to shape the final legislative language.
Content Creators and Rightsholders
The film, music, and publishing industries have enthusiastically endorsed the concept of federal site blocking, viewing it as an indispensable tool against sophisticated, offshore piracy syndicates that routinely evade traditional domestic civil litigation.
Proponents argue that voluntary measures and individual copyright lawsuits are like playing an endless game of "whack-a-mole," as rogue operators instantly spin up mirror domains and change IP addresses the moment a judgment is handed down. Network-level blocking, they contend, provides the systemic friction required to severely degrade the economic viability of commercial piracy.
Internet Service Providers and Tech Intermediaries
ISPs, while recognizing the inevitability of some form of site-blocking legislation, remain deeply divided over the financial and legal burdens involved. Major telecommunications lobbies have consistently argued that if the federal government is going to deputize private companies as the enforcement arms of copyright holders, those companies must be fully indemnified against liability and reimbursed for every penny of compliance expenditure.
The inclusion of VPNs in the ACPA has also drawn fierce opposition from privacy advocates and cybersecurity groups. Representatives from the VPN industry argue that forcing privacy-centric routing services to log, filter, or block traffic undermines the foundational encryption protocols that protect everyday internet users from corporate surveillance, government overreach, and malicious cyber actors.
Future Outlook: The Path Ahead for U.S. Site Blocking
As the 119th Congress progresses, the fate of U.S. site-blocking legislation hinges on a high-stakes legislative reconciliation process. Lawmakers are faced with two fundamentally incompatible statutory visions:
The Broad, Pro-Enforcement Model (ACPA): Favors expansive intermediary reach (including VPNs and medium-sized ISPs), a lower legal threshold for pirate classification, mandatory cost reimbursement including staff overhead, rightsholder bonds, and a sweeping liability shield for network operators.
The Targeted, Balanced Model (DEFEND IP Act): Favors a narrower intermediary footprint (excluding standalone VPNs), a stricter "no commercial purpose" test, discretionary cost recovery excluding overhead and legal fees, preservation of existing DMCA liability standards, and broad judicial discretion.
Compounding the legislative complexity is the impending departure of key congressional champions. With Representative Darrell Issa retiring and Senator Thom Tillis facing the conclusion of his term, the institutional momentum behind these bills carries an expiration date.
Whether leadership opts to merge the two proposals into a hybrid compromise bill—or whether one framework ultimately eclipses the other—will depend on intense backroom negotiations between telecom lobbyists, content industries, and civil liberties advocates. What remains certain is that the decade-long quiet surrounding U.S. site blocking has definitively ended. The legislative machinery is in motion, and the architecture of the American internet is poised for its most consequential regulatory evolution in a generation.