Google's EU Copyright Submission: Site-Blocking Safeguards
Google's filing in the European Commission copyright review argues against broad infrastructure-level site blocking while accepting tightly constrained injunctions as a last resort. The submission targets blocks aimed at DNS resolvers, VPNs, CDNs, and shared IP addresses because those layers can carry lawful services unrelated to the alleged infringement. Google submission PDF, retrieved 10 August 2026.
- Commission record
- F33504634
- https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/18172-Report-on-the-review-of-the-2019-EU-rules-on-copyright-and-related-rights-in-the-digital-single-market/F33504634_en | Retrieved 10 August 2026
- Feedback date
- 9 JUN 2026
- https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/18172-Report-on-the-review-of-the-2019-EU-rules-on-copyright-and-related-rights-in-the-digital-single-market/F33504634_en | Retrieved 10 August 2026
- Ares registration
- 3 JUL 2026
- https://ec.europa.eu/info/law/better-regulation/api/download/090166e52ff2de8c | Retrieved 10 August 2026
- Blocking position
- LAST RESORT
- https://ec.europa.eu/info/law/better-regulation/api/download/090166e52ff2de8c | Retrieved 10 August 2026
CORRECTION TO THE APPROVED LEAD
The lead carried a 13 May date. The Commission portal now records Google's feedback date as 9 June 2026, and the attached filing carries Ares registration 6684370 dated 3 July 2026. This article uses the Commission's current primary-source dates. Portal record, retrieved 10 August 2026; filed PDF, retrieved 10 August 2026.
Google's position
Google says injunctions should be subsidiary. A claimant should first show an attempt to reach the infringer, show that notice and takedown was insufficient, and show that removal at the hosting source was ineffective. Submission pages 29-30, retrieved 10 August 2026.
The company argues that orders should target the appropriate layer and source of infringing content. It gives stream-server IPs whose predominant purpose is infringement as an example of a narrower target, while arguing that injunctions should not target global infrastructure such as DNS resolvers, VPNs, or CDNs. Submission page 30, retrieved 10 August 2026.
Why shared infrastructure matters
The filing says a DNS block makes an entire domain inaccessible, including lawful content, and that modern IP addresses are often shared by multiple domains and services. It argues that blocking one shared address can restrict unrelated lawful sites. Submission pages 27 and 30, retrieved 10 August 2026.
Google also says DNS blocks do not remove content and can be bypassed with an alternative resolver. It cites a 2019 Portugal incident in which blocks on Google-hosted virtual IP addresses disrupted Google services and unrelated Cloud customers sharing those addresses. That incident description is Google's account in its own filing. Submission page 27, retrieved 10 August 2026.
The safeguards Google requested
- Evidence of ownership, infringement, and harm should face judicial scrutiny. Submission page 31, retrieved 10 August 2026.
- Decision-makers should assess proportionality instead of automatically converting rightsholder demands into orders. Submission page 31, retrieved 10 August 2026.
- Decisions, reasons, and routes to challenge a block should be transparent to affected users, third parties, and intermediaries. Submission pages 31-32, retrieved 10 August 2026.
- Injunctions should be limited in time, with extensions subject to judicial review of effect and efficacy. Submission page 32, retrieved 10 August 2026.
- Compliance should not require an intermediary to monitor its traffic, and implementation costs should be shared. Submission pages 31-32, retrieved 10 August 2026.
POSITION PAPER, NOT POLICY
Record F33504634 is Google's advocacy in Commission evidence-gathering. The consultation record does not itself create a site-blocking duty, and Google's incident and scale claims in the filing are not Commission findings. Feedback record, retrieved 10 August 2026; Commission initiative record, retrieved 10 August 2026.
Current status
The Commission initiative page remains a closed call for evidence. Google's filed response provides a specific safeguard proposal for any later measure; it is not the later measure. Commission initiative record, retrieved 10 August 2026; Google feedback record, retrieved 10 August 2026.
Sources
- European Commission feedback record F33504634, retrieved 10 August 2026.
- Google submission attachment 090166e52ff2de8c, retrieved 10 August 2026.
- European Commission targeted-copyright initiative, retrieved 10 August 2026.
Frequently Asked Questions
Did Google ask the EU to prohibit site blocking?
No. Google argued that injunctions should be subsidiary, proportionate, evidence-based, reviewable, and aimed away from shared infrastructure such as DNS resolvers, VPNs, and CDNs. Source: https://ec.europa.eu/info/law/better-regulation/api/download/090166e52ff2de8c. Retrieved 10 August 2026.
Why did Google oppose blocking shared internet infrastructure?
Google said domain and shared-IP blocking can also restrict lawful content and unrelated services, and that alternative resolvers can circumvent DNS blocks. Source: https://ec.europa.eu/info/law/better-regulation/api/download/090166e52ff2de8c. Retrieved 10 August 2026.
Is Google publication F33504634 an EU policy decision?
No. It is Google's contribution to Commission evidence-gathering. The Commission portal record is a consultation surface, not an enacted blocking rule. Sources: https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/18172-Report-on-the-review-of-the-2019-EU-rules-on-copyright-and-related-rights-in-the-digital-single-market/F33504634_en and https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/18173-Targeted-initiative-for-a-better-copyright-environment-for-European-creativity-and-innovation_en. Retrieved 10 August 2026.