Tool workspace

Website Email Finder

Published email addresses with exact source-page evidence.

Mode
Recorded samples
Base URL
api.apify.com/v2/acts
Reference
API catalog
Local discoveryAPI backed

Checking live preview availability…

POSThttps://api.apify.com/v2/acts/meka.im~website-email-finder/run-sync-get-dataset-items
No responseNothing requested yet

Rendered

Contract only
No recorded example

Published contract

Website Email Finder

Contract onlyNo saved response

No recorded sample is available for this product in this build. The fields below are the published contract, including every published type and description. No response values have been inserted.

Published request fields

Inputs accepted by the Actor. They are documentation only here; no request is sent from this view.

FieldTypeDescription
domainsstring[]One domain per line, for example acme-widgets.de. A full URL works too; www. is stripped and duplicates are removed.
startUrlsArray<string | { url: string }>Website URLs to start from, when you want a specific page instead of the homepage. Combined with the domains above.
maxResultsintegerHard cap on how many domains are written to the dataset across the whole run, including a resumed run. Minimum: 1. Maximum: 1000000.
maxPagesintegerHomepage plus up to four more: contact, about, team and legal/imprint. Lower it to 1 to scan homepages only — that is faster and cheaper, and in our own 1,039-domain test it found addresses on 39.9% of domains instead of 53.7%. Default: 5. Minimum: 1. Maximum: 5.
includeFreeMailbooleanKeep gmail.com, outlook.com and similar addresses when they are published as the site's contact address. Small businesses often use one. They are always labelled separately from addresses on the site's own domain. Default: true.
checkMxbooleanAdds mxAvailable to each address: whether the email domain publishes MX records. This is a DNS fact about the domain, not a check of the individual mailbox and not a deliverability guarantee. Default: true.
concurrencyintegerHow many batches of 8 domains run at once. Raise it for large lists, lower it if you want a gentler crawl. Default: 4. Minimum: 1. Maximum: 10.

Fetch outcome

status is the service result (only contacts_found is charged); outcome is the homepage fetch result. Published values are shown without interpretation.

FieldTypeDescription
domainstringThe input domain, lower-cased and without www.
inputValuestringExactly what you passed in.
websiteUrlstringThe URL that was actually reached, after redirects.
statusstringOnly contacts_found is charged. Accepted: "contacts_found", "no_contacts_found", "unreachable".
outcomestringFetch result of the homepage: ok, http_403, http_429, dns_failed, timeout, tls_failed, challenged, http_5xx, …

Discovered emails

Counts are the service's own classifications. Email entries keep their returned structure because nested field names are part of the response contract.

FieldTypeDescription
emailCountintegeremailCount Minimum: 0.
sameDomainCountintegerAddresses on the input domain, subdomains included. Minimum: 0.
freeMailCountintegergmail, outlook and similar, published as the site contact address. Minimum: 0.
otherDomainCountintegerotherDomainCount Minimum: 0.
excludedVendorCountintegerWebsite-builder and tooling addresses that were dropped. Minimum: 0.

Email entries

FieldTypeDescription
emailsobject[]One entry per address, each with its source URL, page type and surrounding text.

Crawl evidence

Pages fetched and how each fetch ended, plus the service's request and elapsed-time measurements.

FieldTypeDescription
requestsintegerrequests Minimum: 0.
tookMsintegertookMs Minimum: 0.
contractVersionintegercontractVersion Minimum: 1.

Pages scraped

FieldTypeDescription
pagesScrapedobject[]Every page that was fetched and how it ended.
No capture date or sample values are availableContract only
No response body yetapplication/jsonRendered ↑

No JSON yet

Run a live request when this product supports it, or choose a recorded sample in the rendered pane.