US Site-Blocking Bills: What Could Change for ISPs and VPNs?
Two competing proposals would put internet intermediaries at the center of foreign piracy enforcement. Their treatment of VPNs, smaller ISPs and compliance costs differs.
Which internet companies should have to act when a US court targets a foreign piracy website? That question runs through the American Copyright Protection Act (ACPA) and the DEFEND IP Act. A fresh TorrentFreak comparison highlights how differently the proposals would divide responsibility.
What are the two bills trying to do?
Both would create court-based routes to restrict US access to foreign piracy sites. Rep. Darrell Issa introduced ACPA, H.R. 10364. DEFEND IP, H.R. 10575, is the competing bipartisan proposal led in the House by Reps. Zoe Lofgren and Ben Cline.
The reporting reviewed here describes proposals under debate. Readers should distinguish publication of a new analysis from introduction of a new bill: these measures were introduced in September.
ACPA vs DEFEND IP: the practical differences
| Issue | ACPA | DEFEND IP |
|---|---|---|
| ISP threshold | At least 100,000 monthly US users or subscribers. | Broadband providers with at least 50,000 subscribers. |
| VPN providers | Included when the provider meets the threshold. | Excludes providers exclusively offering VPN services or similar encrypted routing. |
| DNS providers | Includes qualifying domain-name resolution providers. | Covers public resolvers with annual revenue above $100 million; excludes services exclusively using encrypted DNS protocols. |
| Compliance costs | Reimbursement of eligible costs is required, subject to possible reduction. Some order-specific staff costs qualify. | Reimbursement is discretionary; capital expenditure, infrastructure, overhead and legal fees are excluded. |
| Piracy damages | Adds a monetary-liability shield for carrying traffic to a designated foreign piracy site, unless the provider actively collaborates in infringement. | Does not add the same broad shield; retains existing liability rules and protections for good-faith implementation. |
Sources: introduced ACPA text, sponsor-published DEFEND IP text, and TorrentFreak’s comparison.
What could change for VPN providers?
ACPA’s definition explicitly includes VPNs, a change also examined in EFF’s ACPA analysis. A qualifying provider could therefore be named in a blocking order. The scope of that obligation would matter to a business whose customers use its service to route traffic through an intermediary.
DEFEND IP’s exclusion turns on what the entity exclusively provides. As TechRadar’s reporting notes, that wording deserves attention where a company offers several kinds of service. It should not be treated as a promise that every business selling a VPN product is exempt.
Neither proposal should be described as a general prohibition on VPN use. The debate concerns which providers could receive blocking orders.
What could change for broadband providers?
A lower subscriber threshold means DEFEND IP would reach some ISPs outside ACPA’s scope. For affected providers, the practical questions would include who handles court notices, how an order is implemented, what happens when a target changes, and how customers can report a mistake.
Those are operational implications of a blocking framework, rather than a forecast of any particular ISP’s response. A provider’s eventual workload would depend on the enacted rules and the orders it receives.
Clear ownership of notices and implementation would help avoid inconsistent responses.
Customers would need useful information when a restriction affects a site they use.
The proposals’ different reimbursement rules make documentation a significant issue.
Courts, costs and safeguards matter as much as the block
ACPA requires a judicial designation followed by a blocking-order process. Its text directs courts to consider technical feasibility, provider burden and incidental harm. It also leaves implementation methods to providers.
The DEFEND IP sponsors describe their proposal as a targeted remedy for foreign piracy operations. They emphasize temporary orders, evidence of harm, ongoing monitoring and protections for providers implementing orders.
Those safeguards are central to the dispute. The Electronic Frontier Foundation argues that blocking whole websites can suppress lawful speech and make challenges expensive. Public Knowledge warns that small businesses and nonprofits may bear the consequences of mistaken blocks, and raises concerns about global DNS services.
These are the positions of supporters and critics. A useful assessment should examine the final safeguards and available remedies rather than assume either perfect enforcement or inevitable failure.
What should broadband customers watch?
There is no reason to infer a change to your plan or bill from publication of these proposals. They do not themselves create new blocking duties. Nor does the evidence establish a specific increase in broadband prices.
If a regime is enacted, the details to watch are its scope, start date, transparency requirements and correction process. How easily can a customer identify a restriction? Who handles a lawful site being affected? How quickly can an error be reviewed?
A site failing to load would not, on its own, establish that a court-ordered block is responsible. Any future coverage should tie an access restriction to a named order or a clear provider notice.

ACPA and DEFEND IP pursue similar anti-piracy goals with different obligations for intermediaries. The final rules would determine the effect on broadband customers.
US site-blocking FAQs
Are these proposals a ban on VPNs?
No. Including a qualifying VPN provider in a court-order framework is different from prohibiting VPN use. ACPA includes qualifying VPN providers; DEFEND IP excludes providers that exclusively offer VPN services or similar encrypted routing.
Would every US ISP have to block websites?
No. The introduced proposals use different provider thresholds, and blocking would depend on a court order. Their precise scope could change during the legislative process.
Does this change my broadband service today?
The proposals themselves do not create new blocking obligations. Any change would depend on legislation being enacted and the applicable court orders and implementation dates.
Sources and further reading
- US Government Publishing Office: H.R. 10364, introduced text — ACPA definitions, court procedure, reimbursement and liability provisions.
- Rep. Lofgren: sponsor-published DEFEND IP bill text — provider definitions, costs, implementation protections and existing liability rules.
- TorrentFreak: comparison of the two bills — DEFEND IP provisions reproduced alongside ACPA; differences in coverage and costs.
- Senator Tillis: DEFEND IP sponsor summary — supporters’ explanation of objectives and safeguards.
- Electronic Frontier Foundation — criticism concerning speech, overblocking and challenges.
- Public Knowledge — concerns about small businesses and global DNS blocking.
- TechRadar — context on the VPN exclusion and its wording.
- EFF: ACPA and VPN providers — analysis of the proposal’s reach and procedural protections.
Editorial note: this comparison concerns the proposals reviewed on 4 October 2026, using ACPA’s introduced text and DEFEND IP’s sponsor-published text. It is not a live congressional status tracker. Amendments or later congressional action may change the position.
