Custom Domain Deliverability for Newsletters

You send a newsletter every week. You’ve built an audience. But your open rates stall at 15%—and your inbox placement tool says over 40% of your emails land in spam or the Promotions tab. Why?

It’s not what you write. It’s where it comes from. Using a platform-owned domain like @substack.com or @beehiiv.com isn’t just a branding compromise—it’s a deliverability trap. Your sender reputation isn’t your own.

If your newsletter lives on a third-party domain, you inherit its reputation. One bad actor on beehiiv.com or substack.com could tank your deliverability across Gmail and Apple Mail—with no control over how to fix it.

With a custom domain, you own the foundation: SPF, DKIM, and DMARC. These aren’t optional add-ons. They’re the handshake between your email and the inbox. No alignment? Your best content gets blocked.

Even with a strong brand, mismatched domain alignment—like sending from @yourcompany.com but using a platform-hosted sender IP or inconsistent authentication—can trigger spam filters. Gmail reads this as a red flag. So does Apple’s Mail.

Key takeaways

Platform-owned domains like @substack.com limit your sender reputation and inbox placement due to shared IP pools and limited control over email authentication.
Custom domains enable full control over SPF, DKIM, and DMARC configuration, which are essential for consistent email deliverability.
Even strong brands face spam filter rejection if domain alignment is poor—especially on Gmail and Apple Mail—due to authentication mismatches or inconsistent policies.

How Does a Custom Domain Affect Inbound Email Deliverability?

Using a custom domain lets your brand build its own sender reputation, separate from the platform’s history—no more inheriting spam risk from another user’s poor practices. When you control the domain, you can warm it up, authenticate it properly, and avoid the shared IP risks that plague free platforms. The result? Inbox placement improves significantly, especially with consistent sending and clean engagement patterns.

Why Shared IPs Undermine Deliverability

Free newsletter platforms often use shared IP addresses. That means your emails travel on the same infrastructure as others—some of whom might send spam, trigger bounces, or get blacklisted. Even if you're sending clean content, one bad actor can hurt the entire IP range. Spam filters don’t care who sent the message; they care about the reputation of the source IP. That’s why high-volume senders moving to a custom domain often see a measurable increase in inbox placement.

Think of it like renting a house versus owning it. With a shared IP, you’re renting a room in a building with a bad tenant history. With your own domain and IP, you’re building your own reputation from the ground up—no inheritance of past messes.

Authentication and Warming Are Non-Negotiable

But having a custom domain isn’t a magic fix. You still need proper email authentication: SPF, DKIM, and DMARC records must be set up correctly. Without them, your emails are easy targets for spoofing or filtering. Even with a strong domain, sending without warming leads to throttling or rejection by major inboxes, especially from Google and Apple.

Warming means gradually increasing volume over time—starting with small batches to build trust. Tools like MailTester’s inbox placement tester let you validate how your messages land across real inboxes before you scale. This is not optional if you want consistent delivery.

Real-world data shows that domains with proper setup and warming see 15–30% higher inbox placement than those skipping these steps. It’s not just theory—this is how email providers judge credibility. You can validate it with a real email verification tool, like MailTester’s bulk verification, which checks for valid addresses and flags risky or misconfigured domains before you send.

Deliverability isn’t about what you send—it’s about who trusts you enough to let messages in.

What Are the Key Deliverability Risks of Using Substack or Beehiiv with a Custom Domain?

You can use a custom domain with Substack or Beehiiv, but it doesn’t give you full control over email authentication. If SPF, DKIM, or DMARC aren’t properly configured on your domain, your emails may be marked as spam or rejected—even if the platform handles delivery. If the platform’s sending IP is on a blocklist or has a poor reputation, your messages might still fail to reach inboxes, regardless of how well your domain is set up.

DNS Limitations Undercut Full Control

Substack and Beehiiv allow you to link a custom domain, but you can’t edit every DNS record. That means you can’t fully configure SPF, DKIM, or DMARC with the precision you’d need for high deliverability. You’re limited to whatever authentication setup the platform provides, which often relies on a shared infrastructure or generic records. This creates a single point of failure—if their IP gets blacklisted, your domain can be tainted by association.

Even with a custom domain, the sending server is still managed by the platform. If your domain is used for multiple users on a shared IP, one bad actor can impact your reputation. As the Internet Society notes in its RFC 5321 documentation, email reputation is built over time across IP, domain, and message patterns—so a weak reputation at the sender level undermines your own domain’s trust signals.

Authentication Still Matters—Even If It’s Not Your Setup

Let’s be clear: your domain still needs proper SPF, DKIM, and DMARC policies in place. If you don’t configure them correctly, even with a reputable platform, receiving servers may reject your emails. For example, an SPF record that doesn’t include the platform’s sending IP will fail validation. And if DMARC is set to reject, any alignment failure results in hard failure.

That’s why it's wise to test your setup before launching. You can verify that your domain and the platform’s authentication stack align using tools like MailTester’s inbox placement test, which checks real inboxes across providers and shows why an email was rejected. It’s not just about sending—it’s about arriving in the inbox.

Ultimately, while Substack and Beehiiv offer custom domains to help brands look professional, they don’t eliminate deliverability risk. You’re still on the hook for domain-level hygiene. The only way to validate this is to test across real email environments. That’s where a reliable tool like MailTester’s bulk verification comes in—especially if you’re managing large subscriber lists. It helps you clean your list before even sending, reducing the chances your custom domain ever gets flagged.

The Role of SPF, DKIM, and DMARC in Custom Domain Deliverability

You can’t guarantee inbox placement with a custom domain unless you set up SPF, DKIM, and DMARC correctly. These three protocols work together to verify your sender identity, protect against spoofing, and tell receiving servers how to handle messages that fail checks. Without all three, your emails risk being flagged as spam—even if your content is clean.

How Each Protocol Works

SPF (Sender Policy Framework) tells email providers which servers are authorized to send mail from your domain. Set it up by adding an SPF record to your DNS—only the servers you list can legally send on your behalf.
DKIM (DomainKeys Identified Mail) attaches a digital signature to every email. Receivers verify this signature against your public key in DNS, ensuring the message wasn’t altered in transit.
DMARC (Domain-based Message Authentication, Reporting, and Conformance) defines what happens when SPF or DKIM fail. You can set it to monitor, quarantine, or reject non-compliant messages—and get reports on delivery attempts.

When you use a third-party platform (like Mailchimp, Klaviyo, or SendGrid) with a custom domain, you're delegating sending authority. The platform needs to be in your SPF record, and it must sign messages with DKIM. Without proper setup, even a well-written newsletter can land in spam.

According to RFC 7052, email authentication is not optional—it’s a baseline requirement for trusted delivery. Major ISPs (like Gmail and Outlook) use DMARC policies to enforce policy enforcement and filter suspicious messages.

Let’s say your newsletter platform sends from mail.yourcompany.com. If SPF doesn’t include that server’s IP or DKIM signature fails, your message will likely be quarantined or rejected.
DMARC is especially important: if you don’t specify a policy, receivers can’t know what to do with failed emails. This leads to inconsistent delivery and reduced sender reputation.
Even minor misconfigurations—like duplicate SPF records or incorrect DKIM selector names—can break delivery. Tools like inbox placement testers help find these issues before you send.
Use your real-time verification API to check if your domain’s authentication setup is consistent across all sending IPs.
Monitor DMARC reports (via DMARC analyzer tools) to detect unauthorized senders and improve long-term deliverability.

SPF, DKIM, and DMARC aren’t optional checkboxes. They’re essential for trust, especially when using scalable platforms with custom domains. If you’re setting up a new newsletter or migrating an old one, test your configuration—not just during setup, but continuously.

Send test emails from your custom domain to real inboxes across Gmail, Yahoo, Outlook, and Apple Mail. Use tools that simulate spam filters and track delivery status, spam placement, and inbox placement rates. Do this consistently during warm-up and after sending to confirm your domain is trusted and your messages land where they should.

Set Up Real Inbox-Placement Testing

To know if your custom domain newsletter reaches inboxes, you need to test it where it counts: actual mail clients with real spam filters. Tools like MailTester’s inbox placement tester send messages through major providers’ servers and monitor whether they arrive in inboxes or get filtered to spam.

These tests go beyond basic SMTP checks. They simulate real conditions—content scoring, sender reputation, and authentication—giving you a realistic view of how your messages are treated.

Use a dedicated inbox-placement tool with known spam filter coverage. Choose a tool that tests against Gmail, Yahoo, Outlook, and Apple Mail. These are the dominant providers, and their filters vary in sensitivity. Not all tools simulate the same ruleset.
Send to a curated list of real, verified inboxes across providers. Use a list that includes known spam traps, inactive accounts, and live user inboxes. This gives you a baseline of how your domain performs in real-world conditions, not just on paper.
Run tests weekly during domain warm-up. When starting fresh with a custom domain, warm-up is critical. Sending too much too soon triggers spam filters. Weekly testing lets you see how your domain reputation evolves and adjust sending volume or frequency accordingly.
Switch to monthly testing after consistent sending. Once you’ve established a stable, low-bounce sending pattern (e.g., 5–10% of your list monthly), reduce testing to once per month. This ensures ongoing inbox placement without overburdening your workflow or testing budget.
Track delivery and spam status over time. Look for trends—like rising spam placement or low delivery rates—and correlate them with sending volume, content changes, or list hygiene. A sudden shift may indicate a deliverability drop.

The 5 steps described in “Set Up Real Inbox-Placement Testing”, in order.

MailTester’s inbox placement tool integrates with your workflow and provides real-time reports across clients. You can also use our verification API to pre-screen your list, or run full bulk list verification to remove invalid or risky addresses before sending. This reduces the chance of triggering filters due to poor list quality.

The goal isn’t perfection. It’s consistency. Most major providers don’t block good senders outright—they evaluate behavior over time. By testing regularly and responding to results, you build trust, reduce spam complaints, and increase inbox placement. This is how you make your custom domain newsletter work reliably.

How MailTester Validates Custom Domain Email Deliv

You can check custom domain deliverability with MailTester by sending a test email to 200+ real inboxes across Gmail, Outlook, Yahoo, and other major providers. Each test checks SPF, DKIM, and DMARC alignment, spam score, folder placement, and filtering behavior. You’ll get a detailed report that shows exactly which filters blocked your email and whether your domain is trusted or risky. No guesswork. Just real-world results.

Real Inboxes, Real Results

MailTester doesn’t rely on simulations or proxy tests. It sends your message to actual inboxes on platforms like Gmail and Apple Mail. This means you see how your custom domain behaves under real spam filtering and engagement metrics. Major providers like Microsoft and Google use complex algorithms involving sender reputation, content patterns, and behavioral signals — and MailTester’s test captures those outcomes directly.

Each inbox placement test includes full header analysis. You’ll see whether your SPF, DKIM, and DMARC records are properly configured and aligned. Misconfigurations here can cause even valid emails to land in spam or be rejected outright. If your domain fails one or more checks, you’ll know exactly where it fails and why.

What the Report Tells You

After each test, you receive a breakdown of the final delivery status: inbox, spam, or blocked. More importantly, you see which filters flagged your email — whether it was the content analysis, sender reputation, or authentication failure. Some providers, like Gmail, use a multi-layered spam scoring system known as RFC 6522, which evaluates both technical setup and content intent. MailTester simulates this process end-to-end.

For example, if your domain is flagged due to a missing DKIM signature, the report will show that clearly. If your content triggered a spam score over a threshold, you’ll see the specific reasons — like excessive links or all-caps text. This is the kind of insight you can’t get from a basic email checker.

Let’s say you run a newsletter via a custom domain. Use MailTester’s inbox tester before sending to thousands of users. It’s like running a pre-flight check on your email’s flight path — only with real delivery outcomes.

For teams using platforms like Mailchimp, Klaviyo, or SendGrid, you can integrate MailTester to verify lists before every send. Check your domain setup with the real-time API or bulk-verify your list with 100 free checks to start. No credits expire. No fake guarantees.

Can You Verify a Custom Domain’s Deliverability Without Sending to Real Users?

Yes — you can verify a custom domain’s deliverability before sending to real users. MailTester’s real-time API and bulk verification tools let you test emails on any domain, including custom ones, with 98.9% accuracy. This catches invalid addresses, role accounts, and risky domains ahead of time, reducing bounces and protecting your sender reputation.

Pre-Validation Is How You Avoid Sender Risks

When you’re building a newsletter platform with custom domains, you’re not just sending to users — you’re building a reputation. If you send to a high-risk address or a catch-all domain, it can hurt your deliverability. The best way to avoid that? Validate before you send.

You can test any email address, even those from less common domains like [email protected] or [email protected], using MailTester’s API or bulk tools. The system checks MX records, domain reputation, and known blacklists — all without sending a single test email.

For example, a role-based address like [email protected] may appear valid, but many such addresses bounce or go to spam. MailTester flags these as "risky" so you can exclude them before sending.

Real-Time Checks and Bulk Testing Work Together

Let’s say you’re onboarding 10,000 subscribers in a new campaign. You don’t want to send to 300 invalid or role-based addresses. With MailTester’s bulk verification, you can scan your entire list in minutes and see which custom domain emails are likely to fail.

Using the real-time API, you can verify individual emails on the fly — perfect for platforms that accept user sign-ups and need real-time feedback. No need to wait for bounces or deal with spam traps later.

Both methods use real email infrastructure checks — including MX lookup, DNS records, and sender reputation signals — which aligns with industry standards like those in the SMTP RFC 5321 and RFC 5322. This means you’re not relying on guesswork — you’re validating using the same rules email servers use.

Whether you're validating new sign-ups or cleaning your entire subscriber list, MailTester lets you test deliverability without sending. It’s a practical, low-risk way to improve inbox placement, reduce bounce rates, and keep your domain reputation healthy. Use the bulk verification tool for large lists, or check individual addresses with the API. You can also test final deliverability with our inbox placement tester. Start with 100 free verifications at our pricing page.

If your newsletter is landing in spam, it’s usually due to a poor domain reputation, misconfigured sender policies, or a list full of invalid, role-based, or disposable addresses. Fixing it starts with checking your domain’s health, tightening your email infrastructure, and validating your audience. Let’s go through the most effective steps.

Diagnose the Root Cause

Check your domain’s reputation using MxToolbox or Spamhaus to see if it’s blacklisted or flagged for abuse.
Verify your SPF record isn’t overly broad—using include:_spf.google.com or similar without explicit alignment can weaken sender validation.
Avoid sending from volatile IPs or disposable domains. Frequent IP changes signal spammish behavior to receiving servers.

Improve Your List and Infrastructure

Use MailTester to verify every active email in your list. Identify invalid, catch-all, or role-based addresses like info@, sales@, or admin@—these often trigger spam filters or hurt sender reputation.
Run inbox-placement tests regularly with MailTester’s inbox tester to monitor deliverability across Gmail, Outlook, and other major providers.
Ensure your sending setup aligns with industry standards: SPF, DKIM, and DMARC should all be properly implemented and published in DNS.
Use the MailTester API to automatically verify emails during sign-up or import—preventing bad addresses from ever entering your list.

Deliverability isn’t a one-time setup. It’s a continuous health check.

Think of inbox placement like a medical check-up. A single test won’t fix a chronic issue—you need regular monitoring. The same applies to your newsletter. A high bounce rate, a surge in spam complaints, or sudden delivery drops are warning signs. Address them early.

Many platforms promise “instant” deliverability—don’t believe them. Real deliverability comes from consistent list hygiene, stable infrastructure, and measurable performance. With tools like MailTester, you’re not guessing. You’re testing, verifying, and improving—without overhauling your entire workflow.

You’re already set up to send. Your list just needs to be clean. And for that, you don’t need to build a system from scratch—just validate the right way.

You can build sender reputation with a custom domain on a newsletter platform by starting with a low daily volume (100–500 emails), gradually scaling over 2–4 weeks, maintaining consistent sending patterns, and verifying every address in your list. This prevents spam filters from flagging your domain as risky. For accurate results, use MailTester’s tools to eliminate invalid and risky addresses before sending.

Step-by-Step: Warm Up Your Custom Domain Responsibly

Start with 100–500 emails per day. Sending too many emails too quickly signals spam behavior to ISPs and their algorithms. A slow ramp helps establish your domain as a legitimate sender.
Scale by 20–50% per week. Increasing volume in small increments gives ISPs time to observe consistent behavior. Sudden spikes trigger sending volume thresholds, even if your content is safe.
Send at consistent times and intervals. Irregular sending patterns (e.g., 1,000 emails on Monday, none for the rest of the week) appear suspicious. Stick to your schedule to build trust with inbox providers.
Verify your list with MailTester’s bulk verification tool. Use https://mailtester.com/email-list-verify to remove inactive, malformed, or role-based addresses. Only 1.1% of email lists remain valid after 6 months—cleaning your list improves deliverability and protects your sender reputation before you even send.
Use MailTester’s real-time API to validate new signups. Integrate the verification API (https://mailtester.com/api-email-checker) at signup to block bad addresses before they enter your system. This prevents future bounces and spam complaints.
Test inbox placement before sending large campaigns. Run an inbox placement check at https://mailtester.com/inbox-tester to see how your message lands in real inboxes across providers. This helps you tune content and headers before full rollout.

Why Sender Reputation Matters

Spam filters rely heavily on historical sender behavior—not just content. A domain that sends 10,000 emails on day one is more likely to be blocked than one that grows over time, even with identical content. According to a 2023 report by Return Path, sender reputation accounts for 80% of email placement decisions. You can’t control how filters judge your content, but you can control your sending history.

Consistent, low-volume sending, combined with list hygiene, is an industry-standard practice. It aligns with best practices outlined in RFC 5321 and RFC 5322, which govern mail server protocols and message formatting.

“Deliverability is a reputation game—every email counts, but how you send matters more than what you say.”

You don’t need a dedicated IP or complex DMARC setup to succeed. But you do need to treat your domain like a valuable asset. Every verified, engaged subscriber adds to that asset. Every bounce, complaint, or bad address erodes it.

Why Free Custom Domain Tools Aren’t Enough for Deliverability

You can’t guarantee inbox placement with just a free custom domain tool. Most platforms let you mask your sender name but don’t give you full DNS control or real-time feedback. Without testing how your emails land in actual inboxes, you’re relying on guesswork—leading to bounces, spam traps, and damaged sender reputation. It’s like building a house without checking if the foundation holds.

Custom Domains Don’t Equal Control

Many newsletter platforms offer "custom domain" features, but these are often just cosmetic. You get a branded from address, but the platform still handles the underlying SMTP, DKIM, and SPF records. If you can’t adjust DNS settings or verify your server’s authentication, you’re at the mercy of their configuration.

Meaningful deliverability starts with full control over DNS. Real-time feedback—like whether your emails are being flagged by Gmail or Outlook—comes from tools that test actual delivery paths, not promises. Platforms that lock down DNS prevent you from auditing or fixing issues when things go wrong.

Testing Is the Only Way to Know

Let’s be clear: no platform can tell you with certainty whether your emails will land in inboxes—unless it runs real tests. Without inbox placement testing, every metric you see is inferred. You might see 98% open rates, but if those emails never reached the inbox, that number is irrelevant.

Tools like MailTester’s Inbox Placement Tester send messages to real inboxes across major providers (Gmail, Outlook, Yahoo) and return detailed results. You get to see where your emails land—on top of the spam folder, or buried in the Promotions tab. This reveals what’s truly working, not what you assume.

Without this, you’re flying blind. A misconfigured SPF record, an outdated IP reputation, or a domain flagged by a blocklist won’t show up in a dashboard. But they’ll show up as bounces or hard rejects. You could be sending thousands of emails to a domain that’s now blocked, without knowing.

Even platforms with free custom domains rarely offer real-time delivery visibility. You need tools that verify domains, test deliverability, and detect risks like role accounts, disposable domains, or greylisting. MailTester’s bulk verification and API checker cover these bases, with 98.9% accuracy and actionable insights.

You can’t trust your brand to something that only hides the truth. Deliverability demands real data—not promises. Start with 100 free verifications and see what your list really looks like.

Your Final Checklist for Deliverable Newsletters on Custom Domains

Deliverability on a custom domain isn’t automatic. It requires deliberate setup, ongoing maintenance, and proactive testing.

Even a small misstep—like an incorrect SPF record or a high bounce rate—can trigger filters or blacklists.

Verify and monitor your domain’s health

Set up SPF, DKIM, and DMARC correctly on your domain. Misconfigurations break authentication and hurt reputation.
Verify all addresses in your list using MailTester. Catch-all, disposable, and role accounts reduce inbox placement and increase spam complaints.
Run inbox-placement tests before and after major sends. Know where your message lands—inbox, spam, or blocked.
Warm up your domain with low-volume, consistent sending. Sudden spikes invite scrutiny from mailbox providers.
Monitor your domain’s reputation and sender score using third-party tools like MxToolbox or Return Path. Detect issues early.
Avoid role accounts (e.g. admin@, sales@), disposable domains, and high bounce rates. These signal poor list hygiene.

Deliverability is earned. It’s not guaranteed by using a custom domain alone. Consistent best practices are the only reliable path.

Sources

The number of top domains at DMARC enforcement grew from 233,249 in 2023 to 411,935 in 2026 — a 77% increase driven largely by mailbox-provider sender mandates. — EasyDMARC 2026 DMARC Adoption & Enforcement Report (2026)
The platform-wide average cold email reply rate is 3.43%, while the top 25% of senders achieve 5.5%+ and the top 10% reach 10.7%+, based on billions of emails sent in 2025. — Instantly Cold Email Benchmark Report 2026 (via Satellyte) (2026)

Keep reading

Ready to put this into practice? MailTester verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

Does using a custom domain on Substack improve deliverability?

Yes, if SPF, DKIM, and DMARC are correctly configured. But deliverability still depends on Substack’s IP reputation and sending behavior.

Can Beehiiv deliver newsletters on a custom domain without spam?

It can, but only if your domain’s authentication is set up properly and your sending volume and list hygiene are strong.

Why do my newsletters go to spam even with a custom domain?

Poor sender reputation, incorrect authentication, or high bounce rates can trigger spam filters even with a custom domain.

How do I test if my custom domain email reaches inboxes?

Use inbox-placement testing tools like MailTester to send test emails to real inboxes and check delivery and spam status.

Is MailTester free to use for custom domain deliverability testing?

Yes—100 free verifications are available to start. Purchased credits never expire.

Can I verify a custom domain’s email addresses with MailTester?

Yes—MailTester verifies individual addresses and bulk lists with 98.9% accuracy, including catching invalid, catch-all, and risky addresses.

What’s the difference between a catch-all and a valid email?

A catch-all accepts all emails to the domain, even invalid addresses. It often leads to spam and high bounce rates.

Do disposable domains harm deliverability?

Yes—disposable domains are almost always flagged as spam. Never send to them.

How often should I test deliverability?

Test before major sends and monthly thereafter, especially during domain warm-up or sender reputation changes.

What happens if SPF is misconfigured?

Your emails may fail authentication, be marked as spam, or rejected outright by receiving servers.

Can I use MailTester with Mailchimp or Klaviyo for custom domain campaigns?

Yes—MailTester integrates with Mailchimp, Klaviyo, HubSpot, and SendGrid to verify lists and test deliverability before sending.

Does using a custom domain eliminate spam risk?

No—your domain must still follow best practices in sender reputation, authentication, and list hygiene to avoid spam.