# Check a website email domain for CRM

**Use case:** 

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

```json
{
  "urls": [
    "https://www.python.org/about/help/"
  ],
  "maxWebsites": 1,
  "maxPagesPerSite": 1,
  "includeSubpages": false,
  "detectTechStack": false,
  "validatePhones": false,
  "verifyEmails": true,
  "maxEmailsToVerify": 1,
  "deepEmailVerification": false,
  "exportCrm": true,
  "crmRequireMx": true,
  "crmMxReservePerSite": false,
  "enableAiAnalysis": false,
  "llmProvider": "openrouter",
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

## Output

```json
{
  "url": {
    "label": "URL",
    "format": "string"
  },
  "domain": {
    "label": "Domain",
    "format": "string"
  },
  "result_type": {
    "label": "Result Type",
    "format": "string"
  },
  "billable_contact_found": {
    "label": "Billable Contact Found",
    "format": "boolean"
  },
  "company_name": {
    "label": "Company Name",
    "format": "string"
  },
  "emails": {
    "label": "Emails",
    "format": "array"
  },
  "phones": {
    "label": "Phones",
    "format": "array"
  },
  "phones_validated": {
    "label": "Phones Validated",
    "format": "array"
  },
  "social_profiles": {
    "label": "Social Profiles",
    "format": "object"
  },
  "tech_stack": {
    "label": "Tech Stack",
    "format": "array"
  },
  "is_shopify_store": {
    "label": "Shopify Store",
    "format": "boolean"
  },
  "shopify_store_name": {
    "label": "Shopify Store Name",
    "format": "string"
  },
  "shopify_currency": {
    "label": "Shopify Currency",
    "format": "string"
  },
  "shopify_country": {
    "label": "Shopify Country",
    "format": "string"
  },
  "pages_crawled": {
    "label": "Pages Crawled",
    "format": "integer"
  },
  "scraped_at": {
    "label": "Scraped At",
    "format": "string"
  }
}
```

## How it works

### 1. 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](https://console.apify.com/create-task-from-example/eUbfyjbekICbVGRQh) and you'll land in Apify Console with a copy of this exact task.

### 2. 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, website limit per run, and more, to match your specific use case.

### 3. 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.

### 4. 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](https://apify.com/harvestlab/contact-extractor.md).

## FAQ

### What does an MX-qualified email mean in this task?

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.

### What can the one-site Contact MX example cost on Starter?

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.

### How can I repeat this Contact MX check for 25 websites?

Open the [25-site pilot guide](https://apify.com/harvestlab/contact-extractor#download-crm-import-files). 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.

### How do I schedule a weekly refresh of 1,250 company websites?

Use [weekly MX planner](https://api.apify.com/v2/key-value-stores/L7nr7abk9HDHXa13i/records/contact-weekly-mx-2026-11-20.html?signature=pL1Pz6bW4r3yyujEyZrK&attachment=true) at 200 sites per batch. Pick your tier and download the task plan.

### How should I set caps and timeouts for the weekly Contact batches?

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.

### How can I save the weekly batches as private tasks?

Download [task saver](https://api.apify.com/v2/key-value-stores/L7nr7abk9HDHXa13i/records/save-contact-weekly-mx-tasks-2026-11-20.py?signature=1hhqwFc63KIN3adp2vAq5&attachment=true). Run it with --help for preview and account options.

### How do I control access to a weekly Contact refresh?

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.

### Which MX check mode should I use for the 25-site pilot?

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.

### How do I check the budget for two weekly MX refreshes?

Use the [budget checker](https://api.apify.com/v2/key-value-stores/L7nr7abk9HDHXa13i/records/contact-weekly-mx-budget-2026-11-21.zip?signature=LUkDZcTAZzi82rpnBKZT&attachment=true) to check account limits and prepaid credit.

## About this Actor

This example demonstrates how to use [Bulk Website Contact Extractor & Email Finder](https://apify.com/harvestlab/contact-extractor.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/harvestlab/contact-extractor.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/harvestlab/contact-extractor.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).
