A personal domain email migration checklist is how lastname.com survives registrar hops, website builders, and leftover MX. Inventory the aliases you actually use, map them on MailerZ, lower TTL if you can, cut exclusive MX, probe, then tell schools and banks the address did not change. Long-term ownership is a stable string plus a map you control. Not a builder’s “free email.”
Quick answer for personal domain email migration
The address should survive you changing hosts. That is the point of a personal domain.
RFC 1035 and MX exclusivity are the migration physics.
Builders and old hosts leave MX. Treat leftovers as a hard stop.
HOLD unknown so a migration does not become a catch-all festival.
Tell institutions the string is unchanged. Only the hop changed.
Start free and migrate one personal domain as a rehearsal for later business domains.
Authoritative mail transport is defined in IETF RFC 5321 — Simple Mail Transfer Protocol. Product path: email forwarding, migration planner, and custom-domain email alias.
User problem and decision criteria
Decision criteria: complete list of given-out addresses, NS access, builder leftovers, TTL wait.
If you cannot list the banks, you will discover them as held mail. Budget that.
Do not change the public string during a hop change. That is two migrations.
Family members need to know the shared alias still works.
Agencies should keep the old MX screenshot in the personal-domain folder too.
If send-as matters for invoices you send as yourself, schedule SMTP after inbound.
No inboxing promise to yourself.
If you need IMAP archives on the domain, a hop is not an archive.
Technical mail flow
Inventory → map → TTL → exclusive MX → probe → cancel old email product → notify only if the string changed (it should not).
Rollback is the screenshot.
Held mail during the first week is your missing inventory.
SRS and intact From continue.
Leftover builder MX is the usual thief.
Step-by-step setup / decision path
- Export or remember every given-out alias.
- Create them on MailerZ. HOLD on.
- Find authoritative NS. Lower TTL if you can wait.
- Screenshot old MX.
- Cut exclusive MX. Delete leftovers.
- Probe each named alias and a fake (hold).
- Cancel builder email only after probes.
- Raise TTL later. Keep the sheet.
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
MX before map: 550 to a bank.
Dual MX: split.
Changed the public string: vendor chaos.
No screenshot: no rollback.
Catch-all FORWARD to hide a bad sheet.
Cancelled builder before MX: gap.
Self-send: lie.
Wrong NS panel: fiction records.
Free send-as surprise.
Inboxing promise.
Header rewrite demand.
Lost the domain at the registrar: different disaster—auto-renew first.
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, ten aliases, one seat, fourteen-day store, send-as disabled, SMTP and API disabled. Solo forty dollars a year, twenty-five aliases, ninety-day store, 2,500 outgoing, 20 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
Losing a bank letter costs more than a careful weekend.
Builder email is cheap until leftover MX.
Solo is cheap long-term ownership.
Changing the public string is the expensive move. Avoid it.
TTL wait is calendar cost, not cash.
Agencies can sell this checklist as a personal-domain tidy.
Catch-all after migrate costs attention for years.
Domain auto-renew is mandatory spend.
Operational depth
Auto-renew the domain before you touch MX. A lapsed personal domain is not a forwarding problem.
Put schools, banks, and government in the sheet first. Those hurts are worse than a shop alias.
Family shared alias is a row. Probe it.
If a builder injected MX you never noticed, two resolvers will show it. Delete it.
Do not migrate on the day a tax form is due if you can wait a week of TTL.
Keep a password manager record of NS and MailerZ. Future you in five years is the operator.
Held-mail review in week one is the inventory you forgot.
If you also have a company domain, do not mix the sheets.
Quote Solo if named aliases exceed three or you need send-as.
No SOC 2 for a personal hop. Still exclusive MX.
Re-probe after leftover deletion.
Write a one-page note: where NS lives, where aliases live, who pays the registrar.
Worked scenarios for a personal-domain cut
You used a registrar's 'free email' for eight years. Banks, schools, and Apple ID still have you@lastname.com. The builder is now a leftover MX risk. Sheet every string you remember. Map those on MailerZ. Screenshot old MX. Publish exclusive MailerZ MX. HOLD unknown. Probe from a friend's mailbox. Then disable the builder email. The address did not change. The hop did. That is long-term ownership.
You moved the website to a new host and they 'set up mail' as a courtesy. Courtesy is leftover MX. Delete it. Your identity is not their hosting add-on. Re-query two resolvers after every site migration, not only after email projects.
You dual-published Google and MailerZ 'until you were sure.' Sure never came. Some banks hit Google, some hit MailerZ. Dual publish is not a checklist item. Exclusive plus a probe is.
You have twenty forgotten shop aliases and three you still use. Map the three. HOLD the rest. Catch-all FORWARD will resurrect a decade of breaches into your Gmail. Long-term ownership includes forgetting on purpose.
You want send-as from Gmail as you@lastname.com. That is paid SMTP, dashboard values, Gmail send-as. Free will 550. Do not stack send-as into the same hour as the MX cut if you can unstack. One class per window.
A family member still uses the old builder webmail. After exclusive MX they stop receiving. Tell them before the cut. Destinations become Gmail you actually open. Builder webmail is not a destination you should keep as MX.
Practice and anti-patterns for personal-domain mail
Practice: inventory first. Anti-pattern: cut MX and remember banks later when 2FA codes vanish.
Practice: exclusive MX. Anti-pattern: backup Google 'just in case.'
Practice: HOLD unknown. Anti-pattern: catch-all so you can 'see your whole past.'
Practice: third-mailbox probe. Anti-pattern: emailing yourself from Gmail.
Practice: disable builder email products. Anti-pattern: leaving them on so they republish MX next renewal.
Practice: screenshot old MX. Anti-pattern: no rollback picture when you typed the hostname wrong.
Practice: unstack DNS-host moves and email cuts. Anti-pattern: a Saturday of both and no idea which broke.
Operator closeout for a personal cut
Closeout is the sheet of mapped strings, two-resolver listings, leftover absent, probe IDs, builder email off, and the date you will cancel the old mailbox seat after TTL plus a buffer.
Apple ID, banks, schools, government, and the password manager get a note only if the address changed. If it did not change, write that too so you do not 'update' them into a typo.
If send-as is later, a separate packet: paid plan, dashboard SMTP, Gmail send-as. Do not mix it into the inbound closeout.
Registrar 2FA is yours, not a cousin's. Long-term ownership includes the login that can destroy MX.
A morning re-query after the next website save. Builders republish. You live here for decades. One morning is cheap.
Store the packet where you will find it in five years. A Downloads screenshot named image.png is not ownership.
Edge cases in personal-domain ownership
The domain expires because auto-renew died. MX excellence will not save an expired zone. Registrar calendar is part of the checklist.
WHOIS privacy versus a website that already names you. MailerZ does not hide lastname.com. Ownership is identifiability. If you wanted stealth, you wanted a mask, not a family domain.
A spouse's school requires Google Workspace. They can keep a personal Gmail destination while MX stays MailerZ, or they can move that one life into Workspace. Do not dual-publish to satisfy a form.
Internationalized names or a hyphen you always mistype. Print the exact string you mapped. HOLD will catch the mistype if you do not create it. Decide whether you want the typo alias.
You used plus-tags at Gmail as your only 'aliases.' Those are not domain aliases. You cannot disable a plus tag without changing the mailbox. Move public strings onto MailerZ local-parts you can kill.
Legal name change. The domain can stay. Aliases can add a new person-shaped string. Do not rush a domain drop unless you mean to. Ownership can survive a name; leftover MX cannot survive sloppiness.
Field notes from lastname.com cuts
The people who stay happy are the ones who treated the domain as infrastructure: registrar, DNS, MX, map, probe. The people who stay angry treated it as a website theme setting.
Banks are slow. If you must change the printed address, start with them, not with the MX. If you keep the address, they never need to know you changed hops.
Builder 'free email' is leftover MX with marketing. Read the records, not the banner.
RFC 1035 MX is public. Friends can look. That is fine. Exclusive still matters.
Link /email-forwarding and /docs. Inbound first. Send-as later. Free has no send-as.
No inboxing guarantee to yourself. Your Gmail tab is still Gmail's.
Handoff memo for future you
Registrar, DNS host, MailerZ login, mapped aliases, HOLD policy, where the packet lives, who else has 2FA. If you get hit by a bus, someone should be able to keep lastname.com alive without guessing.
The memo forbids dual MX and builder email products. Future you will be tempted. The sentence has to exist.
Renewal calendar and card on file. Expired domains are identity incidents.
Dashboard is the SMTP source if you later send. No folklore ports.
Link /aliases-catch-all. Unique prefixes for shops. Shared hello@ for humans who must remember it.
Acceptance criteria for the personal migration
Inventory exists. Mapped strings match the life you still live. HOLD for the rest. Exclusive MX on two resolvers. Foreign probe succeeded.
Builder email off. Old seat cancel dated after TTL. Screenshots filed with the domain name.
No dual publish. No self-send gate. No catch-all FORWARD of a decade of leaks.
Registrar 2FA yours. Packet findable. Morning re-query done or scheduled.
Send-as out of band unless you paid and copied the dashboard.
No invented SLA. No SOC 2 story on a family domain.
Operations review of a life-long zone
Once a year: re-query MX, crawl where you printed the address, renew the domain, review aliases you no longer want, confirm HOLD.
After every website host change: leftover MX check. Hosts 'help.'
After every device change: password manager still has MailerZ and registrar.
If you added a shop alias for every store, disable the ones that leaked. That is ownership too.
Quote /pricing if the alias list outgrew Free. Three aliases is the Free cap. Confirm the card.
Do not stack a DNS-host migration into the anniversary review unless you cloned records first.
Annual review for long-term ownership
Is the domain still yours? Are NS where you think? Is MX exclusive? Do the mapped names still match your life?
Did a builder republish mail? Delete. Probe.
Did you start sending without paying? Expect 550. Pay or stop.
Did catch-all sneak on? HOLD unless you wrote a reason.
Does someone else need the handoff memo? Update it.
Author: MailerZ editorial, Secuno LLC. Review when hosts, pricing, or your life change.
Closing notes on keeping lastname.com
A personal domain email migration checklist is inventory, exclusive MailerZ MX, HOLD unknown, a foreign probe, and builder email off. The address stays. The hop becomes yours. Dual publish is not caution. It is a split.
Long-term ownership is a stable string plus a map you control, plus a registrar you still pay. Not a host's free mailbox.
Start free, map the names you actually use, probe, then cancel leftover products. Product path: /email-forwarding, /docs, /aliases-catch-all, /pricing.
People who keep lastname.com alive
You, a deputy who can open the registrar, and anyone who still reads builder webmail. Tell the webmail people before exclusive MX. After the cut they will swear mail is dead. They are on the wrong store.
A spouse or sibling with 2FA is better than a note in a drawer. Single-adult lock-in is how a hospital week becomes an expired domain. Long-term ownership is a two-person problem.
Do not give a website freelancer unrestricted DNS if they like to 'enable email.' Give them A records. You keep MX. People plus permissions.
Schools and banks are slow institutions, not people you can Slack. If the address stays the same, you do not need them in the cut. If you change the string, start with them months early.
Future you is a person. File the packet where future you looks. Downloads is a graveyard.
Proof packet for a personal-domain cut
Inventory sheet, mapped aliases, HOLD on, old MX screenshot, new two-resolver listings, leftover absent, foreign probe IDs, builder email off, cancel date for the old seat, registrar 2FA note.
If send-as is not in this window, the packet says inbound only. Future you will try Gmail send-as on Free and call it a failed migration. Write the 550 in advance.
Apple ID and bank list only if the string changed. If it did not, write 'string unchanged' so you do not create typos in portals.
Filename the domain, not image.png. Five-year-later you will not remember which cut this was.
A morning re-query result belongs in the packet, not only in your memory of a good night.
Appendix: personal-domain traps
Registrar email forwarding that is not MailerZ and not in your sheet. They will keep a silent second hop. Turn it off.
Website builders that recreate MX on SSL renewal. Re-query after 'nothing email-related' work.
Family catch-all FORWARD to relive the 2014 forum era. HOLD. Map what you still use.
Plus-tags as your only aliases. Move public life onto killable domain prefixes.
Domain auto-renew on a dead card. Calendar it. Expired zones are identity incidents.
Stacking a DNS-host move with the MX cut. Clone first or unstack. Empty-zone delegation is an outage that looks brave.
More operator notes for decades, not weekends
The point of lastname.com is that the string outlives hosts. Every time you accept leftover MX, you rent the identity back to a vendor. Delete leftovers. Keep the map.
You will forget aliases. HOLD is how forgetting stays safe. Catch-all is how forgetting becomes a breach reunion.
Once a year is enough operations for a simple household: MX, renew, crawl, disable junk prefixes. Put it near a birthday so it happens.
Internal links: /email-forwarding, /docs, /aliases-catch-all, /pricing, /tools. External: RFC 1035, RFC 5321. No inboxing promise to yourself.
Start free, map the names you actually use, probe, cancel builder email. Upgrade when the list or send-as is real.
Author: MailerZ editorial, Secuno LLC. Review when hosts, family, or pricing change.
Extended narrative of keeping the same address
You have used you@lastname.com since 2014. The registrar's free mail is now a leftover risk. You write the three strings you still give banks and schools. You map them on MailerZ. You screenshot old MX. You publish exclusive MailerZ MX. You HOLD unknown so 2014 forum aliases do not flood you. A friend probes. You disable builder email. You cancel the old seat after the TTL you actually read. Banks never hear from you. The address did not change. That is a personal domain email migration checklist.
Next year the website host 'sets up mail' during an SSL click. You re-query. You delete the gift MX. Ownership is the habit of leftover checks, not a one-time courage.
You do not dual-publish Google to feel careful. Careful is exclusive plus a probe. Dual is a split that will hide a 2FA code in the wrong building.
You file the packet next to registrar 2FA and a deputy who can open it. Downloads/image.png is not a decade plan. Expired auto-renew is an identity incident. Calendar the card.
Send-as waits for a later Saturday if you want it. Unstack. Free has no send-as. When you pay, copy the dashboard. Do not invent a port from a Gmail help page.
Endnote on owning the hop for decades
Long-term ownership is a stable string, a map you control, exclusive MX, HOLD for what you forgot, and a registrar you still pay. Not a host's free mailbox. Not leftover MX as a security blanket.
Product path: /email-forwarding, /docs, /aliases-catch-all, /pricing, /tools. Author: MailerZ editorial, Secuno LLC. Review yearly, and after every host or builder 'favor.'
Last checks before you cancel the old mailbox
Two resolvers exclusive. Builder email off. Foreign probe succeeded. HOLD on. Inventory mapped. Old MX screenshot filed with the domain in the filename. TTL you actually read, plus a buffer, then cancel. Cancel early and the leftover host still answers for cache holders.
String unchanged for banks unless you meant to change it. Do not 'update' portals into a typo. Deputy can open registrar 2FA. Auto-renew card is alive.
Send-as is out of this window or paid with dashboard values. Free will 550. Unstack the Saturday. Dual publish is not caution.
Morning re-query after the next website save is on a calendar. Hosts help. Helping republishes MX. Yearly review is next to a birthday so it happens.
Registrar forwarding and 'email included' toggles are second hops that never appear on your MailerZ sheet. Turn them off in the same sitting as leftover MX. A silent registrar forward is how a bank code lands in a webmail you stopped opening in 2019.
File the packet where the deputy will look—password manager note, not Downloads. Future you during a hospital week is the operator this checklist was for. Plus-tags at Gmail are not domain aliases; move public strings onto prefixes you can disable without changing the mailbox. Empty-zone NS moves are a different Saturday—clone MX first or do not stack them into this cut. Self-send from your destination Gmail is still not the gate.
FAQ
- What is the safest way to handle personal domain email migration?
- Sheet the strings you have given banks and schools. Map them first. Screenshot old MX. Exclusive MailerZ MX. HOLD unknown. Third-mailbox probe. Then cancel builder email. Do not dual-publish.
- 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
- String stays. Hop changes.
- Sheet banks and schools first.
- Exclusive MX. Screenshot rollback.
- HOLD unknown.
- Cancel builder email after probes.
- Auto-renew the zone.
- Keep a five-year operator note.
- Probe named and fake.
Conclusion
Long-term personal domain email is a stable string and a map you can still find in 2030. Exclusive MX is how you get there.
Start free, cut leftovers, and leave the address on the bank profile alone.