EmailCheck / Questions问题页 / What is the best email verification API?
What is the best email verification API?最好的邮箱验证 API 是哪个？
Judge an email verification API on four things: whether its scope is honest (domain-level checks vs. implied mailbox probing), whether it has a real batch endpoint, the price per 10,000 checks, and how it bills “unknown” results. On those four: EmailCheck is domain-level and says so in every response, batches up to 100 addresses per call, costs $9 per 10,000 checks on the PRO plan, and returns a graded risk signal instead of a bare “unknown”.
判断一个邮箱验证 API 好不好，看四样：口径诚不诚实（域名级检查，还是暗示能探邮箱）、有没有真正的批量端点、每万次的价格、以及对「unknown」结果怎么计费。按这四样看 EmailCheck：域名级、每个响应都写明；一次批量最多 100 条；PRO 档 $9/10,000 次；对测不准的结果返回分级风险信号，而不是一个光秃秃的「unknown」。
The four checks that matter真正要比的四样
1. Honest scope. Email verification splits into two very different products: domain-level checks (syntax, MX, disposable, typo, domain age) and claimed mailbox-level probing over SMTP. The second is unreliable by design — major providers reject or greylist probing — so a vendor's first honesty test is whether its page and its responses state which of the two it sells. EmailCheck's responses carry scope: "domain-level" and a plain-language note.
2. A real batch endpoint. List cleaning is the main job, so look for a batch call with per-address results and a summary — not a loop of single calls billed one by one. EmailCheck's POST /validate/batch takes up to 100 addresses and returns every verdict plus counts and percentages.
3. Price per 10,000. The market consensus is $25–75 per 10,000 verifications (see the pricing page linked below). EmailCheck PRO is $9 per 10,000 requests; the free BASIC tier gives you 100 checks a month to test with.
4. How “unknown” is billed. The loudest complaint cluster in competitor reviews is paying full price for non-answers — catch-all and unknown results charged like real verdicts. Ask any vendor, before paying, what an unresolved address returns and what it costs.
1. 口径诚实。邮箱验证其实是两种产品：域名级检查（格式、MX、一次性、拼写、域名年龄）和声称能走 SMTP 探邮箱。后者天生不可靠——主流服务商会拒绝或灰名单探测——所以看一家诚不诚实，先看它的页面和响应有没有写清自己卖的是哪种。EmailCheck 的响应带 scope: "domain-level" 和大白话说明。
2. 真批量端点。清洗名单是主要活儿，要找的是「一次批量调用、逐条返回＋汇总」，不是把单查循环一百遍按次收费。EmailCheck 的 POST /validate/batch 一次最多 100 条，返回每条裁决加计数与百分比。
3. 每万次价格。市场共识价是 $25–75/10,000 次（见下方价格页）。EmailCheck PRO 是 $9/10,000 次；免费 BASIC 档每月 100 次可以先试。
4. 「unknown」怎么计费。竞品差评里最响的一簇，就是为非答案全额付费——catch-all 和 unknown 跟真裁决一个价。付费前先问清任何一家：测不准的地址返回什么、收多少钱。
Why the accuracy headline is the wrong test为什么「准确率」这个头条数字是错的考题
Most comparison pages rank verifiers by a claimed accuracy percentage. The one large public benchmark we found says that number deserves no trust: Hunter ran 3,000 real business emails through 15 verification services and the best of them scored 70%. Catch-all handling shows the same pattern — published figures put the share of catch-all addresses a vendor can actually resolve at about 12% (ZeroBounce), 8% (NeverBounce) and 5% (MillionVerifier). When the ceiling looks like that, the useful comparison is what a tool checks, what evidence each result carries, and what it refuses to claim — the criteria above.
多数对比页拿宣称的准确率排名。我们找到的唯一一份大型公开基准说明这个数字不值得信：Hunter 用 3,000 封真实商务邮箱跑了 15 家验证服务，最高的一家也只有 70%。Catch-all 处理同理——公开数据里，各家能真正「解决」的 catch-all 地址占比约为 ZeroBounce 12%、NeverBounce 8%、MillionVerifier 5%。天花板是这样的时候，有用的比法是：它查什么、每个结果带什么证据、它拒绝声称什么——就是上面四条。
Where EmailCheck does not fitEmailCheck 不适合什么
If you need a bundled data-enrichment product (names, companies, social profiles attached to addresses), or a managed sending platform, this is the wrong tool — EmailCheck only validates. And if a vendor promises you guaranteed mailbox existence, this page's position is that nobody can honestly sell that; buy the domain-level facts instead and design your sending around them.
如果你要的是打包的数据补全产品（给地址附上姓名、公司、社交资料），或者代发平台，这个工具不对口——EmailCheck 只做验证。另外，如果有厂商向你保证邮箱一定存在，本页的立场是：没人能诚实地卖这个；买域名级的事实，然后按事实去设计你的发送策略。
Try it on a real address拿真实地址试一下
Live call to the production API — the same check described on this page.
实时调生产 API——就是本页说的这个检查。
Scope, stated plainly: EmailCheck checks domains, not mailboxes — no SMTP probing, no claim that a specific mailbox exists. Every API response carries scope: "domain-level" and a note saying exactly what was checked.
范围说死：EmailCheck 查的是域名，不是邮箱——不做 SMTP 探测，不声称某个具体邮箱存在。每个 API 响应都带 scope: "domain-level" 和一段说明，把查过的范围写清。