Email Normalizer
Normalize email addresses by removing dots, plus aliases, and fixing case. Handles Gmail, Outlook, and Yahoo rules. Supports batch mode.
Email normalization converts addresses to a canonical form by lowercasing, removing dots from Gmail usernames, stripping plus aliases (sub-addressing), and collapsing known domain aliases like googlemail.com to gmail.com. The result reveals when addresses that look different actually deliver to the same inbox. The tool applies provider-specific rules for Gmail, Outlook, Yahoo, iCloud, and generic domains, and supports batch processing with duplicate detection. All processing runs in your browser.
About Email Normalizer
What Does Email Normalization Do?
Normalization strips cosmetic differences a mail server ignores anyway so that two addresses that deliver to the same mailbox compare as equal in code. Gmail treats j.smith+promo@gmail.com and JSMITH@Gmail.com as the same account, but a naive uniqueness check in a database would see two separate strings. Normalizing both to jsmith@gmail.com before storing or comparing fixes that. The canonical form is a pure lowercase address with dots removed from Gmail usernames, plus-aliases stripped where the provider ignores them, and domain aliases unified.
Provider-Specific Normalization Rules
Different email providers handle dots and plus aliases differently. This tool applies the correct rules based on the domain.
| Provider | Dots in Username | Plus Aliases | Case Sensitivity | Example |
|---|---|---|---|---|
| Gmail (@gmail.com) | Ignored (j.o.h.n = john) | Stripped (user+tag = user) | Case-insensitive | J.Smith+promo@Gmail.com -> jsmith@gmail.com |
| Google Workspace | Ignored | Stripped | Case-insensitive | Same as Gmail rules for custom domains using Google |
| Outlook / Hotmail | Kept (significant) | Stripped | Case-insensitive | j.smith+tag@outlook.com -> j.smith@outlook.com |
| Yahoo | Kept (significant) | Uses - not + for aliases | Case-insensitive | j.smith@yahoo.com -> j.smith@yahoo.com |
| iCloud (@icloud.com) | Kept | Stripped | Case-insensitive | j.smith+news@icloud.com -> j.smith@icloud.com |
| Custom domains | Kept (safest default) | Optionally stripped | Case-insensitive | Depends on the mail server configuration |
The Gmail Dot Trick Explained
Gmail completely ignores dots in the local part of an address. This means all of these addresses deliver to the same inbox:
| Variation | Normalized Form | Same Inbox? |
|---|---|---|
| johnsmith@gmail.com | johnsmith@gmail.com | Yes |
| john.smith@gmail.com | johnsmith@gmail.com | Yes |
| j.o.h.n.s.m.i.t.h@gmail.com | johnsmith@gmail.com | Yes |
| j.ohnsmith@gmail.com | johnsmith@gmail.com | Yes |
This creates a deduplication challenge. A user can sign up for your service multiple times using dot variations, and each address looks unique in your database. Normalizing before storing or checking for duplicates eliminates this problem.
Plus Aliases (Sub-addressing)
Plus aliases let users create unlimited variations of their email address by adding +anything before the @ sign. The part after + is ignored for delivery but can be used for filtering.
| Address | Delivered To | Common Use |
|---|---|---|
| user+shopping@gmail.com | user@gmail.com | Track which sites share your email |
| user+newsletter@gmail.com | user@gmail.com | Filter newsletters automatically |
| user+trial1@gmail.com | user@gmail.com | Create multiple trial accounts (abuse case) |
| user+spam@outlook.com | user@outlook.com | Works on Outlook/Hotmail too |
Stripping plus aliases during normalization catches users who create multiple accounts with the same base address. However, some legitimate users use plus aliases for organisation, so stripping them may not always be appropriate.
Normalization Steps
| Step | What It Does | Applies To |
|---|---|---|
| 1. Lowercase the entire address | Converts JSmith@Gmail.COM to jsmith@gmail.com | All providers (RFC 5321 says domain is case-insensitive, local part technically is provider-specific) |
| 2. Remove dots from local part | j.smith becomes jsmith | Gmail and Google Workspace only |
| 3. Strip plus alias | user+tag becomes user | Gmail, Outlook, iCloud, optionally custom domains |
| 4. Normalize domain aliases | googlemail.com becomes gmail.com | Known domain aliases |
| 5. Trim whitespace | Removes accidental leading/trailing spaces | All |
When to Normalize Emails
| Use Case | Normalize? | Why |
|---|---|---|
| User registration (uniqueness check) | Yes | Prevents duplicate accounts via dot tricks and plus aliases |
| Mailing list deduplication | Yes | Avoids sending duplicate emails to the same inbox |
| CRM contact import | Yes | Merges duplicate contacts |
| Storing the user's email for sending | No - store the original | The user may use the plus alias for filtering; sending to the normalized form bypasses that |
| Email verification link | No | Send to the exact address the user provided |
A common pattern is to normalize for uniqueness checks but store the original address for communication. This gives you deduplication without breaking the user's filtering setup.
Worked Example: Normalizing Five Gmail Variants
Take these five signups collected from a real-world form and trace what normalization produces.
| Raw Input | Step 1 - Lowercase | Step 2 - Remove dots (Gmail) | Step 3 - Strip plus alias | Step 4 - Unify domain | Canonical |
|---|---|---|---|---|---|
| J.Smith+Promo@Gmail.com | j.smith+promo@gmail.com | jsmith+promo@gmail.com | jsmith@gmail.com | jsmith@gmail.com | jsmith@gmail.com |
| JSmith@googlemail.com | jsmith@googlemail.com | jsmith@googlemail.com | jsmith@googlemail.com | jsmith@gmail.com | jsmith@gmail.com |
| j.smith@GMAIL.COM | j.smith@gmail.com | jsmith@gmail.com | jsmith@gmail.com | jsmith@gmail.com | jsmith@gmail.com |
| j.s.m.i.t.h+newsletter@gmail.com | j.s.m.i.t.h+newsletter@gmail.com | jsmith+newsletter@gmail.com | jsmith@gmail.com | jsmith@gmail.com | jsmith@gmail.com |
| JSmith+Free_Trial@Gmail.com | jsmith+free_trial@gmail.com | jsmith+free_trial@gmail.com | jsmith@gmail.com | jsmith@gmail.com | jsmith@gmail.com |
All five reduce to the same canonical address. If your signup form rejects a duplicate signup based on the raw string, five accounts slip through. If it compares the canonical form, only the first one succeeds.
Is the Local Part of an Email Address Case-Sensitive?
Technically yes, in practice no. RFC 5321 §2.3.11 states the local part "MUST be interpreted and assigned semantics only by the host specified in the domain part," which leaves case sensitivity up to the receiving server. RFC 5321 §4.1.2 also instructs SMTP implementations to preserve case during transport because some hosts might care. Every major provider (Gmail, Outlook, Yahoo, iCloud, Fastmail, ProtonMail) has chosen to ignore case in the local part. Lowercasing during normalization is therefore safe for the addresses 99% of users have, but a custom corporate mail server running older software could theoretically distinguish Alice@example.com from alice@example.com. The domain part is always case-insensitive per RFC 5321 §2.3.5 and RFC 1035, so lowercasing domains is always safe.
Known Domain Aliases
Several providers run multiple domains that all route to the same mailbox. Unifying these during normalization improves deduplication accuracy.
| Primary Domain | Known Aliases | Notes |
|---|---|---|
| gmail.com | googlemail.com | googlemail.com was used in the UK, Germany, and a handful of other countries before Google consolidated to gmail.com |
| outlook.com | hotmail.com, live.com, msn.com, outlook.co.uk, hotmail.co.uk | Microsoft routes all Consumer Microsoft accounts to the same mailbox regardless of which alias is used at signup |
| yahoo.com | ymail.com, rocketmail.com, yahoo.co.uk, yahoo.co.in | Yahoo consolidated acquired brands - messages delivered to any alias land in the same inbox |
| icloud.com | me.com, mac.com | Apple retained legacy domains for users who registered before the iCloud transition in 2012 |
| protonmail.com | proton.me, pm.me | Proton rebranded from ProtonMail to Proton in 2022 and now provisions all three domains per account |
How Do Yahoo Disposable Addresses Work?
Yahoo Mail Plus subscribers can create disposable addresses in the form basename-keyword@yahoo.com. The base name is a single short string chosen once per account and cannot be changed, while the keyword varies per address. That means pete-shopping@yahoo.com and pete-amazon@yahoo.com both deliver to the same account as long as the base name is pete. Because the hyphen separates base from keyword, a Yahoo-specific normalizer would strip everything from the first hyphen onwards. This tool leaves Yahoo addresses alone by default because hyphens are also used in normal Yahoo usernames, so stripping them programmatically risks false positives. Treat Yahoo normalization as best-effort and pair it with manual review if duplicate detection matters.
Common Pitfalls When Deduping by Canonical Email
- Storing only the canonical form. Users who filter mail with plus aliases stop receiving your emails if you send to the stripped address. Store the original for sending, the canonical for comparison.
- Assuming Outlook keeps dots. Outlook does preserve dots in the local part, so first.last@outlook.com and firstlast@outlook.com are different inboxes. Do not apply the Gmail dot rule to Microsoft domains.
- Normalizing Yahoo like Gmail. Yahoo does not ignore dots and does not use plus for aliases - dot removal gives you the wrong mailbox.
- Missing googlemail.com. A legacy UK user who signed up as pete@googlemail.com in 2008 and pete@gmail.com in 2024 has one inbox but two entries in your database unless the domains are unified.
- Using a regex to validate email format. RFC 5322 permits quoted local parts, IP-literal domains, and internationalized addresses. Regex attempts at full validation almost always fail. Use a simple presence check for "@" and a DNS or double-opt-in flow for confidence that the address exists.
- Lowercasing addresses before hashing for marketing hashes. Audience APIs from Meta, Google Ads, and LinkedIn require SHA-256 of the lowercased email - so normalization order matters and must match their docs exactly.
Is Dedup by Canonical Email Legal?
Normalizing emails for fraud prevention and account uniqueness is explicitly allowed under GDPR Article 6(1)(f) legitimate interest when it is proportionate and users are informed in the privacy notice. It is also consistent with CAN-SPAM in the US, which only regulates the commercial content of messages, not how you store or compare addresses. However, using canonical form to merge users without informing them can breach data-minimisation principles if the merged profile includes data one of the aliases did not consent to. Document your normalization logic in your privacy policy, and give users a way to see and separate merged accounts if they ask. The Regex Tester is useful for building the simple @-presence check described above; the Remove Duplicates tool handles plain-text list dedup after you have normalized, and the Phone Number Formatter solves the equivalent problem for international phone numbers.
Batch Processing and Copy Formats
Paste multiple email addresses (one per line) and the tool normalizes all of them at once. Duplicates are highlighted after normalization with an amber badge so you can spot addresses that look different but deliver to the same mailbox. Copy results as a clean newline-separated list for pasting into a text editor, or as JSON (original, normalized, provider keys) for importing into a database, CRM, or ETL pipeline. The largest tested batch is 10,000 addresses in under a second; because all processing stays in the browser, the raw list never leaves your machine.
Sources
- RFC 5321 - Simple Mail Transfer Protocol (IETF)
- RFC 5233 - Sieve Email Filtering: Subaddress Extension (plus-addressing spec)
- Google Support - Dots do not matter in Gmail addresses
- Yahoo Help - Create disposable email addresses in Yahoo Mail
- Microsoft Support - Email aliases in Outlook.com
- GDPR Article 6 - Lawfulness of processing
- US FTC - CAN-SPAM Act Compliance Guide
Frequently Asked Questions
What does email normalization do?
It converts email addresses to a canonical form by lowercasing, removing dots in Gmail usernames (j.o.h.n becomes john), and stripping plus aliases (user+tag becomes user). This helps identify duplicate accounts.
Which email providers have special rules?
Gmail ignores dots and plus aliases in the username part. Outlook ignores plus aliases but keeps dots. Yahoo has neither rule. The tool applies the correct rules based on the domain.
Does it work with custom domains?
For non-Gmail, non-Outlook, non-Yahoo domains, the tool lowercases the address and optionally strips plus aliases. Custom domain behaviour depends on the mail server, so the tool shows what a standard normalization would produce.
Can I normalize multiple emails at once?
Yes. Paste multiple email addresses, one per line, and the tool normalizes all of them. It also highlights any duplicates that appear after normalization.
Is this useful for deduplication?
Absolutely. Many users create multiple accounts using dot variations or plus aliases. Normalizing reveals that j.o.h.n+promo@gmail.com and john@gmail.com are the same mailbox.
Related Tools
Link to this tool
Copy this HTML to link to this tool from your website or blog.
<a href="https://toolboxkit.io/tools/email-normalizer/" title="Email Normalizer - Free Online Tool">Try Email Normalizer on ToolboxKit.io</a>