MX Record Checker API - Does This Domain Accept Mail?

The contact validation suite

• Email Verifier & Validator API — emails and phone numbers verified in one run, priced by what could be checked
• Bulk Email List Cleaner API — paste a whole list, get it back deduplicated, verified and scored
• Disposable Email Checker API — the fast, cheap check: throwaway providers, role addresses, free mail, typos, MX
• Phone Number Validator API — numbers in any format in, validity, line type, country and E.164 out

Paste domains or website URLs and get their mail records: MX hosts in priority order, A-record fallback, an accepts-mail flag, and whether the provider is disposable or free mail. Pure computation — nothing is scraped, nothing is sent, no proxy, no API key. Invalid input is free, and you pay less when less could be checked.

Quick start

1. Press Start — the defaults are a working run that shows every verdict.
2. Replace them with your own domains or website URLs, one per line.
3. Take the dataset as JSON, CSV or Excel, or via the API. Every row has a type; the free coverage row says what was asked for, what arrived, and whether mailbox checks were possible from this network.

What people use it for

• Enrichment. Which mail provider a company uses (Google, Microsoft, Proton…) is visible in the MX hosts.
• Feeding an AI agent or workflow. Send objects from n8n, Make or a sheet as records; the email or phone field is found by name and every other field comes back on the row as passthrough.

What the rows look like

A domain row

{
  "type": "domain",
  "input": "https://www.wikipedia.org/",
  "domain": "wikipedia.org",
  "hasMx": true,
  "mxHosts": [{ "exchange": "mx-in1234.wikimedia.org", "priority": 10 }],
  "hasA": false,
  "acceptsMail": true,
  "isDisposable": false,
  "isFreeMail": false
}

What it costs

You pay for	Price
Each domain's mail records checked	$0.50 per 1,000 domains

Free, always: an input that is not an email, a phone number or a domain at all, a duplicate of something already in the run (one inbox spelled three ways is one charge), every input the run did not reach, every error row, the coverage row and the run summary. A run that checks nothing costs nothing.

Set Cost ceiling (USD) to stop any run before it passes a number you choose; the free summary row reports what the run actually spent.

FAQ

Do I need an API key for anything?

No. Everything is handled for you and there is nothing to buy on top. Pure computation — no website is scraped, no proxy is used.

Can I send my CRM rows instead of a plain list?

Yes. Put objects in Records. The email, phone or domain field is found by name (email, e-mail, phone, mobile, tel, domain, website…) and every other field is returned on the row as passthrough, so your ids come back attached.

Will I be charged twice for the same address?

No. Addresses are collapsed on their normalised form — Gmail dots and +tags, upper and lower case — so one inbox is one row and one charge.

Limits, stated plainly

Nothing here contacts WhatsApp, Telegram or any messaging service — those checks need an unofficial client and are not sold.

Use it from n8n, MCP, the API or a schedule

Built to be called by a workflow, not only from the Store form. The Actor is vonsensey/mx-record-checker-api; every snippet below sends {}, which runs the defaults shown on the form — replace it with your own input.

n8n

Install the Apify community node (@apify/n8n-nodes-apify under Settings → Community Nodes, or search "Apify" on n8n Cloud). Add Apify → Run Actor with Actor vonsensey/mx-record-checker-api and your input JSON, then Apify → Get Dataset Items on the run's defaultDatasetId and pipe the rows anywhere. For scheduled runs, the On new Apify Event trigger fires when a run of this Actor finishes.

MCP (Claude, Cursor, VS Code, any MCP client)

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=vonsensey/mx-record-checker-api",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

Your agent then calls vonsensey/mx-record-checker-api as a tool with the same input the form takes and reads the dataset back.

REST API (one call, rows in the response)

curl -X POST "https://api.apify.com/v2/acts/vonsensey~mx-record-checker-api/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" -d '{}'

Python

from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("vonsensey/mx-record-checker-api").call(run_input={})
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(row)

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('vonsensey/mx-record-checker-api').call({});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Make, Zapier, LangChain, CrewAI

The Apify app in Make and Zapier has a Run an Actor module: pick vonsensey/mx-record-checker-api. In LangChain and CrewAI the Apify tool wrappers take the same Actor id. A daily schedule needs nothing but the Console: Schedules → Create → this Actor → cron, and the dataset fills on its own.