# Triage an IP address from an alert or a log

> Triage an IP address from an alert or a log: 0 companies fully do it, 6 with a limit, 9 carry the tag. Every listing in Security intelligence with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/security-intelligence.triage-ip/
- Markdown: https://www.anchorterminal.com/niches/security-intelligence.triage-ip/index.md (~1,200 tokens)
- Slim: https://www.anchorterminal.com/niches/security-intelligence.triage-ip/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/security-intelligence.triage-ip/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 6 | 9 | 24 | 11 |

## What counts as done

For each address a verdict (malicious, benign scanner, business service, unknown) with the evidence behind it (reports, tags, last-seen date), unknown kept distinct from benign, in one call per address or one batch call.

Measured, for our own tests: a 50-address list is triaged in under 2 minutes on the plan used.

How agents ask for it: is this IP malicious; who is hitting my server; should I block 1.2.3.4; is this scanner noise or targeted

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **AbuseIPDB (AbuseIPDB LLC)**: CHECK takes IPv4 or IPv6 and returns abuseConfidenceScore, totalReports, lastReportedAt, usageType, isWhitelisted and, with verbose, the reports. No verdict class: a never-reported IP is score 0, totalReports 0, like a clean one; no multi-IP check, so 50 addresses is 50 calls; acc-07 warns against single-report verdicts.
- **Censys (Censys, Inc.)**: Get a host (or up to 100 per bulk call) returns services with scan_time, labels, threats, vulns and a GreyNoise block. The Benign, Suspicious, Malicious, Honeypot label with top-five evidence is Core and above only, sold by sales; Free has 100 credits a month.
- **GreyNoise (GreyNoise Intelligence, Inc.)**: v3 lookups return classification, business-service trust level, tags, CVEs, actor, spoofable and first and last seen, and POST /v3/ip takes 10,000 with ips_not_found. That needs a sales-priced plan; free is the community endpoint at 50 a week, and acc-14 saw IPv6 errors.
- **Pulsedive (Pulsedive LLC)**: indicator.php returns risk (unknown kept distinct), riskfactors, linked threats and feeds, submission counts and stamp_seen and stamp_probed; an unknown value is a 404. One indicator per call, and the docs give no free-plan numbers, so 50 addresses may exceed a free day.
- **VirusTotal (Google LLC)**: GET /ip_addresses/{ip} takes IPv4 or IPv6 and returns per-engine results, tags and analysis dates, with 404 as unknown; VTAI allows 60 a minute and 1,000 a day. Verdicts are engine counts, with no scanner or business-service class and no batch call.
- **WhoisXML API (Whois API, Inc.)**: The Threat Intelligence API takes an exact or wildcard IPv4, IPv6 or CIDR ioc at 1 credit per 100 results, 30 a second, 100 free credits. Its output fields (threat type, dates, a not-found state) aren't on the requests page, so the verdict rests on the product claim.

- not this job: IPinfo (IPinfo Inc.): Returns location, ASN, as.type, is_hosting and anonymiser flags, not a malicious, scanner or benign verdict or abuse reports; the agent would still need a reputation source.
- not this job: SecurityTrails (SecurityTrails (Recorded Future)): No reputation or verdict; IP endpoints return WHOIS, neighbours, user agents and associated domains for IPv4.
- not this job: Shodan (Shodan (no company name on its pages; shodan.io is registered to John Matherly)): Host lookup returns ports, banners, vulns and tags, not a malicious, scanner or benign verdict or abuse reports; it shows what an IP exposes, not what it does.

## What stops agents finishing

- v3 or paid endpoint needed for anything beyond a weekly community quota
- IPv6 address rejected
- a single unverified report treated as a verdict

## Around it

Before: agent-observability.read-logs, messaging.read-alert. After: security-intelligence.report-and-block, messaging.post-message.

## Where this comes from

Weight 24 of 100 in Security intelligence: 11 of 41 accounts; the most common job in honeypot, chat-ops and finding-triage repos and in HN bot-traffic threads

As data: https://www.anchorterminal.com/api/v1/use-cases/security-intelligence.triage-ip.json, or the MCP tool get_use_case with id security-intelligence.triage-ip. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
