Email Normalizer screenshot

Email Normalizer

Trim an address, lower-case the domain and apply Gmail's dot and plus-tag rules. Syntax only, no verification.

Privacy First
0 Runs
Updated 2026-11-07
Runs in your browser
No account
Nothing is sent

Normalise the syntax of one address

The page trims surrounding spaces and lower-cases the domain for every provider. For Gmail and googlemail.com it also lower-cases the local part, removes dots and cuts everything from + as a tag. Other providers keep the local part exactly as typed.

Every rewrite is listed in the notes, so a change is visible rather than silent. The page does not contact a mail server and cannot tell you whether the mailbox exists.

It checks a simple shape — one @, a non-empty local part, a domain with a dot and no spaces — rather than the full mailbox grammar, so an unusual but legal address can be refused.

This page rewrites one email address into a canonical-looking form. It trims surrounding spaces, lower-cases the domain for every provider and, for Gmail only, applies that service's own rules: the local part is lower-cased, dots are ignored and everything from + is a tag.

For any other domain the local part is preserved exactly, because first.last@ and first+tag@ are commonly different mailboxes there. The page lists every change it made, so a rewrite is visible rather than silent.

It normalises syntax; it does not verify a mailbox. No request is made, no MX record is read and no message is sent, so an address that looks canonical may still not exist.

The rules, provider by provider

Every address is trimmed and its domain is lower-cased, which is safe because domains are case-insensitive. Gmail and googlemail.com are recognized by their domain and then get the local-part rules the service publishes: case is ignored, dots are ignored and +tag addresses deliver to the same inbox.

The page also treats googlemail.com as gmail.com and says so in the notes. It does not apply the Gmail rules to a custom domain hosted by Google, because the page cannot know where a domain's mail is hosted.

  • Trim, then lower-case the domain
  • Gmail: lower-case the local part, remove dots, cut at +
  • Other domains: keep the local part exactly as typed

What normalisation cannot tell you

A syntactically valid address can be undeliverable. Verification needs a mail server conversation the page does not have, and even that cannot prove a human reads the mailbox.

The page checks only the shape it can see: one @, a non-empty local part, a domain with a dot and no spaces. It does not implement the full mailbox grammar, so an unusual but legal address can be refused rather than guessed at.

How to use the address box

Paste one address into the Paste one address box. The page trims spaces, lower-cases the domain, and for Gmail only lower-cases the local part, drops dots and cuts at the plus tag; other domains keep the local part exactly. The Normalised panel lists every change in its notes.

Normalisation is syntax only: no mailbox is contacted and no address is verified as existing. googlemail.com is shown as gmail.com; a custom domain hosted by Google does not get the Gmail rules.

What to Expect

Best for

  • Comparing two Gmail spellings of the same inbox
  • Removing a +tag before a duplicate check
  • Making a pasted address consistent before storing it

Not ideal for

  • Proving that an address exists
  • Validating the full RFC mailbox grammar
  • Applying Gmail rules to a custom domain

What this tool keeps

  • The original address alongside the rewritten one
  • A note for every change the page made
  • Domains lower-cased without touching a non-Gmail local part

What may need cleanup

  • An address the page cannot parse, which is reported rather than rewritten
  • A Gmail local part that is empty after the +tag and dot removal
  • An unusual but legal address outside the page's simple shape check

Common errors

  • Assuming a normalised address is deliverable
  • Applying Gmail dot rules to every provider
  • Expecting the page to detect a disposable domain

Example use cases

  • Collapsing two Gmail aliases for a duplicate check
  • Cleaning a pasted address before a form
  • Showing why two addresses are the same inbox

Sample input

The address “ [email protected] ” with the spaces and mixed case.

Sample output

[email protected], with notes for the +tag, the dots and the lower-cased local part.

Who this is for

  • Anyone cleaning a contact list
  • Developers checking a duplicate-account rule
  • Support staff comparing two spellings of one address

Frequently asked questions

Why is a plus tag removed only for Gmail?

Gmail treats everything after + as a tag for the same inbox and ignores dots in the local part. Other providers commonly treat those as different addresses, so the page leaves them alone.

Does this check whether the address exists?

No. It normalises syntax and never contacts a mail server, so it cannot tell you whether the mailbox exists or will accept a message.

Is the domain changed for googlemail.com?

Yes. googlemail.com is shown as gmail.com because Google treats them as the same mailbox; the page records that rewrite in the notes.

Developer program

Build custom tools for your store

Join the SDK program to create useful ecommerce utilities for your store.