Email Normalizer

How the Email Normalizer Works

What the Tool Does

The Email Normalizer canonicalizes email addresses by lowercasing the entire address, removing dots from the local part (Gmail-style), and stripping plus-addressing aliases (user+tag@domain becomes user@domain). This reveals when multiple seemingly different email addresses actually deliver to the same inbox, helping you detect duplicate accounts and normalize contact databases.

Common Developer Use Cases

Product engineers use email normalization to prevent users from creating multiple free-trial accounts using dot tricks (j.ohn@gmail.com = john@gmail.com) or plus aliases (john+spam@gmail.com). Marketing teams deduplicate mailing lists before sending campaigns to avoid double-sends. Anti-fraud systems normalize emails during signup to detect previously banned users attempting re-registration with cosmetic email variations.

Data Formats, Types, or Variants

Gmail and Google Workspace ignore dots in the local part and support plus-addressing. Outlook/Hotmail ignores plus-addressing but does not ignore dots. Yahoo uses a hyphen-based alias system instead of plus. Fastmail and ProtonMail support plus-addressing. The tool applies Gmail-style normalization rules by default (remove dots, strip plus aliases, lowercase), which covers the majority of consumer email addresses but may over-normalize for corporate mail servers that treat dots as significant.

Common Pitfalls and Edge Cases

Not all mail servers ignore dots — removing dots from non-Gmail addresses can map two distinct users to the same normalized address, causing false deduplication. The domain part of email is case-insensitive per RFC 5321, but the local part is technically case-sensitive (though almost no server enforces this). Plus-addressing is increasingly used as a legitimate privacy tool, so blocking it may frustrate privacy-conscious users. International domain names (IDN) require punycode normalization for proper comparison.

When to Use This Tool vs Code

Use this browser tool to quickly check a handful of addresses for duplicates or test how your normalization rules would transform specific inputs. For production signup flows, implement normalization as a server-side function that applies provider-specific rules (Gmail vs Outlook vs custom domains) and stores both the original and normalized forms so you can display the original while deduplicating on the normalized version.