Knowledge Base / Email organization
Plus Addressing: Email Tags, Uses, and Privacy Limits
Use plus tags to create filters, label sign-ups, and spot when an address appears somewhere unexpected. Do not rely on them for anonymity: the base address is readable, tags can be stripped, and some websites reject the plus character.
Plus addressing adds a tag after the mailbox name and before the at sign, such as name+receipts@example.com. Supporting mail systems deliver it to the base mailbox. It is a convenient organization feature, not a separate inbox and not a reliable way to conceal your real address.
This guide treats tagging as an organization tool, not a replacement for an alias. Follow the address example first, build filters second, and check form compatibility before relying on a tag for an ongoing account. Keep the untagged mailbox protected as well.
How a tagged address works
When a provider supports subaddressing, it treats the text after + as a detail attached to the same local mailbox. Mail to alex+travel@example.com and alex+shopping@example.com can arrive in alex@example.com. No new mailbox or password is created.
Support belongs to the receiving mail system. Do not assume every domain accepts tags, and test the address before depending on it for an important account.
The tag is part of the address supplied to the sender, so keep its spelling consistent. alex+travel@example.com and alex+travels@example.com may reach the same base mailbox but can behave like different values in a website account database. Save the exact version used for login and recovery.
A tag does not create a second security boundary. It shares the base mailbox password, storage, spam controls, and recovery path. If the base mailbox is compromised, every tagged address tied to it is affected.
Useful tagging patterns
- By purpose:
name+receipts,name+news, orname+travel. - By sender: a distinct tag for each merchant or service.
- By project: route registrations or alerts into a project folder.
- By time: a campaign or event tag you can retire from filters later.
Avoid putting secrets, dates of birth, account numbers, or private notes in a tag. The complete address is visible to the sender and can appear in headers, exports, screenshots, and breach data.
Use a naming system you can understand later without exposing private details. A short service or purpose label is easier to audit than a date or random string. For example, alex+receipts describes the mail rule, while a separate alias is better when you need a unique address that does not reveal alex.
Keep the number of patterns manageable. If every sign-up uses an inconsistent tag, filters become hard to review. A small set for receipts, newsletters, projects, and testing is often enough, with a unique sender tag only when leak tracing is genuinely useful.
Turn tags into useful filters
Create a mail rule that checks the delivered-to or recipient field, then applies a label, moves the message, or marks unexpected mail. Test the rule with your own message because mail apps expose recipient fields differently.
Do not auto-delete security messages only because a tag is unfamiliar. A sender may change its infrastructure or normalize the address. Route first, observe, and only then make destructive filtering decisions.
Build the rule in stages. Start by applying a label without moving or deleting mail. Send a test message to the tagged address and confirm which recipient field the mailbox exposes. After several real messages behave as expected, add a folder or notification rule. Keep password resets and security alerts visible even if ordinary marketing mail is archived.
A tag can suggest where an address was used, but it does not prove who disclosed it. A merchant may use another delivery provider, share data under its policy, or have the address copied from a compromised device. Treat unexpected mail as a lead for investigation, not a final accusation.
Privacy limits
The base address is obvious: removing +anything often reveals it. A company can normalize tags across records, and a data broker can group them. The tag can still help identify which address was shared, but it does not create strong separation between identities.
For a unique address that does not reveal the destination, use a forwarding alias. For a message that should disappear with the task, use a temporary inbox. The comparison guide shows the trade-offs.
Compatibility problems and recovery
Some forms incorrectly reject valid plus characters, while other systems accept the tag during sign-up and later remove it during login or recovery. Before relying on a tag, sign out and confirm the service recognizes the exact address. Save the spelling in a password manager.
If login fails, try the account's username first. Do not create a duplicate account casually, especially where purchases or identity checks are involved. Contact the service and state the exact tagged address originally used.
Run a small compatibility test before attaching value to the account: register with the tag, receive the first message, sign out, sign in using the exact address, and start a password-reset request without completing it. If any step normalizes or rejects the address differently, move to a plain durable address or a forwarding alias while you still control the session.
Plus-addressing questions
Does plus addressing create a new inbox?
No. Supported tagged addresses deliver to the same base mailbox.
Can a sender see my normal email address?
Yes. The base address is normally visible by removing the plus tag.
Why does a website reject my plus address?
Its form or account system may not support the plus character or may normalize addresses inconsistently.
Can I stop mail to one plus tag?
You can filter that tag, but you cannot always prevent a sender from removing the tag and mailing the base address. A revocable forwarding alias offers stronger shutoff control.
Filtering and privacy guidance reviewed 2026-11-02.