Email Normalizer

How to use this email normalizer

1. Paste a list of email addresses, one per line.
2. Each one normalizes instantly below.
3. Addresses that normalize to the same value are flagged as duplicates.

What does normalization do?

For Gmail and Google Workspace addresses, dots in the local part are ignored and anything after a "+" is a tag, both stripped out here — since John.Doe+shopping@gmail.com and johndoe@gmail.com deliver to the exact same inbox.

Why Gmail specifically treats dots as meaningless in the first place

Gmail's decision to ignore dots within the local part of an address isn't an accident or a bug — it's a deliberate design choice Google made and has documented publicly. Internally, Gmail's mail routing simply strips dots from an address before delivering it to a mailbox, meaning john.doe@gmail.com, johndoe@gmail.com, and even j.o.h.n.d.o.e@gmail.com all deliver to the exact same single inbox. Google's own stated reasoning is that dots don't functionally distinguish different accounts on their system at all, so users are free to add or remove them from their own address purely for personal readability — to make an address easier to read at a glance — without that choice creating any confusion about delivery or accidentally creating multiple separate accounts. This is specific to Gmail and Google Workspace, though — as this tool's own FAQ notes, this exact convention isn't a universal, industry-wide standard shared by every email provider.

Plus-addressing is a real standard (RFC 5233), not just a Gmail-specific trick

The "+tag" convention (like yourname+shopping@example.com) is formally defined in RFC 5233 as subaddressing, and while Gmail popularized it for a mainstream audience, it's actually broadly supported by most major email providers, including Outlook and many others. Beyond simply helping detect duplicate signups, as this tool does, plus-addressing has several genuinely useful legitimate purposes on its own: creating a unique, distinct tracking address for each specific website or service you sign up with, which makes it immediately obvious if a particular company later sells or leaks your address to spammers, since you can see exactly which specific tag started receiving unwanted mail; and setting up automatic email filtering rules based on the specific tag portion of an address, all without needing to create and separately manage several completely different email accounts just to achieve that same organizational benefit.

Why "normalization" is a well-informed heuristic, not a universal guarantee

It's worth understanding a genuine technical nuance here: the formal email specification (RFC 5321) technically treats the local part of an address (everything before the @ symbol) as case-sensitive, meaning John@example.com and john@example.com could, in strict technical theory, deliver to two entirely different mailboxes. In practice, essentially every major real-world email provider treats the local part case-insensitively for practical usability reasons, which is exactly why this tool and similar normalization approaches work reliably in practice — but it's a widely followed practical convention rather than something the formal specification itself actually mandates. Because different providers can and do genuinely differ in their specific dot-handling and case-handling rules, any email normalization approach is inherently a well-informed, provider-aware heuristic based on documented common behavior, not a mathematically absolute, universally guaranteed rule that holds for literally every possible email provider that exists.

Why server-side email normalization matters specifically for preventing abuse

Beyond simple mailing-list cleanup, email normalization has a genuinely important application in fraud and abuse prevention that's worth understanding. Services that offer a one-time signup bonus, a free trial, or a limited number of free actions per account are a common, frequent target for abuse specifically through the dot and plus-tag tricks described above — someone can sign up dozens of times using what looks like dozens of distinct, different email addresses, while every single one of those signups actually delivers to their one single real inbox. A well-designed backend system normalizes incoming email addresses at the point of account creation specifically to correctly detect and block this exact pattern, rather than relying purely on the raw, literal address string for uniqueness checks, which this specific trick would otherwise trivially and repeatedly bypass.

Limitations of this tool

This tool applies Gmail-style dot-stripping specifically for Gmail and Google Workspace addresses, and strips +tags for all providers generally — it doesn't implement every individual provider's own specific normalization rules, since as explained above these genuinely do vary somewhat by provider, and not every provider publicly documents their exact internal rules the way Gmail does. It also doesn't verify that a given address is actually a real, currently deliverable inbox — it only normalizes the address's text format to help detect likely duplicates, which is a text-transformation task, distinctly different from real mailbox existence or deliverability verification.