EmailCheck / Questions问题页 / Can a catch-all email address actually be verified?
Can a catch-all email address actually be verified?Catch-all 邮箱地址真的能被验证吗？
No — not fully. A catch-all domain accepts mail for every address, so nothing short of actually sending a message (and watching what happens) can confirm an individual mailbox on it. An honest tool returns a risk signal instead of a verdict. Even the biggest vendors barely move this number: published benchmark figures put catch-all “resolution” at about 12% for ZeroBounce, 8% for NeverBounce and 5% for MillionVerifier.
不能——没法完全验证。Catch-all 域名对一切地址都收信，所以除了真发一封信再看后续，没有任何办法能确认上面某个具体邮箱。诚实的工具会返回风险信号，而不是裁决。就连最大的厂商也撬不动这个数字：公开基准数据里，catch-all 的「解决率」约为 ZeroBounce 12%、NeverBounce 8%、MillionVerifier 5%。
What “catch-all” actually means「Catch-all」到底是什么意思
A catch-all (accept-all) mail server is configured to accept messages for any local part at the domain — real mailboxes, former employees, addresses that never existed. From the outside, a probe gets the same “accepted” answer for all of them, which is exactly why verification stalls: the server has promised to never say no.
This is a deliberate, legitimate configuration, common at companies that would rather receive a mis-addressed message than lose it. Roughly 30–40% of the addresses on a typical B2B list sit on catch-all domains, so this is not an edge case — it is a third of your list.
Catch-all（全收）邮件服务器被配置成：域名下任何本地名都收信——真邮箱、前员工、从来不存在的地址，一视同仁。从外面探测，得到的永远是同一个「接受」回答，这正是验证卡住的原因：这台服务器承诺了永不拒绝。
这是有意为之的合法配置，常见于「宁可收错一封、不可漏一封」的公司。典型 B2B 名单里约 30–40% 的地址落在 catch-all 域名上——这不是边角情况，是你名单的三分之一。
What vendors who claim to “verify” catch-all are doing声称能「验证」catch-all 的厂商在做什么
When a tool shows a confident verdict for a catch-all address, it is not reporting a probe — it is scoring: domain age, provider patterns, engagement data from its own sending network, or guesswork. Some of that scoring is useful. What is not honest is presenting it as verification. The published resolution rates — 12%, 8%, 5% for the three best-known vendors — tell you how much certainty is actually available: a graded signal is the truthful product, and it is what EmailCheck returns in the catchAllRisk field, labelled as a signal in every response.
当一个工具对 catch-all 地址给出自信裁决时，它报的不是探测结果，而是打分：域名年龄、服务商模式、它自己发送网络里的互动数据，或者猜测。这类打分有些是有用的。不诚实的是把它包装成「验证」。公开的解决率——三家最知名厂商 12%、8%、5%——说明真实能拿到的确定性就这么多：分级信号才是诚实的产品形态，EmailCheck 在 catchAllRisk 字段里返回的正是这个，并在每个响应里注明它是信号。
What to do with catch-all addressesCatch-all 地址该怎么处理
Keep them, but keep them apart. Segment catch-all addresses out of your main list, rank them by the risk signals you do have (domain age, MX health, whether the address pattern matches a real person's name format), and mail them in small batches with bounce monitoring. The mistake is binary thinking — deleting a third of a B2B list throws away real customers, and mailing it blind risks your sender reputation.
留着，但分开。把 catch-all 地址从主名单里分出来，用你手里有的风险信号排序（域名年龄、MX 健康度、地址格式像不像真人姓名格式），小批量发送并盯退信。二元思维才是错误：删掉 B2B 名单的三分之一等于扔掉真实客户，闭眼群发则拿发信声誉冒险。
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" 和一段说明，把查过的范围写清。