Email senders
MailerLite DMARC setup: SPF, DKIM and alignment
How MailerLite signs your mail, which DNS records it needs for DMARC and what breaks SPF alignment or your other senders during setup.
SPF include for MailerLite
include:_spf.mlsend.com
Add this to the SPF record you already have. A domain must publish only one SPF record, so never create a second one.
- DNS lookups it uses
- 1 of 10
- Needed in your SPF record
- Yes
- Last checked in DNS
- 2026-11-11
DKIM for MailerLite
- Selectors
- litesrv
- How to enable it
- One CNAME record on your domain, litesrv._domainkey, pointing to litesrv._domainkey.mlsend.com. MailerLite also needs an SPF TXT record and a verification TXT record before it marks the domain as authenticated.
MailerLite signs with your domain
Envelope-from and SPF alignment
SPF counts for DMARC only when this domain matches the domain in your From address. If it is MailerLite’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.
- Envelope-from (Return-Path)
- MailerLite does not document this.
Sending ranges of MailerLite
Use these to recognize MailerLite in your reports. They change over time, so do not copy them into your SPF record.
- 185.225.161.0/24
- 185.249.220.0/24
Updated 2026-11-15
Does your domain authorize MailerLite?
Enter your domain. The SPF Checker reads your record and names the senders it authorizes.
MailerLite documentation
- MailerLite: Domain authentication
- checked 2026-11-09
- MailerLite: How to authenticate a domain with GoDaddy
- checked 2026-11-09
- MailerLite: How to authenticate a domain with Cloudflare
- checked 2026-11-09
- MailerLite: How to merge SPF records
- checked 2026-11-09
- MailerLite: Troubleshooting domain authentication
- checked 2026-11-09
- MailerLite: How to align your domain
- checked 2026-11-09
- MailerLite: How domain alignment improves email deliverability
- checked 2026-11-09
- MailerLite: The basics of DMARC
- checked 2026-11-09
How it authenticates
MailerLite DMARC setup starts on the Domains page, where you add the domain you send from. MailerLite then asks for three DNS records: a DKIM CNAME, an SPF TXT record and a verification TXT record.
DKIM (DomainKeys Identified Mail) signs each message. The CNAME named litesrv._domainkey sits under your domain and points to MailerLite, so the signature can align with your From address.
SPF (Sender Policy Framework) lists the servers allowed to send for you. MailerLite will not authenticate the domain without this record, even though DMARC can pass on an aligned DKIM signature alone.
SPF alignment is a separate step. The Domain alignment feature adds A, MX and TXT records on a subdomain you choose, such as mail.example.com. MailerLite does not publish its default bounce domain, also called the envelope-from, so read the SPF domain in your reports before you count on DMARC alignment through SPF.
What to watch for
Some MailerLite host guides tell you to delete other SPF records because its value covers your services. That holds only for a merged value. Click Check DNS records and confirm the new value lists your other senders before you remove anything. A domain can publish only one SPF record.
The DKIM CNAME needs care on some hosts. Add a trailing period if yours appends the domain to the value. On Cloudflare, keep the proxy off.
Use the alignment subdomain for this purpose only, and keep your From address on the main domain. Reusing it for landing pages causes conflicts. Turning alignment off breaks the links in campaigns you already sent.
With the aspf tag set to aspf=s, mail.example.com no longer matches example.com, so DMARC depends on DKIM.
DMARC is a separate TXT at _dmarc.example.com. Preserve an existing policy and report addresses. Otherwise, start with p=none and a monitored rua mailbox. Confirm aligned MailerLite DKIM in reports before you tighten the policy.