# IoC Lookup (`crawland/ioc-lookup`) Actor

Real-time IoC reputation lookups (URL, hash, IP, domain) served from the Crawland threat-intelligence backend.

- **URL**: https://apify.com/crawland/ioc-lookup.md
- **Developed by:** [Crawland](https://apify.com/crawland) (community)
- **Categories:** Developer tools, Other, Integrations
- **Features:** Limited permissions, Single-tenant, Server interface
- **Stats:** 28 total users, 22 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 ioc lookups

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## IoC Lookup

Real-time threat intelligence for file hashes, IPv4 addresses, domains, and URLs — 70+ vendor verdicts in a single call.

### API Overview

IoC Lookup is a real-time threat intelligence API that answers a simple question: **"Is this indicator dangerous?"**

Send any of four indicator types — a file hash (MD5 / SHA-1 / SHA-256), a URL, an IPv4 address, or a domain — and get a structured risk overview that helps you understand the indicator faster.

- **Vendor-level insight:** Compare verdicts from 70+ security engines including BitDefender, Sophos, Forcepoint, Cisco, ESET, Kaspersky, Fortinet, McAfee, and more.
- **Reputation summary:** Quickly assess whether an indicator is trusted, suspicious, or malicious.
- **Detection breakdown:** Review malicious, suspicious, harmless, and undetected counts for faster decision-making.
- **Indicator-specific context:** Get relevant enrichment data depending on the indicator type, such as domain, IP, URL, or file-related intelligence.

### Response Highlights

An IoC Lookup response can include security vendor analysis, detection statistics, reputation data, categories, threat names, URL metadata, redirects, response codes, outgoing links, trackers, DNS records, WHOIS data, certificate details, sandbox verdicts, contacted domains/IPs, and file intelligence depending on the indicator type.

### What can you do with this API?

- 🔎 Look up URLs, domains, IPs, and hashes
- 🛡️ Check vendor-level security analysis
- 📊 Review malicious, suspicious, harmless, and undetected counts
- 🌐 Inspect URL redirects, metadata, response codes, and trackers
- 🧩 Analyze domain data such as DNS, WHOIS, certificates, and reputation
- 📁 Investigate hashes with file metadata, threat labels, and sandbox results

### Response model

Every successful request returns:

```json
{
  "is_success": true,
  "response_code": 200,
  "message": "Success",
  "data": { /* indicator-specific payload */ }
}
```

When an indicator can't be processed (e.g. a malformed value), the call still returns HTTP 200 with `is_success: false` and the underlying `response_code` in the body — inspect `is_success` rather than relying on the HTTP status alone.

### Use cases

#### GET /url

Look up a URL — phishing, defacement, content classification, vendor verdicts.
*Pro tip: pass the full URL including scheme. Query strings and fragments are accepted but normalised internally.*

#### GET /hash

Look up a file by MD5 / SHA-1 / SHA-256.
Returns file metadata, signing info, behavioural tags, and 70+ vendor verdicts.

#### GET /ip

Look up an IPv4 address — reputation, ASN / network ownership, country, vendor verdicts.
*IPv6 is not currently supported.*

#### GET /domain

Look up a domain — reputation, WHOIS, DNS records, popularity ranks (Alexa, Cisco Umbrella, Cloudflare Radar, Majestic), content categories, JARM fingerprint.

### Need something custom or need support?

Looking for a different response format, a bulk lookup option, a custom integration, or help with setup? Send us a DM and we'll be happy to support you and help you find the best setup for your use case.

# Actor input Schema

## `endpoint` (type: `string`):

Which kind of indicator to look up. Maps to the path in Standby mode (/url, /hash, /ip, /domain).

## `query` (type: `string`):

The indicator value to look up.

## Actor input object example

```json
{
  "endpoint": "domain",
  "query": "google.com"
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "query": "google.com"
};

// Run the Actor and wait for it to finish
const run = await client.actor("crawland/ioc-lookup").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "query": "google.com" }

# Run the Actor and wait for it to finish
run = client.actor("crawland/ioc-lookup").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "query": "google.com"
}' |
apify call crawland/ioc-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,crawland/ioc-lookup"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/HpN7J1VV3gElk74c7/builds/ndD853lHe1VfhaSwl/openapi.json