Skip to content
DMARC Pulse

Email senders

MailerSend DMARC setup: SPF, DKIM and alignment

How MailerSend signs your mail, which DNS records make DMARC pass, and what breaks alignment when you send through a sender identity.

SPF include for MailerSend

Resolves in DNS
Add to your SPF recordTXT
include:_spf.mailersend.net

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 MailerSend

Selectors
ms1 ms2
How to enable it
Publish both CNAME records, ms1._domainkey and ms2._domainkey, pointing to MailerSend-hosted 2048-bit keys. Both are required for domain verification.

MailerSend signs with your domain

The signature carries your domain in d=, so DKIM can align with your From address and pass DMARC on its own.

Envelope-from and SPF alignment

SPF counts for DMARC only when this domain matches the domain in your From address. If it is MailerSend’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.

Envelope-from (Return-Path)
mta.yourdomain.tld by default, a subdomain you can change on the Domains page

Sending ranges of MailerSend

Use these to recognize MailerSend in your reports. They change over time, so do not copy them into your SPF record.

1 of 1
  • 212.11.79.0/24

Updated 2026-11-15

Does your domain authorize MailerSend?

Enter your domain. The SPF Checker reads your record and names the senders it authorizes.

MailerSend documentation

How it authenticates

MailerSend DMARC setup starts with a verified sending domain. When you add the domain, MailerSend generates the DNS records for it, and you publish four of them.

The SPF record is a TXT record on the domain itself. SPF (Sender Policy Framework) lists the servers allowed to send for you. MailerSend shows the value already merged with any SPF record you have, so copy it as displayed.

Two CNAME records named ms1._domainkey and ms2._domainkey point to the DKIM keys MailerSend hosts. DKIM (DomainKeys Identified Mail) signs each message. These names sit under your domain, so the signature can align with your From address.

The last CNAME sets the Return-Path, the address that receives bounces, also called the envelope-from. It defaults to mta.example.com and points to mailersend.net. You can pick another subdomain on the Domains page.

DMARC needs one aligned pass. The DKIM pair can provide it alone, and the Return-Path adds a second route through DMARC alignment.

What to watch for

A sender identity confirms one client's address by email and sends through your own authenticated domain, not the client's. MailerSend says SPF and DKIM alignment cannot be achieved that way, and mail may be blocked when the client's domain publishes p=reject. Verify the client's domain instead.

Strict mode changes the Return-Path result. With the aspf tag set to aspf=s, mta.example.com no longer matches example.com, so DMARC depends on DKIM alone.

Publish both DKIM records, since one is not enough for the domain to verify. Domains verified with the older single record need the two new ones before 1 February 2027, and you can leave the old record in place until then.

Keep one SPF record: duplicates block domain authentication. Check it with the SPF checker. DMARC is separate at _dmarc.example.com. Preserve existing DMARC and report addresses. For a first policy, monitor at p=none before you tighten the policy.

Check it now

Find and validate DKIM keys

Frequently asked questions

Which DKIM selectors does MailerSend use?
ms1 and ms2. You publish them as two CNAME records under your domain, and the domain will not verify if either one is missing.
Do I need SPF for DMARC to pass with MailerSend?
DMARC needs one aligned pass, and DKIM on your verified domain can provide it. MailerSend still lists SPF among the records it checks when it verifies the domain, so publish it.
Does the default MailerSend Return-Path align with DMARC?
Yes under relaxed alignment, which is the default, because mta.example.com shares its organizational domain with example.com. Under strict alignment, set with aspf=s, it does not match.
Why does my MailerSend domain stay unverified?
MailerSend names two frequent causes: more than one SPF record on the domain, or only one of the two DKIM CNAME records. If the records look correct after 48 hours, it asks you to contact support.
What changes for older MailerSend domains in 2027?
Support for the older single DKIM record ends on 1 February 2027. If your domain was verified that way, publish the ms1 and ms2 records before then. You do not need to remove the old record in the meantime.

Sources consulted

Related pages

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.