![\"congress\"](\"https:\/\/www.cryptocabaret.com\/wp-content\/uploads\/2025\/06\/congress-3-600x446.jpg\")
After a decade of focusing efforts overseas, the push for website blocking has landed back on American shores.<\/p>\nAfter a decade of focusing efforts overseas, the push for website blocking has landed back on American shores.<\/p>\n
Earlier this year, U.S. Rep. Zoe Lofgren introduced a new site blocking bill, titled: Foreign Anti-Digital Piracy Act (FADPA). <\/p>\n
With piracy blocking efforts expanding globally, the introduction of a U.S. site blocking bill was perhaps only a matter of time. But it took time. The new bill arrived more than thirteen years after the previous SOPA bill was shut down. Interestingly, however, the bill is not alone. <\/p>\n
In addition to FADPA, Representative Darrell Issa is also working on his own version of a pirate site blocking bill. While it has yet to be formally introduced, a discussion draft framework seen by TorrentFreak lays out the intended framework in great detail. <\/p>\n
It\u2019s important to keep in mind that this is a preliminary draft of the framework, not the final bill. Several changes in the text may take place before it is formally introduced, if it\u2019s introduced at all. <\/p>\n
The draft American Copyright Protection Act (ACPA) proposes a streamlined court procedure for U.S. copyright owners to block access to foreign pirate sites, or those whose U.S. operators cannot be found after reasonable investigation.<\/p>\n<\/p>\n
![\"ACPA\"](\"https:\/\/www.cryptocabaret.com\/wp-content\/uploads\/2025\/06\/ACPA.jpg\")
<\/center><\/p>\nThe site blocking process would involve four phases. First, a court determines if a target website qualifies as a \u201cforeign piracy site\u201d based on evidence presented by a copyright owner. This evidence would include proof of ongoing copyright infringement, details of the site\u2019s foreign ownership (or inability to find a U.S. operator), evidence that piracy is its primary purpose and it has no significant non-infringing purpose, or is marketed to induce infringement.<\/p>\n
In the second phase, the court could issue a blocking order requiring service providers, such as ISPs and DNS resolvers, to take \u201call reasonable steps\u201d to prevent U.S. users from accessing the target website. These orders would remain valid for up to 12 months but would not prescribe specific blocking technologies.<\/p>\n
The draft outlines third and fourth stages which cover how a blocking order would be maintained and modified, if necessary. The deadline for implementing a blocking order would be set at 10 days, but copyright owners could request a shorter timeframe when targeting live events.<\/p>\n
The broad description of the new bill doesn\u2019t differ much from the previously introduced FADPA legislation. Both target ISPs and DNS resolvers, for example, but there are several key differences and nuances. <\/p>\n
For example, ACPA proposes that the Judicial Conference of the United States would maintain a list of specific district judges to hear all judicial piracy blocking cases, with at least one judge per regional circuit. Blocking requests would then go through the previously mentioned four-phase process.<\/p>\n<\/p>\n
![\"\"](\"https:\/\/www.cryptocabaret.com\/wp-content\/uploads\/2025\/06\/venue.jpg\")
<\/center><\/p>\nThe FADPA bill, on the other hand, relies on standard U.S. District Court jurisdiction and would establish a \u2018preliminary order\u2019 through a proposed Copyright Act amendment at section \u00a7502A. <\/p>\n
The new ACPA draft further mentions that the Act would preempt state and local laws, with the Government Accountability Office (GAO) providing reports to Congress on the Act\u2019s effectiveness and impact.<\/p>\n
The draft also has some explicit transparency provisions. For example, it tasks the U.S. Copyright Office with maintaining a public website where all active blocking orders are listed. In addition, copyright owners must demonstrate they attempted to notify the target site\u2019s operator and domain name registry of the infringement.<\/p>\n
The proposed bill also places restrictions on the service providers that can be named in a blocking order, excluding those with fewer than 50,000 annual users or, for ISPs, those representing 1% or less of U.S. market share. Operators of coffee shops, libraries, universities, and other premises, would be excluded.<\/p>\n
Finally, overblocking is addressed directly in the draft. While this should be prevented, if a third party\u2019s site other than the pirate site was blocked due to an error caused by the copyright owner, the third party could request up to $250,000 in compensation from the copyright owner. <\/p>\n
Rep. Issa\u2019s proposed framework excludes blocking measures against the root nameservers<\/a> and TLD nameservers. Additionally, DNS resolvers providing services to fewer than 50,000 users annually would be exempt under the general exclusion for small providers. However, based on commentary in response to foreign DNS blocking efforts, the proposal can expect to meet some pushback. <\/p>\n<\/p>\n This week, the Internet Infrastructure Coalition (I2Coalition), which represents major tech companies including Amazon, Cloudflare, and Google, released a detailed report and website<\/a> warning the public about DNS blocking threats. <\/p>\n<\/p>\n The report details various examples of DNS blocking efforts around the world, including pirate site blocking actions in Italy, Spain, and France. According to Christian Dawson, Executive Director of the i2Coalition, the report is a wake-up call. <\/p>\n \u201cDNS resolvers are neutral infrastructure\u2014not censorship tools. When governments use them to enforce content policies, the result is overreach, disruption, and long-term harm to the open Internet.\u201d <\/p>\n \u201cWe\u2019ve built dnsatrisk.org to document these incidents and to help the global community push back with evidence and clarity,\u201d Dawson adds. <\/p>\n Companies running DNS servers are not alone in their concerns. Internet providers will likely want to ensure that their concerns are heard too. Previously, we reported that ISPs would like to have retrospective immunity. <\/p>\n The discussion draft does indeed mention immunity when it comes to liability for any blocking related actions, plus immunity from copyright claims by rightsholders who request blocking orders, insofar these apply to the blocked sites. <\/p>\n \u201cA named service provider in a blocking order that is implementing the order in good faith is immune from all claims of copyright infringement by the copyright owner who obtained the blocking order based specifically on allegedly infringing activity on the foreign piracy site occurring on or after the date when the blocking order was issued, or when the provider was added to the order after issuance (whichever is later).\u201d <\/em><\/p>\n<\/blockquote>\n The proposed immunity would not carry over to other claims of copyright infringement, meaning there would be no impact on the subscriber-related piracy liability lawsuits currently faced by Internet providers such as Cox and Verizon.<\/p>\n The draft framework explicitly and clearly states that the bill would not affect any existing DMCA liability claims, nor would it impact DMCA safe harbor protections. <\/p>\n \u201cExcept as expressly stated in this Act, nothing in this Act shall be construed to change or affect any determination under the DMCA, or modify or expand any existing claims, liability, or immunity under the DMCA, including the scope, protection, and requirements for any safe harbor under section 512. Nothing in this Act shall be construed to provide for any new liability or immunity with respect to the DMCA or any other provision of law outside of this Act.\u201d<\/em><\/p>\n<\/blockquote>\n Although it\u2019s still unclear what type of retrospective immunity ISPs are looking for, the draft framework doesn\u2019t provide any additional detail.<\/p>\n Overall, the discussion draft describes a well-thought-out plan, with some important transparency provisions and accountability for overblocking. That said, the inclusion of DNS providers and potentially \u2018other intermediaries\u2019 is already causing opposition before the final text is ready. <\/p>\n From: TF<\/a>, for the latest news on copyright battles, piracy and more.<\/p>\n![\"dns\"](\"https:\/\/www.cryptocabaret.com\/wp-content\/uploads\/2025\/06\/dns.jpg\")
<\/center><\/p>\n![\"dns](\"https:\/\/www.cryptocabaret.com\/wp-content\/uploads\/2025\/06\/dnsatrisk.jpg\")
<\/a><\/center><\/p>\nImmunity & the DMCA<\/h2>\n
\n
\n