IP Abuse Contact API

Run in Postman

Overview

The Abuse Contact API provides essential contact information to report abusive activity associated with IP addresses. By querying an IP address (IPv4 or IPv6), users receive detailed abuse contact data, including the responsible organization, contact name and kind, contact emails, phone numbers, and registered address. This enables users to swiftly take action to report and mitigate threats such as spam, DDoS attacks, and phishing.

In addition to abuse-specific contacts, the API also includes registration metadata like the registered country, the contact kind and the route the contact covers. This empowers cybersecurity teams, hosting providers, and compliance entities to take appropriate legal or administrative action.


Lookup Abuse Contact

Abuse contact details of an IP address (IPv4 or IPv6) can be obtained using the endpoint mentioned below:
The URL for this API is https://api.ipgeolocation.io/v3/abuse?apiKey=API_KEY&ip=1.0.0.0 and its default JSON response is shown below:

curl -X GET 'https://api.ipgeolocation.io/v3/abuse?apiKey=API_KEY&ip=1.0.0.0'
Response Preview
1{
2  "ip": "1.0.0.0",
3  "abuse": {
4    "route": "1.0.0.0/24",
5    "country": "AU",
6    "name": "IRT-APNICRANDNET-AU",
7    "organization": "",
8    "kind": "group",
9    "address": "PO Box 3646, South Brisbane, QLD 4101, Australia",
10    "emails": [
11      "helpdesk@apnic.net"
12    ],
13    "phone_numbers": [
14      "+61738583100"
15    ]
16  }
17}

Get Specific Fields

You can customize the API response by using the fields parameter to include only the specific data you need. For example, to retrieve only the emails, specify abuse.emails in the fields parameter as shown below.

curl -X GET 'https://api.ipgeolocation.io/v3/abuse?apiKey=API_KEY&ip=1.0.0.0&fields=abuse.emails'
Response Preview
1{
2  "ip": "1.0.0.0",
3  "abuse": {
4    "emails": [
5      "helpdesk@apnic.net"
6    ]
7  }
8}

Excluding Fields

You can exclude specific fields from the API response (except the ip field) by listing them in the excludes parameter as a comma-separated list. For example, to remove emails from the API response, you can put the keys in the excludes parameter like this.

curl -X GET 'https://api.ipgeolocation.io/v3/abuse?apiKey=API_KEY&ip=1.0.0.0&excludes=abuse.emails'
Response Preview
1{
2  "ip": "1.0.0.0",
3  "abuse": {
4    "route": "1.0.0.0/24",
5    "country": "AU",
6    "name": "IRT-APNICRANDNET-AU",
7    "organization": "",
8    "kind": "group",
9    "address": "PO Box 3646, South Brisbane, QLD 4101, Australia",
10    "phone_numbers": [
11      "+61738583100"
12    ]
13  }
14}

Bulk IP Abuse Contact Lookup Endpoint

The bulk endpoint allows you to look up abuse contact details for multiple IPv4 or IPv6 addresses (maximum 50,000) in a single request.

  • Bulk lookup supports the same query parameters as the single lookup (excludes, fields, and output).

1. Bulk lookup request

Send a POST request and pass the ips array as JSON.

curl -X POST 'https://api.ipgeolocation.io/v3/abuse-bulk?apiKey=API_KEY' \
-H 'Content-Type: application/json' \
-d '{"ips":["1.0.0.0","49.12.0.0"]}'
Response Preview
1[
2  {
3    "ip": "1.0.0.0",
4    "abuse": {
5      "route": "1.0.0.0/24",
6      "country": "AU",
7      "name": "IRT-APNICRANDNET-AU",
8      "organization": "",
9      "kind": "group",
10      "address": "PO Box 3646, South Brisbane, QLD 4101, Australia",
11      "emails": [
12        "helpdesk@apnic.net"
13      ],
14      "phone_numbers": [
15        "+61738583100"
16      ]
17    }
18  },
19  {
20    "ip": "49.12.0.0",
21    "abuse": {
22      "route": "49.12.0.0/20",
23      "country": "DE",
24      "name": "Hetzner Online GmbH - Contact Role",
25      "organization": "Hetzner Online GmbH",
26      "kind": "group",
27      "address": "Hetzner Online GmbH, Industriestrasse 25, D-91710 Gunzenhausen, Germany",
28      "emails": [
29        "abuse@hetzner.com"
30      ],
31      "phone_numbers": [
32        "+4998315053",
33        " +4998315050"
34      ]
35    }
36  }
37]

2. Bulk Lookup with Additional Request Parameters

Use fields when you want to return only specific properties from the abuse object. Use excludes when you want to return the full abuse object but omit certain properties.

I. Using fields Parameter

This example uses the fields parameter to return only the emails from the abuse object: fields=abuse.emails

curl -X POST 'https://api.ipgeolocation.io/v3/abuse-bulk?apiKey=API_KEY&fields=abuse.emails' \
-H 'Content-Type: application/json' \
-d '{"ips":["1.0.0.0","49.12.0.0"]}'
Response Preview
1[
2  {
3    "ip": "1.0.0.0",
4    "abuse": {
5      "emails": [
6        "helpdesk@apnic.net"
7      ]
8    }
9  },
10  {
11    "ip": "49.12.0.0",
12    "abuse": {
13      "emails": [
14        "abuse@hetzner.com"
15      ]
16    }
17  }
18]

II. Using excludes Parameter

This example uses the excludes parameter to return the full abuse object except address and phone_numbers: excludes=abuse.address,abuse.phone_numbers

curl -X POST 'https://api.ipgeolocation.io/v3/abuse-bulk?apiKey=API_KEY&excludes=abuse.address,abuse.phone_numbers' \
-H 'Content-Type: application/json' \
-d '{"ips":["1.0.0.0","49.12.0.0"]}'
Response Preview
1[
2  {
3    "ip": "1.0.0.0",
4    "abuse": {
5      "route": "1.0.0.0/24",
6      "country": "AU",
7      "name": "IRT-APNICRANDNET-AU",
8      "organization": "",
9      "kind": "group",
10      "emails": [
11        "helpdesk@apnic.net"
12      ]
13    }
14  },
15  {
16    "ip": "49.12.0.0",
17    "abuse": {
18      "route": "49.12.0.0/20",
19      "country": "DE",
20      "name": "Hetzner Online GmbH - Contact Role",
21      "organization": "Hetzner Online GmbH",
22      "kind": "group",
23      "emails": [
24        "abuse@hetzner.com"
25      ]
26    }
27  }
28]

3. Bulk Lookup Response for Invalid IPs

In a bulk request, each IP address is processed independently.

Surrounding spaces in each entry are trimmed. If an entry is invalid (non-public, non-routable, or malformed), empty, null, or an IP with no abuse contact in our database, the API returns an object containing only a descriptive message field for that entry along with the valid public IP address responses; the rest of the request still succeeds.

curl -X POST 'https://api.ipgeolocation.io/v3/abuse-bulk?apiKey=API_KEY' \
-H 'Content-Type: application/json' \
-d '{"ips":["10.0.0.0","1.0.0.0"]}'
Response Preview
1[
2  {
3    "message": "'10.0.0.0' is a bogon IP address."
4  },
5  {
6    "ip": "1.0.0.0",
7    "abuse": {
8      "route": "1.0.0.0/24",
9      "country": "AU",
10      "name": "IRT-APNICRANDNET-AU",
11      "organization": "",
12      "kind": "group",
13      "address": "PO Box 3646, South Brisbane, QLD 4101, Australia",
14      "emails": [
15        "helpdesk@apnic.net"
16      ],
17      "phone_numbers": [
18        "+61738583100"
19      ]
20    }
21  }
22]

Abuse Contact Details in Main IP Geolocation API Endpoint

Abuse contact data is available only on the Paid plan of the IP Geolocation API. See the Pricing page for plan details.

You can retrieve Abuse details using the /v3/ipgeo endpoint by adding include=abuse to the query. When requested, the response includes the abuse object along with the default location, country metadata, network, currency, ASN, company, and time zone data. Other optional objects, such as security or user_agent, are returned only when you include them as well (for example, include=abuse,security), and security is charged separately from abuse. See the IP Geolocation API documentation.

Abuse contact details are returned in the /v3/ipgeo response once the abuse object is enabled, as shown below.

curl -X GET 'https://api.ipgeolocation.io/v3/ipgeo?apiKey=API_KEY&ip=49.12.0.0&include=abuse'
Response Preview
1{
2  "ip": "49.12.0.0",
3  "abuse": {
4    "route": "49.12.0.0/20",
5    "country": "DE",
6    "name": "Hetzner Online GmbH - Contact Role",
7    "organization": "Hetzner Online GmbH",
8    "kind": "group",
9    "address": "Hetzner Online GmbH, Industriestrasse 25, D-91710 Gunzenhausen, Germany",
10    "emails": [
11      "abuse@hetzner.com"
12    ],
13    "phone_numbers": [
14      "+4998315053",
15      " +4998315050"
16    ]
17  },
18  "location": {
19    "continent_code": "EU",
20    "continent_name": "Europe",
21    "country_code2": "DE",
22    "country_code3": "DEU",
23    "country_name": "Germany",
24    "country_name_official": "Federal Republic of Germany",
25    "country_capital": "Berlin",
26    "state_prov": "Bavaria",
27    "state_code": "DE-BY",
28    "district": "Cham",
29    "city": "Falkenstein",
30    "zipcode": "93167",
31    "latitude": "49.09745",
32    "longitude": "12.48637",
33    "is_eu": true,
34    "country_flag": "https://ipgeolocation.io/static/flags/de_64.png",
35    "geoname_id": "2927917",
36    "country_emoji": "🇩🇪"
37  },
38  "country_metadata": {
39    "calling_code": "+49",
40    "tld": ".de",
41    "languages": [
42      "de"
43    ]
44  },
45  "network": {
46    "connection_type": "",
47    "route": "49.12.0.0/16",
48    "is_anycast": false,
49    "is_cdn": false,
50    "cdn_provider_name": ""
51  },
52  "currency": {
53    "code": "EUR",
54    "name": "Euro",
55    "symbol": "€"
56  },
57  "asn": {
58    "as_number": "AS24940",
59    "organization": "Hetzner Online GmbH",
60    "country": "DE",
61    "type": "HOSTING",
62    "domain": "hetzner.com",
63    "date_allocated": "2002-06-03",
64    "rir": "RIPE"
65  },
66  "company": {
67    "name": "Hetzner Online GmbH",
68    "type": "HOSTING",
69    "domain": "hetzner.com"
70  },
71  "time_zone": {
72    "name": "Europe/Berlin",
73    "offset": 1,
74    "offset_with_dst": 1,
75    "current_time": "2026-10-29 11:33:57.274+0100",
76    "current_time_unix": 1793270037.274,
77    "current_tz_abbreviation": "CET",
78    "current_tz_full_name": "Central European Standard Time",
79    "standard_tz_abbreviation": "CET",
80    "standard_tz_full_name": "Central European Standard Time",
81    "is_dst": false,
82    "dst_savings": 0,
83    "dst_exists": true,
84    "dst_tz_abbreviation": "GMT+02:00",
85    "dst_tz_full_name": "Central European Summer Time",
86    "dst_start": {
87      "utc_time": "2026-03-29 TIME 01:00",
88      "duration": "+1.00H",
89      "gap": true,
90      "date_time_after": "2026-03-29 TIME 03:00",
91      "date_time_before": "2026-03-29 TIME 02:00",
92      "overlap": false
93    },
94    "dst_end": {
95      "utc_time": "2026-10-25 TIME 01:00",
96      "duration": "-1.00H",
97      "gap": false,
98      "date_time_after": "2026-10-25 TIME 02:00",
99      "date_time_before": "2026-10-25 TIME 03:00",
100      "overlap": true
101    }
102  }
103}

Reference to Abuse Contact API Response

Below, we provide separate tables for each JSON object in the response, listing all possible fields available across the abuse contact endpoint.

FieldTypeDescriptionCan Be Empty?
ipstring

The IP address for which abuse contact details are returned.

No
abuse.routestring

Abuse-handling IP range in CIDR notation (<ip>/<prefix_length>), like 195.39.4.200/29, when available.

Yes
abuse.countrystring

The ISO 3166-1 alpha-2 country code (two uppercase letters) representing the country where the abuse contact is registered, for example CZ.

Yes
abuse.namestring

The name/title of the abuse contact role or team.

Yes
abuse.organizationstring

The name of the organization managing provided IP Address.

Yes
abuse.kindstring

Contact type from registry data, possible values group, individual.

Yes
abuse.addressstring

Registered address of the organization owning the queried IP.

Yes
abuse.emailsarray

List of email addresses for contacting the abuse team.

Yes
abuse.phone_numbersarray

List of phone numbers for abuse contact.

Yes

Error Codes

IP Abuse Contact API returns HTTP status code 200 for a successful API request along with the response.

In case of a bad or invalid request, IP Abuse Contact API returns 4xx HTTP status code along with a descriptive message explaining the reason for the error.

Below is a detailed explanation of the specific HTTP status codes and their corresponding error conditions:

HTTP StatusDescription
200
OK
  • For the abuse-bulk endpoint, an error for one entry (an invalid, empty or null IP, a bogon/private IP, or an IP with no abuse contact in our database) doesn't fail the whole request. Entries are trimmed before lookup. The response is still 200, and that entry in the array is replaced by an object with just a message field.
400
Bad Request

It is returned for one of the following reasons:

  • If the provided IPv4 or IPv6 address is invalid.
  • If special characters [ ] { } | ^ ` are passed in the API URL, either as a parameter or its value, especially in the API key.
  • If the request payload is empty or missing, or the provided JSON does not contain the ips field, or the IP addresses JSON list is empty while querying the abuse-bulk endpoint.
  • If more than 50,000 IP addresses are provided while querying from abuse-bulk endpoint.
  • If the abuse-bulk request body is malformed JSON.
  • If the ips field is not a JSON array of strings.
401
Unauthorized

It is returned for one of the following reasons:

  • An API key is required for this request, but the apiKey query parameter is missing and the request doesn't come from a domain added under Request Origin.
  • If an invalid (a random value) API key is provided, or the request has no API key and its Origin or Referer domain is not registered as a Request Origin.
  • If your account has been locked because of abuse or illegal activity.
  • If you haven't verified the email address on your account.
  • When the request uses an API key associated with a database subscription.
  • When the subscription associated with the API key is paused.
  • If you're making API requests after your subscription trial has expired.
  • The IP Abuse Contact lookup endpoint is called with a Free plan API key.
  • The bulk IP Abuse Contact endpoint is called with a Free plan API key.
  • If the bulk IP abuse contact lookup endpoint is called using Request Origin (CORS) authentication. Bulk requests require an apiKey and cannot be authenticated using Request Origin.
402
Payment Required
  • If your paid subscription's active-until date has passed (one day after it for an active or trialing subscription) and you need to renew or upgrade your subscription. Paused subscriptions and expired trials get 401 instead.
403
Forbidden
  • If the API key has an IP allow-list and the request comes from an IP address that isn't on it.
404
Not Found

It is returned for one of the following reasons:

  • If the IPv4 or IPv6 does not exist in our database.
  • If an IPv4 or IPv6 address is passed as a path variable instead of as a URL parameter (ip=).
  • If an endpoint that does not exist in our API is called.
405
Method Not Allowed
  • If wrong HTTP request method is used for calling the endpoints. Only GET and POST methods are allowed. POST method for abuse-bulk endpoint and GET method for abuse endpoint requests.
413
Content Too Large
  • If the passed data in the POST requests is more than the limit of the API.
415
Unsupported Media Type
  • If the Content-Type header is not set to application/json, while sending a request to the abuse-bulk endpoint.
423
Locked
  • If the passed IP address is from a bogon IP range, or is part of a private network.
429
Too Many Requests

It is returned for one of the following reasons:

  • If the API usage limit has been reached on a Free plan, on an active trial (100,000 API credits), on a paid plan with surcharge usage turned off (it is on by default on all paid plans), or on a subscription with the status 'past due' or 'deleted'.
  • If the surcharge API usage limit has been reached against the subscribed plan.
499
Client Closed Request
  • If the client has set the very short request or connection timeout, leading to the server closing the request prematurely.
5XX
Server Side Error
  • If a 500 (Internal Server Error), 502 (Bad Gateway), 503 (Service Unavailable), 504 (Gateway Timeout), or 505 (HTTP Version Not Supported) status code is returned, it indicates an issue on our end. Please contact us with your request at support@ipgeolocation.io for further assistance.
  • A 503 is returned if your API key can't be verified because of a temporary internal error (message: "We're unable to verify your API key (...) due to an internal error..."). Retry after a short wait.

OpenAPI Specification

The IP Abuse Contact API has an OpenAPI 3.0 specification in JSON and YAML, published in our OpenAPI repository on GitHub. Import it into Postman, Insomnia or another API client, or use it to generate client code. To try the endpoints without any setup, open our Postman workspace.


Other Ways to Use the IP Abuse Contact API

You can also find abuse contacts for IP addresses using our CLI, MCP server, or third-party integration tools.


Frequently Asked Questions

IP address abuse refers to the misuse of IP addresses for harmful activities such as spamming, phishing, DDoS attacks, and unauthorized access attempts.
You can report abusive IP addresses by contacting the responsible organization managing those IPs using the abuse contact information associated with the IP address.
The abuse data is updated daily to ensure accuracy and provide the most current information available.
Abuse contact information allows organizations to report malicious activities directly to responsible parties. It enables them to take swift action to mitigate threats.
Common forms of abuse include activities such as spamming, phishing, DDoS attacks, IP spoofing, and unauthorized IP address scanning and open ports.
IP spoofing involves falsifying IP addresses to disguise malicious activities, making it challenging to trace and prevent unauthorized access.
IP hijacking, also known as prefix hijacking, occurs when unauthorized entities take control of IP address blocks and redirect traffic.
Businesses can implement security measures like firewalls, intrusion detection systems, and monitor network traffic to prevent IP abuse.
IP Abuse Contact API and Malicious Activity Reporting

Looking for features, modules, and use cases? Visit the IP Abuse Contact API page.

Explore IP Abuse Contact API

Subscribe to Our Newsletter

Get the latest in geolocation tech, straight to your inbox.