EmailCheck / Questions问题页 / How do I fix email address typos in a mailing list?
How do I fix email address typos in a mailing list?怎么修复邮件名单里的邮箱拼写错误?
Fix the domain, never guess the name. Most typos in a mailing list live in the domain — gmial.com for gmail.com, a missing @, the wrong TLD — and those have an obvious correction a verifier can suggest. Apply a suggestion only when it is unambiguous, re-verify the corrected address before it rejoins the list, and delete addresses whose local part looks wrong instead of inventing a mailbox for a real person.
修域名,永远不要猜名字。名单里的拼写错误大多出在域名上——gmail 写成 gmial、漏了 @、顶级域名写错——这些都有明确的纠正,验证工具能给出建议。只在建议毫无歧义时才采用,纠正后的地址重新验证过再放回名单;本地部分(@ 前面)看着不对的地址直接删掉,不要替真人编一个邮箱出来。
The typos that are safe to fix — and the ones that aren't哪些拼写错误能安全修,哪些不能
Safe: domain typos with one obvious correction. Transposed or missing letters in a major provider domain (gmial.com, gmal.com, hotmial.com), a missing @, a wrong TLD (.con for .com), a doubled dot. The intended domain is not in doubt, and the person typed their real local part — you are restoring what they meant to type.
Unsafe: anything in the local part. If the name before the @ looks wrong, there is no way to know the right one — jonsmith@ could be johnsmith@, jon.smith@, or a different person entirely. Guessing delivers someone else's mail, or a stranger's, and can put you on the wrong side of consent. Delete those rows, or recover them through a channel where the person confirms the address themselves.
能修:纠正唯一明确的域名拼写。大服务商域名里字母颠倒或漏字(gmial.com、gmal.com、hotmial.com)、漏 @、顶级域名写错(.con 应为 .com)、多打一个点。目标域名没有疑问,而本地部分是本人真实输入的——你只是在还原他想打的字。
不能修:本地部分的任何猜测。@ 前面的名字看着不对时,没办法知道对的是哪个——jonsmith@ 可能是 johnsmith@、jon.smith@,也可能完全是另一个人。猜中了是把信发给别人,猜错了是发给陌生人,还可能踩到授权同意的边。这类行删掉,或者走能让本人自己确认地址的渠道去找回。
A safe fix workflow一套安全的修复流程
- Check the whole list first. Run the list through the bulk email checker. Rows with a likely typo come back flagged, with a suggested correction attached (EmailCheck returns the suggestion and marks the address typo-likely).
- Apply only unambiguous suggestions. One candidate correction, a real major domain, the local part untouched. Anything else stays unapplied.
- Re-verify every corrected address. A fixed domain doesn't make the row good — run it again and let it earn its verdict like any other address.
- Keep the audit trail. Store original → corrected pairs. If a subscriber ever asks why mail arrived at an address they "never gave you", the trail is your answer.
- 先把整个名单查一遍。用批量检查器跑一遍。疑似拼写的行会被标出来并附上纠正建议(EmailCheck 返回 suggestion 并标记 typo-likely)。
- 只采用毫无歧义的建议。只有一个候选纠正、是真实的大域名、本地部分不动。其他的都不采用。
- 每个纠正后的地址都重新验证。域名修对了不等于这一行就好了——再跑一遍,让它和其他地址一样挣自己的裁决。
- 留好审计记录。存下「原地址 → 纠正后」对照。哪天订阅者问为什么信发到了一个他「从没给过」的地址,这份记录就是你的回答。
Stop the next batch of typos at the door让下一批拼写错误进不了门
Fixing a list is the expensive way to learn this. The cheap way is to check the address while the person is still on the form: a domain typo can be flagged and confirmed with them on the spot ("did you mean gmail.com?"), which is why catching typos at signup beats cleaning them up quarterly, and why teams verify at signup with an API instead of after the first campaign bounces. The list you already have gets the workflow above; the list you're building shouldn't need it.
修名单是学到这一课的贵办法。便宜办法是趁人还在表单上就把地址查掉:域名拼写可以当场标出来并和他确认(「你是想填 gmail.com 吗?」),这正是为什么在注册环节抓拼写胜过每季度清理一次,也是为什么团队选择在注册时用 API 验证、而不是等第一封群发退信了再说。已有的名单走上面的流程;正在攒的名单不应该再需要它。
Try it on a real address拿真实地址试一下
Live call to the production API — the same check described on this page.
实时调生产 API——就是本页说的这个检查。
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 裁决。
Related questions相关问题
- How do I catch email typos like gmial.com at signup?
- Bulk email checker — verify a whole list in one call
- How do I verify emails at signup with an API?
Running this in bulk? The 3,500 Credits Pack ($9.99, one-time) runs EmailCheck through the API at 1 credit per check — credits never expire and work across every connected NewKwLab API.
要批量跑?3,500 积分包($9.99,一次性)通过 API 跑 EmailCheck,每次扣 1 分——积分永不过期,在全部已接入的 NewKwLab API 通用。