A custom sending domain is the address your list speaks from. Most newsletter tools let you set one. Few explain why it's the difference between a reputation you keep when you move and a reputation that stays with whatever tool you're on this year.
The first page of results for this query is almost all help docs. Add this record, point that DNS entry, wait for verification. The mechanics are correct. The framing is wrong. A custom sending domain isn't a setup task. It's the part of the spine that travels.
What a custom sending domain actually is
A sending domain is the part after the @ in the address your emails go out from. news@yourbrand.com uses a custom sending domain. yourbrand@app.newslettertool.com does not. The first one is yours. The second is rented.
Inbox providers like Gmail, Yahoo, Outlook, and Apple Mail score every send. One of the signals they score is the sending domain's history. How long it's been active. What it sends. How recipients respond. That history is called domain reputation, and modern mailbox providers weight it heavily, by some counts more than the IP address the email passed through.
When you send from your own domain, you're building that history. When you send from the platform's shared domain, you're renting someone else's, and not the part of theirs you'd want.
The shared-domain tax
On a shared sending domain, your sender reputation is tied to everyone else who sends through the same domain. Guidance from the delivery specialists at Suped puts it plainly: your reputation is tied to the sending practices of every other user on that domain. One spammy sender on the same shared address can pull your messages into the promotions tab, or further, the spam folder.
You also can't take it with you. If your tool doubles its price next year, or a feature you depend on disappears, you can move your subscribers. The reputation you built on the shared domain doesn't move. You start over.
And the address itself looks borrowed. A reader sees writer@app.beehiiv.com and reads the second half as the brand. The default sending address trains the reader to associate the work with the tool, not the writer.
Why the reputation is the asset
Inbox providers reward continuity. They're trying to detect a sender who shows up on time, in volume, with engaged recipients, over a long period. A domain that has been sending the same newsletter to opted-in subscribers for two years is, to Gmail, a known quantity. A brand-new shared subdomain is not.
This is where the "your domain stays yours" promise lives. Buttondown puts it in their own words: with a custom domain, that reputation is yours. You can start on one tool, move to another, come back, and the inbox providers still recognize the sender they've been delivering to all along. The tool changes. The address does not.
On the same logic, Gmail and Yahoo now require DMARC for senders above a small daily threshold. Without it, inbox placement falls off a cliff. DMARC is a policy you publish on your own domain. There is no way to publish it for an address you do not control. That is another reason the custom sending domain isn't optional anymore for any list serious about reaching the inbox.
Setup in plain language: SPF, DKIM, DMARC
Three records. All live in the DNS settings for your domain (the panel at the registrar where you bought it).
- SPF tells inbox providers which servers are allowed to send mail on behalf of your domain. It is a guest list.
- DKIM adds a cryptographic signature to every email you send, so the inbox provider can verify the message wasn't altered in transit and that it actually came from your sending tool.
- DMARC tells inbox providers what to do when a message fails SPF or DKIM. Most lists start in monitor mode and tighten the policy as the reports come in.
Most newsletter tools generate the exact records for you. You copy them into your DNS panel and verify. DNS propagation typically resolves in fifteen minutes to twenty-four hours, after which the tool flips a green check. That is the setup. The technical part is the easy part.
The deeper version of this conversation lives in our beginner's guide to email deliverability, which covers reputation, content, and list hygiene end to end. Read it once if you haven't.
The portability test
There is one question worth asking before you commit to any newsletter tool. If I move next year, what comes with me?
The list comes with you. Every serious tool will export it. The archive of past posts will usually export too, in some form. The sending domain's reputation comes with you only if the sending domain was yours to begin with. If it was the platform's, you're starting from zero on the next tool, and Gmail will treat your first sends like cold sends.
That is the second reason this matters. The list is the spine, and we've made the economic case for that elsewhere. But the spine has an address. If the address stays behind when you move, you've left part of the spine behind too.
Nashra's position on this is the same one we take on the list itself. Your reader trusts the address. The address is yours. We send through Mailgun for inbox placement and ask you to set up your own sending domain on day one, not as a setup chore but as the part of the list that travels. The email newsletter product walks you through it in about ten minutes.
A subscriber converts roughly 10× better than a follower. That math only holds if the sends actually arrive in the inbox, on a domain you keep. Set the sending domain up once. Keep it for the next decade. The list, the reputation, and the address travel together.
