Notable sites hosted on DMCA-ignored / offshore providers
Curated, dated record of well-known websites and services historically hosted on the providers in this directory (or on closely-adjacent offshore providers). Useful for assessing real-world track records when choosing a host: a provider that has weathered hosting WikiLeaks under sustained pressure has a different kind of credibility than a provider with no public incidents on its books.
Updated . Inclusion is editorial; based on publicly reported facts.
Why this list exists
"Has anyone famous used this provider?" is a question we get often. The honest answer is that most legitimate operators don't publicly disclose their hosting choices for operational reasons. But over the years, a number of high-profile sites have either been publicly disclosed as using a particular host, or had their hosting revealed through court records / press coverage. This page compiles those public cases.
The Pirate Bay
- Hosting history: hosted on PRQ (Sweden) for many years; intermittently on other providers after seizures.
- Significance: the most-targeted site in the history of cross-border copyright enforcement. PRQ's continued operation through repeated raids established the modern playbook for free-speech hosting.
- Status: still operational as of 2026.
WikiLeaks
- Hosting history: most famously at Bahnhof's Pionen datacenter (Stockholm, in a former nuclear bunker) from 2010. Also has used PRQ, OVH, Amazon (briefly, before being kicked off), and others over the years.
- Significance: the canonical case for offshore + jurisdiction-resilient hosting. Bahnhof's Pionen became a globally photographed piece of "free-speech infrastructure".
- Status: still operational as of 2026, though Julian Assange's case has shaped much of the surrounding ecosystem.
Sci-Hub
- Hosting history: hosted across various offshore providers; jurisdictionally distributed by design. Has used Russian and East European infrastructure heavily.
- Significance: large-scale academic-paper liberation site, sustained DMCA / publisher-takedown pressure for over a decade. Survived through aggressive multi-jurisdiction architecture.
- Status: operational with ongoing legal battles in multiple jurisdictions.
Z-Library
- Hosting history: distributed across multiple offshore jurisdictions; uses a mix of clearnet and Tor onion services.
- Significance: large book-piracy site that survived a major US-led seizure attempt in 2022 and continues operating from offshore infrastructure.
- Status: operational from rotating infrastructure.
The Internet Archive (clearnet)
- Hosting: not offshore — operates from the US — but is included as a reference point because they have weathered substantial publisher-driven legal pressure under US law.
- Significance: shows that even US-based archives can survive aggressive litigation if structured correctly. Not a direct DMCA-ignored case but adjacent.
SecureDrop deployments
- Hosting history: SecureDrop instances run by major newsrooms (NYT, WaPo, The Guardian, ProPublica, etc.) typically use a mix of in-house infrastructure and offshore-friendly providers for the public-facing announcement layer.
- Significance: the canonical whistleblowing-platform stack. Each deployment is its own architecture but the pattern of "Tor-only intake at offshore host + clearnet announcement at separate jurisdiction" is well-established.
- Status: dozens of active deployments.
Daily Stormer (cautionary case)
- Hosting history: dropped by GoDaddy and Google in 2017, then dropped by Cloudflare in a high-profile policy decision. Subsequently moved through a long series of offshore providers, with each pulling them in turn.
- Significance: cautionary case demonstrating that "offshore" doesn't mean "any host will keep you" — providers (legitimately) refuse content they find objectionable even when not legally compelled.
- Lesson for operators: even DMCA-ignored hosts have AUPs; read them.
Kiwi Farms (cautionary case)
- Hosting history: dropped by Cloudflare in 2022 after sustained advocacy campaigns; subsequently moved through several offshore providers including periods at BuyVM (later dropped), and continues to migrate.
- Significance: similar to Daily Stormer, but a more recent reference case. Demonstrates that even content-permissive offshore hosts will sometimes pull customers under sustained pressure.
- Lesson for operators: have a migration playbook before you need it.
Open-source projects on offshore infrastructure
A number of well-known privacy-tech and free-software projects use the providers in this directory:
- Various Tor relays / exit nodes are operated on FlokiNET, Privex, BuyVM Luxembourg, and HostHatch's non-US locations.
- Mastodon / Fediverse instances run by privacy-focused communities are often hosted on 1984 Hosting or FlokiNET.
- Cock.li (free email service) operates from offshore infrastructure.
- Tahoe-LAFS storage grids are sometimes deployed across multi-jurisdiction offshore VPS combinations.
Patterns observed
From this dataset, a few patterns emerge for operators planning their own infrastructure:
- Multi-jurisdiction is normal: long-running sites use 2-5 hosts across 2-4 jurisdictions, not one provider.
- Migration capacity is essential: every site on this list has migrated providers at least once. Plan for it.
- Tor onion services as backup: many sites maintain a parallel
.onionaddress as failover when clearnet hosting becomes contested. - Domain at one provider, hosting at another: separating the registrar from the host is the norm. Domain at Njalla, hosting elsewhere.
- Public legal-track-record providers (PRQ, Bahnhof, FlokiNET) appear repeatedly because operators value a host that has demonstrably handled pressure.
Inclusion criteria
A site appears on this list if:
- It is publicly known to have used a particular host (via press coverage, court records, or the operator's own public statement).
- The hosting fact is material to assessing the host's track record.
- The site itself is a notable cultural / political reference point (not just any legal-but-controversial site).
We don't include rumors, unverified claims, or sites where the hosting hasn't been publicly disclosed. Suggestions for additions should include a public source — see contact.
Related
- Hosting-incident timeline — dated record of raids, takedowns, pushbacks.
- The state of DMCA-ignored hosting in 2026 — broader landscape essay.
- Use case: journalists — patterns for newsroom infrastructure.
- Use case: whistleblowing platforms — SecureDrop architecture.