Blocking an IP protects you but does not stop the attack — the machine simply moves on to other targets. Reporting the address to the responsible network operator often does shut the source down, because behind it there is usually a compromised server whose owner has no idea.
1. Gather the evidence first
A good report is one the abuse team can act on without asking you anything. It should carry:
- The attacking IP address and, where relevant, your target address
- Timestamps with a time zone, ideally UTC. The operator uses the time to work out which customer held the address; without a clear zone, nothing lines up.
- Raw log lines — the originals, not a rewritten summary
- Protocol and port, plus the type of incident (brute force, scanning, exploit attempt, spam)
- Your contact details
Before sending, strip third-party data from the logs that has nothing to do with the incident.
2. Find the right abuse contact
Every IP block has a registered responsible party. An RDAP query returns the managing organization's abuse-c contact — the shortest path to the right mailbox. If the company runs its own abuse form, prefer it: forms are usually processed faster than email. If the address belongs to a cloud provider, the attacking machine is almost certainly one of its customers' servers, and your report will be passed on to them. On IP-DB, every IP profile shows that mailbox on its “Network Information” card as “Abuse contact” whenever the registry lists one — type the address into the search box to get it.
3. Write the report
Keep it short, limited to one incident, and machine-readable. Put the IP address and incident type in the subject line. In the body, one sentence of context and then the raw log lines is enough. Emotional language, threats, or damage claims speed nothing up — they usually slow things down.
4. What happens next
- The operator logs the report and uses the timestamp to identify the customer who held the address.
- The customer gets a warning; for a compromised server, suspension or a demand to clean it up usually follows.
- For severe or repeat cases, service is terminated.
- Getting no reply is normal. Many operators don't respond individually, for privacy and workload reasons — that does not mean nothing was done.
If the attack continues, send exactly one reminder a few days later with fresh evidence, under the same subject. Firing the same incident at several addresses backfires.
5. Escalation paths
If the operator stays silent and the attack persists: notify the upstream provider announcing the block, involve your national CERT/CSIRT, and go to law enforcement where a crime is involved. Regional registries such as RIPE or ARIN police neither content nor conduct; they only care that contact records are current.
6. Report it to the community
Alongside writing to the operator, filing the address in an open reputation database prepares other systems for it too. On IP-DB.com you can submit a category and short description through the report form, and see whether others have already reported the same address. For many entries at once there is bulk reporting.
What not to do
Don't hack back: it is a criminal offence, and the source address almost always belongs to an innocent third party's hijacked machine. Don't try to identify a person from the IP alone either — the accuracy of location data does not support that conclusion.
Comments 0
Share a question, your experience or a correction. You can comment as a registered user or anonymously.
No comments yet. Be the first.