## Why typos still create hard bounces in 2026 Hard bounces are not only disposable domains and abandoned mailboxes. A large share of them starts with a human mistake at capture: `gmial.com`, a missing letter in a corporate domain, an extra `.con`, or a transposed character in a long address. The form accepts the string, your CRM stores it, and the first campaign pays the reputation cost.
Mailbox providers treat repeated hard bounces as a sender-quality signal. Fixing the typo later in a suppression list is better than nothing, but it is still late. The durable fix is to catch likely mistakes at the moment of signup—before the address ever becomes a send target.
This guide covers practical typo correction at capture: what to detect, how to prompt without blocking conversions, how to log decisions, and how to connect correction to deeper validation so you protect deliverability without annoying real customers. ## What “typo correction at capture” actually means Typo correction is not a replacement for full email validation. It is an early, lightweight gate that sits beside syntax checks and before (or alongside) MX and mailbox-level verification.
At capture you typically want three outcomes: 1. **Accept as typed** — the address looks plausible; proceed. 2. **Suggest a fix** — high-confidence alternative; ask the user to confirm. 3. **Soft-block or warn** — the address fails basic checks or matches a high-risk pattern; do not silently “fix” it into something else.
The critical product rule: never rewrite an email address without an explicit user confirmation when the change could redirect mail to a different person. Silent auto-correct of `j.smith@acme.com` into `j.smith@acne.com` is a privacy and trust failure, even if your distance metric liked the second domain. ## The typo patterns that show up most often ### Consumer domain misspellings Public mailbox domains dominate signup volume, so their misspellings dominate bounce volume.
Common families include: - Adjacent-key errors (`gmial`, `gamil`, `hotmial`) - Missing or doubled letters (`outlok`, `yahho`) - Wrong TLD (`gmail.con`, `yahoo.cm`) - Regional variants confused with the global brand domain Build a curated dictionary of high-volume legitimate domains and a set of known misspellings mapped to the intended domain. Prefer precision over recall: a wrong suggestion trains users to ignore your form.
### Corporate and custom-domain slips B2B forms see different mistakes: - Missing hyphen or subdomain (`mail.company.com` vs `company.com`) - Old brand domains after a rename - Internal-only hostnames that look like email domains but do not accept public mail Here, aggressive “correction” is dangerous. Prefer MX presence checks and a gentle “did you mean?” only when the typed domain has no MX and a single near-neighbor corporate domain is overwhelmingly likely.
### Local-part mistakes The part before `@` is harder. People mistype their own names less often than domains, but copy-paste from chat, plus suffixes like `+tag`, create edge cases. Avoid inventing local-parts. You can still flag: - Consecutive dots - Leading or trailing dots (where the provider rejects them) - Extremely short or punctuation-only local parts - Characters invalid under common provider rules Treat local-part issues as warnings or validation failures, not as auto-rewrites.
## A layered capture flow that converts and protects ### Layer 1: Syntax and normalization Normalize carefully: - Trim whitespace - Lowercase the domain (not necessarily the local-part if you must preserve provider-sensitive casing—most systems lowercase the whole address safely for matching, but store the user’s confirmed form) - Reject spaces and illegal characters early Return a clear inline error for syntax failures.
Do not proceed to typo suggestion until the string is a syntactically valid email shape. ### Layer 2: Dictionary and edit-distance suggestions For the domain: 1. Exact match against an allowlist of known-good high-volume domains → accept. 2. Exact match against a misspelling map → suggest the mapped domain with confirmation. 3.
Else compute small edit distance (typically 1, sometimes 2 for longer domains) against the allowlist → suggest only if a single candidate wins clearly. 4. Else leave the domain as typed and continue to MX / risk checks. Score suggestions with more than raw distance.
Weight by: - Historical signup frequency of the candidate domain in your traffic - Whether the typed domain has MX records - Whether the candidate is in your trusted set If the typed domain already has valid MX, do **not** overwrite it with a “popular” neighbor. That is how you “correct” a real niche provider into a giant free mailbox by accident.
### Layer 3: MX and disposable / role signals After the user confirms the address (original or suggested): - Check MX (or equivalent DNS mail capability) - Flag disposable and high-churn domains per your policy - Flag role accounts (`info@`, `admin@`, `support@`) when your program needs person-level engagement These checks answer “can and should we mail this?” Typo correction answered “did the human mean what they typed?” ### Layer 4: Optional mailbox verification For high-value
flows (paid signup, trial activation, passwordless login), add a deeper mailbox check or confirmation email. Keep it off the critical path for low-friction newsletter forms if latency or provider throttling would hurt conversion—unless bounce risk in that channel is already hurting you. ## UX patterns that users accept ### Suggest, do not silently replace Show the typed value and the suggestion side by side: > You entered **name@gmial.com**. Did you mean **name@gmail.com**?
Buttons: **Use suggestion** / **Keep what I typed** Log which path they chose. That telemetry improves your dictionary and reveals false-positive suggestions. ### Keep latency invisible Typo dictionaries are local and fast. DNS and mailbox checks are not.
Design the UI so: - Syntax + suggestion feel instant - Deeper checks run async with a short spinner only when necessary - Timeouts fail open or fail closed based on risk: paid checkout may fail closed; a content newsletter may accept and validate asynchronously, then suppress before the first blast ### Do not shame the user Copy should feel helpful, not pedantic.
Avoid “invalid email” when you mean “possible typo.” Reserve hard errors for true invalidity. ### Mobile keyboards amplify typos On mobile, adjacent-key errors spike. If a large share of your signups are mobile, bias slightly toward suggestion prompts for the top misspelling families—still with confirmation.
## Policy choices product and deliverability teams must align on ### When “Keep what I typed” is allowed Always allow it when the address passes syntax and MX, even if you suggested something else. The user may have a niche domain you do not know. Punish bad domains later with validation and engagement rules, not by trapping people in a forced rewrite.
### When to hard-block Hard-block (with a clear reason) for: - Domains with no MX and no recoverable suggestion the user accepts - Addresses on your deny list (known spam traps, abused domains you refuse) - Syntax that cannot be a mailbox ### Role and disposable handling Typo correction will not save a `mailinator`-style address, and it should not turn `info@company.com` into a personal mailbox.
Keep those as separate policy layers with their own UX (“Use a personal work email” vs domain suggestion). ## Connecting typo correction to list hygiene downstream Capture is the beginning, not the whole system. 1. **Store provenance** — `capture_source`, `suggested_domain`, `user_accepted_suggestion`, raw vs final address. 2. **Suppress confirmed hard bounces quickly** — if a “kept as typed” address hard-bounces, do not keep retrying; feed the domain misspelling back into your dictionary if patterns emerge. 3.
**Separate confirmation state** — double opt-in or magic-link confirmation remains valuable for proving mailbox ownership beyond typo heuristics. 4. **Protect warmups and blasts** — new, unconfirmed, or high-risk addresses should not ride along on reputation-sensitive IP warmups. Teams that only buy a validation API but skip capture UX still leak bad addresses through CSVs, manual imports, and partner syncs.
Apply the same checks on import: batch-suggest or quarantine rows with high-probability domain typos for human review instead of blasting them.
## Metrics that prove the feature is working Track before/after for the same acquisition channels: - Hard bounce rate on first-send cohorts - Suggestion show rate and accept rate - False-suggestion complaints (support tickets: “you changed my email”) - Signup completion rate (ensure the prompt does not crush conversion) - Time-to-first-validation / added latency at submit A healthy pattern: hard bounces drop, completion stays flat or dips only slightly, and accept rate on suggestions stays
high (often well above 70% for top consumer misspellings w
Related Articles
Learn how to build responsive email templates that load fast, reinforce trust, and improve clicks, conversions, and revenue without hurting deliverability.
Invalid email addresses quietly tax every campaign. They waste sends, distort analytics, increase bounce rates, and can push mailbox providers to distrust...
Email remains one of the strongest direct channels for engagement and revenue. Results still depend on list quality. Stricter filters, privacy expectations,...
Clean phone data is a practical asset for SMS, voice outreach, and account security. Without validation, teams waste spend, hurt carrier reputation, and...
Discover the critical differences between real-time and batch email validation, their benefits, and how to integrate both for optimal email list hygiene and deliverability in 2026.
Discover how seed list testing is crucial for email deliverability and protecting your sender reputation. Learn best practices for inbox placement and campaign success.
Introduction Every bounce is more than a failed delivery. It is a quiet signal to mailbox providers that your list may be careless, outdated, or pu...
Discover the true financial drain of poor data quality and how strategic list hygiene practices in 2026 can transform your marketing, boost efficiency, and deliver substantial ROI.
Explore SESender
SESender brings audience preparation, contact validation, sender and provider controls, scheduling, delivery tracking, and campaign reporting into one workspace. Review the current product and pricing information before deciding whether the platform fits your messaging workflow.
Explore the platform or review pricing.