Email verification that tells you exactly what it checked 把「到底查了什么」写清楚的邮箱验证 API

EmailCheck is an email verification API that checks an address at domain level — syntax, MX routing, disposable and role-account signals, likely typos with a correction, domain age from registration records, and a catch-all risk signal — and returns a 0–100 score with a valid / risky / invalid verdict, for one address or a batch of up to 100. It does not probe whether an individual mailbox exists: no SMTP check, and every response says so. Free tier: 100 checks a month on RapidAPI; PRO is $9/month for 10,000.

EmailCheck 是一个邮箱验证 API，在域名层检查地址——格式、MX 路由、一次性与角色账号信号、疑似拼写错误及纠正建议、来自注册记录的域名年龄、catch-all 风险信号——返回 0–100 分与 valid / risky / invalid 裁决，支持单条或一次最多 100 条批量。它不探测单个邮箱是否存在：不做 SMTP 探测，每个响应里都写明这一点。免费档：RapidAPI 上每月 100 次；PRO 为 $9/月、10,000 次。

01What it checks — and what it doesn't它查什么——以及不查什么

02How it works怎么用

1. Send one address to GET /validate?email=... (or POST /validate with a JSON body).
2. Read the verdict, the score, and the individual checks behind it — nothing is a bare true/false.
3. For a list, POST /validate/batch with up to 100 addresses returns per-address results plus summary counts and percentages. A bad entry marks only itself; it never fails the batch.

1. 把单个地址发给 GET /validate?email=...（或用 JSON body 走 POST /validate）。
2. 读裁决、分数和它背后的逐项检查——不是只有一个 true/false。
3. 整批名单用 POST /validate/batch，一次最多 100 条，返回逐条结果加 summary 计数与百分比。坏条目只标自己，不连坐整批。

curl "https://emailcheck-api.pages.dev/validate?email=test@gmial.com"

{
  "email": "test@gmial.com", "valid": false, "score": 40, "verdict": "invalid",
  "checks": { "syntax": true, "domainExists": true, "mxFound": false,
              "disposable": false, "roleAccount": false, "freeProvider": false },
  "suggestion": "test@gmail.com", "typoLikely": true,
  "domainAgeDays": 8581, "domainAgeSource": "RDAP",
  "catchAllRisk": "unknown", "scope": "domain-level",
  "note": "Domain-level validation only: ... Mailbox existence is not probed
           (no SMTP check), so a valid result does not confirm the
           mailbox exists. The score is a domain risk score."
}

Batch errors are named JSON (MISSING_EMAIL, EMPTY_BATCH, BATCH_TOO_LARGE, INVALID_JSON), so your pipeline can react to each one. Full docs and keys live on the listings below.

批量错误都是具名的 JSON（MISSING_EMAIL、EMPTY_BATCH、BATCH_TOO_LARGE、INVALID_JSON），管线可以逐个处理。完整文档与密钥在下面两个平台的产品页里。

03Pricing价格

Subscriptions run on the marketplaces — checkout, keys and billing live there, and the total at checkout is whatever the platform shows for your region, which may include local taxes. The plans, per platform:

订阅在平台上完成——结账、密钥与计费都在平台侧，结账页总价以平台按你所在地区显示的为准，可能含当地税费。各平台档位如下：

The free tiers differ on purpose: RapidAPI gives 100 calls every month; api.market gives a 7-day trial with 100 calls. A Zyla listing has also been submitted and is under review.

两处免费口径不一样，别看混：RapidAPI 是每月 100 次；api.market 是 7 天试用共 100 次。Zyla 也已提交，正在审核中。

04Questions buyers actually ask买家真正在问的问题

• What is the best email verification API?
• Why does my email verifier charge full price for "unknown" and catch-all results?
• Can a catch-all email address actually be verified?
• How accurate are email verification APIs, really?
• How much should it cost to verify 10,000 emails?
• Does an email verification API check whether the actual mailbox exists?
• How do I verify a list of emails in bulk without calling the API one by one?
• What does a "risky" verdict mean — should I still send to risky addresses?
• How do I catch email typos like gmial.com at signup?
• Why are a third of the addresses on my B2B list on catch-all domains?

05FAQ常见问题