Of all the ways a sign-up quietly fails, the domain typo is the most maddening, because everything looks fine. The user typed an address, hit submit, saw a success screen — and then jane@gmial.com bounced into a void she’ll never check. She thinks she signed up. You think she gave a bad address. Nobody’s wrong exactly, and the lead is gone. A typo checker exists to catch that mistake in the half-second before it becomes permanent.
How the check works
The domain half of an email is remarkably predictable — a huge share of consumer sign-ups land on a short list of providers: gmail.com, yahoo.com, hotmail.com, outlook.com, icloud.com, aol.com. That predictability is what makes typo correction reliable. The tool measures the edit distance (also called Levenshtein distance — the number of single-character insertions, deletions or substitutions) between the domain someone typed and each known good domain. When a typed domain is one or two edits away from a popular one, it’s almost certainly a slip, and we surface a “did you mean” suggestion:
gmial.com→ transposed letters, one edit fromgmail.comhotnail.com→ one substitution fromhotmail.comyaho.com→ one deletion fromyahoo.comoutlok.com→ one deletion fromoutlook.comgmail.co/gmail.con→ a mistyped TLD on an otherwise correct domain
Because it’s distance-based, the check is deliberately conservative: a domain that’s genuinely different from every provider on the list gets left alone. Your own company domain or a niche host won’t be “corrected” into something it isn’t.
Why this matters more than it looks
Typos aren’t just lost leads — they actively hurt your sending. Mail to a misspelled domain either bounces immediately (if the typo’d domain doesn’t resolve) or, worse, gets accepted by a squatter domain that registered the common misspelling on purpose. Either way your bounce rate climbs, and mailbox providers read a rising bounce rate as a reputation signal. The fix is almost free: catch the typo at the point of entry, show the suggestion, let the user confirm. One extra click saves a lead and protects your deliverability.
Typo checking vs. verification
A typo checker corrects the obvious domain slips, but it doesn’t know whether the corrected address has a real mailbox behind it, and it won’t catch a mistyped local part (jhon@gmail.com instead of john@) because that’s indistinguishable from a legitimate name. For those, you need to go further:
- Pair it with the Email Syntax Validator to reject structurally broken addresses first.
- Run the corrected address through the Email Verifier to confirm the domain has MX records and the mailbox answers over SMTP.
- Screen for throwaways with the Disposable Email Checker.
Put it on the form
The highest-value place for typo detection is the sign-up form itself, in real time, while the user is still on the page and can fix it. Wire this check in through the API so a “Did you mean gmail.com?” prompt appears the moment someone tabs out of a fat-fingered address. It’s one of the rare deliverability improvements your users will actually thank you for.
Frequently asked questions
- How does the email typo checker work?
- It measures the edit distance (Levenshtein) between the typed domain and common providers like gmail.com and outlook.com. One or two edits away triggers a suggestion; genuinely different domains are left untouched.
- Does it fix typos in the local part before the @?
- No — only the domain. A mistyped name like
jhon@is indistinguishable from a real one, so there’s nothing safe to correct against. The domain half is the predictable part. - Will it wrongly change my company or niche domain?
- No. It only suggests when a domain is one or two edits from a known provider, so your company or niche domain — which isn’t close to any of them — is left exactly as typed.
- Does catching a typo mean the address is valid?
- No — correcting the domain doesn’t prove the mailbox exists. Follow up with the Email Verifier for MX and SMTP checks, and the Syntax Validator for malformed input.