What is an email alias? Examples, uses, and limitations

Quick answer for what is an email alias

Create a named alias, publish exclusive MailerZ MX, delete leftovers, and probe from another mailbox. That is what is an email alias in production: a custom domain alias that forwards, not a new inbox.

Examples: hello@, support@, billing@, a per-vendor string. Uses: brochure names, leak tracing, roles without seats. Limitations: three on Free, no send-as on Free, hold unknowns, leftover MX kills the map.

An email forwarding alias is the hop. A role address is an alias with an owner. Plus tags on Gmail are not this.

Privacy-mask products are a different aisle. Cite their docs. Do not invent parity.

MailerZ Free is one domain, three aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year only. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise.

Google’s own Send mail as steps live in Google Gmail Help — Send mail from a different address. Workspace as a product is described on Google Workspace — product overview. Transport still follows IETF RFC 5321 — Simple Mail Transfer Protocol.

custom domain alias: the real decision

Teams buy seats because they wanted printed strings.

They print plus tags on a homepage.

They enable catch-all and call it aliases.

Criteria: named list, exclusive MX, external probe, send-as only if a From must travel.

Technical mail flow for what is an email alias

RCPT TO matches the name. MailerZ opens hop two to Gmail or Outlook. Header From stays. SRS may rewrite the envelope.

Unknowns hold on Free. That is a limitation, not a bug.

Two destinations are a copy. Name the reply owner.

Outbound is a later hop. Unauthorized send is 550 / 550 5.7.1.

MailerZ is inbound MX plus authenticated SMTP from Secuno LLC. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME are never rewritten. Not Google Workspace, not IMAP, not webmail, not an open relay. Unauthorized send is SMTP 550 / 550 5.7.1. Leftover MX is a hard stop. Self-send from Gmail to the same Gmail account can hide routing errors. Not SOC 2, not ISO 27001, not HIPAA.

email forwarding alias

Define the name, then publish MX. Do not invert that.

1. List the printed names.
2. Add and verify the domain.
3. Create those aliases. Map destinations you already read.
4. Publish MailerZ MX. Delete leftovers.
5. Probe each name from another mailbox.
6. Leave catch-all off.
7. Attach send-as only for Froms that reply as the domain.
8. Document owners and leak status.

Failure modes and proof

Bought seats for strings.

Printed plus tags.

Catch-all as the list.

Self-send.

Leftover Google MX.

MailerZ workflow and product boundary

MailerZ Free is three aliases, one domain, hold unknowns, no send-as. Related: aliases and catch-all, email alias service, custom domain email alias, pricing.

Not IMAP. Not a suite. Not an inbox SLA.

Related pages: aliases and catch-all, email alias service, custom domain email alias, and pricing.

role address

Three names on Free versus three Workspace seats is the usual math. Solo starts send-as. Confirm pricing.

A privacy-mask subscription is a different invoice.

MailerZ Free is one domain, three aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year only. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise.

Field notes you can reuse

Recite the list or shorten it.

Retire leaked vendor names.

Agencies: per-client lists.

Outlook dest is fine.

Hold review weekly if you print many names.

Quarterly leftover MX review.

Do not promise Primary.

The custom-domain alias page is the hop without a second inbox.

Deeper field notes for what is an email alias

A definition you can defend in a meeting

An email alias is a public local-part plus domain that does not host its own IMAP store. Mail for that string is accepted because you created a named map, then forwarded to a mailbox you already have. What is an email alias, technically: RCPT TO matches a name you published, hop two delivers to Gmail or Outlook, Header From on inbound stays the original author. It is not a Google user. It is not plus addressing on gmail.com. It is not a privacy mask on someone else’s domain. It is not catch-all.

Examples that hold: hello@, support@, billing@, invoices-2026@, a per-vendor string you retire when they leak. Uses: printed brochure names, leak tracing, role routing without seats. Limitations: Free allows three aliases. An alias is not send-as. Creating hello@ inbound does not let you send as hello@. Catch-all is a leftover policy, not an unlimited alias feature. Plus tags on your domain are not Gmail plus tags.

Alias versus mailbox versus forward versus plus

A mailbox is a login and a store. A forward is the hop an alias uses. Plus addressing on @gmail.com is a Gmail filter trick. A custom-domain alias is a name you created on a zone you control. Privacy-alias products hide a destination on a provider domain — useful, different aisle. Cite SimpleLogin’s own blog if you compare; do not invent parity. MailerZ is the delivery layer when the public string is your domain.

People say “alias” for all four. That sloppiness is how they buy Workspace seats for printed strings, or print you+billing@gmail.com on a footer. Write the word you mean. This page means named custom-domain aliases into an existing store.

What an alias cannot do

It cannot pull history from an old suite. It cannot lock a shared queue. It cannot promise Primary. It cannot replace Calendar. It cannot mint a From on Free. It cannot survive leftover MX — if Google still answers, the alias map never runs. It cannot strip plus tags on your domain the way Gmail does on gmail.com.

Unlimited aliases as marketing will not save a missing list. Three named aliases you can recite beat fifty you cannot. Hold unknowns. Promote a leftover only when a real person used it.

Role examples that stay honest

support@ to ops Gmail, sales@ to founder, billing@ to bookkeeper. That is three aliases, one or more stores, no extra seats. If support must reply as support@, that is paid send-as plus Gmail Send mail as. If sales only receives, stay receive-only. Do not attach one SMTP password to every role.

Agencies: per-client lists. Do not copy one client’s roles onto another zone. Agency plan capacity exists so you can hold more domains. It does not replace a named list.

A complete worked story

A footer that was a plus tag

A founder printed you+hello@gmail.com and called it an alias. Customers wrote it. It worked until they wanted hello@yourdomain. They created the named alias, cut leftover registrar MX, and probed from a supplier. Same Gmail store. Real domain string. The plus tag came off the site. That is the definition in one week.

Operator brief

A longer operator brief for what is an email alias

Teams that bookmark What Is an Email Alias? Examples, Uses and Limitations usually arrive after a missed invoice, a form that never notified anyone, or a migration that looked clean in one resolver. The useful brief is still boring. Name the store. Name the printed local-parts. Name the nameservers that actually answer. Publish one MailerZ MX set. Delete leftover hosts. Probe from a mailbox that is not the destination. Only then talk about what is an email alias as a send-as, catch-all, or comparison problem.

MailerZ remains inbound MX plus authenticated SMTP around Gmail or Outlook. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME stay intact. It is not a hosted mailbox, not IMAP, not webmail, and not an open relay. Unauthorized send is 550 / 550 5.7.1. Free cannot finish send-as: SMTP and API stay off. Solo is $40 per year when the domain From must travel. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm the live pricing page. Those numbers are ceilings, not an inbox-placement service-level agreement.

If leftover Google, Microsoft, Cloudflare routing, or registrar MX is still public, stop widening what is an email alias. The map you built never saw that copy. Priority numbers are an order, not load balancing. A higher preference host is idle while a leftover host still accepts mail. Save the old MX set before you delete anything. Check more than one public view because TTL lies.

Catch-all forward is not a safety feature for what is an email alias examples uses and limitations. Hold unknowns on everyday production. Review the store. Promote a leftover only when a real person used it. Paid forward belongs to a dated cutover. Fan-out of unknowns into two inboxes trains two spam buttons. Plus addressing on Gmail is not a custom-domain unknown policy. MailerZ will not strip plus tags on your domain the way Gmail does on @gmail.com.

Send-as is a second hop. Creating an inbound alias does not approve outbound. Catch-all does not mint a From. Copy the dashboard host, port, and TLS pair together. Set From to an identity you created. Do not paste a Gmail password into a CMS, a cron file, or a ticket. Do not mail SMTP secrets to support. Send a 550 line, a timestamp, and a Message-ID. Rotate if a secret already leaked.

Self-send from Gmail to the same Gmail account can short-circuit. That green result is why people swear what is an email alias works while customers vanish. Use a second provider. Put a unique subject on the probe so delivery history is searchable. If Header From was rewritten by some other forwarder, authentication stories get noisier. MailerZ does not rewrite Header From on inbound.

Agencies should keep what is an email alias per client zone. Separate SMTP credentials. Do not pour every client into one catch-all because the spreadsheet got long. Agency plan capacity exists so you can hold more domains and aliases. It does not replace a named list. Offboard means delete MX you own, revoke SMTP, and stop forwarding leftovers into the agency inbox.

Legal and security questions have published answers on the security, privacy, terms, DPA, and subprocessors pages. MailerZ is not SOC 2, not ISO 27001, and not HIPAA. The 14-day Free store, the 90-day Solo–Agency store, and the 180-day Unlimited store are recovery windows for hops this layer saw. They are not an archive and not legal hold. If counsel wants eDiscovery, buy eDiscovery.

Comparisons only help after the hop is honest. Cloudflare Email Routing is inbound routing. A privacy-mask product hides a destination on a provider domain. A suite hosts mailboxes, Calendar, and admin. Proton-class mailboxes encrypt a store. MailerZ is the delivery layer when you already have Gmail or Outlook and you need a domain route you can prove. Cite the other product’s documentation. Do not invent feature parity.

When What Is an Email Alias? Examples, Uses and Limitations is closed, the next physical action is a lookup and a probe, not another tab. Start free on one domain you can break. Sign in if the zone already lives here. Review quarterly, or sooner after a nameserver move, a plugin swap, or a staff departure. That is how what is an email alias stays a runbook instead of an incident.

A second worked pass for what is an email alias: write the last change on a sticky note before you open the dashboard. Nameserver move, leftover MX, new form plugin, contractor laptop, or a registrar forwarding toggle are the usual five. MailerZ history only shows hops that reached this layer. If the sticky note says leftover MX, you do not have a what is an email alias mystery. You have a split. Delete the leftover. Wait for TTL. Probe again.

A third worked pass: print the public list. If you cannot print it, you are not ready for production unknowns and you are not ready for a bigger alias ceiling. Unlimited aliases as marketing will not save a missing list. Three named aliases on Free are enough to stop printing a personal Gmail on a homepage. Grow the list when a real person used a leftover, not when a harvest guessed admin@.

More working detail

Examples that fail the definition

A shared Workspace user named support@ is a mailbox, not an alias. A Gmail filter that forwards you@gmail.com to a colleague is not a custom-domain alias. A catch-all that accepts admin@ because you never created it is not an example of what is an email alias — it is an unknown policy. A disposable provider address is not your domain. If you cannot point at a named row in MailerZ, you are not looking at this product.

Uses that stay in-lane: printed hello@ on a homepage, support@ into ops, a unique string per ad platform so a leak is a row you retire. Uses that leave the lane: legal hold, shared assignment, bulk marketing, Calendar. Say no. Point at pricing ceilings. Free is three names. That limitation is how small teams stay honest.

A limitation people skip: aliases do not merge two domains on Free. One domain. If you want brand-b hello@ in the same Gmail, you need a plan with another domain slot and another exclusive MX set. The definition does not merge DNS.

Another limitation: plus tags you invent on your domain are literal local-parts unless you created them. MailerZ will not strip +tag the way Gmail does on gmail.com. If you print hello+stripe@yourdomain, create that name or it sits in hold.

How to teach the word in onboarding

Have the new person create one alias, cut leftover MX on a sandbox zone, and probe from their personal Outlook. Then have them try to send as that From on Free and read the 550. The definition sticks. Slides do not.

One more working distinction

Limitations you should put in the sales deck

Not a mailbox. Not Calendar. Not Vault. Not unlimited on Free. Not send-as on Free. Not an inbox SLA. Not SOC 2. What is an email alias stays sellable when those nos are early. The yes is a named string into Gmail. That is enough for most footers. It is not enough for a bank’s email hosting RFP. Send them to a suite.

SimpleLogin-class products are aliases too, on someone else’s domain. If the buyer wants to hide their Gmail, that aisle is fine. If they want hello@theirbrand, they want this hop. Do not win the deal by pretending the aisles match.

A short operating rule

If a teammate asks for “just an alias” and means a second Gmail login, correct the word before you click. What is an email alias in this product is a map. Give them a destination or a filter, not a seat, unless they need the suite.

Field close

Print the three Free names on a sticky note next to the MX operator. If a fourth name appears in a mockup, the limitation is a plan talk, not a catch-all. That is what is an email alias as an operating constraint, not only a definition.

FAQ

What is the safest way to handle what is an email alias?

Treat it as a named custom-domain map into Gmail or Outlook, not a seat or a plus tag. Create the names, publish exclusive MX, hold unknowns, and probe from another mailbox. Inbound is not send-as.

Does this require a new mailbox?

No. MailerZ is not IMAP and not webmail. Gmail or Outlook remains the store unless you separately buy a hosted mailbox product.

Will it work with Gmail or Outlook?

Yes for inbound when the destination is a verified mailbox. Branded replies need paid send-as plus Gmail Send mail as or a manual Outlook SMTP identity. Free has no send-as.

What DNS records are involved?

A verification TXT, one MailerZ MX set on the authoritative nameservers, leftover host MX removed, and SPF, DKIM, and DMARC if you also send as the domain.

What should I test before production?

Send a uniquely titled message from an unrelated provider into each named alias. Confirm Header From and delivery history. Do not email yourself from the same Gmail account.

Key takeaways

• Named map, not a seat.
• Not plus tags.
• Not catch-all.
• Three on Free.
• Probe externally.
• Send-as is separate.
• Hold unknowns.
• Leftover MX first.

Conclusion and next action

An email alias is a named public string that forwards into an inbox you already have. MailerZ is that map. Print only what you created. Cut leftover MX.

Start free. Sign in if the names exist and Google still answers.

Review quarterly, or sooner if Gmail, Workspace, or MailerZ scope changes. Author: MailerZ editorial, Secuno LLC.