Contact Scraper: Validated Emails + Phones, Pay Per Site
Pricing
from $5.00 / 1,000 site processeds
Contact Scraper: Validated Emails + Phones, Pay Per Site
Crawl business websites for emails, phones, and socials β then VALIDATE every email (DNS/MX, disposable, role, placeholder filtering) so you get deliverable contacts, not regex soup. Failed fetches never billed.
Pricing
from $5.00 / 1,000 site processeds
Rating
0.0
(0)
Developer
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
15 days ago
Last modified
Categories
Share
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 templatejane.doe@example.com β demo addresslogo@2x.png β an image filename that looks like an email2024-09-10 β a date the phone regex mistook for a numbersupport@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) andmaxPhonesPerSite(default 15); the true totals are reported inemailsFound/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.
