Family custom domain email means you own lastname.com and still keep Gmail. Create named aliases for each person and one shared household string. Map them to the inboxes people already open. Do not buy a mailbox seat per child if they only need a public address. Exclusive MX. HOLD unknown so guessed family names do not flood the parents.
Quick answer for family custom domain email
Own the zone. Keep Gmail or Outlook as the store. MailerZ is the hop.
Individual aliases are privacy between siblings. Shared hello@ is the household contract.
RFC 5321 delivers to MX. Leftover registrar email MX steals birthday RSVPs.
HOLD unknown. Dictionary first names will be guessed.
Paid send-as if someone must send as the domain. Free cannot. Copy dashboard values.
Start free: one domain, three aliases. That is often one shared plus two people.
Authoritative mail transport is defined in IETF RFC 5321 — Simple Mail Transfer Protocol. Product path: email forwarding, aliases and catch-all, and custom-domain email alias.
User problem and decision criteria
Decision criteria: who gets a named alias, who shares, parental access, leftover MX from a website builder.
Do not give a child a catch-all. That is a spam cannon and a safety issue.
If a teen needs send-as, that is credentials. Treat them like production secrets.
Website-builder “email included” leftovers are common on family domains.
Plus-addressing on Gmail is not a family domain.
Privacy-mask apps are not lastname.com.
Do not invent a family inboxing rate.
If you need a true kids account suite, that is a host or Google Family, not MailerZ IMAP.
Technical mail flow
MX to MailerZ, named local-part, hop to a parent or child Gmail, SRS, intact From.
Shared alias to one staffed inbox.
Destination changes when a child gets their own Gmail.
History if a school swears they mailed you.
HOLD for guessed names.
Step-by-step setup / decision path
- Buy or keep the family domain. Find authoritative NS.
- Create shared plus individual aliases up to plan limits.
- HOLD unknown.
- Exclusive MX. Delete website-builder leftovers.
- Probe each alias.
- Enable send-as only for adults who need it.
- Remap when inboxes change.
- Review held mail for real school typos only.
Classify the next failure before a second DNS edit.
HOLD unknown unless you wrote a FORWARD reason.
Quote live pricing before promising alias counts.
Failure modes and proof
Catch-all for kids: junk and risk.
Leftover builder MX: missing RSVPs.
Printed personal Gmail on the family site: future lock-in.
Free send-as: refuse.
Shared SMTP password in a family chat: leak.
Self-send: lie.
Dual MX: split.
Unlimited aliases on Free: three.
IMAP expectation: no.
Inboxing promise: no.
Header rewrite: no.
Disabled shared alias in a fight: household outage.
MailerZ workflow and product boundary
MailerZ is custom-domain aliasing and forwarding with optional paid send-as. Secuno LLC operates mailerz.net. The app is mail.mailerz.net. Not Workspace, not IMAP, not an open relay, not a campaign ESP.
Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME stay intact. Exclusive MX. Hold unknown on Free. Copy SMTP host, port, and TLS or STARTTLS from the dashboard when you send.
Free: one domain, three aliases, one seat, fourteen-day store, fifty outgoing a month, no send-as. Solo forty dollars a year, fifteen aliases, ninety-day store, one hundred outgoing, five send-as per hour. Starter eight or eighty. Business nineteen or one hundred ninety. Agency thirty-nine or three hundred ninety. Quote pricing. No SOC 2, ISO, HIPAA, SLA, or inboxing percentage.
Cost, alternatives, and trade-offs
A domain plus Solo can beat several leftover builder seats.
Catch-all looks free and costs junk time.
Gmail remains free as a store.
Website-builder email is often the leftover MX you pay for with incidents.
Do not buy Workspace for a family of aliases unless you need the suite.
Agencies should price family domains as a small map, not a suite.
Send-as is optional spend.
No inbox KPI.
Operational depth
Write who may read the shared alias. That is a household policy, not a DNS record.
Schools and sports clubs should get the stable shared string, not a parent’s changing personal address.
When a child leaves home, remap their alias or disable it. Do not leave it pointing at an inbox they abandoned.
HOLD will show scanners guessing family names. That is why HOLD exists.
Do not publish every child’s first name on the website if you do not want those aliases guessed.
Exclusive MX after you cancel a builder’s “free email.”
If two households share a domain, stop and write governance first.
Quote Solo if you need more than three aliases or send-as.
Keep campaigns and family newsletters off reply SMTP if volume grows. An ESP or a simple BCC may be enough—do not blast through caps.
Probe after every remap.
Store windows help if a school mail was held. Act inside the window.
No SOC 2 story for a family domain. The security page is still honest.
Worked scenarios for family-domain mail
lastname.com has mom@, dad@, and family@ mapped to two Gmail accounts and one shared destination. Kids do not have aliases yet. HOLD unknown so guessed child names do not flood the parents. Exclusive MX. A friend probes each public string. That is a finished household setup. No mailbox seat per child.
A teen gets their own Gmail. You create firstname@ and remap when they should own it. You do not buy IMAP. You do not enable catch-all FORWARD 'so they can invent addresses.' Invented addresses are a leak surface and a moderation problem.
Grandparents want mail on the domain but will only open one inbox. Map grandma@ and grandpa@ to the inbox they actually open, or to a child who will print messages. A pretty alias into an unopened mailbox is not kindness.
A school form demands a unique address per child. Create named aliases. Map them to a parent until the child should see the mail. Remap later. The school never needs a new domain. They need a stable string.
Someone turns on catch-all FORWARD so cousins can 'just use any name.' Cousins, marketers, and harvesters will. HOLD. Named aliases only. Free is three aliases. Confirm /pricing before you promise every relative a prefix.
The family website host enables 'email included.' Leftover MX splits school mail. Disable the product. Delete the records. Morning re-query after the next 'site update.'
Practice and anti-patterns for household aliases
Practice: named people plus one shared string if you want it. Anti-pattern: catch-all as a family feature.
Practice: destinations people open. Anti-pattern: aliases into a Gmail nobody checks.
Practice: exclusive MX. Anti-pattern: leftover builder mail 'for the kids' webmail.'
Practice: remap when a teen should own the destination. Anti-pattern: forever parent-read without a conversation.
Practice: HOLD unknown. Anti-pattern: invent-an-address night as a game.
Practice: third-mailbox probes. Anti-pattern: dad emails himself from the destination.
Practice: quote alias caps. Anti-pattern: promising the whole reunion on Free.
Operator closeout for the household
Closeout is the list: alias, destination, who opens it, who remaps, HOLD on, exclusive MX listings, probe IDs, builder email off.
Kids who do not have aliases are listed as 'not yet' so a well-meaning relative does not create them in a panel you share.
Registrar and MailerZ logins live in a password manager a second adult can open. Single-adult lock-in is how a hospital week becomes an identity incident.
If send-as exists for a family newsletter, it is paid, dashboard-copied, and not a list blast. Caps apply. An ESP is for actual lists.
A simple talk with teens: the domain is a family name, not stealth. Sites can see lastname.com. Unique prefixes help leaks. They do not hide the household.
Morning re-query after website work. Hosts help. Helping breaks MX.
Edge cases in family mail
Divorce or household split. Remap destinations. Decide who keeps the domain. MX exclusive to one hop. Do not leave both adults as leftover admins without a written plan.
A child address becomes a harassment target. Disable that local-part. Create a replacement. Update the school. Do not flap MX. Do not catch-all to 'watch' the abuse.
Elders forward everything onward to another Gmail, which forwards back. Loops. Terminate the chain. One destination that people open.
A relative wants anonymity on the family domain. They cannot have it. The registrable name names the family. Buy a mask for that job or accept identifiability.
International relatives mistype the hyphen. Decide on a typo alias or HOLD. Do not FORWARD all guesses.
Legal guardian changes. Remap school aliases the same week you change the school file. The domain can stay stable while destinations move.
Field notes from household domains
Families who treat lastname.com like a group chat regret catch-all. Families who treat it like a few printed doors stay calm.
Kids will publish an alias on a game. Unique prefixes let you kill that string without renaming the parents.
Shared family@ into two people without a rule becomes unread. Pick an opener. Deputies are fine. Nobody is not.
RFC 5321 does not care that you are related. Exclusive MX still applies. Leftover builder MX still splits report cards.
Link /aliases-catch-all and /email-forwarding. Family mail is inbound first. Send-as is optional and paid.
No HIPAA story because a relative is a clinician. MailerZ is not HIPAA. /security is the page.
Handoff memo for the other adult
Registrar, DNS, MailerZ, mapped aliases, destinations, HOLD, who talks to the school when a string changes.
The memo forbids catch-all FORWARD and leftover builder email. It forbids printing a child's Gmail on the family site if you meant to use the domain.
Free caps are written. More kids than aliases means /pricing, not a catch-all.
Dashboard SMTP only if you send. No folklore ports. Free has no send-as.
If one adult leaves the household, the memo says who keeps the domain and who loses the seat the same week.
Acceptance criteria for family aliases
Named aliases for people you will staff. Shared alias optional. HOLD unknown. Exclusive MX. Foreign probes succeeded.
Destinations opened by living people. Builder email off. Caps match the plan.
A remap story exists for the next teen. A disable story exists for a leaked kid alias.
Second adult can log in or the risk is written. No single-point password on a napkin.
No stealth claim. No catch-all game. No invented SLA.
Website host cannot republish MX without someone noticing the morning check.
Operations review of the household map
Once a school year: crawl forms and the website, diff the alias sheet, remap leavers, disable leaked game names.
After any host or theme change: leftover MX check.
When a child gets a phone: decide whether they get a destination or still land on a parent.
Review alias count versus /pricing. Do not silently overflow Free.
Review shared family@ unread count. If nobody opens it, pick an opener or disable it.
Rehearse a disable-and-replace on a lab prefix so a school-year leak is not the first time.
Yearly review of family-domain mail
Who still lives here, who still needs a string, what the school has on file, what leaked in a game.
Did catch-all sneak on? HOLD. Did leftover MX return? Delete.
Did we promise every cousin a name? Retract or upgrade the plan.
Did send-as appear on Free? Expect 550. Pay or stop.
Does the other adult still have the handoff? Update it.
Author: MailerZ editorial, Secuno LLC. Review when the household, pricing, or hosts change.
Closing notes on shared and individual family addresses
Family custom domain email is a few named aliases and maybe one household string, mapped to inboxes people open, with HOLD for guesses and exclusive MX. It is not a mailbox per child and not a catch-all playground.
Own lastname.com. Keep Gmail. Remap when kids grow. Disable what leaks. Do not claim stealth. The domain names you.
Start free if three strings are enough. Upgrade when the household list grows. Product path: /aliases-catch-all, /email-forwarding, /pricing.
People in a household map
Two adults who can open the registrar and MailerZ, the humans who actually open destinations, and the teens who will publish prefixes on games. If only one adult has the keys, write the risk. Hospital weeks happen.
Kids without aliases are people too. List them as not-yet so a relative does not create kid@ in a shared panel as a surprise. Surprises become leaks.
Grandparents who will not open Gmail need a human printer, not a prettier alias. Staff the destination. Do not romanticize the domain.
Schools are institutions. They need a stable string and a parent who remaps when custody or devices change. They do not need catch-all.
A well-meaning cousin with the DNS password is leftover authority. Seats and registrar access are family security, not vibes. /security does not become HIPAA because a relative is a nurse.
Proof packet for the household
Alias list, destinations, openers, HOLD on, exclusive MX listings, foreign probe IDs, builder email off, alias count versus /pricing, second-adult access yes/no.
A remap story for the next teen and a disable story for a leaked game name. If those stories are missing, the first leak will become a domain panic.
Screenshots filed with lastname.com in the filename. School-year you will not remember which Wi-Fi you were on.
If family@ is shared, the packet names the opener. Shared with nobody is unread report cards.
Stealth is not in the packet. The domain names the family. Unique prefixes isolate leaks. They do not hide lastname.com.
Appendix: household ideas that backfire
Catch-all so kids can invent names. You will receive the internet and a few targeted guesses. HOLD.
A mailbox seat per child 'to be proper.' Proper is a destination they open. IMAP per noun is sprawl.
Builder webmail for elders 'because it came free.' Free is leftover MX. Map to the inbox they open.
Printing a child's Gmail on the family site while also owning a domain. Then you have two identities and no plan. Pick the domain string or pick Gmail. Do not print both as if they were the same.
Family newsletter via SMTP loop to two hundred relatives. That is a list. Caps and filters will say so. Use an ESP or do not blast.
Dual MX with Google because a school form mentioned Workspace. Forms do not get leftover MX. Exclusive plus a Gmail destination is enough unless they require the suite as exchanger.
More operator notes for school years
Once a school year, crawl forms, disable game leaks, remap devices, re-query MX after any website 'help.' That is the operations calendar. It is shorter than a password-reset weekend after catch-all.
Talk to teens in plain words: the name is public, prefixes are killable, HOLD is why random names do not hit dad. They will still publish something. You will disable it. That is the system working.
Divorce, custody, and household splits are remap plus registrar decisions. This article cannot be counsel. It can say exclusive MX and living destinations. Do those.
Internal links: /aliases-catch-all, /email-forwarding, /pricing, /security. External: RFC 5321. No stealth. No badges.
Start free if three strings are enough. Upgrade when the household list is real. Do not invent unlimited cousins on Free.
Author: MailerZ editorial, Secuno LLC. Review when the household, hosts, or pricing change.
Extended narrative of a school-year domain
August: you map mom@, dad@, and school@ to two Gmail accounts. HOLD is on. A friend probes. Builder email is off. September: a teacher uses an unpublished kids@; HOLD has it; you decide whether to create the alias or ask them to use school@. October: a game leak hits a prefix the teen invented in a panel they should not have had; you disable it; you create a replacement; you update the game, not MX.
January: the website host enables email included. Morning re-query catches leftover MX. You delete it. Report cards keep arriving. That year is family custom domain email when it is operations, not a cute idea.
The teen wants stealth on lastname.com. You explain that the name is the family. Unique prefixes isolate leaks. They do not hide the household. If they need a mask for a different job, that is a different product. You do not dual-publish Google to look less like a forwarder. Exclusive MX stays.
A second adult can open the registrar. You practiced that in August, not during a hospital week. family@ has an opener. Shared with nobody is unread.
Free had three aliases. A fourth child string means /pricing, not catch-all. You quote the card. You do not invent unlimited cousins. You do not run a reunion blast through SMTP. Lists are lists.
Endnote on doors instead of a playground
A few named doors, destinations people open, HOLD for guesses, exclusive MX, remap as kids grow, disable what leaks. Not a mailbox per child. Not catch-all as a game. Not stealth.
Product path: /aliases-catch-all, /email-forwarding, /pricing. Author: MailerZ editorial, Secuno LLC. Review each school year and after any host 'help.'
Last checks before the school year
Named aliases only. Destinations people open. HOLD on. Exclusive MX. Foreign probes done. Builder email off. Alias count matches /pricing. Second adult can log in or the risk is written.
family@ has an opener. Kids without aliases are listed as not-yet. Teens know the domain is not stealth. Game leaks have a disable story. Catch-all is off.
School forms have the strings you mapped. Unpublished nouns will HOLD. You will decide create versus ask, not FORWARD everything to 'be safe.'
No list blast through SMTP. No leftover host MX after a website favor. No mailbox seat per child unless a suite job exists. Doors, not a playground.
Custody or household changes are remaps plus registrar decisions, not new domains in a panic. Keep exclusive MX. Move destinations. Tell the school the string stayed or the new string you actually mapped. Do not catch-all to paper over a messy week.
If a relative wants unlinkable mail on lastname.com, they want a different product. The registrable name names the family. Unique prefixes only isolate leaks. Say that once, in writing, so the next holiday argument is shorter. Confirm the live alias cap on /pricing before you promise every cousin a door. Elders who will not open Gmail need a human who will print messages, not a prettier unopened alias. A friend-probe to each public string beats dad emailing himself from the household inbox.
FAQ
- What is the safest way to handle family custom domain email?
- Create named aliases for each person you will staff and one shared alias if you want it. HOLD unknown. Exclusive MX. Probe from a third mailbox. Do not catch-all FORWARD “so kids can invent addresses.” Remap when a teen gets their own inbox.
- Does this require a new mailbox?
- No. MailerZ is not IMAP. Keep Gmail or Outlook unless you need a suite for other reasons.
- Will it work with Gmail or Outlook?
- Yes as destinations. Self-send is not proof. Use a third mailbox and open original.
- What DNS records are involved?
- Exclusive MX, verification TXT, one SPF if you send-as. Leftover MX is a hard stop. Dashboard values only for sending.
- What should I test before production?
- A uniquely titled probe from an unrelated provider to each public alias. Confirm Header From and hop history.
Key takeaways
- Named people plus optional shared.
- HOLD unknown. No kid catch-all.
- Exclusive MX. Delete builder leftovers.
- Remap as inboxes change.
- Free: three aliases, no send-as.
- Secrets are not family-chat material.
- Probe each alias.
- School gets the stable string.
Conclusion
Own lastname.com without owning a mailbox farm. Map people. Hold guesses.
Start free with a shared alias and two names, then print the shared string on the school form.