EmailCheck / Questions问题页 / Why do emails bounce, and what can I check before I send?
Why do emails bounce, and what can I check before I send?邮件为什么会退信?发送前能先查什么?
Emails bounce for two families of reasons. Hard bounces are permanent: the domain does not exist, it has no mail server, or the mailbox is gone. Soft bounces are temporary: a full mailbox, a busy or greylisting server, a message refused for size or content. The hard-bounce causes a pre-send check catches — dead domains, missing MX records, typos like gmial.com, disposable addresses — are exactly what EmailCheck screens for, so they never reach your sender reputation.
邮件退信分两大类。硬退是永久性的:域名不存在、没有邮件服务器、或者邮箱已经注销。软退是临时性的:邮箱满了、服务器忙或灰名单、邮件因大小或内容被拒。发送前检查能抓住的硬退原因——死域名、没有 MX 记录、gmial.com 这类拼写错误、一次性地址——正是 EmailCheck 筛的,让它们到不了你的发信声誉那里。
Hard bounce vs. soft bounce硬退与软退
A hard bounce means the receiving server says the address can never accept mail: SMTP replies in the 550 family (“user unknown”, “domain not found”) are the usual shape. Mailing a hard-bounced address again does not help — providers count repeat hard bounces against your sender reputation, and lists are expected to remove them after the first occurrence.
A soft bounce means “not right now”: mailbox full, server temporarily unavailable, greylisting, or a local policy refusal. Soft bounces can clear on their own, but an address that soft-bounces campaign after campaign is telling you something — most sending platforms eventually treat chronic soft bounces as dead addresses and suppress them.
硬退是接收服务器明说这个地址永远收不了信:SMTP 550 一族的回复(「用户不存在」「域名找不到」)是常见形态。对硬退过的地址再发没有用——服务商会把重复硬退记在你的发信声誉上,名单规范是第一次硬退就移除。
软退是「现在不行」:邮箱满了、服务器暂时不可用、灰名单、或本地策略拒收。软退可能自己恢复,但一个地址连续多轮活动都软退,就是在给你信号——多数发送平台最终会把长期软退当作死地址压掉。
The causes you can catch before sending发送前能拦住的原因
Four common hard-bounce causes are visible without sending anything:
- Dead or parked domains — the domain no longer resolves or has no MX records, so there is no mail server to deliver to. This is the single most mechanical cause, and a pre-send check catches it every time.
- Typos — gmial.com, hotmial.com, yahoo.con and friends, typed at signup or mangled in a spreadsheet. A checker flags the likely-intended domain instead of letting the address bounce.
- Disposable addresses — they accept mail today and are gone tomorrow; mailing them later is a scheduled bounce.
- Syntax damage — missing @ signs, spaces, doubled dots from CSV imports and form bugs. Trivial, and embarrassingly common in imported lists.
EmailCheck checks exactly this layer — syntax, domain and MX health, disposable and role flags, typo suggestion, domain age — and returns each one in every response. Paste a list into the batch box on this page and you will see the dead weight separated out before it costs you reputation.
四种常见硬退原因,不发信就能看见:
- 死域名或停放域名——域名不再解析、或没有 MX 记录,根本没有邮件服务器可投。这是最机械的一种原因,发送前检查每次都能抓到。
- 拼写错误——gmial.com、hotmial.com、yahoo.con 之类,注册时手误或在表格里弄坏的。检查工具会标出大概率想写的是哪个域名,而不是放它去退信。
- 一次性地址——今天收信、明天消失;过后再发就是预定的退信。
- 格式损坏——CSV 导入和表单 bug 带来的缺 @、空格、双点。很低级,但在导入名单里尴尬地常见。
EmailCheck 查的正是这一层——格式、域名与 MX 健康、一次性与角色标记、拼写建议、域名年龄——每一项都写在响应里。把名单贴进本页的批量框,发送前就能把死重量先分出来,别拿声誉去付账。
What pre-send checks cannot see发送前检查看不见什么
Be suspicious of any tool that promises a bounce-free list. Two causes call for a sending strategy rather than a check. A mailbox closed on a live domain — an employee who left, a mailbox deleted last month — sits behind a healthy domain with healthy MX records, and surfaces as a bounce on the first send; remove hard bounces after the first occurrence and it never costs you twice. And catch-all domains accept everything, so score those addresses with the catch-all risk signal and handle them as their own segment (see the linked page on what to do with them: segment, do not delete and do not mix).
The honest target is not zero bounces. It is removing every bounce you could have known about, so the small residue that remains is the kind no tool could have caught — and your bounce rate stays in the range providers consider normal list decay rather than neglect.
任何承诺「零退信名单」的工具都值得怀疑。有两个原因要的不是检查,而是发送策略。一是活域名上已关闭的邮箱——员工离职、上个月注销的邮箱——域名和 MX 都健康,会在第一次发送时以退信现形:第一次硬退就移除,它就不会让你付第二次账。二是 catch-all 域名对一切地址照单全收,用 catch-all 风险信号给这些地址打分、单独成段处理(怎么办见链接页:分区,不要删、也不要混)。
诚实的目标不是零退信,而是把「本来能知道」的退信全清掉,剩下的少量残余是任何工具都抓不到的那种——这样你的退信率会停留在服务商眼里「正常名单老化」的范围,而不是「疏于维护」。
A five-minute pre-send routine五分钟发送前流程
- Batch-check the list (the box on this page takes a pasted list; the API takes up to 100 per call) and remove the invalid verdicts — dead domains, no-MX, syntax damage — outright.
- Fix or drop the typos: a suggested correction like gmial.com → gmail.com is a real subscriber recovered; an uncorrectable one is a bounce avoided.
- Segment the catch-all and risky rows into their own send, small and watched, instead of mixing them into your verified core.
- Suppress your own history: anyone who hard-bounced before comes off before the new check, not after — verification is for new addresses, your own bounce log is ground truth for old ones.
- 批量查名单(本页的框可直接贴名单;API 一次最多 100 条),把 invalid 裁决——死域名、无 MX、格式损坏——直接移除。
- 拼写错误能改就改:gmial.com → gmail.com 这样的建议纠正,救回的是一个真实订阅者;改不了的,就是躲过一次退信。
- 把 catch-all 和 risky 行单独分区,小批量、盯着发,不要混进已验证的核心名单。
- 先压自己的历史:以前硬退过的人,在新检查之前就下名单,不要等查完——验证是给新地址的,你自己的退信记录对老地址就是地面真相。
Try the batch endpoint试一下批量端点
One address per line (up to 100). This posts to the production POST /validate/batch.
一行一个地址(最多 100 条)。直接调生产 POST /validate/batch。
What gets checked: address format, domain and MX health, disposable and role-account signals, likely typos with a correction, domain age from registration records, and catch-all risk — combined into a 0–100 score and a valid / risky / invalid verdict.
查什么:地址格式、域名与 MX 健康、一次性与角色账号信号、疑似拼写错误及纠正建议、来自注册记录的域名年龄、catch-all 风险——合成 0–100 分与 valid / risky / invalid 裁决。