Give it a list of company domains. Get back a clean, unmasked contact record per site: email addresses, phone numbers, and social profile links — plus the pages each was found on.

No API key. No upgrade wall. The full result is in your dataset.

What it does

For each domain you pass in, the actor:

1. Fetches the homepage through an Apify proxy (RESIDENTIAL by default) using browser-grade TLS, so sites serve it like a normal visitor.
2. Discovers contact-bearing pages — /contact, /about, /team, /imprint, /impressum, /legal, and their localized variants — and crawls a few of them.
3. Extracts and de-duplicates across all crawled pages:
   • Emails — from mailto: links and page text, including de-obfuscated forms like name [at] domain [dot] com, info(at)company.io, HTML-entity tricks.
   • Phones — from tel: links and text, normalized and validated (7–15 digits, E.164).
   • Socials — first profile URL per network: LinkedIn, X/Twitter, Facebook, Instagram, YouTube, GitHub, TikTok.
4. Verifies emails (optional) — looks up each email domain's MX records and flags disposable and role (info@, sales@, …) addresses, so you can prioritize.

One record is produced — and one charge is made — only for sites where at least one contact was found.

Why this one

Many "website email finder" actors mask the output behind a "this is a sample, upgrade your plan to see the rest" wall. This actor returns everything it finds, unmasked, in your own dataset — and adds the verification layer (MX + disposable/role flags + email de-obfuscation) that the freemium-bait tools skip.

Input

Field	Type	Default	Description
domains	array of strings	—	Domains or URLs (e.g. stripe.com, https://shopify.com). Required.
maxPagesPerSite	integer	4	Homepage + up to N-1 discovered contact pages.
verifyEmails	boolean	true	MX-verify emails + flag disposable/role.
proxyConfiguration	object	RESIDENTIAL	Apify Proxy used to reach sites.
maxItems	integer	0	Cap total site records (0 = no limit).

Example input

{
  "domains": ["stripe.com", "basecamp.com", "ghost.org"],
  "maxPagesPerSite": 4,
  "verifyEmails": true,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

Output

One record per site that yielded contacts:

{
  "domain": "basecamp.com",
  "emails": ["support@basecamp.com", "press@basecamp.com"],
  "emailsVerified": [
    { "email": "support@basecamp.com", "mxFound": true, "mxHost": "aspmx.l.google.com",
      "isDisposable": false, "isRoleAccount": true }
  ],
  "phones": ["+13125551234"],
  "socials": {
    "linkedin": "https://www.linkedin.com/company/basecamp",
    "twitter": "https://twitter.com/basecamp"
  },
  "emailCount": 2,
  "phoneCount": 1,
  "sourcePages": ["https://basecamp.com", "https://basecamp.com/about"],
  "scrapedAt": "2026-06-13T12:00:00Z"
}

Pricing

Pay-per-result: you are charged once per site that returns at least one contact. Sites with no contacts found are not charged. The buyer's Apify account pays for proxy + compute.

Notes

• The actor never touches a site from a bare IP — every request is proxied.
• MX verification is a $0, no-key signal. Live SMTP mailbox probing is intentionally not performed (cloud egress commonly blocks port 25); MX presence + disposable/role flags are the reliable signal that travels.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Yellowpages Scraper
• Yelp Scraper
• Zoominfo Scraper
• 2GIS Places Scraper
• B2B Leads List Builder
• Company Lookup Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.