Who reads the complaintSomebody complained about your site. Here is what happened next.

The abuse desk is the least understood part of hosting and the one most likely to end your project. It is not a legal department and it is usually not a person who read your site. Understanding what it actually is changes how you write to it, and occasionally changes the outcome.

How hosts work · 10 minute read · Published 30 juillet 2026

What it is

At most hosts, abuse handling is a queue worked by people measured on how fast they close tickets. They are not lawyers, they did not choose the policy, and they have a template for almost everything. At scale a decision gets somewhere between twenty seconds and two minutes.

That is not laziness. A large host receives complaints in volumes that make individual consideration genuinely impossible, and the economics point one way: suspending a customer costs the host almost nothing, and defending one costs staff time and legal exposure. Every incentive in the building points at switching you off and moving to the next ticket.

What actually arrives

Complaints reaching a host fall into a few recognisable shapes:

KindUsually fromTypical handling
Automated copyright noticeA monitoring vendorMachine-parsed, forwarded or actioned automatically
Phishing or malware reportA security clearing houseFast suspension, often correctly
Spam reportA blocklist operatorRate-limited or suspended, reputation-driven
A person who is angryAn individualJudgement call, and the one you can influence
Law-enforcement requestAn agencyEscalated, and handled quite differently

The fourth row is where writing well changes outcomes, and it is a bigger share of suspensions than most people assume. A determined individual who sends a well-formatted complaint to an overloaded desk gets results that have nothing to do with whether they are right.

How to write to an abuse desk

  1. Put the answer first. One sentence, at the top, saying what you did or why the complaint is wrong. Nobody reads to paragraph four.
  2. Quote their ticket reference and the specific URL. You are making their queue work easier, which is the only lever you have.
  3. Be concrete about remediation. "Removed at 14:20 UTC, cache purged, here is the log line" closes a ticket. "I take this seriously" does not.
  4. Do not argue the law with someone who cannot apply it. Save that for the escalation, and ask for the escalation explicitly if you need it.
  5. Never be rude. Not for moral reasons — a rude ticket gets the template, and the template is suspension.

The structural problem this reveals

None of the above changes the underlying arrangement: a private company decides, in under a minute, on incentives that are not yours, with no obligation to explain. That works acceptably for phishing and appallingly for anything contested.

The only real fix is structural. If removing your content requires a court order rather than a persuasive email, then a determined complainant has to convince a judge instead of a queue worker, and that changes who wins by default. This is what the phrase "a takedown process that begins with a judge rather than an email" on this site’s footer actually means.

How this desk works

It is worth being concrete rather than making a claim. Here, a complaint is read by an engineer, not a queue. It is answered. It is forwarded to the customer in full, with the complainant named, and the customer gets fourteen days to respond before anything further is considered. Content is removed on a court order from a jurisdiction that reaches the company holding the server, and on nothing else.

Two categories are terminated immediately and without notice, they are named on the acceptable use policy, and that list does not grow. The whole process, with timelines, is on the abuse handling page, and the count of what arrives and what it produced is published quarterly.

Questions people actually ask

Can I find out who complained about me?

At most hosts, no. Here the complaint is forwarded to you in full with the complainant named, because a complaint you cannot see is one you cannot answer.

Is a fast suspension ever the right call?

Yes — phishing pages and active malware harm people in real time and waiting is the wrong answer. The problem is applying that reflex to a contested copyright claim or an angry email.

What if the complaint is simply false?

Answer it in writing, factually, and keep the record. If your host suspends anyway on an unevidenced complaint, you have learned the important thing about your host, and the suspension article is the next step.

Written by the people who answer the notices, and corrected when it is wrong. Last revised 30 juillet 2026.

Every price on this estate is published in full, in one place. See the whole catalogue