The services that lasted
6Cut off following copyright notices
6| Host | Server country | Result |
|---|---|---|
| PrivateAlpsprivatealps.net | Switzerland | Notice no. 8 |
| HostSailorhostsailor.com | Romania | Notice no. 6 |
| FlokiNETflokinet.is | Iceland | Notice no. 2 |
| AlexHostalexhost.com | Not recorded | Notice no. 2 |
| 1984 Hosting1984.hosting | Iceland | Notice no. 1 |
| HostHatchhosthatch.com | Not recorded | Notice no. 1 |
Stopped for other reasons
3| Host | Server country | Result |
|---|---|---|
| Shinjirushinjiru.com | Not recorded | Phishing report. |
| Njallanjal.la | Not recorded | Cut-off related to the domain name. |
| BitHostingbit.hosting | Not recorded | Cut off before any notice. |
Testers’ records. The notice range covers the full period; services cut off early received fewer notices.
triedandtested.org · DATA
The test data
One record per provider: status at the close, server country where established, triggering notice, reason for interruption and recorded aftermath. The data comes from the testers.
To cite this record: triedandtested.org, offshore VPS test from March 1, 2026 to September 1, 2026, updated on September 7, 2026.
Unavailable values remain null in JSON and blank in CSV. Individual counts are not inferred from the overall range.
Cut-off details
Fell to a copyright notice
From most to least resistant, by the notice that triggered the cut-off.
| Host | Server country | Fell at | What happened |
|---|---|---|---|
| PrivateAlpsprivatealps.net No legal entity published | Switzerland | Notice no. 8 | Copyright notice. Copyrighted adult or video streaming material, published without authorisation. The exact type was not recorded for this server.
|
| HostSailorhostsailor.com HOST SAILOR LIMITED — United Arab Emirates | Romania | Notice no. 6 | Copyright notice. Copyrighted adult material, published without authorisation. |
| FlokiNETflokinet.is FlokiNET ehf — Iceland | Iceland | Notice no. 2 | Copyright notice. Copyrighted video streaming material, published without authorisation.
|
| AlexHostalexhost.com AlexHost SRL — Moldova | — | Notice no. 2 | Copyright notice. Copyrighted adult material, published without authorisation.
|
| 1984 Hosting1984.hosting 1984 ehf. — Iceland | Iceland | Notice no. 1 | Copyright notice. Copyrighted adult material, published without authorisation.
|
| HostHatchhosthatch.com HostHatch LLC — United States | — | Notice no. 1 | Copyright notice. Copyrighted video streaming material, published without authorisation. |
Stopped for other reasons
| Host | Server country | Fell at | What happened |
|---|---|---|---|
| Shinjirushinjiru.com Shinjiru International Inc | — | Notice no. 1 | Phishing report. Copyrighted adult or video streaming material, published without authorisation. The exact type was not recorded for this server. |
| Njallanjal.la Njalla SRL — Costa Rica | — | Before any notice | Cut-off related to the domain name. Copyrighted adult material, published without authorisation. Service cut in under 2 days. |
| BitHostingbit.hosting ОсОО «Альянс Торг Компани» — Kyrgyzstan | — | Before any notice | Cut off before any notice. Copyrighted adult or video streaming material, published without authorisation. The exact type was not recorded for this server. |
How the test was run
VPS rented at public prices, without announcing the test. Selected tier: 2 GB of memory.
Countries reported in the records: Finland, Romania, Iceland, Switzerland. Each server’s country appears in the table where established.
Where the notices came from
Protected content was published on the VPS. Rights holders and their automated systems sent the notices; the testers sent none.
Volume and timing varied by service. VPS cut off early received fewer notices.
The figures in this report
Figures from the test and consulted sources, with their calculation methods.
- 15
- offshore VPS hosts rentedSubscriptions paid at the public price, without announcing the test.
- 6
- months of continuous observationFrom 1 March to 1 September 2026.
- 80–100
- copyright notices received per serverSent by the rights holders and their automated systems, not by the testers. Hosts that dropped out early received fewer.
- 6/15
- services still working at the end of the periodService state checked on 1 September 2026. The other 9 had been cut off, each with its reason and the rank of the notice that ended the service.
- 4
- server countriesFinland, Romania, Iceland and Switzerland. The country is the server’s, never the company’s: several of these hosts are established elsewhere. Attributing each instance to its country remains a provider claim, absent independent verification of the routing layers.
- 2 GB
- of memory on the plan chosen everywhereThe same tier at every host, to make comparison possible. At no fewer than four of the six services still running, that tier is the entry plan.
- 5/15
- hosts publishing no dedicated copyright policyReading their terms, acceptable use policies and abuse pages, and testing the usual paths, which return 404.
- 10/15
- hosts publishing the name of a legal entitySearched on contact pages and legal notices. For the other four there is no identifiable recipient, neither for a customer nor for a rights holder.
- 1 hour
- the only numeric removal deadline in European Union lawIt concerns terrorist content and runs from an authority’s removal order. No numeric deadline exists for copyright.
- 6 %
- of worldwide annual turnover: cap on the administrative fineThe sanction for how notices are handled under the Union regime. It depends on no court decision.
- 6
- mandatory elements of a United States noticeA notice that does not substantially comply with them is disregarded when assessing the provider’s knowledge.
- 39
- legal references cited article by articleEach read on its official source, then put through a review tasked with refuting it. References that could not be verified were removed.
“DMCA”: what the word names, and what it does not require
The text the whole industry calls “DMCA” is a United States federal law of 28 October 1998. Its title II inserted section 512 into title 17 of the United States Code, and that is where — and only where — the notice-and-takedown procedure lives.
That procedure is not written as an obligation to remove. Every limb of section 512 opens with the same formula — 17 U.S.C. § 512(a): “A service provider shall not be liable for monetary relief [...] if the service provider” meets certain conditions. Acting promptly after a notice is one of those conditions, not a duty. The text even states expressly, at § 512(l), that “the failure of a service provider’s conduct to qualify for limitation of liability under this section shall not bear adversely upon the consideration of a defense by the service provider”.
So what is presented as the law forcing hosts to take content down is in fact a liability shelter that a host is free not to seek. The United States Copyright Office itself writes that responding to a notice is always voluntary — bearing in mind that this is a public frequently-asked-questions page, an administrative explanation with no normative force, and that the same Office adds that a service targeting United States users may incur liability under United States law.
It would be wrong, however, to conclude that section 512 imposes nothing on anyone. Under § 512(h), the recipient of a properly issued subpoena must disclose the information required, whether or not it acted on any notice: the clerk “shall expeditiously issue and sign the subpoena” and the provider must comply. And the text provides for injunctions under § 512(j) which do bind the provider.
- What “DMCA ignored” actually describes
- A stance towards a mechanism that conditions a liability shelter, not a refusal to obey an obligation to remove. The phrase says nothing about the law applicable to the host, nor about what it will do with a court order.
- What the text does not require
- No monitoring of the service, no active search for infringing material — § 512(m) states that the shelter may not be conditioned on “a service provider monitoring its service or affirmatively seeking facts indicating infringing activity”. Designating an agent with the Copyright Office, often presented as a mandatory formality, is a condition for the hosting limb alone: not designating one forfeits that shelter, it is not a breach sanctioned as such.
- What is not settled
- The United States definition of a service provider contains no criterion of nationality, seat or equipment location. Whether a foreign host can invoke section 512 before a United States court is settled by no text we were able to read. We therefore assert it in neither direction.
- A false statement carries a price
- 17 U.S.C. § 512(f): anyone who “knowingly materially misrepresents” that material is infringing “shall be liable for any damages, including costs and attorneys’ fees, incurred by the alleged infringer [...] or by a service provider, who is injured by such misrepresentation”.
What a notice actually triggers, country by country
In the European Union the framework is the Digital Services Act. It applies wherever a service is offered to recipients located in the Union, whatever the provider’s place of establishment. It neither displaces the United States text nor makes it applicable: these are two regimes answering different questions.
The important point lies elsewhere. Under this regime what counts is not the receipt of a message but what the notice makes it possible to establish. Article 16 of Regulation (EU) 2022/2065 requires notices that “allow a diligent provider of hosting services to identify, without a detailed legal examination, that it is clear that the content is illegal”. An automated, imprecise notice, or one without the exact location of the material, may therefore have no legal effect — while a substantiated notice produces one, whatever its form. The Court of Justice so held on 22 June 2021, in joined cases C-682/18 and C-683/18, under the provision the regulation has since replaced.
Losing the benefit of the exemption is not being found liable. The regulation’s rules determine cases of non-liability; they provide no positive basis. An inactive host exposes itself to the ordinary law, not to an automatic finding against it.
A word on deadlines, because they circulate widely: the only numeric removal deadline in Union law is one hour, it concerns terrorist content, and it runs from an authority’s removal order. The twenty-four or forty-eight hours often presented as standards appear in none of the texts we verified.
- Finland
- Since 17 February 2024 there is no national copyright-specific procedure left: it was repealed, no regulation running parallel to the Union regulation being able to survive. No numeric deadline, only the requirement to act promptly. Compelled removals go through the courts — cessation action, interruption order, interim order that may be made without hearing the alleged infringer, blocking order where the infringer is unknown. The reputation for inertia rests on that requirement of a court decision; it holds up poorly against two findings: those interim orders can be made urgently, and the administrative fine for mishandling notices — up to 6 % of worldwide annual turnover — depends on no court decision at all. We verified no published decision applying these orders to a host: the practice remains unknown.
- Romania
- Of the three, this is the country where the announced regime is the least favourable — the exact reverse of its reputation. On top of the Union regime, Romania kept national obligations the Union regime does not impose: informing the competent public authorities without delay of apparently illegal activity, disclosing on request the data identifying hosting customers, and interrupting on an authority’s order. The implementing norms add informing the authorities within 24 hours of a complaint, and a free electronic complaint procedure published on the provider’s site. Qualification to carry: those norms refer to articles repealed since 18 April 2024, and no source consulted establishes whether they were adapted.
- Iceland
- No formalised national procedure: the one that existed for copyright was repealed in 2019. The applicable regime remains that of the e-commerce directive, transposed in 2002. The Digital Services Act is not applicable there as our sources stand — the Icelandic Ministry for Foreign Affairs’ European affairs database, consulted on 7 September 2026, classifies it among acts under review, with no decision of the European Economic Area Joint Committee; the primary EFTA record was inaccessible to us, so the finding rests on a single source. The consequence: no notice-mechanism obligation, no coordinator, no capped administrative fine. The constraint there is judicial, and it exists: an injunction against hosting data can target the host without it being liable, and breaching it intentionally or through gross negligence is punishable.
- What the Icelandic reputation rests on
- A parliamentary resolution of 2010, which is a mandate to the government with no substantive rule and no provision on hosting, and whose committee report explicitly rejected the idea of an extraterritorial position. What is established in Iceland is not immunity: it is an earlier regime.
What was measured
The records describe service status at the end of the test and, for cut-offs, the trigger. They do not measure individual notice handling or the legal validity of complaints.
Results cover the stated period. Server country and company country are separate data points.
Additional data
Prices paid and notice details for each service still active: unpublished. The legal analysis of Switzerland remains to be completed.
Sources
Official texts cited in the legal analysis.
Sources consulted on September 7, 2026
United States law
- Digital Millennium Copyright Act, Public Law 105-304, 112 Stat. 2860sections 1, 201 and 202(a)www.govinfo.gov
- United States Code, title 1717 U.S.C. § 512(a), (b)(1), (c)(1)(A) to (C), (d)www.govinfo.gov
- United States Code, title 1717 U.S.C. § 512(c)(3)(A)(i) to (vi) and (c)(3)(B)www.govinfo.gov
- United States Code, title 1717 U.S.C. § 512(k)(1)(A) and (B)www.govinfo.gov
- United States Code, title 1717 U.S.C. § 512(l) and § 512(m)(1) and (2)www.govinfo.gov
- United States Code, title 17, and Code of Federal Regulations, title 3717 U.S.C. § 512(c)(2); 37 CFR 201.38(a)www.ecfr.gov
- United States Code, title 1717 U.S.C. § 512(h)(1), (5) and (6); § 512(j)(1)(B)(ii) and (j)(2)www.govinfo.gov
- United States Code, title 1717 U.S.C. § 512(f)www.govinfo.gov
European Union law
- Règlement (UE) 2022/2065 sur les services numériquesarticle 2, paragraph 1eur-lex.europa.eu
- Règlement (UE) 2022/2065 sur les services numériquesarticle 16, paragraphs 1 to 6eur-lex.europa.eu
- Règlement (UE) 2022/2065 sur les services numériquesarticle 6, read with recital 17eur-lex.europa.eu
- Règlement (UE) 2022/2065 sur les services numériquesarticle 56 and recital 123eur-lex.europa.eu
- Directive 2000/31/CE sur le commerce électroniquearticle 2, point (c), and recital 19eur-lex.europa.eu
- Cour de justice de l’Union européenne, arrêt du 22 juin 2021, affaires jointes C-682/18 et C-683/18decided under article 14, paragraph 1, of Directive 2000/31/ECcuria.europa.eu
- Directive 2001/29/CE sur le droit d’auteur dans la société de l’informationarticle 8, paragraph 3eur-lex.europa.eu
- Règlement (CE) n° 864/2007 sur la loi applicable aux obligations non contractuellesarticle 8, paragraph 1eur-lex.europa.eu
- Règlement (UE) 2021/784 relatif aux contenus à caractère terroriste en lignearticle 3, paragraph 3eur-lex.europa.eu
- Directive 2000/31/CE sur le commerce électroniquearticle 5, paragraph 1, points (a) to (d) and (g); recitals 19 and 57eur-lex.europa.eu
Finland
- Tekijänoikeuslaki 404/1961 (Finnish Copyright Act)sections 60 c to 60 ewww.finlex.fi
- Laki 917/2014 (Finnish Act on Electronic Communications Services)section 185www.finlex.fi
Romania
- Legea nr. 365/2002 privind comerțul electronicarticle 16, paragraphs 1 to 6legislatie.just.ro
- Methodological rules approved by HG nr. 1308/2002article 11legislatie.just.ro
- Legea nr. 8/1996 privind dreptul de autorarticle 188, paragraphs 3 and 5legislatie.just.ro
Iceland
- Lög nr. 30/2002 um rafræn viðskipti (Icelandic electronic commerce law)articles 12 to 14 and 18www.althingi.is
- Lög nr. 54/2019articles 1 and 2, repealing the copyright-specific notice procedurewww.althingi.is
- Höfundalög nr. 73/1972 (Icelandic Copyright Act)article 59 a, paragraph 2www.althingi.is
- Þingsályktun nr. 23/138 (Icelandic parliamentary resolution of 2010 and report of the General Affairs Committee)mandate to the government, with no substantive hosting provisionwww.althingi.is
Technical verification
- IANA “IPv4 Address Space” and “Autonomous System (AS) Numbers” registriesPrefix, Designation, WHOIS and RDAP columns; ranges and the assigned regional registrywww.iana.org
- RFC 3912, « WHOIS Protocol Specification »response format and security considerationswww.rfc-editor.org
- RFC 9082 and RFC 9083 (RDAP query and response formats)search URL patterns; JSON response structureswww.rfc-editor.org
- RIPE document ripe-826, IPv4 allocation and assignment policiessections 4.0 (registration requirements) and 6.2www.ripe.net
- RIPE document ripe-705, abuse contact management in the RIPE Databasemandatory abuse-c: attribute and annual validation of abuse-mailbox:www.ripe.net
- RIPE Database documentation, “Descriptions of Primary Objects”inetnum object: status:, org:, mnt-by:, abuse-c:, geofeed: attributesdocs.db.ripe.net
- ARIN Number Resource Policy Manualsections 4.2.3.7.1, 4.2.3.7.2, 6.5.5.1 and 6.5.5.2; definitions in section 2.5www.arin.net
- RIPE NCC, Routing Information Service and RIPEstat platformroute collectors; Routing Status, BGP State and Looking Glass endpointswww.ripe.net
- RFC 9582, « A Profile for Route Origin Authorizations (ROAs) »signed-object profile and validation procedureswww.rfc-editor.org
- RIPE Database documentationcountry: attributedocs.db.ripe.net
- RFC 8805 and RFC 9632 (self-published geolocation feeds)geofeed format and publicationwww.rfc-editor.org
- RFC 9224, RFC 9082 and RFC 9083 (RDAP protocol)service discovery and registration querieswww.rfc-editor.org