EmailCheck / Questions问题页 / What does a “risky” verdict mean — should I still send to risky addresses?
What does a “risky” verdict mean — should I still send to risky addresses?「Risky」裁决是什么意思——有风险的地址还要不要发？
“Risky” means the address scored 50–79, or its domain looks like a typo of a known provider. It does not mean “will bounce” — it means “don't treat this like a clean address”. Fix the typo if the response carries a suggestion; if you mail risky addresses at all, send to them separately, in small batches, and watch the bounces before ever mixing them into your main list.
「Risky」意味着这个地址得分在 50–79，或者它的域名看起来是某个已知服务商的拼写错误。它不等于「一定退信」——它等于「别把这当成干净地址」。响应带 suggestion 就先改对拼写；如果你决定给 risky 地址发信，分开发、小批量发、盯住退信，永远别把它们混进主名单一起发。
What pushes an address into “risky”什么会把地址推到「risky」
The score starts at 100 and loses points for concrete, named reasons — you can see them in the checks object of every response:
- Disposable domain. Try the box on this page with
someone@mailinator.com: the live API scores it 50 — risky — purely because the domain is a throwaway inbox service. - Likely typo. A misspelled provider domain (gmial.com) is flagged with a correction; the person is probably real, the address is not.
- Catch-all risk. The domain accepts everything, so the address cannot be confirmed either way.
- Role account / missing signals. Role addresses and domains with thin registration or routing data lose points without being outright invalid.
Risky is deliberately a “handle with care” bucket, not a polite word for invalid: invalid means the address failed basic checks (bad syntax, no MX, a score under 50).
分数从 100 起，因为具体、具名的原因扣分——每个响应的 checks 里都能看到：
- 一次性域名。用本页的框试
someone@mailinator.com：生产 API 给它 50 分——risky——纯粹因为该域名是临时收件箱服务。 - 疑似拼写错误。拼错的服务商域名（gmial.com）会被标记并给纠正建议；人多半是真的，地址是假的。
- Catch-all 风险。该域名全收，地址无法往任何一边确认。
- 角色账号/信号稀薄。角色地址、注册或路由数据单薄的域名会扣分，但不至于直接判无效。
Risky 是刻意设的「小心处理」桶，不是 invalid 的委婉说法：invalid 意味着地址没过基本检查（格式错、无 MX、分数低于 50）。
A practical playbook for risky addressesRisky 地址的实用处理法
- Apply the suggestion first. If
typoLikelyis true and asuggestionis present, that address is one corrected character away from being clean — fix it in your data, or better, at the source (see the typo page linked below). - Segment, don't blend. Keep risky addresses in their own segment so a bounce spike can never touch the reputation your main list depends on.
- Test small, then decide by evidence. Send to a small slice, read the actual bounces and engagement, and promote or suppress based on what happened — not on the label alone.
- Suppress on first hard bounce. A risky address that hard-bounces has told you everything; remove it permanently.
- 先用纠正建议。如果
typoLikely为真且有suggestion，这个地址只差改对一个字符就干净了——在数据里改掉，或者更好，在源头改（见下方拼写页）。 - 分仓，别混。把 risky 地址放进独立分区，退信尖峰永远碰不到主名单依赖的声誉。
- 小批试投、按证据决定。先发一小片，读真实退信与互动，再决定升舱还是压掉——不要只看标签。
- 第一次硬退就永久压掉。Risky 地址硬退了，该说的都说了，永久移除。
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" 和一段说明，把查过的范围写清。