# Contact Details & Email Scraper — Phones, Socials, Email Types (`insanedev/contact-details-scraper`) Actor

E-mails sorted by type (sales, support, management, legal…), phones, WhatsApp, social profiles, company legal name and address from any list of websites, each with its source page. Plain HTTP, fast. Pay only per website with contacts. Lead enrichment for any domain list.

- **URL**: https://apify.com/insanedev/contact-details-scraper.md
- **Developed by:** [Insane Developer](https://apify.com/insanedev) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Features:** Limited permissions
- **Stats:** 8 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.40 / 1,000 website 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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

### What is Contact Details & Email Scraper?

**Contact Details & Email Scraper** takes a list of websites and returns, for each one, **the e-mail addresses
sorted by type (sales, support, management, legal, press, personal…), phone numbers, WhatsApp and other messengers,
social profiles, contact-form pages, and the company's legal name and postal address**. Every value comes with the page
it was found on.

You pay **$3 per 1,000 websites with contacts** ($2.70 on Scale, $2.40 on Business), and **the first 10 are free** for
every Apify account. A website where nothing is found, that is down or that blocks us costs nothing. To try it, keep the three example domains in the input and click **Start**.

![On the same 500 websites: e-mail on 344+ vs 254, phone on 274+ vs 140, any contact on 436+ vs 427](https://api.apify.com/v2/key-value-stores/RWAoVG2O9MHUgawJ0/records/contact-details-scraper-coverage.png)

### Who uses it?

- Sales and lead-generation teams turn a list of company domains into e-mails, phones and LinkedIn pages.
- Agencies and freelancers enrich a CRM export or a Google Maps result list with contact details.
- Lead enrichment: give it the domains from a lead list and each row comes back with the company's typed e-mails,
  phones, socials, legal name, address and VAT number, matched by `domain`. It does not verify mailboxes, so run the
  e-mails through your usual verifier before a cold campaign.
- Marketplaces and directories check that the contacts they list still match the company's website.
- Researchers collect the legal name and registered address of companies from their imprint pages.

### What can it do?

![E-mails found on 500 websites by type: general, support, legal, sales, press, marketing, management, HR](https://api.apify.com/v2/key-value-stores/RWAoVG2O9MHUgawJ0/records/contact-details-scraper-email-types.png)

- **E-mail types.** Every e-mail is tagged general, support, sales, marketing, management, legal, billing, HR, press,
  personal or technical, from the mailbox name, the words around it on the page and the page itself. Set **Only these
  e-mail types** to keep, say, sales and support mailboxes only. The filter is free.
- It reads the homepage, then the contact, imprint (Impressum, mentions légales, aviso legal),
  about, team, support and privacy or terms pages it links to, found by keywords in a dozen languages. When the menu
  has no such link, it reads the sitemap, then common paths such as `/contact` and `/impressum`.
- It decodes Cloudflare's e-mail protection (`[email protected]` on the page), spelled-out
  addresses ("info \[at] example \[dot] com"), HTML-entity and URL-encoded addresses, `mailto:` links and schema.org data.
- Phones come from `tel:` links, schema.org data, numbers after a label (Phone, Tel., Telefon, Téléphone…),
  international `+CC` numbers and North American numbers.
- Social profiles: LinkedIn company page, Facebook, Instagram, X, YouTube, TikTok, Pinterest, Snapchat, Telegram,
  Threads and Discord, one profile per network, without share buttons or platform pages.
- Messengers: WhatsApp, Telegram, Viber, Signal, Facebook Messenger, LINE, Skype and WeChat when the site links to
  them, and the pages that carry a contact form (for sites that publish no e-mail).
- Optional: technical mailboxes the domain publishes in DNS (DMARC reports, SOA hostmaster), only on the domain itself.
- Company details: legal name (schema.org, or a name with a legal form such as GmbH, Ltd or LLC in the footer or
  imprint), postal address, EU VAT number and commercial register number (HRB, UK company number, SIRET, KvK).
- Plain HTTP, no browser, many websites in parallel through Apify Proxy. A page behind a bot check is retried with a
  Chrome-like connection, then through residential proxy; websites that time out get a second try at the end of the run.
- A website your account read in the last 7 days with the same options comes back from your own key-value store
  `contact-details-scraper` at once, without reading it again (switch off with **Reuse results of the last 7 days**).

### What data does it return?

One row per website:

| Field                | Description                                                                                           |
| -------------------- | ----------------------------------------------------------------------------------------------------- |
| `domain`             | The website's domain                                                                                  |
| `status`             | `ok` (contacts found, the only billed status), `noContacts`, `noMatchingContacts`, `failed`, `blocked` |
| `emails`             | The site's own domain first, then other domains; contact mailboxes (info@, sales@) before others      |
| `emailDetails`       | Each e-mail with its `type` and the page it came from: `{email, type, sourceUrl}`                     |
| `phones`             | Digits with an optional leading `+`                                                                   |
| `whatsapp`           | Numbers from wa.me links                                                                              |
| `socials`            | One profile per network: `linkedin`, `facebook`, `instagram`, `x`, `youtube`, `tiktok`…               |
| `messengers`         | `telegram`, `viber`, `signal`, `messenger`, `line`, `skype`, `wechat` when present                    |
| `contactForms`       | Pages with a contact form                                                                             |
| `legalName`          | The company behind the site                                                                           |
| `vatId`              | EU VAT number from the imprint or footer (`DE123456789`)                                              |
| `registrationNumber` | Commercial register or company number (`HRB 123456`, UK company number, SIRET, KvK)                   |
| `address`            | Postal address                                                                                        |
| `sources`            | Every value with the page it came from: `{type, value, sourceUrl}`                                    |
| `url`                | Homepage after redirects                                                                              |
| `pagesFetched`       | Pages read for this website                                                                           |

A real row (shortened):

```json
{
    "domain": "dynavin.de",
    "status": "ok",
    "emails": ["info@dynavin.de", "support@dynavin.de", "anregungen@dynavin.de", "jobs@dynavin.de"],
    "emailDetails": [
        { "email": "info@dynavin.de", "type": "general", "sourceUrl": "https://www.dynavin.de/" },
        { "email": "support@dynavin.de", "type": "support", "sourceUrl": "https://www.dynavin.de/unternehmen/" },
        { "email": "anregungen@dynavin.de", "type": "support", "sourceUrl": "https://www.dynavin.de/kontakt/" },
        { "email": "jobs@dynavin.de", "type": "hr", "sourceUrl": "https://www.dynavin.de/unternehmen/" }
    ],
    "phones": ["+4972469445030", "+49724694450333"],
    "socials": {
        "instagram": "https://www.instagram.com/dynavin.official",
        "facebook": "https://www.facebook.com/dynavin.official",
        "youtube": "https://www.youtube.com/user/dynavin1"
    },
    "legalName": "Dynavin GmbH",
    "address": "Dynavin GmbH, Industriestraße 28, 76470 Ötigheim, Deutschland",
    "sources": [
        { "type": "email", "value": "anregungen@dynavin.de", "sourceUrl": "https://www.dynavin.de/kontakt/" },
        { "type": "phone", "value": "+4972469445030", "sourceUrl": "https://www.dynavin.de/kontakt/" }
    ],
    "url": "https://www.dynavin.de/",
    "pagesFetched": 5
}
```

### Contact Details & Email Scraper vs. vdrmota Contact Details Scraper

Both Actors on the same 500 random websites (small businesses, colleges, media and shops in the UK, US, Canada,
Germany and France), on the Apify platform on 2 November 2026. Our three clean runs give the ranges:

|                                   | Contact Details & Email Scraper (this Actor) | vdrmota Contact Details Scraper      |
| --------------------------------- | -------------------------------------------- | ------------------------------------ |
| Websites with an e-mail           | **344–364 of 500**                           | 254 of 500                           |
| Websites with a phone number      | **274–285 of 500**                           | 140 of 500                           |
| Websites with a social profile    | 368–391 of 500                               | 392 of 500 (384 with a real profile) |
| Websites with any contact         | **436–455 of 500**                           | 427 of 500                           |
| Time for 500 websites             | **5.2–5.8 min** (1 GB memory)                | 9.1 min (4 GB memory)                |
| Paid for these 500 websites       | **$1.31–1.37** (436–455 with contacts)       | $3.82 (1,906 pages)                  |
| Per 1,000 websites with an e-mail | **about $3.70–3.90**                         | about $15                            |

On 8 of its 392 websites the only "social profile" is a share button, an embedded YouTube video or a Facebook category
page; we leave those out. With its default input (only the list of websites) the other scraper is not usable for a
list: on the same 500 it crawled two sites deep, hit its request limit and returned 2 rows.

vdrmota was run with its own settings: up to 4 pages per website, link depth 1, same domain only (run
`BFTJC0fUSXioZHg3S`). Most of the difference comes from contact and imprint pages that it doesn't reach within its page
limit, and from e-mails hidden by Cloudflare. It charged for all 1,906 pages it read, including 89 pages on 37 websites
where it found no contact at all.

|                                      | Contact Details & Email Scraper             | vdrmota Contact Details Scraper |
| ------------------------------------ | ------------------------------------------- | ------------------------------- |
| E-mail type (sales, support, legal…) | yes, free                                   | no                              |
| Legal name, address, VAT number      | yes                                         | no                              |
| Page each value was found on         | yes                                         | no                              |
| Contact-form pages, messengers       | yes (Telegram, Viber, Signal, LINE, Skype…) | WhatsApp, Telegram              |
| How you pay                          | per website with contacts                   | per page read, plus add-ons     |

### How much does it cost?

![$3 per 1,000 websites with contacts; for the same 500 websites we charged $1.37, a pay-per-page scraper $3.82](https://api.apify.com/v2/key-value-stores/RWAoVG2O9MHUgawJ0/records/contact-details-scraper-price.png)

Our price looks higher than "$2 per 1,000" in the Store list because it counts websites, not pages. A pay-per-page
scraper reads about 4 pages on every website, so 1,000 websites cost around $7.70 there, and it charges for every page
read, including on websites where it finds no contact (89 pages on 37 such websites in our 500-site test). Here you pay
only for websites with contacts; empty, unreachable and blocked websites are free.

| Websites with contacts | Free and Starter plans | Scale plan | Business plan |
| ---------------------- | ---------------------- | ---------- | ------------- |
| 100                    | $0.30                  | $0.27      | $0.24         |
| 1,000                  | $3                     | $2.70      | $2.40         |
| 10,000                 | $30                    | $27        | $24           |

**The first 10 websites with contacts are free** for every Apify account.

**Pay only for what you need.** By default any contact counts: e-mail, phone, social profile or messenger. In
**Pay only for websites with** you can pick, say, only E-mail. A website with just a Facebook link is then free and comes
back without contacts (status `noMatchingContacts`).

Apify's free plan includes $5 of credit a month,
enough for about 1,600 websites with contacts. Set **Maximum cost per run** in the run options and the run stops
before going over it.

### How do I use it?

1. Click **Try for free**.
2. Paste your websites into **Websites**, one per line (`example.com` or a full URL both work).
3. Optional: raise **Max pages per website** for large sites (default 5).
4. Click **Start**.
5. Download the results as CSV, Excel or JSON, or open the **Contacts** view.

Input example:

```json
{
    "websites": ["nec.ac.uk", "welshmountainzoo.org", "dynavin.de"],
    "maxPagesPerSite": 5
}
```

If you already use another contact scraper, `startUrls` with `{"url": "https://…"}` objects works too.

### How do I get e-mails for my Google Maps Scraper results?

Copy the dataset ID of your Google Maps Scraper run (Console → the run → **Storage** → Dataset ID) into
**Websites from datasets** and click **Start**. The Actor reads the `website` of every place; places without a
website are skipped and cost nothing. Each result row has the `domain`, so you can join it back to your places.

```json
{
    "datasetIds": ["<your Google Maps Scraper dataset ID>"],
    "billableContacts": ["email"]
}
```

With `billableContacts: ["email"]` you pay only for websites where an e-mail was found. The same works for any
dataset with a `website`, `url` or `domain` field (our
[Shopify Store Leads](https://apify.com/insanedev/shopify-store-list) gives `domain`, a CSV you uploaded as a dataset
gives whatever its column is called: name it in **Website field in those datasets**). Console links to a dataset
work as well as bare IDs. Up to 100,000 items are read per run.

### How do I use it in Clay?

Clay runs Apify Actors as an enrichment, one table row at a time.

1. In Clay, open **Settings → Connections → Add Connection → Apify** and paste your Apify API token
   ([Console → Settings → API & Integrations](https://console.apify.com/settings/integrations)).
2. In your table, click **Add enrichment**, search for **Apify** and pick **Run Apify Actor**.
3. Choose `insanedev/contact-details-scraper` and paste this input, with your website column in place of
   `Website`:

```json
{
    "websites": ["{{Website}}"],
    "maxPagesPerSite": 5,
    "billableContacts": ["email"]
}
```

4. Run it on a few rows, then add columns from the result: `emails` (all e-mails), `emailDetails` (each e-mail with
   its type, e.g. keep `sales` and `personal`), `phones`, `socials.linkedin`, `legalName`, `address`.

Each row is one website, so it costs $0.003 when an e-mail is found and nothing when it isn't. For thousands of rows,
one run with all websites (or a dataset, see above) is faster than one run per row; import the results back by
`domain`.

### Can I use it from the API, Make, Zapier or an AI agent?

Yes. Run it through the [Apify API](https://docs.apify.com/api/v2), the JavaScript or Python client, on a schedule,
from Make, Zapier or n8n, or from an AI agent through the [Apify MCP server](https://mcp.apify.com).

### What does it not do?

- It reads only what the website itself publishes. It doesn't guess e-mail patterns, look up people on LinkedIn or
  verify mailboxes.
- A few websites behind a strict bot check (1 of our 50 test sites) still don't open. For them the Actor reads
  search-engine snippets of the website's own pages instead. Websites that are down or show an error page are not
  searched unless you turn on **Search also for websites that are down**. When nothing is found, the row comes back
  as `blocked` or `failed`, free of charge.
- Pages built only in the browser by JavaScript show fewer contacts; most sites still render their footer and contact
  page on the server.

### Is it legal to collect contact details from websites?

The Actor collects business contact details that companies publish on their own websites. Some of them, such as an
employee's work e-mail, can be personal data under GDPR and similar laws. How you store and use the results, for
example for outreach, is your responsibility; check the rules that apply to you.

Results of the last 7 days are kept in your own Apify key-value store `contact-details-scraper` (the contacts found per
website, compressed), so a list read again is answered at once; delete that store to clear them.

At the end of each run, the Actor sends its developer an anonymous summary: the event counts and prices, the run cost,
your Apify plan level (free or paid), your pricing tier and how the run was started (Console, API or schedule). It also
carries a random customer tag, made on your first run of any of our Actors and kept in your own `insanedev-customer`
key-value store (not derived from your account; deleting that store starts a new one), the days since your previous run,
and how the run was set up: whether it came from a task you saved, the band of the maximum cost you set, and the API
client by name (such as Python, n8n or Make; never the IP address). The summary contains no input, output or account
identifiers.

### Troubleshooting

| What you see                 | What to do                                         |
| ---------------------------- | -------------------------------------------------- |
| `failed`, `unreachable`      | The site didn't answer, twice. Try it again later. |
| `blocked`, `challenge`       | The site shows a bot check. Not billed.            |
| `noContacts` on a large site | Raise **Max pages per website** to 10 or 15.       |
| A value you don't expect     | `sources` shows the page it came from.             |

### Support

Questions, a website where it misses contacts, or a field you need: open an issue in the **Issues** tab.

# Changelog

This Actor's version history is a separate document: https://apify.com/insanedev/contact-details-scraper/changelog.md

# Actor input Schema

## `websites` (type: `array`):

Domains or URLs, one per line (example.com, https://www.example.com/page). Each website is read once; duplicates of the same domain are skipped.

## `datasetIds` (type: `array`):

Dataset IDs (or their Console / API links) of earlier runs, e.g. a Google Maps Scraper run: the website of every item is read, places without a website are skipped for free. Works with any dataset whose items have a website, url or domain field.

## `datasetWebsiteField` (type: `string`):

The item field that holds the website, e.g. website (Google Maps Scraper) or domain (Store Leads). Leave empty to use the first of website, websiteUrl, companyWebsite, domain, companyDomain, homepage, url, site that an item has.

## `maxPagesPerSite` (type: `integer`):

The homepage plus the contact, imprint, about, team and legal pages it links to (or its sitemap lists). 5 finds e-mails on most sites; more pages = more e-mails on large sites, a bit slower.

## `emailTypes` (type: `array`):

Keep only e-mails of these types (empty = all). Free. Types come from the mailbox name (sales@, datenschutz@), the words before the address and the page it is on; personal = a mailbox that reads like a person's name.

## `billableContacts` (type: `array`):

A website is billed only when at least one contact of these kinds is found (empty = all four). E.g. pick only E-mail: a website with just a Facebook link is free, and comes back without contacts (status noMatchingContacts). WhatsApp counts as a phone and as a messenger.

## `dnsEmails` (type: `boolean`):

Also read the domain's DNS: DMARC report addresses and the SOA hostmaster mailbox, when they are on the domain itself (type technical). Useful when the website publishes no e-mail; these mailboxes are often read by IT, not by sales.

## `searchFallback` (type: `boolean`):

When a website shows a bot check, read the search-engine snippets of its own pages (site:example.com contact email) and its social profiles from search. Only results on the website's own domain count.

## `searchUnreachable` (type: `boolean`):

Also use the search fallback for websites that don't answer or show an error page. Mostly dead websites; off by default.

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

How many websites are read at the same time. Most of the time goes to waiting for slow websites, so 120 keeps 1 GB of memory busy without running out of CPU.

## `useResidentialFallback` (type: `boolean`):

When a website blocks the datacenter proxy (403, 429, bot check), try once more through Apify residential proxy.

## `startUrls` (type: `array`):

Same as Websites, as request objects ({"url": "https://example.com"}) — handy when you switch from another contact scraper.

## `useCache` (type: `boolean`):

A website your account already read in the last 7 days, with the same options, is delivered from your own key-value store `contact-details-scraper` instead of being read again (faster; billed like a fresh result). Turn off to force fresh reads.

## Actor input object example

```json
{
  "websites": [
    "nec.ac.uk",
    "welshmountainzoo.org",
    "dynavin.de"
  ],
  "maxPagesPerSite": 5,
  "billableContacts": [
    "email",
    "phone",
    "social",
    "messenger"
  ],
  "dnsEmails": false,
  "searchFallback": true,
  "searchUnreachable": false,
  "maxConcurrency": 120,
  "useResidentialFallback": true,
  "useCache": true
}
```

# Actor output Schema

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

No description

## `summary` (type: `string`):

No description

# 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 = {
    "websites": [
        "nec.ac.uk",
        "welshmountainzoo.org",
        "dynavin.de"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("insanedev/contact-details-scraper").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 = { "websites": [
        "nec.ac.uk",
        "welshmountainzoo.org",
        "dynavin.de",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("insanedev/contact-details-scraper").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 '{
  "websites": [
    "nec.ac.uk",
    "welshmountainzoo.org",
    "dynavin.de"
  ]
}' |
apify call insanedev/contact-details-scraper --silent --output-dataset

```

## MCP server setup

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

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/0mh75aW0t64kyT0Ak/builds/54xeRTq9H5YPplGS6/openapi.json
