Check a website email domain for CRM
harvestlab
Check one public website for an email with a qualifying mail domain. Review the CRM files. MX checks mail domain capability. A selected contact is conditional. On Starter/Bronze, a useful site costs $0.008 plus $0.008 for a qualifying MX check. The Actor cap is $0.10. SMTP, AI and phone formatting are off. See the Actor guide for the 25-site pilot.
Input
Output fields
Sign up on Apify or log in
The Bulk Website Contact Extractor & Email Finder Actor is ready to run with the inputs already set for "Check a website email domain for CRM". Sign up or log in and you'll land in Apify Console with a copy of this exact task.
Start the "Check a website email domain for CRM" task
The Bulk Website Contact Extractor & Email Finder Actor will start running based on the input automatically. You can also change all the input fields, like company website or contact-page urls, verify email deliverability (mx-record check), and more, to match your specific use case.
Receive the "Check a website email domain for CRM" output
Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as URL, domain, result type, and more.
Integrate into your workflow
The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "Check a website email domain for CRM" task via API.

MX checks the email domain. SMTP is off, so mailbox reachability stays unknown. Open full Output Dataset JSON without a view or filters. Compare emails and emails_verified for recorded checks. See CRM-EXPORT and CRM-contacts.csv for selection.
At Starter/Bronze rates, this Contact MX input can incur up to $0.016 in Actor events for one useful site and one qualifying MX check. The saved Actor charge cap is $0.10. Separate post-run storage usage can apply.
Open the 25-site pilot guide. Use the same 25 approved sites seven UTC days apart. Set a $0.40 Starter/Bronze or $0.50 base cap per run. The review request is optional.
Use weekly MX planner at 200 sites per batch. Pick your tier and download the task plan.
Match the MX attempt budget to site count. For full yield, set $3.20 Starter/Bronze or $4.00 base per 200-site task, and $0.80 or $1.00 for 50 sites. Set caps and timeouts in Apify. Start with Contact's 3,600-second timeout and check coverage.
Download task saver. Run it with --help for preview and account options.
For a private roster, select Restricted under General resource access in the account that runs the tasks. Check run, dataset and key-value store sharing before scheduling. Use only the opt-in title in a public pilot issue.
Use per-site reservation when early sites with many addresses could consume the 25 checks. Standard allocation allows more tries at individual sites. Use the same mode for both weekly runs and compare the number of MX-qualified sites.
Use the budget checker to check account limits and prepaid credit.