Most newsletter creators don't think twice about their sending address. They sign up for a platform, start writing, and emails go out from something like [email protected] or [email protected].
It works. Until it doesn't.
The problem with borrowed domains
When you send from a platform's domain, you're sharing that domain's reputation with every other sender on the platform. If someone else on the same platform gets flagged for spam, your deliverability takes a hit too.
Think of it like a shared apartment building. One tenant throws loud parties every night, and eventually the whole building gets a bad reputation. The landlord — Gmail, Outlook, Yahoo — starts treating everyone in that building with suspicion.
This is exactly what happens with shared email domains. Your carefully written newsletter about product design ends up in the same reputation bucket as someone blasting crypto promotions. You didn't do anything wrong, but your emails land in spam anyway.
What custom domain sending actually means
When we say "send from your own domain," we mean that your newsletters arrive from [email protected] instead of [email protected]. The technical setup involves three DNS records:
DKIM (DomainKeys Identified Mail) — A cryptographic signature that proves the email actually came from your domain. Think of it as a wax seal on a letter.
SPF (Sender Policy Framework) — A list of servers authorized to send email on behalf of your domain. It tells inbox providers "these servers are allowed to send as me."
DMARC (Domain-based Message Authentication, Reporting, and Conformance) — A policy that tells inbox providers what to do when an email fails DKIM or SPF checks. It's the enforcement layer.
Together, these three records tell Gmail, Outlook, and every other inbox provider: "This email is legitimate, it came from an authorized server, and here's the cryptographic proof."
Why custom domains improve deliverability
Inbox providers use sender reputation as a major signal for filtering. When you send from your own domain, you build your own reputation — isolated from everyone else.
Here's what that means in practice:
Your reputation is yours alone. If you consistently send emails that people open, click, and don't mark as spam, your domain builds a strong reputation. Nobody else can damage it.
Authentication passes cleanly. With proper DKIM, SPF, and DMARC records, your emails pass every authentication check. Inbox providers see a fully verified sender and give your emails preferential treatment.
Brand recognition in the inbox. When someone sees [email protected] in their inbox, they know exactly who it's from. This increases open rates because the sender is recognizable and trusted.
Portability. If you ever switch newsletter platforms, your domain reputation comes with you. You're not starting from zero because the reputation is tied to your domain, not the platform.
The brand trust factor
Beyond deliverability, there's a simpler argument: professionalism.
Imagine you run a design studio. Would you rather your clients receive emails from [email protected] or [email protected]? The answer is obvious.
Your domain is your brand. Every email you send either reinforces that brand or dilutes it. A custom sending domain says "this is a real business" in a way that a platform subdomain never can.
This matters especially for:
- Freelancers and consultants building personal brands
- Small businesses establishing credibility
- Media companies where brand trust is everything
- Developer tools where technical credibility matters
The counterargument (and why it's weak)
Some creators argue that platforms like Substack have such strong domain reputation that sending from their domain is actually better for deliverability.
This used to be partially true. Large platforms do invest in deliverability infrastructure. But the argument breaks down for two reasons:
First, shared reputation is a liability, not just an asset. One bad actor can hurt everyone. Platform providers try to police this, but it's a constant battle.
Second, inbox providers have gotten much smarter. They now look at individual sender signals within shared domains. But if you're going to be judged individually anyway, you might as well own the domain and get full credit for your good behavior.
How to set it up (it's easier than you think)
Setting up custom domain sending used to require a sysadmin. Today, most newsletter platforms walk you through it:
- Add DNS records. You'll add 2-3 records (DKIM, SPF, sometimes DMARC) to your domain's DNS settings. This takes about 5 minutes.
- Wait for propagation. DNS changes can take up to 48 hours to propagate globally, though most are done within an hour.
- Verify. The platform checks that your records are set up correctly and starts sending from your domain.
CocoMail includes guided domain authentication and custom-domain sending on every paid plan instead of reserving it for a higher tier.
The bottom line
Your newsletter is your direct line to your audience. Don't let someone else's domain sit between you and your readers. Custom domain sending protects your deliverability, strengthens your brand, and gives you independence from any single platform.
The setup takes minutes. The benefits last as long as you keep writing.
Ready to send from your own domain? Start sending with CocoMail. Custom-domain sending is included on every paid plan.