A site blocking order is a court injunction that compels internet service providers to stop their subscribers from reaching a specific website. The site itself stays online, untouched, wherever it is hosted. What changes is the on-ramp: on every covered network, the domain simply stops resolving.
This remedy exists for sites whose infrastructure is built to ignore takedown notices: offshore hosting, anonymous operators, registrars that shrug. It is a rights-holder tool, not a government program, you bring the evidence, a court weighs it, and the order lands on the ISPs. It is how hundreds of pirate domains lost most of their audience in the UK, across the EU, and in Australia.
What a site blocking order actually does
A takedown and a block solve different problems. A takedown asks a cooperative host to remove a file or a page; it works one URL at a time, and only where somebody answers. A blocking order removes the audience instead. The ISPs serving a country's internet are ordered to stop their customers loading the site at all, so one order covers every page, every upload, and every future update on the domain, and you stop negotiating with the pirate entirely.
That scale is why blocking suits established operations. Ad-funded piracy is a traffic business: a domain that will not load for most of its market stops earning, stops growing, and starts paying for replacement domains. If you are comparing instruments, how a DMCA takedown notice differs from a court order is the distinction to have straight first.
One limit matters from the outset: the block follows geography, not the site. A UK order does nothing for the same site's audience in the US or Brazil, though the same evidence can support parallel applications elsewhere.
Where courts grant blocking orders
The UK is the oldest and fastest venue. Section 97A of the Copyright, Designs and Patents Act 1988 lets the High Court order ISPs to block sites used to infringe copyright. The first major order came in 2011, against a Usenet indexing site; since then the practice has hardened into routine, with hundreds of domains blocked across the major ISPs. The mechanism survived Brexit; it sits in domestic statute.
Australia runs the closest equivalent outside Europe. Section 115A of the Copyright Act 1968 lets the Federal Court block offshore sites that infringe or facilitate infringement, the standard tool since 2015, with later amendments making it faster to extend an order to mirror domains without filing a fresh case.
The EU works through Article 8(3) of the InfoSoc Directive (2001/29/EC), which requires member states to let rights holders seek injunctions against intermediaries whose services are used by infringers. Germany, France, Italy, Spain and most other member states grant them routinely. The Court of Justice confirmed in 2014 that an ISP can be ordered to block even without proof that its own subscribers infringed, and separately that a linking site can infringe while hosting nothing at all.
Beyond those three, Indian courts grant dynamic injunctions that pick up mirror sites without a fresh case, Singapore blocks, and the list keeps lengthening. The conspicuous exception is the US: Congress has repeatedly considered site-blocking bills, and none has passed. For what works where, including whether a DMCA notice works internationally, the country-by-country takedown playbook covers each jurisdiction's courts, forms, and evidence.
When a blocking order is the right tool
Blocking is the last rung of the ladder, not the first. The profile that justifies it is specific: an established site, real traffic, monetization through ads or subscriptions, infrastructure built to ignore notices, and operators who hop domains when pressed. Courts weigh proportionality, and your strongest input is the record showing cheaper remedies already failed, notices sent, hosts silent, registrars indifferent.
That failure record is what an escalation ladder for copyright removal is designed to produce: every channel tried, every outcome logged. You can run the notice stage yourself for almost nothing. Blocking is where self-help ends and an attorney begins.
It is the wrong tool for one infringing page on an otherwise lawful platform, that is notice work. It is usually wrong against a US-hosted site, which will answer a DMCA notice long before any court date. And it is wasted on a site too small to have an audience worth blocking.
How a blocking application works
Because the respondents are the market's ISPs rather than the pirate, the procedure is shorter and more predictable than ordinary litigation. The shape, in the mature jurisdictions:
- Map the target. Hosting, registrar, traffic scale, existing mirrors, start with how to find out where a site is actually hosted. Courts need technical facts, not impressions.
- Exhaust and document the cheap channels. Notices to the host, registrar, search engines, and advertisers, each with dates and outcomes.
- Instruct local counsel. Blocking is jurisdiction-specific; a UK lawyer cannot file in Sydney, so this is the moment to weigh when to hire a copyright lawyer, the application is attorney work end to end.
- Build the evidence bundle. Sworn statements covering ownership, infringement samples, traffic, and the failure record.
- File against the major ISPs. Practice is to name the handful of largest providers; smaller ones tend to block voluntarily once the order exists.
- Agree the technical schedule. ISPs usually appear, negotiate implementation details, and consent. Contested blocking trials are rare.
- Implement. Blocks go live within days or weeks of the order.
The evidence package courts expect
Applications are decided on written evidence, so the bundle is the case. Courts expect three layers.
First, ownership: chain of title for the works, licenses if you enforce someone else's rights, and any registrations, a US registration carries real evidentiary weight even in foreign courts.
Second, infringement: sampled URLs with dates and captures, enough to show the site's business is infringement rather than a stray page. Judges look for a pattern, a site structured around distributing pirated material, not a lawful site with a problem.
Third, necessity, the layer applicants most often underprepare. Proportionality lives in the notice record: every notice sent, every non-response, every counter-notice, every domain hop. A dated file of ignored and rejected takedowns converts a rights complaint into a blocking case, what to do when takedowns get ignored or rejected is how you build one, and our takedown evidence checklist covers the full inventory.
What the order does at the network level
ISPs implement orders with a familiar stack of techniques. The simplest is DNS tampering: the provider's resolvers stop translating the domain into an address, so the site never loads. IP blocking drops connections to the site's servers outright. Modern orders also work on encrypted traffic: providers read the server-name field in a browser's connection setup and block by hostname, which lets a court block one domain on a shared server without touching its neighbors.
None of this deletes anything. The site still exists; determined users reach it through VPNs, alternate resolvers, or direct IP entry. But the audience that matters, casual searchers, bookmark visitors, referral traffic, mostly does not circumvent. Drops in visits from blocked networks are steep, and operators feel it in ad revenue immediately.
The arms race is the mirror domain. When a blocked operator registers a replacement, rights holders respond with re-blocking applications that append the new domain to the existing order; UK and Indian practice has developed dynamic injunctions that make adding a mirror a short administrative step rather than a new case.
Costs, timeline, and who pays
Blocking is not a free remedy. You are funding a court application, counsel, evidence assembly, and an enforcement relationship after the order exists. The verified comparison is per-unit economics: what takedowns cost run notice by notice, against one order covering an entire site for an entire market.
Timeline is faster than most people expect. A standard application runs weeks to a few months from filing to injunction; implementation then takes days, because the major ISPs already operate blocking systems from earlier orders. Implementation costs have consistently stayed with the ISPs, courts treat blocking as a cost of doing business, while rights holders carry their own application costs. One more expectation to set: this is a relationship, not an event. Sites change domains, orders get extended, and the budget should include enforcement after the injunction.
If your problem sits in the United States
The US has no blocking statute, so the American playbook attacks a stubborn site through its dependencies. Attrition first: notices to the host and to search engines still do real work, because even offshore sites crave search traffic. Infrastructure second: registrars will suspend domains on a credible abuse record, not reliably, but often enough to matter. Then the money: following the money through ad networks and payment processor cutoffs is the closest American analog to a block, since a pirate site that cannot collect or advertise is as good as dead.
Two supporting instruments. A 512(h) subpoena can compel a US service provider holding the site's account or registration information to identify its operator. And criminal-scale operations do sometimes lose their domains to federal seizures, a government action you can refer to, not a remedy you can start.
One point US rights holders miss: you do not need to be British to use a British order. Blocking remedies run with your rights, not your address. If a US company's work is pirated to UK subscribers, that company can apply in the High Court alongside domestic rights holders. The strategic question is where the pirate's audience lives, not where you do.
Special case: live sports and time-critical events
Blocking has one feature nothing else in the kit has: it can move at the speed of the content it protects. A takedown is useless against a boxing match, by the time anything happens, the event is over and the audience has gone. An injunction is the only remedy that helps mid-stream.
English courts pioneered this. Live Premier League orders, granted since 2017, let rights holders identify streaming servers while matches are in progress and have them blocked within the same match window; the orders reach unnamed future servers and are reused event after event. The same machinery now serves boxing pay-per-views and similar windows, where every available hour is the whole harm. How sports blocking orders work covers the mechanics, and the logic now extends to subscription IPTV enforcement, where courts increasingly treat the streaming infrastructure itself as the target.
Frequently asked questions
Can I get a site blocking order in the United States?
No. There is no federal statute authorizing courts to order ISPs to block infringing sites, and the bills that would have created one have all failed. The workable American substitutes are notice-based attrition, registrar pressure, and cutting off the site's revenue. A US rights holder can still pursue blocking abroad, wherever the pirate site's audience lives.
How long does a site blocking order take?
A standard application runs several weeks to a few months from filing to injunction, mostly because ISPs respond predictably rather than fight. Implementation adds only days, since major ISPs already run blocking systems from earlier orders. Live-event injunctions collapse the timeline to days, sometimes the same week they are sought.
What happens when the blocked site moves to a new domain?
The order does not follow automatically, but it can be extended quickly. UK and Indian practice allow mirrors to be appended to an existing order through a short application, and Australian law was amended for the same purpose. Monitoring certificate logs catches replacement domains at issuance, before they go live.
Do I have to prove the ISP's own subscribers infringed?
No. The Court of Justice of the EU held in 2014 that an ISP can be ordered to block a site even without proof that specific customers of that provider used it to infringe. What you must show is that the site itself infringes or facilitates infringement and that blocking is proportionate.
Is a blocking order the same as getting the site taken down?
No. The site and its files stay online and reachable from networks the order does not cover. Blocking removes the audience, not the content, and works at market scale rather than URL scale. Serious campaigns pair the two: takedowns against what responds, blocking against what does not, monitoring for whatever gets rebuilt.
What to do next
- Confirm the fit: an established site that ignores notices, with an audience concentrated in blocking jurisdictions.
- Exhaust the cheap channels and log every result, that record becomes your proportionality evidence.
- Map the target's infrastructure and monetization so counsel gets technical facts, not impressions.
- Get jurisdiction-specific advice where the audience is; the same evidence supports parallel filings.
- Line up mirror monitoring before the order lands, because domain-hopping starts the day the block goes live.
Blocking is the heaviest instrument in private copyright enforcement, and the only one whose effects scale faster than a pirate can rebuild.