# Domain to Contacts – Validated Emails, Phones & Social Finder (`filexy634/domain-to-contacts`) Actor

Turn a list of company domains into validated emails, phone numbers and social profiles. Crawls contact, about and team pages, checks that emails can receive mail, and scores each one. You only pay for domains where contacts are found.

- **URL**: https://apify.com/filexy634/domain-to-contacts.md
- **Developed by:** [felix gerald](https://apify.com/filexy634) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $1.00 / 1,000 domain with contacts

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 to Contacts

Give it a list of domains. Get back validated emails, phone numbers (E.164), social profiles and basic company info, ready to drop into your CRM or outreach tool.

### What you get per domain

- **Emails** – found in `mailto:` links, page text, obfuscated forms (`name [at] site [dot] com`), JSON-LD and Cloudflare-protected markup. Each email has a type (`generic`/`personal`), the page it came from, an MX check result and a 0–100 confidence score. Emails on domains that cannot receive mail are dropped.
- **Phones** – validated and normalised to international format.
- **Socials** – LinkedIn, Facebook, Instagram, X/Twitter, YouTube, TikTok, GitHub.
- **Company name and description** from page metadata.

### Pricing

You are charged **only for domains where at least one email or phone was found**. Unreachable domains and pages without contacts are free.

### Input

| Field | Description |
|---|---|
| `domains` | Domains or URLs, one per line |
| `maxPagesPerDomain` | Homepage + contact/about/team/imprint pages (default 5) |
| `validateEmails` | MX check, default on |
| `includeGenericEmails` | Include info@, sales@ etc., default on |
| `defaultPhoneCountry` | ISO code (e.g. `PL`, `US`) for numbers without a country prefix |
| `proxyConfiguration` | Optional |

### Limitations

- Static HTML only. Sites that render contact details purely with client-side JavaScript will return `no_contacts`.
- Only publicly visible information on company websites is collected. You are responsible for using the data in line with GDPR/CAN-SPAM and local laws.

### Output example

```json
{
  "domain": "acme.com",
  "status": "ok",
  "companyName": "Acme",
  "emails": [{ "email": "jane@acme.com", "type": "personal", "mxValid": true, "confidence": 100, "sourceUrl": "https://acme.com/contact" }],
  "phones": ["+14155552671"],
  "socials": { "linkedin": "https://www.linkedin.com/company/acme" }
}
```

### Developer notes

```
npm install
npm run build
apify run     # or: apify push
```

PPE event to create in Console → Monetization: `domain-enriched` (suggested start: $0.003).

# Actor input Schema

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

Domains or URLs to enrich, one per line (e.g. acme.com or https://acme.com).

## `maxPagesPerDomain` (type: `integer`):

Homepage plus contact/about/team/imprint pages. Higher finds more contacts but costs more compute.

## `validateEmails` (type: `boolean`):

Drops emails whose domain cannot receive mail and raises confidence for those that can.

## `includeGenericEmails` (type: `boolean`):

Include role addresses such as info@, sales@, support@.

## `defaultPhoneCountry` (type: `string`):

Two-letter ISO country code (e.g. US, PL, GB) used to parse phone numbers written without a country prefix.

## `maxConcurrency` (type: `integer`):

How many pages are fetched in parallel. Lower it if target sites rate-limit you.

## `proxyConfiguration` (type: `object`):

Optional. Most small-business sites work without a proxy.

## Actor input object example

```json
{
  "domains": [
    "apify.com",
    "crawlee.dev"
  ],
  "maxPagesPerDomain": 5,
  "validateEmails": true,
  "includeGenericEmails": true,
  "maxConcurrency": 20,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `contacts` (type: `string`):

Dataset of enriched domains.

# 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": [
        "apify.com",
        "crawlee.dev"
    ],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("filexy634/domain-to-contacts").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": [
        "apify.com",
        "crawlee.dev",
    ],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("filexy634/domain-to-contacts").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": [
    "apify.com",
    "crawlee.dev"
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call filexy634/domain-to-contacts --silent --output-dataset

```

## MCP server setup

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

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/DB4jQdG43Q2viSDhD/builds/bmMfzfe72KvSvV7rY/openapi.json