SPF, DKIM and DMARC for MailerSend

Short answer: MailerSend mail passes Gmail, Yahoo and Microsoft checks when you turn on DKIM with your own domain, add include:_spf.mailersend.net to your one SPF record and publish a DMARC record at _dmarc (start with p=none). The exact records and clicks are below.

SPF	TXT at `@`	v=spf1 include:_spf.mailersend.net ~all MailerSend's verification asks for its SPF value in your root SPF record: add `include:_spf.mailersend.net` to your one existing record instead of creating a second one. SPF alignment for DMARC comes from the `mta` return-path record below.
DKIM	CNAME / TXT	Copy the DKIM records exactly as MailerSend lists them for your domain. New domains get two CNAME records; domains added earlier use one CNAME `mlsend2._domainkey` → `mlsend2._domainkey.mailersend.net`, and the oldest a TXT key at `mlsend._domainkey`. Return-path: a CNAME at `mta` → `mailersend.net`.
DMARC	TXT at `_dmarc`	v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com Start with `p=none` and a mailbox you read, or a free report address that turns the reports into a dashboard; build your own.

Step by step

In MailerSend open Email → Domains → Add domain and enter the domain you send from.
At your DNS host add the records from the domain's verification page: the SPF value (merged into your one SPF record), both DKIM CNAMEs, and the return-path CNAME mta → mailersend.net.
Optional: switch on Custom DNS records for tracking and add the tracking CNAME it shows (default email subdomain).
Tick I have added DNS records and click Finish verification. It usually takes a few minutes; after 48 hours, check the values and click Re-check now.
No DMARC record yet? Publish one at _dmarc on your root domain with p=none and watch the reports before enforcing.

Mistakes that break it

Values are case-sensitive: paste them exactly, and keep a single SPF record (TXT starting with v=spf1) on the root.
On Wix, add the SPF value as a normal TXT record, not in Wix's SPF section, or MailerSend won't see it.
Already using mta for something else? Click Edit on the Domains page to pick another return-path name, then add that CNAME instead.
Keep your existing DKIM records until the new ones verify.
On Cloudflare, set the CNAMEs to DNS only (grey cloud): proxied records never verify.

Check that it worked

After the fix, send a test email to see SPF, DKIM and DMARC pass on a real message, then keep an eye on it: free DMARC monitoring shows every service that sends mail as your domain and which ones fail, in plain English.

Rather not touch DNS? I set up SPF, DKIM and DMARC without breaking your other senders, with a before/after report.

Get it fixed on Fiverr

Prefer to do it yourself? Get the step-by-step Fix Kit ($15) – 28-page guide, checklist, 20+ providers.

Did this fix it?

Other setup guides

Google Workspace Microsoft 365 Zoho Mail Hostinger Email Titan Email GoDaddy email (Microsoft 365 and Professional Email)Namecheap Private Email IONOS Mail Proton Mail Cloudflare Email Routing Mailchimp SendGrid Amazon SES Shopify Email Klaviyo HubSpot Brevo Mailgun Postmark Zendesk Constant Contact MailerLite Kit (ConvertKit)ActiveCampaign Freshdesk Intercom Zoho Campaigns Help Scout Squarespace Email Campaigns Mailjet Campaign Monitor Salesforce Account Engagement (Pardot)Wix Email Marketing (Ascend)Gorgias SparkPost Resend Elastic Email