Plus Addressing: One Inbox, Many Addresses
Plus addressing, also called subaddressing, is the practice of adding a tag after a "+" sign in the local part of an email address: jane+news@example.com. On providers that support it, mail to the tagged address reaches the same inbox as jane@example.com. Trueguard's email validation API returns a rawEmail with the +tag removed for matching, and a quality.isSubaddress flag.
For a product with a free tier, the same feature has a second use. One person can produce any number of distinct strings that land in one inbox, and each string passes a unique-email check. The safe response is narrow. Keep the address as typed, match on a canonical key, and act on a match without rejecting the "+" itself.
How does user+tag@domain work?
The address splits into a user part, a separator and a detail part. RFC 5233, published by the IETF in January 2008, defines subaddressing as "the practice of augmenting the local-part of an [RFC2822] address with some 'detail' information in order to give some extra meaning to that address." The separator it gives as an example is "+". In jane+news@example.com, jane is the user, + is the separator and news is the detail.
The "+" is a legal character. RFC 5322 lists it among the atext characters permitted in a local part. The full syntax rules are in our guide to RFC 5322 email syntax.
What the tag means is decided by one party only. RFC 5321 states that "the local-part MUST be interpreted and assigned semantics only by the host specified in the domain part of the address." RFC 5233 adds that when the separator appears more than once, the logic used to split the address "is implementation-defined." A signup form is not the host named in the domain. It has no standard basis for treating "+" as a separator on someone else's domain, so any rule that does so is an assumption.
Which email providers support plus addressing?
Gmail, Google Workspace, Microsoft 365 (Exchange Online), Fastmail and Proton all document plus addressing on official pages. All five use "+" as the separator, and none of the pages read for this article lists a setup step for users. For Outlook.com, iCloud Mail, Yahoo Mail and Zoho Mail, no official page on the subject was found. The table marks those rows as not found.
| Provider | Separator | Default | Source (read 2026-11-21) |
|---|---|---|---|
| Gmail | + | Works on any address; no setup step given | Official Gmail Blog, "2 hidden ways to get more from your Gmail address", March 2008 |
| Google Workspace | + | Works on the current address; no setup step listed | Google Workspace Learning Center, "Create task-specific email addresses" |
| Microsoft 365 / Exchange Online | + | On by default; an admin can turn it off for the organization | Microsoft Learn, "Plus Addressing in Exchange Online" |
| Fastmail | +, plus subdomain addressing | Works automatically with any alias for most users | Fastmail Help, "Plus addressing and subdomain addressing" |
| Proton | + | No setup needed | Proton support, "Addresses and aliases" |
| Outlook.com (consumer) | No official page found (read 2026-11-21) | No official page found (read 2026-11-21) | No official page found (read 2026-11-21) |
| iCloud Mail | No official page found (read 2026-11-21) | No official page found (read 2026-11-21) | No official page found (read 2026-11-21) |
| Yahoo Mail | No official page found (read 2026-11-21) | No official page found (read 2026-11-21) | No official page found (read 2026-11-21) |
| Zoho Mail | No official page found (read 2026-11-21) | No official page found (read 2026-11-21) | No official page found (read 2026-11-21) |
Fastmail also offers a second form that carries no "+" at all. Subdomain addressing, in Fastmail's words, "works the same as plus addressing, but instead of alias+whateveryoulike@domain.tld, you can use an address of the form whateveryoulike@alias.domain.tld." Fastmail recommends it because some sites reject "+". A matching rule that looks for "+" will not see these addresses. The tag sits in the domain, and the address looks like any other.
The free plan includes 100 email validations a month, with no card required. Get your free API key.
How is plus addressing different from email aliases and disposable addresses?
A plus address is a variation of the owner's own address and reveals the base address in its text. An alias from a forwarding service is a separate, generated address that forwards to the owner's real inbox. A disposable address is a temporary inbox at a temp-mail service. Plus addresses and aliases both reach a real person.
| Plus address | Alias from a forwarding service | Disposable address | |
|---|---|---|---|
| What it is | The owner's address with a +tag added | A generated address that forwards to the owner's inbox | A temporary inbox from a temp-mail service |
| Who controls the inbox | The owner, at their own provider | The owner, through the forwarding service | The temp-mail service |
| Reaches the real person | Yes, in the regular inbox | Yes, by forwarding | Only through the temporary inbox |
| How it looks at signup | jane+trial@ at the owner's domain | A generated local part at the service's domain | An address at a temp-mail domain |
Proton states the practical difference: "Keep in mind that your real address is easy to guess from a plus address." A forwarding alias carries no base address in its text, so string rules cannot link it to its owner. Several services offer such aliases. Each description below is from the provider's own page, read 2026-11-21.
- Apple Hide My Email. An iCloud+ feature that "generates unique, random email addresses that automatically forward to your personal email inbox." Apple's page names the domains
@private.icloud.comand@privaterelay.appleid.com. - Firefox Relay. Mozilla describes masks as "masked, or private, email addresses that forward messages to your true email address." Relay has a free tier and a Premium tier. Mozilla adds: "We don't recommend using masks when you need your identity verified."
- DuckDuckGo Email Protection. "a free email forwarding service that removes multiple types of hidden email trackers and lets you create multiple unique private email addresses on the fly."
- addy.io. An open-source service whose Free plan "includes unlimited standard aliases (within your monthly bandwidth limit)."
- Proton hide-my-email aliases. Up to 10 on Proton Free or Proton Mail Plus, unlimited on higher-tier plans such as Proton Unlimited.
Every service above forwards to a person who can read the mail. None of them is a temp-mail service. For temporary inboxes, see our page on disposable email signups.
Why do people use plus addresses?
Mostly to sort mail and to see who shares their address. Google's Workspace guidance describes the first use: messages to any variation "all arrive in your current inbox. You can then set up filters to route or handle the messages based on the address." Fastmail automates it. Mail to alias+hiking@domain.tld goes "straight to" a folder called Hiking when one exists.
The second use is leak tracking. The 2008 Gmail Blog post gives the example: "I added "+donation" when I gave money to a political organization once, and now when I see emails from other groups to that address, I know how they got it."
Both uses depend on the tag surviving intact. Both are also why a site that refuses "+" loses real users. Fastmail names this as the main downside of the feature: "addresses with a + are incorrectly considered invalid by some websites, and may not allowed on some registration forms."
How do abusers use plus addresses for repeat signups?
By registering the same inbox many times. Each new tag gives a new string, and a database that checks for a unique email sees a new user every time. Proton describes plus aliases as "unlimited variations" of an address. Google lets a Workspace user add "any word." The person behind jane+1@, jane+2@ and jane+3@ reads all three accounts' mail in one place.
That is enough to claim a free trial again, redeem a one-per-customer promo code again, or refer oneself for credit. Google acknowledges a related problem with a different variant, dotted Gmail addresses: "Unfortunately, we can't prevent people from accidentally or maliciously using a dotted version of your address to sign up for subscription emails."
The research for this page found no published figure for how often plus addresses appear in signups, or for what share of them is abuse. A plus address is also the easiest form of repeat signup to see, because the base address is in the string. Forwarding aliases, subdomain addresses and new accounts at other providers leave no such trace. Our page on free-tier abuse covers the signals that remain.
How do you normalise plus addresses at signup without blocking real users?
Store two values. The address as typed is the one you send to. A canonical key derived from it is the one you match on. Then act on a match by limiting what the new account gets, and let the signup through.
- Keep the address as typed. Send mail to it and use it for login. Never overwrite it with the stripped form.
- Compute a canonical key for matching. Lowercase it and remove the "+" and everything after it up to the "@". Map domains only where you have a basis for treating them as equivalent.
- Index the key and look it up at signup. Reserve a unique constraint for products where one account per inbox is a hard rule.
- On a match, limit or flag the new account. Withhold a second trial, a second promo redemption or a self-referral credit, or send the account to review.
- Never reject "+" itself. It is legal under RFC 5322, and people use it to filter their own mail.
The open-source library validator.js ships a normalizeEmail function that makes these assumptions per provider. The table shows what a widely used library assumes, read 2026-11-21. Every option listed defaults to true.
| Option | What it does, per the validator.js README |
|---|---|
all_lowercase | Lowercases the local part of all email addresses |
gmail_remove_dots | Removes dots from the local part, "as Gmail ignores them" |
gmail_remove_subaddress | Removes the part following a "+" ("foo+bar@gmail.com" becomes "foo@gmail.com") |
gmail_convert_googlemaildotcom | Converts @googlemail.com to @gmail.com, "as they're equivalent" |
outlookdotcom_remove_subaddress | Removes the part following a "+" for Outlook.com, covering Windows Live and Hotmail (outlookdotcom_lowercase also on) |
yahoo_remove_subaddress | Removes the part following a "-" ("foo-bar@yahoo.com" becomes "foo@yahoo.com") |
icloud_remove_subaddress | Removes the part following a "+" for iCloud, including MobileMe (icloud_lowercase also on) |
The README flags its own default: lowercasing "may violate RFC 5321, which gives providers the possibility to treat the local part of email addresses in a case sensitive way (although in practice most - yet not all - providers don't)." Its Yahoo rule splits on "-", which a "+" rule never touches. No official Yahoo page confirming that behaviour was found.
The trade-off is the same for any key. Stripping "+" on every domain groups addresses that only the receiving host can interpret. Exchange Online, for example, first tries to resolve the full tagged address to a known mailbox and falls back to the untagged address only if that fails. Grouping is acceptable for a matching key. It is never acceptable for a send address.
Gmail goes further with dots: "Gmail doesn't recognize periods as characters in addresses -- we just ignore them." Dots and per-provider rules are covered in our email normalisation guide.
How Trueguard handles this
Trueguard's email validation API returns email, trimmed and lowercased, and rawEmail, a canonical form for matching. rawEmail is lowercased, has the "+" and everything after it up to the "@" removed, and maps some provider domain aliases to one domain: googlemail.com maps to gmail.com. Use rawEmail as the dedupe key and keep sending to the address the user typed.
quality.isSubaddress is true when the local part contains "+". It is a quality flag. It does not make an address invalid or risky, and Trueguard does not mark plus addresses as disposable. Status (safe, risky, invalid or unknown) is decided separately.
In the fraud event API, the multiple_aliases signal fires when the same project has already seen the base address of the incoming email. The documented example: test@gmail.com signs up, then test+2@gmail.com.
A free key includes 100 validations a month. Checks beyond that cost $0.001 each.
The free plan includes 100 email validations a month, with no card required. Get your free API key.
Frequently asked questions
Plus addressing, or subaddressing, adds a tag after a "+" in the local part of an email address, as in jane+news@example.com. On providers that support it, the tagged address delivers to the same inbox as jane@example.com, and the owner can filter on the tag. RFC 5233 defines the idea as adding "detail" information to the local part, with "+" as a common separator. Trueguard's email validation API returns rawEmail, the address lowercased with the +tag removed, so you can match tagged signups to their base address. It also returns quality.isSubaddress when the local part contains "+".
Yes. RFC 5322 lists "+" among the atext characters allowed in the local part, so jane+news@example.com is a well-formed address. Rejecting it is a validation error on the site's side. Fastmail's help center says addresses with a "+" "are incorrectly considered invalid by some websites, and may not allowed on some registration forms," and offers subdomain addressing as a workaround for that reason. Whether the tagged address delivers is a separate question that only the receiving host can answer. Syntax rules are covered in our RFC 5322 email syntax guide.
Yes. The Official Gmail Blog described it in March 2008: "Append a plus ("+") sign and any combination of words or numbers after your email address." Its example sends mail to hikingfan+friends@gmail.com for the owner of hikingfan@gmail.com. Google's Workspace Learning Center describes the same behaviour for Workspace addresses, with every variation arriving in the current inbox and filters available to route it. Both pages were read on 2026-11-21. Neither lists a setup step.
No. The "+" is legal under RFC 5322, and people use it to filter mail and to track which companies share their address. Blocking it turns away real users and leaves forwarding aliases and subdomain addresses untouched. Match on a canonical key instead, with the +tag removed and the address lowercased. When a new signup matches an existing account, limit what the new account receives, such as a second trial, or flag it for review. Keep the address as typed for sending.
No. A plus address is a variation of the owner's real address, and Proton notes that mail to it "arrives in your regular inbox." The person who typed it reads it. Forwarding aliases such as Apple Hide My Email or Firefox Relay also reach a real person. Trueguard does not mark plus addresses as disposable, and quality.isSubaddress does not make an address risky. Temporary inboxes from temp-mail services are a different category, covered on our disposable email page.
No. Send to the address exactly as typed. RFC 5321 reserves interpretation of the local part for the host named in the domain, so a sender has no basis to assume jane+news@ and jane@ are the same mailbox. Exchange Online first tries to resolve the full tagged address and falls back to the untagged one only if that fails. Stripping the tag also breaks the recipient's filters. Fastmail files alias+hiking@ mail into a Hiking folder. Use the stripped form only as a matching key.
Compute a canonical key at signup: lowercase the address and remove the "+" and everything after it up to the "@". Look the key up before granting a trial, a promo code or referral credit, and withhold the benefit when the key already exists. Do not reject the signup. A string rule covers plus addresses only, so forwarding aliases and new accounts at other providers need other signals. Trueguard's rawEmail provides the key, and the multiple_aliases fraud signal fires when a project has already seen the base address. More on free-tier abuse.
