Fraud and risk scores
How to Find the Abuse Contact for an IP Address
A practical guide to finding the right abuse contact when an IP is involved in spam, scanning, fraud, or attacks.
- Author
- Mojahid Ul Haque
- Updated
- Reading time
- 6 min read
When abuse contact lookup helps
Abuse contacts are the right route when an address is involved in spam, credential attacks, port scanning, scraping, malware callbacks or a violation of the operator's own terms. The goal is to reach the network operator or hosting provider responsible for the address range, who can look at the account behind it, not to identify a private person from the address alone, which the registry data cannot do and the operator will not do for you.
Two cases call for a different first step. If the problem is a website or email domain rather than a bare address, the domain's own abuse mailbox applies as well: RFC 2142 reserves the abuse mailbox name at every domain for reports of inappropriate public behaviour. And if the traffic is a handful of failed logins or a scan that your firewall already handled, a report will cost the operator more than it saves; reserve reports for sustained or damaging activity, and keep the firewall blocking guide for the rest.
Where the abuse contact lives: RDAP
The registries publish abuse contacts as part of the registration record for each address block. In RDAP, the JSON successor to WHOIS defined in RFC 9083, the record carries entity objects with roles, and the abuse role is defined as the entity that handles network abuse issues on behalf of the registrant. Querying the registry's RDAP service for the address returns the block and, with it, the abuse entity's contact details.
A worked example: querying ARIN's RDAP service for 8.8.8.8 returns the block registered to the organisation GOGL (Google LLC) and an abuse entity with the handle ABUSE5250-ARIN, which carries the mailbox to use. To find which registry serves an arbitrary address, start at IANA's RDAP bootstrap file for IPv4 (data.iana.org/rdap/ipv4.json), which maps address ranges to the responsible registry's RDAP base URL. The WHOIS and RDAP guide walks through the query itself; this page is about what to do with the contact once you have it.
How each registry records it
The five regional registries store the contact in slightly different shapes, which matters when you read a raw record. RIPE NCC uses an abuse-c attribute on the organisation object that references a role object holding an abuse-mailbox attribute, and requires every organisation object linked to a resource to carry one. APNIC uses an irt (incident response team) object in which the abuse-mailbox attribute is mandatory. ARIN attaches point-of-contact records to each registration, including an abuse contact, which its Whois and RDAP services return with the network record.
LACNIC and AFRINIC publish abuse contacts in their own databases, reachable through the same IANA bootstrap. Whatever the shape, the contact belongs to the block holder as recorded at the registry, which may be an ISP, a hosting company, a cloud provider or an enterprise, and is the party expected to act.
Sub-allocations, referrals and provider forms
Address blocks are often reassigned downwards: a registry allocates a large block to an ISP, which assigns a smaller block to a hosting customer, which may record its own contact. The most specific block that covers the address usually carries the most useful contact, because that is the party closest to the machine. If the record shows a parent and a child block with different contacts, report to the child first and copy the parent only if nothing happens. Where the registry data points to another regional registry, follow the referral and query there.
Large operators usually prefer a web form to the registered mailbox and say so in their records or documentation. AWS asks for reports through its abuse form and offers an email route for automated reports; Cloudflare publishes its own abuse process, and because its addresses are normally a proxy in front of someone else's origin, a report about a Cloudflare address goes through that process rather than to a hosting customer. The Cloudflare proxy guide explains why the address you see is not the site's own.
What a usable report contains
A report that gets acted on is short, factual and verifiable: the address, the exact timestamps with their timezone (UTC in RFC 3339 form removes any ambiguity), the destination ports or URLs, request identifiers, the relevant headers, a few raw log lines showing the behaviour, what you are asking for (investigate, stop, or confirm), and a way to reach you. Send one report per incident rather than one per log line, and do not attach the whole log; an operator wants enough to match the activity against their own records, not a forensic archive.
Keep the original logs rather than screenshots, and keep them unmodified: raw lines with their timestamps can be matched against the operator's records, and a shared-address operator cannot act at all without them. The incident-response triage checklist covers how to preserve evidence so that the report rests on records you can still produce later. Precision matters most where the address is shared: a VPN provider can only enforce its own terms, a Tor exit operator learns nothing about the user from your report, as the Tor exit guide explains, and an ISP running carrier-grade NAT can usually only trace a connection with the exact timestamp and source port, which is why the CGNAT guide stresses precise logging.
For email abuse there is a standard container: RFC 5965 defines the Abuse Reporting Format (ARF), the machine-readable format mail receivers use to send feedback about abusive messages, and many providers accept it directly. Whatever the format, include only the personal data the report needs; your logs may contain other visitors' addresses and account details, and the privacy-safe logging guide covers how to trim an excerpt.
Sources
- RFC 9083: JSON Responses for the Registration Data Access Protocol (RDAP)
- RFC 2142: Mailbox Names for Common Services, Roles and Functions
- RFC 5965: An Extensible Format for Email Feedback Reports (ARF)
- RFC 3339: Date and Time on the Internet: Timestamps
- RIPE NCC: abuse-c Information
- APNIC: irt object template
- ARIN: Point of Contact Records
- ARIN: Using Whois
- IANA: RDAP bootstrap file for IPv4 address space
- ARIN RDAP: record for 8.8.8.8
- AWS re:Post: Report abuse of AWS resources
- Cloudflare: Abuse approach
Frequently asked questions
Keep reading
Related guides
- IP lookup essentials5 min read
How to Find Someone's IP Address: A Simple Guide
Where IP addresses legitimately show up (email headers, server logs, game hosts), how to look one up, and the limits of what the result can tell you.
Updated
- ISP, ASN and network ownership8 min read
IP WHOIS and RDAP Lookup: What They Show and When to Use Them
Geolocation estimates where an IP is used; WHOIS and RDAP record who holds it and whom to contact about abuse. When to use each during an investigation.
Updated
- Fraud and risk scores3 min read
IP Fraud Score: What the Numbers Actually Mean
A plain-language guide to reading IP fraud scores — what the 0–100 scale means, what triggers a high score, and how to use it without over-blocking.
Updated
- Fraud and risk scores6 min read
IP Risk Score Explained: How Fraud Teams Use It to Stop Bad Actors
What goes into an IP risk score, how fraud teams combine it with geolocation, proxy and blocklist signals, and why the score is evidence rather than a verdict.
Updated