Network and security
Abuse report from Hetzner or OVH: deadline and how to reply
We forward complaints about your server to your e-mail and to a ticket. You need to reply and remove the violation within 24 hours, or access to the server or IP address will be restricted. Below: how to find the cause, what to write in your reply and how to avoid the next complaint.
In short
- The deadline is 24 hours, or less if the data center has shortened it: the exact deadline is in the message. Without a reply in time, access to the server or IP address is restricted (clause 4.5.1 of the offer).
- Access may be restricted immediately, without notice, if attacks, scanning or spam come from the server, it hosts phishing or malware, or the data center requires it (clause 4.5.2).
- A reply has three parts: what you found, what you fixed and how you will prevent it from happening again. Reply in the ticket, and if the data center’s e-mail has a link to a reply form, through that form as well.
- After three justified complaints within 12 months, we may terminate the contract without a refund (clause 4.5.4).
Contents
You will need
- The text of the complaint: it arrives at the e-mail address in your profile and in a ticket in my.abcd.host.
- SSH or RDP access to the server. If access is already restricted, we will request a console for the investigation.
- 30–60 minutes to find the cause.
What a complaint is and how it reaches you
A complaint (abuse report) is a report by a third party, a data center or a public authority about a violation related to your service (section 2 of the offer, “Definitions”). It may come, for example, from the owner of a network that was scanned from your address, from a spam recipient or from a copyright holder. Usually the complaint goes to the data center, Hetzner or OVH, and the data center forwards it to us.
We forward the complaint to the e-mail address in your profile and to a ticket (clause 4.5.1). Data centers’ e-mails are usually in English and include logs: the address, the time, the ports. Sometimes several copies of the same e-mail arrive within a few minutes.
Not every e-mail needs a reply. For example, a notice that your address is under attack and DDoS protection has kicked in only tells you what is happening; you do not need to reply to it. If you are not sure whether there is a deadline, ask in a ticket.
Deadlines and when access is restricted
| Situation | Rule of the offer |
|---|---|
| A complaint has arrived | You must reply and remove the violation within 24 hours, or within a shorter time if the data center has set one: the deadline is stated in the message (clause 4.5.1) |
| No reply in time | Access to the server or IP address is restricted (clause 4.5.1) |
| Access may be restricted at once, without notice | The server hosts child sexual abuse material, phishing or malware; attacks, scanning or spam come from the server; a data center or a public authority requires it; the incident threatens our network or other clients. We tell you the reason within 2 hours after blocking (clause 4.5.2) |
| You disagree with the complaint | Write an explanation in the ticket. We take it into account but make the decision ourselves (clause 4.5.3) |
| When the restriction is lifted | Once the violation is removed (clause 4.5.4) |
| Repeated complaints | After three justified complaints within 12 months, or a violation listed in clause 4.5.2, we may terminate the contract without a refund (clause 4.5.4) |
| Time blocked | Not counted in the SLA and not compensated (clause 4.5.5) |
The offer has a separate rule for blacklists. If our addresses are blacklisted (Spamhaus and similar) through your fault, or you used other people’s IP addresses, the service is suspended immediately. You reimburse our actual costs of delisting and restoring the network’s reputation, including data center invoices, plus an incident handling fee of €425. We provide a breakdown of the costs on request (clause 4.3).
Data center rules apply together with the offer, and where they are stricter, they take precedence (clause 1.4). Hetzner sets short deadlines for replying to complaints, and OVH may suspend a server on a complaint at short notice (Appendix 1 to the offer), so the deadline in the e-mail can be less than a day. If a complaint about the service is received, we may also request proof of identity (clause 5.2).
How to reply to a complaint
Find the address, the time and the substance in the e-mail
Write down the IP address the complaint is about, the time of the events and what exactly they were: scanning, spam, file sharing, a phishing page. Times in logs are often given in UTC; convert them to your time zone. Check the reply deadline as well.
Find the cause on the server
What to check first is covered in the next section.
Remove the violation
Stop the program that is sending mail or scanning, close the service that is open to everyone, delete the files the complaint is about. If the server has been hacked, follow the section “If the server has been hacked”.
Send your reply
Reply in the ticket the complaint came in. If the data center’s e-mail has a link to a reply form, send your explanation through that form too: the data center does not see a reply that is only in our ticket. If there is no link, we will pass the reply from the ticket on to the data center ourselves. What to write is covered below.
If you cannot find the cause in the time given, reply before the deadline anyway: say what you have already done and that you are still looking. There is a sample of such a reply below.
Common causes and what to check on the server
| What the complaint is about | Common cause | What to check |
|---|---|---|
| Port scanning, password guessing (netscan, brute force) | The server has been hacked, and a scanner was launched from it | Processes and outgoing connections |
| Spam, the address is on Spamhaus | A hacked website or mailbox is sending mail, or the mail server accepts mail from anyone | The mail queue, connections to port 25 |
| Copyright infringement (DMCA), torrents | A torrent client is sharing files | Running torrent clients |
| Phishing, malware | Someone else’s pages or files were placed on a hacked website | The files at the address in the complaint, recently modified website files |
| Open proxy, DNS resolver or mail relay | The service is reachable from the internet without authentication | Which ports the server is listening on |
| MAC errors (Hetzner) | A virtual machine in bridged mode goes out to the network without a virtual MAC | The virtual machines’ network: virtual MACs for additional addresses |
| A complaint about an address you have only just been given | The address used to belong to another client | The date the server was delivered: give it in your explanation |
On Linux, start with these commands. The first shows all the services that accept connections and the programs behind them: look for anything unfamiliar and anything that is open to everyone without need, such as databases or proxies.
sudo ss -tulpn
The second shows established TCP connections and the programs holding them. Hundreds of connections to different addresses on port 22 or 3389 look like a scanner or password guessing.
sudo ss -tnp state established
The third shows only connections to mail port 25: if there are many of them and you do not run a mail server, spam is going out from the server.
sudo ss -tnp state established '( dport = :25 )'
The fourth lists the processes that load the CPU the most: scanners and miners are usually at the top of the list.
ps aux --sort=-%cpu | head -n 15
Three more commands show how an attacker may have gained a foothold on the server: root’s scheduled jobs, the keys that allow logging in as root, and successful SSH logins over the last week. Look for unfamiliar keys, jobs and addresses.
sudo crontab -l
sudo cat /root/.ssh/authorized_keys
sudo journalctl --since "7 days ago" | grep "Accepted "
The mailq command shows the mail queue if a mail server is installed on the server. Thousands of messages you did not send are a sign that spam is going out.
On Windows Server, open PowerShell as administrator. netstat -ano shows the connections and the process ID (PID) of each one, and you can find the process by its ID in Task Manager, on the “Details” tab. This command lists the processes that have used the most CPU time:
Get-Process | Sort-Object CPU -Descending | Select-Object -First 15
Windows servers are often hacked by guessing the RDP password. How to close this hole is covered in the article on securing RDP.
If the server has been hacked
Unknown processes, unfamiliar SSH keys and users, logins from unfamiliar addresses mean that an outsider has access to the server. Cleaning up such a system is unreliable: the attacker may have left a backdoor that you will not notice.
The reinstall in step 3 erases all data on the disks. Copy everything you need first and check that the copy opens.
Stop the damage
Kill the process that is scanning or sending mail. If it starts again, boot the server into Rescue: your system does not run there, but the files on the disks are accessible. How to do this is covered in the articles on the Hetzner Rescue System and on Rescue on OVH.
Copy the data you need
Databases, website files, settings. Before you put them back on the server, check that they contain no foreign files or scripts.
Reinstall the system
A clean install removes everything the attacker left behind. A reinstall erases the disks: reinstalling Linux in Robot, reinstalling in the OVHcloud Control Panel.
Change all passwords and keys
The passwords for root and the administrator, control panels, databases and mail, and the SSH keys that were used to log in to the server.
Close the way in
Install updates, allow SSH logins by key only, and leave open only the ports you need. Under the offer, server security is the client’s responsibility, and if the server is compromised through a vulnerability on the client’s side, the client is responsible for the consequences, including complaints and attacks from the server (clause 5.3).
When you are done, describe these steps in your reply to the complaint: they show the data center that the way into the server is closed and the problem will not happen again.
What to write in your reply
Three parts are enough: what you found, what you did and how you will prevent it from happening again. Reply to the data center in English. Write only what you have actually found and done, without guesses. Below is an example for a hacked server that was used for scanning: replace the address and the details with your own.
Hello,
Thank you for the report about 203.0.113.10. We have found and removed the cause.
What happened: someone gained access to the server by guessing a weak SSH password and used it to run a port scanner.
What we did: we stopped the scanner, copied our data and reinstalled the operating system from scratch. All passwords and SSH keys have been changed.
What we changed: SSH now accepts key-based logins only, the firewall allows only the ports our services use, and security updates are installed automatically.
Best regards,
[Your name]
If you have not found the cause by the deadline, reply anyway: say what you have already stopped and when you will send the details.
Hello,
Thank you for the report about 203.0.113.10. We are investigating it. As a first step, we have stopped [the service or process] on the server. We will send you the results by [date].
Best regards,
[Your name]
If you believe the complaint is a mistake, say so and explain why, for example: This IP address was assigned to us on 21 November 2026. The events in the report happened before that date. Send the explanation to the ticket as well (clause 4.5.3).
If access has already been restricted
We will tell you what has been blocked, the address or the whole server, and what the data center asks for in order to unblock it. Send your replies in the ticket or through the form from the e-mail, and we will pass them on right away. If the link to the form does not open after the block, reply in the ticket.
If the investigation needs access to the blocked server, we will request a console. Access is restored once the violation is removed (clause 4.5.4), and the time blocked is not compensated (clause 4.5.5).
What is prohibited on the servers
This is the list from clause 4.2 of the offer. It is prohibited to host on the servers or use them for:
- spam: bulk e-mail, SMS or messenger mailings without the recipients’ consent, and promoting resources hosted on our servers through spam. Mailings are allowed only to subscribers who opted in and can unsubscribe;
- malware: viruses, exploits, botnets, command and control (C&C) servers, distribution of malware;
- prohibited content: anything prohibited by the laws of the Republic of Moldova or of the country where the server is located, including child sexual abuse material, extremist material, and the sale of drugs or medicines without a license;
- copyright infringement: pirated content and torrent trackers with illegal releases;
- attacks and intrusion: DDoS attacks, outgoing port scanning, password brute forcing, phishing, carding, unauthorized access to other systems;
- open services: proxies, mail relays and DNS resolvers available without authentication;
- a commercial VPN or proxy service for third parties;
- cryptocurrency mining on a VPS, and on servers in data centers whose rules prohibit it: Hetzner prohibits mining and blockchain nodes on all servers.
It is also prohibited to use IP addresses that were not assigned to you (clause 4.3). The full text of the rules, including the rules on legal adult content and on VPS load, is in the offer.
FAQ
A complaint came in about an address I have only just been given. What should I do?
I replied in the ticket, but the data center says it has no reply. Why?
How many complaints can I get before the contract is terminated?
Do you compensate for the time the server was blocked?
Did this guide help?
Thank you! This tells us which guides work.
What went wrong?
Tell support at which step you got stuck and include the link to this guide, so you don’t have to explain from scratch.