All APIs/Website Email Finder
Available on Apify · by Meka

Website Email FinderPublished contacts, with proof.

Find email addresses that actually appear on public company websites, with the exact source page and surrounding text for verification.

$4 per 1,000 domains with contacts. No start fee.
No guessing or mailbox claims. Domains with no result are not billed.

ONE ADDRESS. VISIBLE SOURCE.Example
@info@example.comPublished on the company contact page

Public contact

Same domain · Role address

SOURCE EVIDENCE

Exact source URL, page type, extraction method, surrounding text, domain relationship, provider labels, and optional MX status.

Page
Contact
Source
mailto
MX
Available
WHAT YOU GET

Contact data you can verify yourself.

Enrich company and local-business datasets with addresses the organization chose to publish on its own website.

01 / address

Published emails only

Deduplicated addresses found in mailto links, JSON-LD, Cloudflare obfuscation, HTML entities, structured scripts, marked obfuscation, or plain text.

02 / evidence

Exact public source

Source URL, homepage or contact/about/team/legal page type, extraction method, and the surrounding page text for direct review.

03 / labels

Useful classification

Same-domain, free-mail and disposable-domain flags, role or personal type, vendor exclusions, and optional email-domain MX availability.

A published address is not consent to send email. Users remain responsible for GDPR, CAN-SPAM, CASL, platform rules, and other applicable requirements.

FROM DOMAIN TO CONTACT SET

Your first run.
Three simple steps.

Provide domains or start URLs—never a person’s name.

Run on Apify
  1. 1

    Add websites

    Enter domains such as example.com or specific public website URLs. Duplicates and www variants are normalized.

  2. 2

    Choose the scope

    Scan one to five pages per domain, optionally keep published free-mail addresses, and choose whether to check email-domain MX records.

    5 pages · public pages only
  3. 3

    Review outcomes

    Receive one ordered record per domain: contacts found, no contacts found, or unreachable—with precise fetch outcomes and source evidence.

FOR DEVELOPERS

Domain in. Auditable contact set out.

Pair it with the Google Maps or LinkedIn Company APIs by passing their website fields into this Actor.

An honest contact contract

Every input keeps its order and gets an outcome. Blocked, challenged, DNS-failed, timed-out, and no-contact domains remain distinct instead of disappearing.

View Actor API & documentation ↗

An Apify account and API token are required for programmatic access.

EXAMPLE ACTOR INPUT
{
  "domains": [
    "apify.com",
    "example-shop.co.uk"
  ],
  "maxPages": 5,
  "includeFreeMail": true,
  "checkMx": true
}
Inspect output fields +

Domain-level fields include domain, websiteUrl, status, outcome, contact counts, emails, and pagesScraped. Each email includes sourceUrl, sourcePage, sourceType, context, classification flags, addressType, and mxAvailable.

See the full output reference ↗
BEFORE YOU START

A few useful answers.

Ask us a question ↗
Does it guess email addresses?+

No. It only returns addresses literally present on public website pages. Names, patterns, info@ fallbacks, and database lookups are not used.

Does MX availability mean the mailbox works?+

No. mxAvailable only indicates that the email domain publishes DNS MX records. It does not verify the individual mailbox or guarantee deliverability.

How is it priced?+

Each domain where at least one public address is found costs $0.004, equivalent to $4 per 1,000 successful contact sets. Empty, blocked, timed-out, dead, and duplicate domains are not charged.

Which pages are checked?+

The homepage plus up to four relevant same-domain pages selected from public links: contact, about, team, and legal or imprint. JavaScript is not executed.

Can I provide a person’s name to find a work email?+

No. Person-name lookup is outside the product. Such input is rejected instead of constructing or guessing an address.

Find the contact a site publishes.

Start with domains. Keep the source evidence.

Run on Apify