> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/list-growth/popups/email-typo-validation.md). # Email Typo Validation Explains how popups now catch mistyped email domains at submission and suggest the correct address. Your popups now spot mistyped email domains and offer a correction, so fewer subscribers are lost to hard bounces. When someone enters their email in your popup and misspells the domain — `gmial.com` instead of `gmail.com` — the address still looks valid, so it gets collected. Every message you send to it then hard-bounces, and that subscriber never hears from you. Your popups now catch these at submission and offer the right address instead. ### What's new * Popups check the email domain when a subscriber submits, and suggest a correction when it's a near-miss of a common provider * Covers `gmail.com`, `icloud.com`, `outlook.com` and `aol.com`, along with common wrong endings such as `.co` or `.cm` in place of `.com` * The suggestion is optional. A subscriber can accept it in one tap, or submit their original address anyway * Anything outside those domains passes through exactly as before — work addresses, regional domains like `outlook.co.uk`, and alternative providers are left alone * **Nothing changes in your setup.** This is on automatically across all your existing popups ### Why this matters In a year of bounce data from one store, around 1.4% of hard bounces came from correctable domain typos. Catching them at signup means a cleaner list, better deliverability, and subscribers who actually receive the welcome message they were expecting. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.recart.com/list-growth/popups/email-typo-validation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.