{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/security-intelligence.triage-ip/",
    "json": "https://www.anchorterminal.com/niches/security-intelligence.triage-ip/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/security-intelligence.triage-ip/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/security-intelligence.triage-ip/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 6 | 9 | 24 | 11 |\n\n## What counts as done\n\nFor 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.\n\nMeasured, for our own tests: a 50-address list is triaged in under 2 minutes on the plan used.\n\nHow 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\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n\n- 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.\n- not this job: SecurityTrails (SecurityTrails (Recorded Future)): No reputation or verdict; IP endpoints return WHOIS, neighbours, user agents and associated domains for IPv4.\n- 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.\n\n## What stops agents finishing\n\n- v3 or paid endpoint needed for anything beyond a weekly community quota\n- IPv6 address rejected\n- a single unverified report treated as a verdict\n\n## Around it\n\nBefore: agent-observability.read-logs, messaging.read-alert. After: security-intelligence.report-and-block, messaging.post-message.\n\n## Where this comes from\n\nWeight 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\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Triage an IP address from an alert or a log",
        "url": ""
      }
    ],
    "description": "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.",
    "facts": null,
    "h1": "Triage an IP address from an alert or a log",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/security-intelligence.triage-ip/",
    "published": "",
    "section": "agents",
    "title": "Triage an IP address from an alert or a log | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/security-intelligence.triage-ip/"
  },
  "tokens": {
    "markdown": 1200,
    "slim": 280
  },
  "version": 1
}
