Our verdict
Start a new newsletter on a dedicated sending subdomain such as news.yourdomain.com, authenticate it fully, and leave your root domain for person-to-person email and invoices. Some providers recommend this directly: beehiiv says sending from a subdomain protects your main domain's reputation and can improve deliverability, and Yahoo says each sending IP and DKIM domain has its own reputation and recommends keeping bulk or marketing mail apart from user and transactional mail. [5] [3]
But do not treat the subdomain as a firewall. Mailbox providers still see the organizational domain, Google counts your volume across it, and a strict DMARC policy on the root can apply to the subdomain. The benefit is organization and clarity: marketing mail has its own name, its own records and its own reports.
What a subdomain separates, and what it does not
Google's sender guidelines FAQ says that when it calculates the bulk-sender threshold, close to 5,000 messages a day to personal Gmail accounts, it counts all messages sent from the same primary domain. Its example: 2,500 messages from solarmora.com plus 2,500 from promotions.solarmora.com makes the sender a bulk sender, because all 5,000 came from the same primary domain. It also says bulk status is permanent once assigned. [2]
Google's FAQ describes alignment in terms of the organizational domain: the organizational domain in the From header must align with either the SPF or the DKIM organizational domain. [2] Google's sender guidelines page does not say how far reputation is kept apart between a subdomain and its parent. [1] Yahoo's best-practices page does not mention subdomains, but it says each IP and DKIM domain has a reputation and recommends separating mail types by sending IP or DKIM domain, which a subdomain signed with its own DKIM domain can help with. [3] Treat any separation as partial.
| Question | Root domain ([email protected]) | Subdomain ([email protected]) |
|---|---|---|
| Counts toward Gmail's bulk threshold (close to 5,000 a day) for yourdomain.com | Yes [2] | Yes, combined with the root [2] |
| Can align for DMARC with DKIM signed as yourdomain.com | Yes | Yes in relaxed mode; no in strict mode [4] |
| DMARC policy if no record at the subdomain | The root's p tag | The root's sp tag, or p if sp is absent [4] |
| Keeps newsletter records and reports distinct from staff email | No | Yes |
| Reputation separated from the root | Not applicable | Partly: Yahoo says each DKIM domain has its own reputation [3]; Google's pages do not address it [1]; beehiiv says it protects the main domain [5] |
How alignment works with a subdomain
DMARC passes when SPF or DKIM passes for a domain that aligns with the visible From domain. Google and Yahoo both require bulk senders to align the From domain with either the SPF or the DKIM domain. [1] [3]
RFC 9989, the current DMARC standard published in 2026 and obsoleting RFC 7489, defines two alignment modes. Relaxed alignment means the two domains share the same organizational domain; strict alignment means they are identical. The adkim and aspf tags set the mode for DKIM and SPF, and both default to relaxed. [4] So a newsletter From news.yourdomain.com with a DKIM signature for news.yourdomain.com aligns in either mode, while a signature for yourdomain.com aligns only in relaxed mode.
RFC 9989 also changed how the organizational domain is found, using a DNS Tree Walk that queries _dmarc records up the domain's labels, and it removed the pct tag in favor of a t tag for test mode. [4] If your DMARC tool still writes pct, check what it is generating.
Which DMARC policy applies to the subdomain
When a message arrives From news.yourdomain.com, the receiver first looks for a record at _dmarc.news.yourdomain.com. If none exists, it walks up to the parent and uses the organizational domain's record. There, the sp tag sets the policy for existing subdomains; if sp is absent, the p tag applies to subdomains too. A separate np tag covers subdomains that do not exist. [4]
This is where many setups go wrong. If the root domain is at p=reject because staff email is fully authenticated, a newsletter subdomain that is not yet authenticated inherits reject and its mail can be refused. Either finish authenticating the subdomain before the first send, or set sp to a gentler policy while you test.
| Records you publish | Policy applied to news.yourdomain.com |
|---|---|
| Only _dmarc.yourdomain.com with p=reject | reject [4] |
| _dmarc.yourdomain.com with p=reject; sp=none | none [4] |
| A record at _dmarc.news.yourdomain.com with p=quarantine | quarantine; the subdomain's own record wins [4] |
| No DMARC records at all | No DMARC policy; does not meet Google's requirement that bulk senders set up DMARC [1] |
Setup steps in MailerLite with Namecheap DNS
MailerLite requires domain authentication when you send from a custom domain; new accounts can send their first campaigns unauthenticated only during the 14-day trial. [6] Its article does not discuss subdomains specifically, so if the form does not accept your subdomain sender address, contact MailerLite support before changing DNS.
- In MailerLite, open Account settings, then the Domains tab, click Add domain, enter the sender address (for example [email protected]) and click Save. [6]
- Use automatic setup if your DNS provider is a MailerLite partner; otherwise choose the option labelled Or manually authenticate your domain. [6]
- MailerLite shows three records: DKIM as a CNAME, SPF as a TXT, and a domain verification TXT. Their names and values cannot be changed in MailerLite, so they must match exactly. [6]
- In Namecheap, open Domain List, Manage, Advanced DNS, and add each record. In Host, enter only what comes before yourdomain.com; for a subdomain record that includes the subdomain part, such as the portion ending in news. [7]
- Leave TTL on Automatic; Namecheap's default is 30 minutes. [7]
- Back in MailerLite's Domains tab, click Authenticate, then the Check DNS Records button. MailerLite says updates can take up to 24 hours but usually finish within minutes. [6]
- Add or review DMARC as described above, then send a test to a Gmail address and confirm DKIM and SPF pass and align.
Worked example: a shop with invoices and a weekly newsletter
A small online shop sends order confirmations and staff email from yourdomain.com, about 400 messages a day, with DMARC at p=reject. It is launching a weekly newsletter to 6,000 subscribers, about 4,800 of them on personal Gmail addresses, and about 300 of its daily order and staff messages also go to Gmail users.
Using news.yourdomain.com keeps the newsletter's DKIM records and DMARC reports separate from the shop's mail, which makes problems easier to trace. It does not avoid Gmail's bulk rules: on newsletter day, 4,800 newsletter messages plus about 300 order messages to Gmail come to roughly 5,100 from the same primary domain, which meets the threshold, and Google says bulk status stays once assigned. [2] The shop should meet the bulk requirements from the first send, including SPF, DKIM and DMARC, From alignment, one-click unsubscribe, and spam rates below 0.30%, with Google recommending under 0.10%. [1]
Because the root policy is reject and has no sp tag, the newsletter subdomain inherits reject. [4] The owner authenticates news.yourdomain.com in MailerLite, confirms a test passes, and only then schedules the first issue.
Who should use a subdomain, and who should skip it
- Use one: a new newsletter on a domain that also carries staff, sales or billing email.
- Use one: anyone who wants marketing DMARC reports and DNS records kept separate from company mail.
- Skip it: an existing newsletter with a healthy sending history on its current domain; beehiiv advises keeping the same sending domain when migrating. [5]
- Skip it: a one-person publication whose domain sends nothing but the newsletter; a subdomain adds records without separating anything.
- Either way: do not expect it to dodge bulk-sender rules or a weak list. Volume and complaints count against the primary domain. [2]
Questions before you decide
Does a subdomain avoid Gmail's bulk sender rules?
No. Google's sender FAQ says messages sent from the same primary domain count toward the 5,000 limit, with an example where 2,500 messages from a domain and 2,500 from its promotions subdomain make the sender a bulk sender.
Will news.example.com pass DMARC if DKIM signs as example.com?
Under relaxed alignment, yes: both share the organizational domain example.com. Relaxed is the default for both adkim and aspf in RFC 9989. Under strict alignment, the domains must match exactly.
Do I need a separate DMARC record for the subdomain?
Not necessarily. If no record exists at _dmarc.news.example.com, DMARC discovery walks up to the organizational domain's record and applies its sp tag, or its p tag if sp is absent. Publish a subdomain record only when you want a different policy.
Should I move an existing newsletter to a new subdomain?
beehiiv's guidance for people migrating platforms is to keep the same email domain or subdomain you already send from, to protect your sender reputation. A switch starts the new name without history.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Google: Email sender guidelines Accessed 29 Oct 2026
- Google: Email sender guidelines FAQ Accessed 29 Oct 2026
- Yahoo Sender Hub: Best practices Accessed 29 Oct 2026
- RFC 9989: Domain-based Message Authentication, Reporting, and Conformance (DMARC) Accessed 29 Oct 2026
- beehiiv Support: How to use a custom domain for your publication Accessed 29 Oct 2026
- MailerLite Help: How to verify and authenticate your domain Accessed 29 Oct 2026
- Namecheap Knowledgebase: How do I set up host records for a domain? Accessed 29 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.