🏢 B2B Lead Enricher — Email Finder, LinkedIn, Tech Stack & Company Data

Paste a list of company websites and get back enriched B2B leads. For each one you get:

• business emails with a confidence score;
• phone numbers;
• the LinkedIn company page and other social profiles;
• the technologies the site runs on;
• domain data: WHOIS, SSL, and the email provider (Google Workspace, Microsoft 365, …);
• a 0–100 lead score with an A–D grade.

Every value comes with the evidence of where it was found.

No API keys, no logins, no browser — fast HTTP crawling that works on the free Apify plan.

Keywords: email finder · company email finder · B2B lead enrichment · LinkedIn company URL finder · tech stack detector · WHOIS lookup · MX record check · email provider lookup · lead scoring · CRM enrichment · Hunter.io alternative · Apollo alternative · Clearbit alternative · website contact scraper

---

✨ What makes it different

	This actor	Typical email finders
Emails from homepage + contact, team, about, impressum, support and press pages	✅	✅
Cloudflare-protected emails decoded, written-out emails (sales [at] acme [dot] com) and JSON-LD structured data	✅	❌
Confidence score with reasons for every email	✅	partial
Personal vs role mailboxes (info@, sales@, press@ …)	✅	✅
Company's real email format detected from published emails (first.last, f.last …)	✅	❌
100+ technologies, each with the exact code signal that proves it — no false hits from logos or blog mentions	✅	❌
Email provider (Google Workspace / Microsoft 365 / Zoho …) plus SPF and DMARC	✅	❌
Social profiles ranked so the company's own accounts come first, not authors or partners	✅	❌
Filters: required technology, lead grade, domain age, keywords, email only	✅	❌
Websites that fail show the reason and how to fix it — and are never charged	✅	❌

🎯 Use cases

• Sales prospecting: turn a list of target accounts into contacts plus a priority grade.
• Tech-based targeting: find every prospect running Shopify, HubSpot, WordPress or Stripe.
• Microsoft vs Google targeting: see which companies run Microsoft 365 or Google Workspace.
• Inbound lead qualification: check domain age, SSL and mail server to tell real businesses from throwaways.
• CRM enrichment: feed the results into HubSpot, Salesforce or Pipedrive through Make, n8n or Zapier.
• Recruiting and partnerships: pull HR, careers and partnerships mailboxes.

🔧 Input

{
  "urls": [
    "https://stripe.com",
    "figma.com",
    "jane@shopify.com",
    "acme-robotics.com | John | Doe"
  ],
  "firstName": "John",
  "lastName": "Doe",
  "maxPagesPerSite": 6,
  "requiredTech": ["Shopify", "HubSpot"],
  "minLeadGrade": "B"
}

Option	What it does
urls	Domains, URLs or emails, one per line. Optionally add names to a line: site.com | First | Last. Duplicate domains are removed.
firstName, lastName	Contact name used to guess their email at every company. Names on a line override these.
maxPagesPerSite	Homepage plus the most useful internal pages, between 1 and 20 (default 6).
includeExecutiveEmails	Role guesses such as ceo@, cto@, hr@ and sales@. Always marked unverified.
checkWhois, checkSsl, checkDns	Domain data. Turn any of them off for speed.
includeFailedSites	Adds a row with the reason for every site that couldn't be crawled. These rows are free.
onlyWithEmail, onlyWithContact, requireMx	Contact-quality filters.
minLeadGrade, requiredTech, minDomainAgeYears, companyKeywords	Targeting filters. Profiles they remove are never charged.
skipPreviouslyScraped	Remembers domains across runs, so scheduled runs only charge for new companies.
proxyConfiguration	Off by default, which is cheapest. Turn it on if many sites come back blocked.

📤 Output (60+ fields per company)

{
  "status": "ok",
  "domain": "stripe.com",
  "company_name": "Stripe",
  "lead_grade": "A - Hot Lead",
  "lead_score": 75,
  "primary_email": "media@stripe.com",
  "scored_emails": [
    { "email": "media@stripe.com", "confidence": 85, "type": "generic",
      "evidence": ["mailto link on stripe.com/newsroom"] }
  ],
  "phones": ["+1 888 926 2289"],
  "linkedin": ["https://www.linkedin.com/company/stripe"],
  "twitter": ["https://x.com/stripe"],
  "tech_stack": ["Next.js", "Nginx"],
  "email_provider": "Google Workspace",
  "has_spf": true,
  "dmarc_policy": "reject",
  "registrar": "SafeNames Ltd.",
  "domain_created": "1995-09-12",
  "ssl_valid": true,
  "person_email_guesses": { "best_guess": "john.doe@stripe.com", "verified": false },
  "executive_emails": { "verified": false, "patterns": { "CEO": "ceo@stripe.com" } }
}

Fields

• Company: domain, website, company name (and its source), description, page title, language, address, founding date, employee count.
• Emails: primary email, all emails, personal emails, generic emails, and scored emails with confidence, type, pages and evidence.
• Phones: primary phone, phones, and phone evidence.
• Social: LinkedIn company, LinkedIn people, X/Twitter, Facebook, Instagram, YouTube, TikTok, GitHub.
• Tech: tech stack, count, categories, and the evidence for each one.
• Email setup: MX records, email provider, SPF, DMARC policy.
• Domain: registrar, created and expiry dates, domain age, plus the full WHOIS object.
• SSL: valid or not, issuer, days left, plus the full SSL object.
• Patterns: detected email format with evidence, person email guesses, executive email patterns.
• Scoring: lead score, grade, and the reason for every point; keyword match evidence.
• Crawl details: pages crawled, status, error, how to fix, input, scraped at.

The dataset has three views: Overview, Contacts only and Tech & domain.

Lead score (12 signals)

Points	Signal
+15	Any email found
+15	A named person's email found
+5	An email on the company's own domain
+10	Phone found
+10	LinkedIn company page
+5	Two or more other social profiles
+10	Domain receives email (MX records)
+5	Rich tech stack (5+ tools)
+5	Pays for marketing or sales tools (CRM, chat, email marketing, ads)
+5 / +10	Domain older than 2 / 5 years
+5	Valid SSL certificate
+5	Company name and description published

A - Hot Lead 75–100 · B - Warm Lead 50–74 · C - Cool Lead 25–49 · D - Cold Lead 0–24

Email confidence

Each email starts at 40 points, and the reasons are listed on the email itself:

Points	Signal
+30	On the company's own domain
+20	On a sister domain (for example acme.io for acme.com)
−25	On an unrelated domain (vendor or agency)
+15	Published as a mailto link or in structured data
+10	Found on a contact or team page
+5	Found on several pages
+5	A named person

📊 Run summary

Each run writes a RUN_SUMMARY record with:

• companies saved, how many have contacts, and charged events;
• a count for every status and every skip reason, with examples;
• the grade distribution and the email providers found;
• the most common technologies;
• request and block counts, and field fill rates.

💰 Pricing

You only pay for companies that are saved:

Event	When
company-lead	Company enriched, no public email or phone found
company-lead-with-contact	Company enriched with at least one email or phone

Websites that are unreachable, blocked or invalid, duplicates, domains already saved in earlier runs, and companies removed by your filters are never charged.

❓ FAQ

Are the emails verified? Emails published on the site are real addresses the company put there. They're ranked by confidence, and each one says where it was found. Person and role guesses are always marked verified: false; check them with an email verifier before sending.

Does it work on JavaScript-only sites? It reads the HTML the server sends, plus structured data. Most marketing sites work fine. Pure single-page apps may give fewer results.

Some sites come back blocked. That site has bot protection. Turn on the proxy (Apify Proxy, RESIDENTIAL gets through most) and run again. WHOIS, DNS and SSL data are still included in the failed row.

Why is the domain age empty for .de and some other domains? Some registries don't publish registration dates. The field stays empty and is never estimated.

Does it find people's LinkedIn profiles? It returns company pages, plus any personal profiles linked from the site (for example on team pages) in linkedin_people.

⚖️ Notes

This actor reads public company websites and public DNS/WHOIS data only. You are responsible for using contact data in line with privacy and anti-spam laws in your market (GDPR, CAN-SPAM, etc.).