# Triage an IP address from an alert or a log (slim)

> 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.

- Full: https://www.anchorterminal.com/niches/security-intelligence.triage-ip/index.md (~1,200 tokens) · this version ~280 tokens · JSON https://www.anchorterminal.com/niches/security-intelligence.triage-ip/index.json · canonical https://www.anchorterminal.com/niches/security-intelligence.triage-ip/
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-15
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all. Full fit: 0 companies, with a limit: 6, tagged: 9. Weight 24, 11 accounts.

Done when: 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.
caveat: abuseipdb (AbuseIPDB LLC)
caveat: censys (Censys, Inc.)
caveat: greynoise (GreyNoise Intelligence, Inc.)
caveat: pulsedive (Pulsedive LLC)
caveat: virustotal (Google LLC)
caveat: whoisxml-api (Whois API, Inc.)

Data: https://www.anchorterminal.com/api/v1/use-cases/security-intelligence.triage-ip.json
