Public Business Email Finder — Snov.io Alternative

Find business email addresses visibly published on company websites. Supply domains and export email evidence, source URLs, domain-MX signals, and collection times for contact review. No guessed addresses or sending. For contact researchers, each dataset result groups the published business-email evidence found for one supplied target domain.

Workflow: put the results to work

Start with company domains you are authorized to research. Follow the source URLs for each published email and use the domain-MX signal as infrastructure context. Review contact suitability separately before any approved outreach.

Best fit for this Actor

• You have a company domain and need public business-email evidence that can be reviewed or joined back to a CRM by externalId.
• You want an on-demand, API-readable public-web workflow alongside your existing prospecting tools.
• You need to distinguish a published email from a DNS MX signal. This Actor never guesses an address and does not claim mailbox deliverability.

Pair this Actor with an approved email-verification service when your process needs SMTP-level deliverability classification. Choose a broader sales platform when your workflow includes a proprietary contact database, CRM, campaign sending, email warm-up, LinkedIn automation, team collaboration, or historical engagement tracking.

How this workflow compares with Snov.io

This is a bounded workflow alternative for collecting current, visibly published business-email evidence from caller-supplied company domains. Snov.io remains the broader fit for proprietary finder data, Email Verifier, prospect management, campaigns, warm-up, LinkedIn automation, CRM, and team features.

Decision	This Actor	Snov.io	Best fit
Scope	Reads one company homepage and directly linked same-site contact-style pages; returns only visible emails with sources.	Provides a wider prospecting, verification, campaign, CRM, and deliverability suite.	Choose this Actor for attributable public-web email evidence; choose Snov.io for its broader suite.
Billing and cost	Pay per event plus platform usage; see the Pricing tab for current rates.	Current plans bundle monthly credits and broader product access.	Compare the exact workload, account costs, and platform usage before choosing.
Input friction	Starts with a public company domain and optional known business name; no third-party API key is required.	Supports name, domain, social, database, and account-based workflows.	Use this Actor when the domain is already known and public sources are sufficient.
Output and provenance	Returns a stable JSON row with publishedBusinessEmails, emailEvidence.sourceUrls, collectedAt, and explicit outcomes.	Provides product-specific prospect and verification outputs.	Use source-linked rows when an operator must review where a value appeared.
Integrations and efficiency	The result is a dataset/KV workflow that can be started and read through the Apify API; same-job efficiency is workload-dependent.	Snov.io includes a wider set of suite integrations and automation features.	Use this Actor for a bounded public-data step; retain Snov.io if the wider integration suite is required.

Snov.io is a trademark of its owner. This independent Actor is not affiliated with, associated with, or endorsed by Snov.io.

A practical B2B research workflow

Give the Actor a short list of company domains from an approved account list. It retrieves each homepage, selects only directly linked same-site contact, about, team, legal, privacy, or terms pages, then emits a source-cited row. Your next workflow can review the source URL, select the role addresses meeting your criteria, or route selected rows to an approved verification or CRM process.

Quick start

{
  "targets": [
    {
      "companyDomain": "apache.org",
      "companyName": "Apache Software Foundation",
      "externalId": "account-001"
    }
  ],
  "maxTargets": 1,
  "maxPagesPerTarget": 3,
  "useApifyUnblockerFallback": true
}

Input reference

Field	Type	What it controls
targets	array	One to 25 authorized company domains, plus optional labels and known business contact names.
maxTargets	integer	Safety cap from 1 to 25; default 10.
maxPagesPerTarget	integer	Homepage plus up to four directly linked, same-site contact-style pages; default 3.
requestTimeoutSecs	integer	Per-page timeout from 5 to 45 seconds; default 20.
useApifyUnblockerFallback	boolean	Enables one bounded Apify Unblocker retry after a direct classified response.
preferApifyUnblocker	boolean	Uses the optional proxy first for an authorized target with observed direct blocking.

What one result means

One dataset item represents one supplied company domain, not one person and not a mailbox-verification result.

{
  "externalId": "account-001",
  "companyDomain": "example.com",
  "publishedBusinessEmails": ["sales@example.com"],
  "emailEvidence": [
    {
      "email": "sales@example.com",
      "sourceUrls": ["https://example.com/contact"]
    }
  ],
  "emailDomainMx": "MX_PRESENT",
  "collectionOutcome": "PUBLIC_EMAIL_FOUND",
  "collectedAt": "runtime ISO-8601 collection timestamp"
}

emailDomainMx is a DNS signal for the company domain. MX_PRESENT does not prove that any particular mailbox exists or can receive email. publishedBusinessEmails only contains values visibly present on a fetched public page, and every value has a source URL in emailEvidence.

Outcome guidance

The compact OUTPUT record and detailed RUN_SUMMARY record expose a stable outcome for completed collection, useful partial collection, valid empty collection, input guidance, upstream availability, or configuration attention. They also expose counts, safe diagnostics, route activity, and the named event count without returning tokens, cookies, or credentials.

Use through the Apify API

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~snov-io-alternative/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"targets":[{"companyDomain":"apache.org","externalId":"account-001"}],"maxTargets":1}'

Read the finished run's default dataset for rows and its OUTPUT / RUN_SUMMARY records before a downstream action. This Actor is read-only and has no sending, CRM-writing, or contact-enrichment side effect.

Use with AI agents through Apify MCP

For these authorized company domains, collect visibly published business emails. Return each email with its public source URL and collection time. Keep email patterns ungenerated, and label rows with no public email evidence separately.

Set up Apify MCP from Apify MCP, then have the agent read the terminal outcome and preserve source URLs when reviewing results. Client-specific routing evidence is added after an end-to-end evaluation.

Best results

• Supply the company website you are authorized to research, using a public hostname rather than a social profile, IP address, or internal host.
• Start with one or two domains to inspect output fields and evidence quality before increasing the batch size.
• Treat role accounts and MX results as review signals. Obtain a lawful basis and appropriate verification before sending any outreach.
• Use direct-only mode for a direct-access audit, or enable the bounded fallback for public, authorized targets with observed direct blocking.

Builder's note

I designed the page-selection rule to be deliberately conservative. The Actor fetches the homepage first, then follows only directly linked same-site contact-style pages. That preserves provenance, keeps URL selection grounded in the website itself, limits unnecessary requests, and makes collection diagnostics useful to reviewers.

Responsible use

Use only with public company pages and data you are authorized to process. Respect applicable law, website terms, consent, and any internal outreach policy. This Actor is read-only and operates without sign-in, access-control changes, messaging, or unlisted-contact inference.

Pricing and run costs

This Actor uses Pay per event plus Apify platform usage. The Pricing tab lists the current event rates and billing terms.

Event	Billing unit	When it applies
apify-actor-start	Actor Start	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
business-email-evidence-found	Source-cited business email evidence	Charged after a complete persisted target record contains visible business-email evidence and source URLs.

Run cost combines the charged events and Apify platform usage. Review the run charge limit and requested result count before starting.