> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/abuseipdb.md).

# AbuseIPDB

Check IP and CIDR reputation and report abusive addresses to the AbuseIPDB community database.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| AbuseIPDB | API key        |

#### AbuseIPDB

Connect AbuseIPDB with an account API key to check and report IP reputation.

**Set up in AbuseIPDB**

1. Prepare the AbuseIPDB account or service that the workflow will access. Grant access to the required resources and operations.
2. **API key:** Create an API key on your AbuseIPDB account's API page (Account > API). One key per account; it grants everything your subscription tier allows.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **AbuseIPDB**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required | What to enter                                                                                                                                                                                                    |
| ------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| API key       | Yes      | Create an API key on your AbuseIPDB account's API page (Account > API). One key per account; it grants everything your subscription tier allows. [Provider instructions](https://www.abuseipdb.com/account/api). |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **AbuseIPDB** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### Check IP Reputation

Look up an IP address and get its abuse confidence score, country, ISP, and how often it was reported. Each run uses one lookup from your AbuseIPDB daily check quota.

**Inputs**

| Field                   | Type    | Required | Description                                                                                |
| ----------------------- | ------- | -------- | ------------------------------------------------------------------------------------------ |
| IP address              | string  | Yes      | The IPv4 or IPv6 address to check.                                                         |
| Look-back window (days) | integer | No       | Only count reports from this many days back (1-365). Leave empty for 30 days. Default: 30. |

**Outputs**

| Field                  | Type     | Description                         |
| ---------------------- | -------- | ----------------------------------- |
| IP address             | string   | The address checked.                |
| Is public              | boolean  | Is public.                          |
| IP version             | integer  | IP version.                         |
| Is whitelisted         | boolean  | Is whitelisted.                     |
| Abuse confidence score | integer  | 0-100 likelihood the IP is abusive. |
| Country code           | string   | Country code.                       |
| Usage type             | string   | Usage type.                         |
| ISP                    | string   | ISP.                                |
| Domain                 | string   | Domain.                             |
| Hostnames              | array    | Hostnames.                          |
| Is Tor exit node       | boolean  | Is Tor exit node.                   |
| Total reports          | integer  | Reports in the window.              |
| Distinct reporters     | integer  | Distinct reporters.                 |
| Last reported at       | datetime | Most recent report time.            |

#### List IP Reports

List the individual abuse reports filed against an IP address, up to 100 per run. Each run uses one call from your AbuseIPDB daily reports quota.

**Inputs**

| Field                   | Type    | Required | Description                                                                               |
| ----------------------- | ------- | -------- | ----------------------------------------------------------------------------------------- |
| IP address              | string  | Yes      | The IPv4 or IPv6 address whose reports you want.                                          |
| Look-back window (days) | integer | No       | Only list reports from this many days back (1-365). Leave empty for 30 days. Default: 30. |
| Start page              | integer | No       | Continue from an earlier result's next page. Leave empty to start at the newest reports.  |

**Outputs**

| Field         | Type          | Description            |
| ------------- | ------------- | ---------------------- |
| Reports       | object\_array | Reports.               |
| Total reports | integer       | Total in window.       |
| Next page     | integer       | Page to continue from. |

#### Check CIDR Block

Check a whole subnet and list the addresses in it that were reported for abuse. The free plan accepts networks up to /24. Each run uses one call from your AbuseIPDB daily block-check quota.

**Inputs**

| Field                   | Type    | Required | Description                                                                                                     |
| ----------------------- | ------- | -------- | --------------------------------------------------------------------------------------------------------------- |
| Network (CIDR)          | string  | Yes      | The subnet to check, in CIDR notation.                                                                          |
| Look-back window (days) | integer | No       | Only count reports from this many days back (1-365; free plan: up to 30). Leave empty for 30 days. Default: 30. |

**Outputs**

| Field              | Type          | Description                   |
| ------------------ | ------------- | ----------------------------- |
| Network address    | string        | Network.                      |
| Netmask            | string        | Netmask.                      |
| Minimum address    | string        | Lowest address in range.      |
| Maximum address    | string        | Highest address in range.     |
| Possible hosts     | integer       | Number of addresses in range. |
| Address space      | string        | Address space description.    |
| Reported addresses | object\_array | Reported IPs.                 |

#### Report IP

Report an abusive IP address to the AbuseIPDB community database. The report is public, is filed under your account, and can raise the address's abuse confidence score. You can report the same address only once every 15 minutes.

**Inputs**

| Field       | Type                       | Required | Description                                                                                                                                                                                                                                                                                                                                                    |
| ----------- | -------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| IP address  | string                     | Yes      | The IPv4 or IPv6 address to report.                                                                                                                                                                                                                                                                                                                            |
| Categories  | multiple\_select (integer) | Yes      | What kind of abuse you saw. Pick one or more. Available values: DNS Compromise, DNS Poisoning, Fraud Orders, DDoS Attack, FTP Brute-Force, Ping of Death, Phishing, Fraud VoIP, Open Proxy, Web Spam, Email Spam, Blog Spam, VPN IP, Port Scan, Hacking, SQL Injection, Spoofing, Brute-Force, Bad Web Bot, Exploited Host, Web App Attack, SSH, IoT Targeted. |
| Comment     | textarea                   | No       | Optional public note, such as a log excerpt showing the attack. Everyone on AbuseIPDB can see it. Leave empty to file the report without a note.                                                                                                                                                                                                               |
| Attack time | string                     | No       | When the attack happened. Leave empty to use the current time.                                                                                                                                                                                                                                                                                                 |

**Outputs**

| Field                  | Type    | Description       |
| ---------------------- | ------- | ----------------- |
| IP address             | string  | Reported address. |
| Abuse confidence score | integer | Updated score.    |

#### Bulk Report IPs

Report many abusive IP addresses at once from CSV rows. The reports are public and filed under your account. The free AbuseIPDB plan allows 5 bulk uploads per day, and some rows can be rejected even when the upload succeeds.

**Inputs**

| Field    | Type     | Required | Description                                                                   |
| -------- | -------- | -------- | ----------------------------------------------------------------------------- |
| CSV rows | textarea | Yes      | One report per line: IP, categories, comment, date. A header row is optional. |

**Outputs**

| Field         | Type          | Description            |
| ------------- | ------------- | ---------------------- |
| Saved reports | integer       | Rows accepted.         |
| Rejected rows | object\_array | Rows rejected and why. |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/abuseipdb.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
