Catching Email Typos Without Blocking Anyone

gamil.com is not a typo to your form

Someone finds your organization, decides you're worth contacting, fills in your form, and types their email one letter off: gamil.com instead of gmail.com. Every validator on earth waves it through, because it should — it's a perfectly formed address. It just belongs to nobody.

Then your reply, your report, your registration confirmation goes out, bounces silently somewhere you'll never look, and the visitor waits. From their side of the screen the story is simple: they wrote to you, and you never answered. The typo was theirs; the silence looks like yours.

Where it actually costs you

This is a lead-capture problem wearing a technical costume. The people typing their email into your site are the ones you spent everything else to get there — the member renewing, the donor mid-decision, the event guest, the prospect requesting your report. Losing one to a transposed letter means the most expensive part already worked and the cheapest part failed.

And the volume is not theoretical. A few percent of hand-typed addresses carry a typo, and the most common ones are boringly predictable: gamil, gmial, hotmial, yaho, and the .cm and .con endings where a finger missed the o.

When to check — and when to leave people alone

Checking on every keystroke is the eager-intern version: technically attentive, practically exhausting. Half-typed addresses all look wrong, so the form spends ten seconds flagging an 'error' the visitor was two characters from fixing on their own.

The calm version checks exactly twice: when the visitor leaves the field after typing, and once more when they hit submit. Those are the two moments the address is supposed to be finished — the only moments a suspicion is worth raising.

Ask, explain, and let them win

When the check does fire, it should read like a colleague glancing over your shoulder, not a bouncer: “gamil.com is usually a typo of gmail.com. One tap fixes it — or keep what you typed if that's really your address.” The explanation matters. 'Invalid email' teaches nothing and insults the people who are right; naming the suspected slip lets the visitor make the call in one second.

And it must be a question, never a wall — because improbable addresses are real all the time. Somebody genuinely has that domain. The safe design flags only a short list of famous typos and obvious .com slips, never second-guesses an organization's own domain (yourorg.cm might really be Cameroonian), and remembers the answer so it never asks twice.

Every public form on this site works exactly this way — the contact form, the booking flow, event RSVPs, and the free scanner. Type gamil.com into any of them and watch it ask, once, politely.

The quiet rule underneath

The pattern generalizes past email: validation exists to protect the visitor's intent, not the database's feelings. A form that blocks real people to catch hypothetical mistakes has its loyalties backwards. Catch what you can name, ask instead of assume, and make being right effortless for the human on the other end.

That's this series: the small, specific decisions that separate a form people finish from a form people abandon — one decision at a time.