Copyright enforcement against streaming services runs through several mechanisms that are often described as if they were one. A notice sent to a hosting provider, a court order requiring ISPs to block a domain, and a search engine removing a host from its index are different actions with different triggers, different scopes and different timelines. Understanding the difference explains why some sites disappear overnight while others keep reappearing under new addresses.
This article describes the mechanisms at a general level. It is not legal advice, and it does not describe the position of any particular rights holder or service.
Notice-and-takedown in outline
The US Digital Millennium Copyright Act established a framework that most platforms now mirror in some form. A copyright owner sends a notice to a service provider identifying the work, the material said to infringe, its location, their contact details, a good-faith statement, a statement of accuracy under penalty of perjury, and a signature. If the notice is substantially complete, the provider removes or disables access to the material and notifies the uploader.
The provider gains protection from monetary liability for user material when it follows this process, which is why platforms act quickly even when the claim is contested. The incentive is procedural compliance, not adjudication of who is right.
The scope of a notice is deliberately narrow. It identifies a location. On a site with thousands of pages, one notice reaches the pages named in it. That is why rights holders send notices in volume, and why a service that rotates links can stay ahead of a queue of individual URL complaints for a while.
| Mechanism | Who initiates | Scope | Typical timescale | What it removes |
|---|---|---|---|---|
| DMCA notice | Rights holder to host or platform | Named URLs | Days | The identified material |
| Platform enforcement | Store or app platform | An app or developer account | Days to weeks | Distribution, not the file |
| Court blocking order | Rights holder against ISPs | A domain or IP range | Months | Access through those ISPs |
| Search deindexing | Court order or platform policy | A hostname | Weeks | Discovery via search |
| Registrar or host action | Registrar, registry or host | A domain or account | Days to weeks | Resolution or hosting |
URL-level action and its limits
URL-level notices are cheap, fast and precise. They are also easy to work around. A new path on the same host, a new subdomain, or a new host altogether resets the target. For live sport the material is transient anyway: by the time a notice is processed, the event may be over, which is why enforcement focuses on the service rather than on the individual stream.
This is the level at which most day-to-day takedown activity happens, and it is the level described on the DMCA page for this site. A notice that identifies a page here is answered; a notice that identifies a third-party stream is redirected to the party that actually controls it.
Domain-level action
Domain-level action changes the economics. Instead of chasing pages, the rights holder asks a court for an order that requires internet service providers to block access to a hostname. The UK has a specific route for this in section 97A of the Copyright, Designs and Patents Act 1988, and the Premier League has used it repeatedly against streaming domains. Similar blocking orders exist in other jurisdictions, with different procedural thresholds.
A blocking order does not delete the site. It makes the domain unreachable through the ISPs named in the order. The site can move to a new domain, which is why orders are often granted on a rolling basis and why rights holders return to court to add addresses.
Search deindexing is a separate lever. A search engine that removes a hostname from its index does not touch the server, but it removes the route by which most users find it. Deindexing is typically justified by a legal order or by a platform policy against facilitating infringement, and it is harder to reverse than a single URL removal because it applies to the whole host.
Why rotating a homepage is not a defence
A domain-level action attaches to the hostname. Page paths, titles and homepage layouts are irrelevant to it. If a site moves its index from one path to another, the hostname is unchanged, and the order or deindex still covers it.
There are three practical reasons this matters:
- The identifier is the domain. Courts, search engines and blocking lists operate on hostnames and IP ranges, not on the page that happens to be the current front door.
- Discovery is the bottleneck. A site that cannot be found through search loses most of its traffic regardless of what its homepage shows. Rotating content does not restore the discovery path.
- History accumulates. A domain that has received repeated notices and orders carries that record into any assessment of a new complaint. Starting a new path does not reset it.
The same logic applies to apps, with different identifiers. An APK has a package name and a signing certificate. Removing one download page does not change either. A repackaged file with a different signer cannot install over the genuine one, which is why the certificate is the useful identity check and why the download page publishes it.
Counter-notices
A counter-notice is the other side of the US framework. If material was removed and the uploader believes the removal was a mistake or a misidentification, they can send a counter-notification identifying the removed material, stating under penalty of perjury that they have a good-faith belief the removal was mistaken, and consenting to the jurisdiction of a suitable court.
If the counter-notice is valid, the provider may restore the material after 10 to 14 business days, unless the rights holder notifies the provider that it has filed a court action. Restoration is not automatic, and it does not apply where a court has ordered the material removed.
Counter-notices are rare in live sport for an obvious reason: the material has no lasting value once the event ends, and the jurisdiction requirement is a real cost. They are more common for archival or commentary uses, where the material persists and the fair-use question is arguable.
Repeat-infringer policies
The US framework makes a repeat-infringer policy a condition of the safe harbour. The statute does not prescribe a fixed number of strikes; it requires a policy that is reasonably implemented and that terminates subscribers and account holders who are repeat infringers in appropriate circumstances. Platforms implement this with strike counters, escalating suspensions and eventual account termination.
For a streaming service, the practical effect is that the account, the developer account or the domain becomes the unit of enforcement rather than the individual link. That is why a service can lose distribution even when no single page was the subject of a successful claim: the pattern is the evidence.
The EU approach adds notice-and-action obligations through the Digital Services Act, with its own transparency and redress requirements. The terminology differs; the direction is the same.
What this means for a client app
An app that surfaces third-party links sits at a distance from the material, but distance is not immunity. The legal question is whether the service facilitates access to unlicensed content, and the enforcement question is which identifier is easiest to act against.
For users, the practical consequences are:
- availability changes without notice, because sources are removed or blocked;
- a working link can stop working between one evening and the next;
- the app’s own distribution can be affected even when the app hosts nothing;
- the licensed broadcaster in your country remains the only route with a contractual guarantee.
The legal guide covers the framework by country, and the disclaimer states the limits of what this site publishes. Neither replaces advice from a lawyer in your jurisdiction.
The short version
Notice-and-takedown is a URL-level tool. Domain blocking and deindexing are host-level tools. Counter-notices are a procedural remedy with a narrow window. Repeat-infringer policies turn a pattern of complaints into an account-level outcome. Rotating a homepage addresses none of these, because none of them depend on which page is currently at the front.
If you want a stream that does not depend on any of this, the licensed alternatives are the answer, and the free versus paid comparison explains what the difference actually costs.
