Contact Details Scraper PRO — emails that actually deliver

Feed it a list of company websites. Get back validated contact details: emails, phones, and social profiles — with every email DNS-checked and graded, not dumped raw.

Why "PRO"? Because raw contact scrapers lie to you

A plain regex scraper run on a real site returns this:

billing@example.com        ← placeholder in the page template
jane.doe@example.com       ← demo address
logo@2x.png                ← an image filename that looks like an email
2024-09-10                 ← a date the phone regex mistook for a number
support@acme.com           ← the one address you actually wanted

You pay for all five, then your campaign bounces and your sender reputation tanks. This actor filters the noise: placeholders are dropped, image/asset false-positives are removed, phones come only from real tel: links (so no dates or CSS decimals), and every surviving email is checked:

Field per email	Meaning
verdict	valid / risky / disposable / invalid / unknown
score	0–100 deliverability confidence
roleBased	info@, sales@ (lower-value for personal outreach)
disposable	throwaway provider
freeProvider	gmail/outlook etc.

Verdicts also include service (telemetry/CDN keys like Sentry DSNs or git@github.com — dropped, never billed as contacts) and placeholder (demo addresses — dropped).

What you get per site

{
  "domain": "acme.com",
  "pagesScanned": 4,
  "emails": [
    { "email": "founder@acme.com", "verdict": "valid", "score": 100,
      "roleBased": false, "freeProvider": false }
  ],
  "phones": ["+1 415 555 0100"],
  "socials": { "linkedin": "https://linkedin.com/company/acme", "twitter": "..." },
  "summary": { "validEmails": 1, "totalEmails": 3, "phones": 1, "socials": 2 }
}

It scans the home page plus auto-discovered contact / about / team pages.

Billing you can trust

• One charge per site we actually processed — even a site with zero public contacts is a real answer you asked for.
• Sites we can't reach (DNS failure, timeout, hard block) are never billed.
• Email DNS lookups are cached per run (on success), so many contacts on one domain cost one lookup.
• Any reachable URL is billed once — including parked or placeholder domains, because a 200-page with no contacts is indistinguishable from a real one without crawling it. Only genuinely unreachable URLs are free.
• Results are capped at maxEmailsPerSite (default 50, kept by deliverability score — never alphabetically) and maxPhonesPerSite (default 15); the true totals are reported in emailsFound / phonesFound.

Honest limits

• Server-rendered HTML only (no JavaScript execution) — contacts injected by client-side JS won't be seen.
• Phones are taken from tel: links only. This is deliberate: text-regex phone extraction is wrong more often than right. Higher precision, some recall lost.
• A real but fictional demo address on a page (e.g. a "John Wick" example) can still pass DNS validation — validation proves the domain accepts mail, not that the person exists.
• Sites behind heavy bot protection may need the proxy input (RESIDENTIAL).

Built by the maker of the Email Validation API (same validation engine) and a whale-tracking + MCP suite — same rules everywhere: clean data, errors never billed.