Website Contact & Tech Enricher
Pricing
$5.00 / 1,000 company reports
Website Contact & Tech Enricher
Enrich company websites with public emails, phones, socials, technology signals and email-domain MX checks. One company row with source URLs. Bounded crawling, robots.txt respected, predictable pricing per successful report.
Pricing
$5.00 / 1,000 company reports
Rating
0.0
(0)
Developer
Riccardo Vecchi
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
11 days ago
Last modified
Categories
Share
Turn company website URLs into contact records with evidence. Get one row per website with public emails, valid published phone links, social profiles, technology signals and email-domain MX checks. Designed for existing company lists from a CRM, directory or research workflow.
What you get
- Public email addresses with exact source URLs. Addresses are never guessed.
- Primary email and phone, plus flat fields for CSV and spreadsheets.
- Social profile links with sharing links filtered out.
- 33 known HTML technology signals, including WordPress, Shopify, WooCommerce, Webflow, Next.js, analytics and support tools.
- MX domain results: mx_found, no_mx, null_mx or unknown.
- One company row even when several contact pages are checked.
- Explicit diagnostic rows for blocked or inaccessible websites.
Quick start
Paste domains or website URLs into Company websites or domains and click Start. Export the dataset as JSON, CSV or Excel.
{"websites": ["https://apify.com"],"maxPagesPerWebsite": 5,"checkEmailDomains": true,"businessEmailsOnly": false}
Enable Role-based business emails only to keep addresses such as info@, sales@, support@, contact@ and contatti@. The optional startUrls field accepts Apify-style URL lists for integrations. Duplicate domains are merged.
Pricing
$5 per 1,000 successful company reports ($0.005 each), with platform usage included. No start fee, per-page charge or paid add-on. A successful report requires at least one HTML page fetched and analyzed; it may have no contacts if none are published. Failed and robots-excluded websites return diagnostic rows without the company-enriched charge. Set your maximum charge to bound charged results.
Output
| Field | Meaning |
|---|---|
| website, domain, status | Website and result status |
| primaryEmail, primaryPhone | Preferred published contact |
| emailsText, phonesText, technologiesText | Flat export fields |
| emails | Address, classification, method and sourceUrls |
| phones | Valid tel links and evidence |
| socialLinks | Profiles grouped by platform |
| technologies | Technology signals and matched evidence |
| emailDomainChecks | Domain MX results |
| pagesScanned, scannedUrls, warnings | Coverage and limitations |
The SUMMARY key-value record reports successful and failed websites and whether the charge limit stopped the run.
How it works
The Actor checks robots.txt, reads each starting page and prioritizes same-site contact, about and legal links, with conventional contact paths as fallbacks. It uses bounded HTTP requests, without a browser, proxy configuration or external paid API. It reads ordinary HTML and decodes explicitly published [at]/[dot] and Cloudflare email markup.
Limits
- JavaScript-only, CAPTCHA-protected, login-only or blocked pages are unsupported and are not bypassed.
- MX records indicate domain mail configuration, not mailbox existence or deliverability. No SMTP probe or email is sent.
- Technology detection is based on known HTML signals; it is not a complete inventory.
- Phones come from valid published tel links. Set a default country for local numbers.
- Up to 1,000 websites per run, eight attempted pages per website and approximately 45 seconds per website. Up to five sites run concurrently. Time limits can produce partial coverage.
- Respect website terms and applicable requirements for downstream use. Public availability does not grant permission for every use.
Automation and support
Run with the Apify API or a schedule to refresh company lists. Map structured output into Make, n8n, Zapier, spreadsheets or CRM workflows. For support, open an Actor issue with a public URL, run ID and expected result. Do not post credentials or private customer data.