AbuseIPDB
AbuseIPDB is a community-driven project to help system administrators, webmasters, and security analysts check the reputation of IP addresses and report malicious activity. The free APIv2 surface lets developers query a single IP, check a CIDR block, retrieve paginated reports, download a curated blacklist, submit single or bulk abuse reports, and clear their own past reports for an address. AbuseIPDB underpins fail2ban, UFW, Cloudflare WAF, Wazuh, Splunk SOAR, and dozens of other firewall and SIEM integrations across the security community.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles AbuseIPDB the way a machine reads it — 63 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — AbuseIPDB scores 72.8/100 (exemplar), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile AbuseIPDB
Each block below is one kind of artifact we hold for AbuseIPDB. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 4
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
AbuseIPDB Blacklist API
Endpoints for downloading the community blacklist.
AbuseIPDB Management API
Endpoints for managing your own reports.
AbuseIPDB Reports API
Endpoints for submitting and retrieving abuse reports.
AbuseIPDB Reputation API
Endpoints for looking up the abuse data of an IP or CIDR network.
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
AbuseIPDB APIv2
POSTMANOpen Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
AbuseIPDB APIv2
OPEN COLLECTIONArazzo Workflows 7
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
AbuseIPDB Blacklist Triage
Download the community blacklist and enrich its top entry with a full single-IP check.
ARAZZOAbuseIPDB Block Scan And Check
Scan a CIDR network block for reported addresses and deep-check the most abusive host.
ARAZZOAbuseIPDB Bulk Report Then Verify
Upload a CSV of abuse reports in bulk, then spot-check one submitted IP to confirm it landed.
ARAZZOAbuseIPDB Check Then Report
Check an IP's reputation and conditionally file an abuse report based on its confidence score.
ARAZZOAbuseIPDB Clear False Positive
Check an IP and clear your own reports against it when it turns out to be whitelisted or clean.
ARAZZOAbuseIPDB Investigate IP
Check an IP and, when it is abusive, pull its full paginated report history.
ARAZZOAbuseIPDB Report Then Verify
Submit an abuse report for an IP and immediately re-check it to confirm the updated score.
ARAZZOScroll within the panel for all 7 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Abuseipdb Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Abuseipdb Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
IP Reputation Lookups
Query any IPv4 or IPv6 address for its abuse confidence score, total reports, distinct reporters, and country/ISP metadata.
Community-Sourced Blacklist
Downloadable daily blacklist of high-confidence abusive IPs, with configurable confidence threshold, country filters, IP version, and result limit.
Abuse Reporting
Submit single or bulk abuse reports tagged with one or more standard category IDs (e.g. SSH Brute-Force, DDoS, Web App Attack).
CIDR Block Checking
Score whole subnets in one call via the CHECK-BLOCK endpoint, with subscriber tiers supporting up to /16 networks.
Categorised Abuse Taxonomy
23 standard report categories (DNS Compromise, Open Proxy, Brute-Force, Phishing, etc.) for consistent classification.
Self-Service Report Clearing
Remove your own reports for a given IP via the CLEAR-ADDRESS endpoint if a report was made in error.
Standard Rate-Limit Headers
Every response carries X-RateLimit-Limit / Remaining / Reset and Retry-After, simplifying back-off in clients.
Whitelist Awareness
Responses include an `isWhitelisted` flag so consumers can avoid blocking known-good infrastructure.
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Abuseipdb Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
AbuseIPDB API Rules
SPECTRALAbuseIPDB API Rules
SPECTRALJSON Schema 3
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AbuseIPDB Blacklist Entry
JSON SCHEMAAbuseIPDB Check Response
JSON SCHEMAAbuseIPDB Report
JSON SCHEMAJSON Structure 3
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Abuseipdb Blacklist Entry Structure
JSON STRUCTUREAbuseipdb Check Response Structure
JSON STRUCTUREAbuseipdb Report Structure
JSON STRUCTUREExamples 6
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Abuseipdb Blacklist Example
EXAMPLEAbuseipdb Check Example
EXAMPLEAbuseipdb Report Example
EXAMPLEAbuseipdb Reports Example
EXAMPLESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
SSH / RDP Brute-Force Defence
Auto-block and report SSH/RDP brute-force sources via fail2ban, UFW, or endlessh integrations.
WAF Augmentation
Enrich Cloudflare / Nginx / custom WAF rulesets with the AbuseIPDB blacklist for IP-based pre-filtering.
SIEM / SOC Enrichment
Add AbuseIPDB context to Splunk SOAR, Wazuh, and TheHive alerts for analyst triage.
Bot and Crawler Filtering
Score request source IPs before serving e-commerce or login pages to block known-abusive infrastructure.
Threat Hunting and OSINT
Combine AbuseIPDB with VirusTotal, Shodan, GreyNoise and similar feeds (e.g. malwoverview) during incident response.
Bulk Reporting from Edge Logs
Convert nightly access logs into CSV bulk reports to feed the AbuseIPDB community blacklist.
Integrations 11
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Fail2Ban
Pre-packaged AbuseIPDB action ships with fail2ban; reports banned offenders directly to AbuseIPDB.
UFW (Uncomplicated Firewall)
Multiple community projects (sefinek/UFW-AbuseIPDB-Reporter, jseutens/ufw-abuseipdb) ingest UFW logs and report or ingest the AbuseIPDB blacklist.
Cloudflare WAF
sefinek/Cloudflare-WAF-To-AbuseIPDB streams Cloudflare WAF events into AbuseIPDB reports.
Splunk SOAR
Official splunk-soar-connectors/abuseipdb connector enriches Splunk SOAR playbooks with AbuseIPDB reputation.
Wazuh
marciuscosta/abuseipdb-wazuh-integration wires AbuseIPDB enrichment into Wazuh with a local cache and multi-key support.
CrowdSec
goremykin/crowdsec-abuseipdb-blocklist converts CrowdSec data into AbuseIPDB blocklists.
Endlessh
elhenro/endlessh-auto-report-abuseipdb auto-reports SSH tarpit visitors to AbuseIPDB.
Nginx
tmiland/abuseipdb-php-nginx-blacklist-create generates an Nginx-ready blocklist file from AbuseIPDB.
Zen Cart
CcMarc/AbuseIPDB plugs AbuseIPDB into the Zen Cart e-commerce platform.
TheHive
AbuseIPDB enrichment is used by SOAR/IR pipelines like malwarekid/SOAR-Flow alongside Wazuh and TheHive.
IPinfo
AbuseIPDB sources its IP geolocation, ISP, usage type, and domain data from IPinfo.
Scroll within the panel for all 11 ·
Solutions 4
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Individual (Free)
1,000 checks/day, 100 block checks, 5 blacklist downloads. Aimed at hobby admins and home labs.
Basic
$25/mo. 10,000 checks/day, 1,000 block checks, 100 bulk reports, customisable blacklist up to 100,000 IPs.
Premium
$99/mo. 50,000 checks/day, 5,000 block checks, 500 bulk reports, customisable blacklist up to 500,000 IPs.
Enterprise
Custom-priced direct data access for ISPs and large security organisations.
Resources
Every other property we hold for AbuseIPDB — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 9
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 9 ·
Build 8
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 8 ·
Access & Security 2
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 6
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/abuseipdb · machine-readable index on apis.io