# Domain OSINT Recon (`prooflio/domain-osint-recon`) Actor

Aggregates WHOIS, DNS records, certificate-transparency subdomains and PTR records for a domain into one structured report.

- **URL**: https://apify.com/prooflio/domain-osint-recon.md
- **Developed by:** [Prooflio AI](https://apify.com/prooflio) (community)
- **Categories:** AI, Agents, Automation
- **Features:** Limited permissions
- **Stats:** 8 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $0.50 / 1,000 domain osint recons

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Domain OSINT Recon

Give it a domain, get back a single structured report combining four **public, open-source** intelligence sources:

- **WHOIS** — registrar, creation/expiry dates, nameservers
- **DNS** — A, AAAA, MX, NS, TXT, CNAME records
- **Subdomains** — discovered from multiple public sources in parallel (crt.sh, Cert Spotter, AlienVault OTX); if one source is down, the others still answer
- **Reverse DNS** — PTR records for the resolved IPs

One dataset item is produced per domain. Sources are collected in parallel, and any single source failing leaves you with a partial report rather than a failed run.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `domains` | string\[] | — | Root domains to investigate (e.g. `example.com`). Required. |
| `includeWhois` | boolean | `true` | Run the WHOIS lookup. |
| `includeDns` | boolean | `true` | Resolve DNS records. |
| `includeSubdomains` | boolean | `true` | Enumerate subdomains via crt.sh. |
| `includeReverseIp` | boolean | `true` | PTR lookups for resolved A records. |

Example:

```json
{
    "domains": ["example.com"],
    "includeSubdomains": true
}
```

### Output

```json
{
    "domain": "example.com",
    "scannedAt": "2025-01-01T00:00:00.000Z",
    "whois": { "registrar": "...", "createdDate": "...", "expiryDate": "...", "nameServers": "...", "raw": {} },
    "dns": { "a": ["..."], "aaaa": [], "mx": [], "ns": ["..."], "txt": ["..."], "cname": [] },
    "subdomains": ["www.example.com", "mail.example.com"],
    "reverseIp": { "93.184.216.34": ["..."] }
}
```

A source that fails returns `{ "error": "<message>" }` in its slot.

### Legal & acceptable use

This tool queries only publicly available, open data sources (public WHOIS, the public DNS system, and public certificate-transparency logs). It performs no authentication, no scraping behind logins, and collects no personal data beyond what registrars publish in public WHOIS. You are responsible for ensuring your use complies with applicable law (including data-protection regulations) and the terms of the data sources. Do not use it to harass, stalk, or target individuals.

# Actor input Schema

## `domains` (type: `array`):

Root domains to investigate, e.g. example.com. One report is produced per domain.

## `includeWhois` (type: `boolean`):

Registrar, creation/expiry dates and nameservers.

## `includeDns` (type: `boolean`):

A, AAAA, MX, NS, TXT and CNAME records.

## `includeSubdomains` (type: `boolean`):

Enumerate subdomains from public certificate-transparency logs.

## `includeReverseIp` (type: `boolean`):

PTR records for the resolved A records.

## Actor input object example

```json
{
  "domains": [
    "example.com"
  ],
  "includeWhois": true,
  "includeDns": true,
  "includeSubdomains": true,
  "includeReverseIp": true
}
```

# Actor output Schema

## `reports` (type: `string`):

All domain reports in the default dataset (Overview view).

# 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 = {
    "domains": [
        "example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("prooflio/domain-osint-recon").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 = { "domains": ["example.com"] }

# Run the Actor and wait for it to finish
run = client.actor("prooflio/domain-osint-recon").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 '{
  "domains": [
    "example.com"
  ]
}' |
apify call prooflio/domain-osint-recon --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,prooflio/domain-osint-recon"
        }
    }
}
```

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/wHgEmpalLW4jDfNQG/builds/OPclnrQC0kE07iokd/openapi.json