Email Finder by Name and Domain — MX-Checked Lookup

Email Finder by Name and Domain — MX-Checked Lookup

Email finder by name and domain. Give a person's name and a company domain and get likely business email addresses, each checked for working MX records. You can also crawl websites you supply for publicly listed emails, or verify a list of addresses you already have. Bulk-ready dataset, no Hunter key, no LinkedIn.

Be clear about what "verified" means here: we check syntax and MX records only. We do not run a live SMTP mailbox check, so a name+domain result is a labeled candidate / mx_only guess, never a confirmed deliverable mailbox.

Also searched as: email finder, find email by name and domain, email finder by name and domain, email address finder, work email finder.

What it does

Mode	Behavior
Website	Fetches homepage + common /contact paths on your domains/URLs and extracts mailto: / visible emails
Patterns	Builds common name@domain formats and confirms the domain has MX records
Both	Runs website scrape then pattern candidates
Verify (emails[], any mode)	Checks a list you already have: syntax → MX → role / free / disposable flags → confidence 0-100 and status good | risky | bad with a reason. Every checked address is returned. good = syntax + MX pass (max confidence 65) — never a confirmed mailbox. An address that is both in emails[] and found on a crawled page is returned once, as the verify row. Addresses are lowercased and unicode domains punycoded; inputEmail keeps what you sent. Rows beyond maxItems are not checked (the run status message says how many were).

Outdo checklist (vs typical email finder APIs)

• Query-first Email Finder & Verifier title for Store/Google
• Name+domain pattern waterfall with MX validation
• Website crawl emails (not just patterns)
• Bulk people/domains input → dataset out
• Role-account-aware confidence labels (candidate / mx_only / public_listing)
• No LinkedIn scrape, no breach corpora, no bundled paid enrichment keys

What it deliberately does not do

• No Hunter / Apollo / paid enrichment APIs
• No SMTP RCPT probing (Apify blocks outbound port 25; would require a buyer-supplied external verifier)
• No LinkedIn scraping, no credential stuffing, no breach dumps
• Pattern results are labeled candidate / mx_only — never claimed deliverable

Input

{
  "emails": ["info@iana.org", "not-an-email"],
  "mode": "both",
  "domains": ["iana.org"],
  "startUrls": [{ "url": "https://www.iana.org/contact" }],
  "people": [{ "fullName": "Example User", "domain": "iana.org" }],
  "maxItems": 20,
  "onlyReturnFound": true
}

Output fields

email, domain, source (website | pattern_mx | verify), sourceUrl, mxValid, mxHost, mailProvider, pattern, confidence, status (found | candidate | not_found | input_error for finder rows; good | risky | bad for verify rows), reason (verify rows only), verificationLevel (public_listing | mx_only), isRoleAccount, roleScore, isFreeProvider, isDisposable, checks, inputEmail (verify rows), note, foundAt

Pricing

PAY_PER_EVENT: each Actor.pushData item bills apify-default-dataset-item. Actor start is a separate small event.

Related IntelScrape tools

• Website Contact Scraper — Email & Phone Finder — named contacts + emails/phones from company sites
• Google Maps Email Extractor — local business emails from Maps leads

Soft CTA (cross-sell mesh) — SOFTCTA_LINKS_EMAIL_FINDER_1_2_9

Every email/verify row (and the batch summary) includes a softCta object pointing to related IntelScrape Actors:

• Skip Trace PRO / TruePeopleSearch / Watson — deepen people intel from a name or email
• Google Maps Email Extractor / Website Leads / Contact Info Scraper — harvest more company emails from domains and sites

SoftCTA is additive metadata only. PPE pricing and billing events are unchanged. Skip Trace PRO code stays frozen (links only).