How to verify an email address with an API (syntax, MX, disposable)

Updated 2026-11-10

Use when an agent must decide whether an email address looks deliverable before sending or storing it.

From an MCP client, add https://tanod.dev/mcp and call verify_email; the first 5 calls per IP per UTC day are free (shared by domain inspections and RDAP, email and IP lookups), then each call is USD 0.001 with x402, no key or signup.

POST an address to /v1/email/verify. It checks syntax, MX records (including null MX and the A/AAAA fallback), disposable domains, role accounts and free providers, and returns a verdict: deliverable_likely, undeliverable, risky or unknown.

Request

email is the address to check, up to 320 characters.

curl, using the free tier
curl -s -X POST https://tanod.dev/v1/email/verify \
  -H 'X-Tanod-Free: 1' -H 'content-type: application/json' \
  -d '{"email":"postmaster@example.com"}'

Response

Response (the example from the OpenAPI spec, trimmed)
{
  "email": "someone@gmail.com",
  "normalized": "someone@gmail.com",
  "syntax_valid": true,
  "domain": "gmail.com",
  "has_mx": true,
  "mx_hosts": ["gmail-smtp-in.l.google.com", "alt1.gmail-smtp-in.l.google.com"],
  "null_mx": false,
  "disposable": false,
  "role_account": false,
  "free_provider": true,
  "verdict": "deliverable_likely",
  "reasons": ["free_provider"],
  "smtp_checked": false,
  "notes": ["DNS-only check: the mail server was not contacted, so mailbox existence is not verified"]
}

Recipe: before an agent's first batch

A new sending address has no reputation, and a stale list spends what little it has. Before the first batch:

  1. Check every address with this route (USD 0.001 each, so USD 0.50 for 500). Drop the undeliverable ones, meaning no MX or a null MX, which would bounce for certain. Hold back risky ones (disposable domains, role accounts such as info@) for a later, slower lane.
  2. Check your own sending domain once with /v1/domain/inspect (USD 0.004 to 0.01): SPF and DKIM passing and aligned with the From domain, plus a DMARC record. Gmail and Yahoo have required these of senders of 5,000+ messages a day since February 2024.

This check never contacts the mail server, so a mailbox that no longer exists on a valid domain still gets through. Keep hard-bounce suppression in your send path for those.

Compared with a Google Sheets add-on

The most-installed email checker in Google's Workspace Marketplace, "Email Verification" by Duffco Ventures, showed 29K+ users and 322 reviews on 14 Oct 2026. It sells prepaid packs from USD 9 for 500 checks (USD 0.018 each) to USD 599 for 500,000 (USD 0.0012 each), after 50 free sign-up credits. Its listing names Hunter, ZeroBounce and NeverBounce as the tools it replaces, which check whether mailboxes exist. This route is USD 0.001 per address with no pack to buy, but it checks format and domain only (see below). For a list in a sheet, a cheap order of work is this check first, then a mailbox checker for the addresses that pass.

Limits and caveats

Format and domain only, not existence. The check uses DNS. The mail server is never contacted (no SMTP probing), so a deliverable_likely verdict means the domain can receive mail, not that the mailbox exists.

When you need mailbox existence too. Services that probe SMTP connect to the receiving server and ask about the mailbox. That is slower, some providers rate-limit or flag repeated probes, and catch-all domains still answer "unknown". A cheap order of work for a large list: run this DNS check first to drop bad syntax, dead domains, disposable and null-MX addresses, then send only the survivors to an SMTP prober. You pay the higher probing price only on addresses that can receive mail at all.

Lists are incomplete. Disposable-domain and role-account detection are list-based and can miss new services. Treat the verdict as a filter for sign-up forms, not as proof.

Do not use the result alone to reject a real user; offer a confirmation email instead.

Price and free allowance

USD 0.001 per call, paid in USDC on Base, Polygon, Solana, BNB Chain or Arbitrum with x402. 5 free per IP per UTC day with the header X-Tanod-Free: 1; the pool is shared with domain inspection, RDAP and IP lookup. MCP tool: verify_email at https://tanod.dev/mcp, where the free tier is automatic.

Paying by card instead? The same check (DNS only, no SMTP probing) runs as an Apify actor, Bulk Email Validator (tanod/email-validator), billed through your Apify account at USD 0.0015 per address.

All endpoints →

Use it from Claude without writing code: in claude.ai or Claude Desktop, add https://tanod.dev/mcp/web?via=email-verification-api as a custom connector (steps), then ask in plain words, for example "Does the email address info@example.com look deliverable?" The free daily allowance is applied automatically over MCP. Beyond it a call needs an x402 payment, which these clients can make.

Related guides: What email verification APIs cost over x402, How to check a domain's SPF, DMARC and DKIM with an API, Whois (RDAP) lookup API for domains, IPs and AS numbers, IP address to ASN lookup API (network, org, abuse contact). Back to tanod.dev or the guide index. Results are automated and heuristic.