EmailCheck / Questions问题页 / How do I catch email typos like gmial.com at signup?
How do I catch email typos like gmial.com at signup?怎么在注册环节抓住 gmial.com 这类邮箱拼写错误？
Check the domain, not just the format. When an address's domain looks like a misspelling of a known provider, EmailCheck returns typoLikely: true and a suggestion — gmial.com becomes gmail.com. Put that check in your signup form and ask “did you mean …?” before the account is created: recovering a mistyped address at signup is far cheaper than a bounced confirmation email and a lost user.
查域名，不只是查格式。当地址的域名看起来像某个已知服务商的拼写错误时，EmailCheck 返回 typoLikely: true 和一个 suggestion——gmial.com 变回 gmail.com。把这个检查放进注册表单，在账号创建前问一句「你是不是指……？」：在注册环节救回一个拼错的地址，比事后一封退信的确认邮件加一个流失的用户便宜得多。
Why typos sail through format checks为什么拼写错误能穿过格式检查
test@gmial.com is a perfectly well-formed email address: valid syntax, and the domain itself exists. What is broken is invisible to a regex — the user meant Gmail. Run it in the box on this page and look at the live result: score 40, verdict invalid (the typo domain has no MX records), with suggestion: test@gmail.com attached. Two facts did the work: the domain is one edit away from a major provider, and it cannot actually receive mail.
The cost of missing this at signup is paid later and in silence: the confirmation email goes nowhere, the user never activates, and support eventually hears “your emails never arrive” — if the user bothers at all.
test@gmial.com 是一个格式完全合法的邮箱地址：语法没错，域名本身也存在。坏掉的地方正则看不见——用户想写的是 Gmail。用本页的框跑它，看生产结果：40 分、裁决 invalid（这个拼错域名没有 MX 记录），并附 suggestion: test@gmail.com。起作用的是两个事实：该域名与主流服务商只差一次编辑距离；且它实际上收不了信。
在注册环节漏掉它的代价是事后默默付的：确认邮件无处可去，用户永远不激活，客服最终听到「你们的邮件从来没到过」——如果用户还愿意说的话。
The form pattern that fixes it能修好它的表单模式
- On submit (or on blur of the email field), call
GET /validate?email=...— it is one fast, local-computation check. - If
typoLikelyis true, show the suggestion inline: “Did you mean test@gmail.com?” with one-tap accept. Never rewrite the address silently — the suggestion can occasionally be wrong, and the user owns their address. - If the verdict is invalid for other reasons (no MX, disposable domain), say so specifically rather than with a generic “invalid email” — the response tells you which check failed.
- Log the correction rate. Teams are routinely surprised how much of their “bad email” problem is this one pattern.
- 在提交时（或邮箱字段失焦时）调
GET /validate?email=...——一次快速的本地计算检查。 - 如果
typoLikely为真，内联显示建议：「你是不是指 test@gmail.com？」并给一键接受。永远不要静默改写地址——建议偶尔也会错，地址是用户的。 - 如果裁决因其他原因 invalid（无 MX、一次性域名），把具体原因说出来，而不是笼统一句「邮箱无效」——响应里写了是哪项检查没过。
- 记录纠正率。团队通常会惊讶：他们的「坏邮箱」问题有多大比例就是这一个模式。
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" 和一段说明，把查过的范围写清。