DMCA-Ignored Hosting Explained: What It Really Means

"DMCA-ignored hosting" is one of the most misunderstood phrases in the hosting market. Some providers use it as a wink: host anything, nobody will bother you. That reading is wrong, and acting on it can get a server suspended and its owner into real legal trouble.

The accurate meaning is narrower and more useful. A hosting company that operates outside the United States isn't bound by the procedure a US law sets out for takedown notices. When a notice arrives, it is read against the law of the country where the server actually sits, rather than being processed automatically on a timer. Copyright still applies. Courts still apply. Only the automatic part goes away.

This guide covers what the DMCA is, why it doesn't directly govern a server in Iceland or Moldova, what a host like MercureHosting does with a notice, and how to run an offshore project that stays legal. It's a plain-language explainer, not legal advice. If your project has real legal exposure, talk to a lawyer who knows the countries involved.

What the DMCA actually is

The Digital Millennium Copyright Act is a United States federal law passed in 1998. The part that matters for hosting is Section 512 of the US Copyright Act (17 U.S.C. § 512), usually called the safe harbor provisions.

The safe harbor bargain

Section 512 offers online service providers a deal. A provider that hosts material uploaded by its users can avoid liability for money damages for that material, provided it meets certain conditions. The best known of these: when it receives a proper notice that specific material infringes copyright, it has to remove or disable access to that material expeditiously.

A valid notice under the statute has to include certain elements, among them:

• identification of the copyrighted work said to be infringed
• identification of the material said to be infringing, with enough detail to locate it
• contact information for the complaining party
• a statement of good-faith belief that the use isn't authorised
• a statement, under penalty of perjury, that the sender is authorised to act for the rights holder
• a physical or electronic signature

Counter-notices

The user whose material was removed can send a counter-notice saying the takedown was a mistake or a misidentification. If the complaining party doesn't file a lawsuit within the window the statute allows, the provider can restore the material. The statute also creates liability for knowingly misrepresenting that material is infringing, although in practice that remedy is hard to use.

Why US hosts act fast

For a US provider, the safe harbor is extremely valuable, so the rational move is to comply quickly and ask questions later. Many large providers run notices through a semi-automated queue: content comes down first, and the customer's chance to object is a counter-notice after the fact. That's how lawful material such as reviews, criticism, quotations and archives sometimes disappears because of an automated or careless notice.

Why a US notice doesn't bind a non-US server

Section 512 is a US statute. It sets the conditions under which providers can claim a US safe harbor. A hosting company incorporated outside the United States, running hardware outside the United States, doesn't depend on that safe harbor in the same way. A DMCA notice sent to it is, legally speaking, a letter from a rights holder citing a foreign law.

That doesn't make the letter meaningless. It may describe real infringement, and real infringement is illegal in the country where the server is too. What changes is the procedure. The host has no reason to follow the US timetable and form-checking process, and every reason to ask the question that matters locally: does this complaint show infringement that is actionable under the law here?

Copyright is international, the procedure isn't

The Berne Convention for the Protection of Literary and Artistic Works, together with later agreements such as the WTO's TRIPS agreement, means the vast majority of countries protect foreign authors' works under their own copyright law. A film made in the US is protected in Iceland under Icelandic law, and in Switzerland under Swiss law.

So the real difference between a US host and an offshore host isn't "copyright vs. no copyright". It's "US notice-and-takedown procedure vs. the local legal process of the hosting country". Each country decides for itself how complaints reach a host, what a host must do, and what role the courts play.

The location you pick matters

MercureHosting runs servers in seven countries, and none of them is the US. They aren't interchangeable:

• Netherlands and Romania are EU member states. EU rules on hosting liability and notice-and-action apply, now centred on the Digital Services Act. The Netherlands in particular takes notice-and-takedown seriously, so it's a performance location, not a legal-distance one.
• Iceland isn't in the EU but is in the European Economic Area, so a lot of single-market law applies alongside Iceland's own tradition of media protection.
• Switzerland is outside the EU with its own copyright act and data-protection law. Foreign requests generally go through Swiss legal channels. Swiss law is strict, not lawless.
• Panama, Moldova and Russia are outside both the EU and US frameworks, and each has its own copyright and procedural rules. Russia's domestic law has its own content and data requirements, so read its considerations carefully.

If foreign-notice handling is your main reason for going offshore, the non-EU pages are the ones to read first. Our jurisdiction selector scores each location on privacy, speech, latency and price, and the offshore VPS jurisdiction guide goes into the tradeoffs.

What "DMCA-ignored" means at MercureHosting

Our Terms of Service put it in one paragraph: every complaint is reviewed under the law of the country where the server is located. Foreign notices, including US DMCA notices, don't cause automatic takedowns. Where a complaint is valid under local law, we contact you and give you a reasonable chance to respond, unless the law or the severity of the issue requires immediate action. Copyright infringement as defined by the hosting jurisdiction's law isn't allowed. We comply with valid court orders issued in the hosting jurisdiction.

In practice, that breaks down like this.

What DMCA-ignored hosting is not

This is where most marketing goes wrong, so it's worth being blunt.

It isn't permission to pirate

Hosting films, music, software, games or books you don't have the right to distribute is copyright infringement in every country we operate in. It's against our Acceptable Use Policy. If a complaint shows infringement that is actionable under local law, we act on it. A "DMCA-ignored" label doesn't change that, and providers who suggest otherwise are setting their customers up to fail.

It isn't immunity from courts

A valid court order from the hosting jurisdiction is followed. Rights holders who are serious can and do use local courts. Requests from other countries have to go through that jurisdiction's process, which takes time and needs a real legal basis, but it's a process, not a wall.

It doesn't change the law that applies to you

You live somewhere, and your own country's law applies to what you do there, wherever your server is. Choosing an offshore host changes which rules govern the host's handling of a complaint. It doesn't remove your personal legal responsibility for what you publish or distribute.

It doesn't stop other intermediaries

Your server is only one link in the chain. Search engines run their own delisting processes for copyright notices. CDNs, DNS providers, domain registrars, app stores and payment processors each have their own policies, and many act on DMCA notices because they're US companies or have US exposure. A site can stay online on an offshore server and still disappear from search results or lose its CDN. Plan for that.

It doesn't override the rest of the AUP

Some things are suspended immediately in every location, whatever the notice and whatever the country: child sexual abuse material, malware and botnet infrastructure, phishing and fraud, spam, attacks on systems you don't own, and anything else illegal where the server is. Our privacy policy also lists exactly what we keep and how we answer legal requests, so you can see where the limits are.

Who actually benefits from this kind of hosting

If the point isn't piracy, who is it for? The people who gain the most are those whose lawful material gets caught by fast, mechanical takedown systems.

Publishers hit by notice spam

Bulk notices sent by automated systems sometimes target pages that merely mention a title, quote a short passage, or link to an official trailer. Reviewers, critics and small news outlets end up handling complaints that wouldn't survive a careful reading. On a host that reads each complaint against local law, those notices stop being an off switch.

Commentary, criticism and parody

Many legal systems allow some use of copyrighted material without permission: fair use in the US, and various exceptions for quotation, criticism, review, news reporting or parody elsewhere. The details differ from country to country. A process that looks at whether a use is lawful where the server sits, before anything comes down, suits this kind of work.

Archivists and research mirrors

Mirrors of public records, open datasets, historical web pages and research material often attract automated complaints. A sensible pattern is to keep the primary copy in a country whose rules you've actually read, keep a second copy elsewhere, and document where every item came from. The censorship-resistant hosting page covers mirror setups in more detail.

Projects that want jurisdictional diversity

Some operators simply don't want a single foreign legal system to be a single point of failure. Spreading infrastructure across countries with different procedures is ordinary resilience planning, the same reasoning behind offshore hosting generally.

How to stay within the law on an offshore server

A DMCA-ignored host gives you a fairer process. Staying legal is still your job. These habits keep you out of trouble and make any complaint quick to resolve.

1. Know what rights you hold

For everything you host, you should be able to say why you're allowed to: you created it, you licensed it, it's openly licensed (Creative Commons, GPL and so on, with conditions honoured), it's in the public domain, or a specific legal exception applies. If you can't answer, don't host it.

2. Keep records

Store licences, permissions, invoices for stock media and the source of every archived item. A short text file next to each dataset is enough. When a complaint arrives, being able to show a licence in minutes is the difference between a closed ticket and a dispute.

/archive/2026-press-photos/
  SOURCE.txt     where it came from, date retrieved
  LICENSE.txt    licence text or written permission
  NOTES.txt      what was removed or redacted, and why

3. Run your own complaint channel

If you publish user-uploaded content, give people a working way to report infringement to you directly, and respond to it. Fixing a genuine problem yourself is faster and cheaper than having it escalate to your host or a court.

4. Practise takedown hygiene

When a complaint is valid, remove the specific item, not the whole site. Note what you removed and when. When a complaint is wrong, reply with the facts: your licence, the exception you rely on, or the fact that the material isn't what the notice says it is.

5. Respond when we contact you

If we write to you about a complaint, it means we've reviewed it and think it may have merit under local law. Answer through the contact method on your account. Our terms give you a reasonable chance to respond in most cases, but that only helps if you actually use it. Keep your contact address current; a mailbox you've abandoned can't receive the warning.

6. Pick the location deliberately

Read the considerations on each location page before ordering. If legal distance from EU instruments is the goal, an EU location is the wrong fit. If you need low latency across Europe more than legal distance, the Netherlands may be the right call and you accept mainstream EU notice handling with it.

7. Think about the domain too

Your domain name is governed by its registry and registrar, not your host. Country-code domains follow their own national rules, and generic domains follow the registry's policies and the registrar's terms. A registrar that acts quickly on complaints can take a site offline at the DNS level while the server keeps running. Choose the registrar and the TLD with the same care as the server location.

8. Separate the high-risk from the routine

Don't put a controversial archive on the same server as your shop or mail. If one project draws complaints, the others shouldn't share its fate.

How ordering works

If you've read this far and the model fits your project, the practical side is simple. Accounts need only an email address you control; there's no ID upload. You add credit with a manual crypto top-up: pick a coin and network, send to the address shown, and wait for staff to confirm the transfer. Then order a VPS or dedicated server in the country you've chosen and pay from your balance. The step-by-step version is in how to pay for a VPS with crypto, and what no-KYC VPS hosting really means explains what we do and don't ask for.

For workloads that need Windows or a GPU, the same rules apply. The Windows RDP and GPU server checklist covers setup and privacy for those.

Keep an eye on the warrant canary too. It's our standing statement about secret legal orders, updated on a schedule.

The bottom line

DMCA-ignored hosting, described honestly, is a statement about process. A US takedown notice sent to a non-US host is a complaint to be weighed under local law, not an automatic order. That protects lawful publishers, critics, archivists and researchers from mechanical takedowns, and it gives every customer time to respond.

It doesn't make infringement legal, it doesn't stop courts, and it doesn't control what search engines, registrars or payment providers do. Treat it as one layer of resilience, keep your own house in order, and it does exactly what it should.