The DNS records
MailerLite's Cloudflare and troubleshooting articles give these DKIM values. Copy the SPF and verification values from your own account, because the verification value is unique to it.
DKIM selector litesrv
Type: CNAME · Host: litesrv._domainkey
litesrv._domainkey.mlsend.com
Some hosts want a trailing period (litesrv._domainkey.mlsend.com.) so they don't append your domain to the target.
SPF record (on the same host as any existing SPF record)
Type: TXT · Host: @
v=spf1 a mx include:_spf.mlsend.com ~all
MailerLite's example. Merge the include into an existing record instead of adding a second one.
Domain verification
Type: TXT · Host: @
<verification value shown in MailerLite>
Set it up and turn on signing
- Go to Account settings, select the Domains tab and click + Add sending domain. Enter the address you send from and click Save.
- If your DNS provider is a MailerLite partner, use the automatic option. Otherwise choose Authenticate manually.
- Create the CNAME with the name
litesrv._domainkeyonly; MailerLite says adding your domain to the end of the name isn't necessary. At Cloudflare, set the record to DNS only. - Add the SPF and verification TXT records, leaving TTL at the default.
- Back in MailerLite, open the … menu next to the domain and click Check DNS records.
DMARC alignment
The litesrv key lets MailerLite put your domain in the DKIM signature, so the DKIM result matches the domain in your From address and DMARC can pass on it. MailerLite requires this authentication before you send from a custom domain once the 14-day trial ends. Its help articles don't describe a custom return path, so plan on DKIM as the aligned result.
Key length and rotation
Because the name is a CNAME into mlsend.com, the public key stays in MailerLite's zone and MailerLite can replace it without asking you to edit DNS. The selector litesrv is the same for every account, which is why the record value never changes. MailerLite doesn't publish its key length or a rotation schedule in these articles.
Common mistakes
- A doubled name such as
litesrv._domainkey.example.com.example.com. Enter onlylitesrv._domainkeywhen your host adds the domain. - The target rewritten to
litesrv._domainkey.mlsend.com.example.com. End the value with a period if your host appends the zone. - A proxied record at Cloudflare. MailerLite asks for proxy status off (DNS only).
- Records in a zone that isn't live. Check that your nameservers point to the provider where you edited DNS.
Check your MailerLite DKIM key
The selector is filled in for you; add your domain. Free, reads public DNS only.
Frequently asked questions
What is MailerLite's DKIM selector?
litesrv. The record is a CNAME named litesrv._domainkey on your sending domain, pointing to litesrv._domainkey.mlsend.com. Check it with our DKIM Checker using the selector litesrv.
How long does MailerLite take to verify DKIM?
MailerLite says approval often takes minutes, propagation is usually complete within 24 hours, and it can take up to 72. Click Check DNS records again once the CNAME resolves.
Why does MailerLite say my CNAME value is wrong?
Many DNS hosts silently append your domain to the target. MailerLite's fix is to enter the value with a trailing period, litesrv._domainkey.mlsend.com., so the host stores it exactly.
Sources
- MailerLite Help: Domain authentication
- MailerLite Help: How to authenticate a domain with Cloudflare
- MailerLite Help: Troubleshooting domain authentication
- RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
- RFC 8301: Cryptographic Algorithm and Key Usage Update to DKIM
Checked against MailerLite's documentation on November 3, 2026. Providers change their setup screens; if yours differs, follow the values your admin console shows.
DKIM records for other providers
- Microsoft 365CNAME: selector1, selector2
- Google WorkspaceTXT: google
- Zoho MailTXT: you choose (e.g. zoho)
- GoDaddyCNAME: secureserver1, secureserver2
- FastmailCNAME: fm1, fm2, fm3
- Proton MailCNAME: protonmail, protonmail2, protonmail3
- iCloud MailCNAME: sig1
- HostingerCNAME: hostingermail-a, hostingermail-b, hostingermail-c
- Private EmailTXT: privateemail, default (bought before 2 June 2026)
- IONOSCNAME: s1-ionos, s2-ionos, s42582890
- Rackspace EmailTXT: shown in the Cloud Office Control Panel
- Amazon SESCNAME or TXT: <token1>, <token2>, <token3> (Easy DKIM), your own (BYODKIM)
- SendGridCNAME or TXT: s1, s2
- MailgunTXT or CNAME: assigned by Mailgun (e.g. pic, krs, smtp), pdk1, pdk2 (Automatic Sender Security)
- PostmarkTXT: <timestamp>pm (e.g. 20131031155228pm)
- MailjetTXT: mailjet
- SMTP2GOCNAME: shown in SMTP2GO for your domain
- SparkPostTXT: scph<number> (generated, e.g. scph0316), your own (API)
- Elastic EmailTXT: api
- ResendTXT: resend
- MailerSendCNAME: ms1, ms2
- MailchimpCNAME: k2 and a second CNAME (Marketing), mte1, mte2 (Transactional)
- BrevoTXT or CNAME: mail (TXT), 2 CNAMEs from your account
- HubSpotCNAME: hs1-<number>, hs2-<number>
- KlaviyoCNAME: km1, km2 (marketing), kt1, kt2 (transactional), ks1, ks2 (service)
- ActiveCampaignCNAME: acdkim1, acdkim2
- Constant ContactCNAME or TXT: ctct1, ctct2 (CNAME), generated per key (TXT)
- SquarespaceCNAME: squarespace
- Dynamics 365 Customer InsightsCNAME: CNAME1 and CNAME2 from the wizard (e.g. namkey1)
- Campaign MonitorTXT: cm, your own (existing keys)
- KitCNAME: cka
- MarketoTXT: chosen by you in Marketo
- Account Engagement (Pardot)TXT: shown in Expected DNS Entries
- Customer.ioTXT: cio
- Zoho CampaignsTXT: numbered per account (e.g. 2232)
- SalesforceCNAME: you choose two (e.g. example-sf-a, example-sf-b)
- ZendeskCNAME: zendesk1, zendesk2
- Help ScoutCNAME: strong1, strong2
- IntercomCNAME: intercom
- OdooCNAME: odoo
Compare every provider's selectors in one table · SPF record for MailerLite
Related guides
How to find a domain's DKIM selector, and check its key
Find a DKIM selector from the s= tag in an email header, see the selectors Microsoft 365, Google Workspace and common senders use, then check the key.
8 min read SPF, DKIM & DMARCHow to rotate DKIM keys without breaking email
How often to rotate DKIM keys, which key length to use, how to name selectors, and how to rotate in Microsoft 365, Google Workspace and on your own server.
9 min read SPF, DKIM & DMARCDKIM "body hash did not verify" and other DKIM failures: causes and fixes
Fix DKIM failures: body hash did not verify, signature did not verify, no key for signature and short keys. Causes from mailing lists to broken TXT records.
9 min readLast updated