How to set up DMARC/DKIM/SPF for MailerSend

Updated on 24 Oct 2026: We updated the MailerSend DKIM migration deadline and clarified SPF matching and DMARC enforcement without pct-based staging.
MailerSend authentication needs one SPF TXT record, two DKIM CNAME records, and a Return-Path CNAME copied from the domain verification screen. DMARC is a separate TXT record at _dmarc. Add your domain, publish the authentication records, configure DMARC, and then test a fresh message.
Use the values shown in MailerSend
The SPF include is commonly _spf.mailersend.net and the Return-Path target is mailersend.net. Copy the current Name and Value fields for every record, including both DKIM CNAMEs, from MailerSend instead of guessing them.
Add your domain
Add the domain used after the @ in your visible From address. MailerSend will not send production mail for that domain until its required DNS records verify.
- Open Domains: In MailerSend, go to Email > Domains and select Add domain.
- Enter the sender domain: Use example.com when mail comes from billing@example.com, or use a dedicated subdomain when that is your sending design.
- Choose a connection method: Continue with automatic authentication when your DNS provider is supported, or close the connection prompt to configure DNS manually.
- Copy every record: For manual setup, copy the SPF row, both DKIM rows, and the Return-Path row exactly as displayed.
- Publish in authoritative DNS: Add the records where the domain's nameservers are hosted, not automatically at the registrar.
- Finish verification: Select I have added DNS records, then Finish verification. Use Re-check now after correcting a failed record.

MailerSend Add domain dialog with example.com entered
|
|
|
|
|---|---|---|---|
SPF | TXT | @ | Authorize senders |
DKIM | CNAME | ms1._domainkey, ms2._domainkey | Publish signing keys |
Return-Path | CNAME | mta | Support SPF alignment |
DMARC | TXT | _dmarc | Set policy and reports |
Records shown during manual MailerSend domain authentication
MailerSend documents the current automatic and manual flow in its domain authentication guide. Use the displayed DNS values when they differ from an example on this page.
Set up SPF
MailerSend supports Return-Path alignment. Publish its SPF authorization and Return-Path CNAME, while keeping exactly one SPF record at each hostname.
- Check existing SPF: Look for a TXT value beginning with v=spf1 at the exact host MailerSend names.
- Create or merge: If no SPF record exists, add MailerSend's value. Otherwise, check that its suggested merged value preserves every existing authorized sender, then update the existing record. Do not add the MailerSend include twice.
- Avoid duplicates: Never publish a second v=spf1 TXT record at the same host. Multiple SPF records cause PermError.
- Delegate Return-Path: Publish the MailerSend CNAME, commonly mta pointing to mailersend.net. Use the custom Name and Value shown in your account. Do not publish a TXT or MX record at the same hostname as this CNAME.
- Stay within the SPF lookup limit: SPF permits at most ten DNS lookup terms during evaluation, including nested records. Count include, a, mx, ptr, exists, and the redirect modifier; exceeding ten causes PermError.
MailerSend-only SPF exampleDNS
v=spf1 include:_spf.mailersend.net ~all
Merged SPF patternDNS
v=spf1 include:_spf.mailersend.net include:spf.example.net ~all
The merged pattern is only a structure example. Replace the second include with a sender already authorized by your real SPF record, and preserve the intended final qualifier.
SPF checker
Find SPF syntax issues, lookup limits, and weak records.
?/16tests passed
Run the checker against the domain or subdomain that hosts the SPF record. A syntactic pass is not enough, so confirm that the evaluated record includes MailerSend and stays within the ten-lookup limit.
SPF passing does not guarantee DMARC
DMARC needs SPF or DKIM to both authenticate and match the visible From domain under DMARC rules. The MailerSend Return-Path CNAME helps SPF meet that requirement.

MailerSend SPF TXT and custom Return-Path CNAME records
Set up DKIM
MailerSend provides two CNAME records for 2048-bit DKIM keys. Both records must resolve before MailerSend will mark the sending domain as authenticated. MailerSend explains the deadline in its DKIM migration notice.
- Copy DKIM one: Copy the first DKIM CNAME Name and Value from the MailerSend DNS records panel.
- Copy DKIM two: Repeat for the second DKIM CNAME. Publishing only one key leaves verification incomplete.
- Enter hosts carefully: If your DNS provider appends example.com automatically, enter only the host portion supplied by MailerSend.
- Disable proxying: Keep email authentication CNAME records in DNS-only mode when the DNS provider offers HTTP proxying.
- Retain older keys: MailerSend retires legacy DKIM TXT support on February 1, 2027. Migrate to both new CNAMEs before that deadline; older single-CNAME setups should also upgrade. Keep existing keys until the new records verify and old signatures have cleared delivery queues.

MailerSend DNS verification showing ms1 and ms2 DKIM CNAME records
Query each full selector hostname after publishing. A valid result returns the exact CNAME target displayed by MailerSend, without an unexpected extra copy of the root domain.
Check both DKIM CNAME recordsBASH
dig +short CNAME ms1._domainkey.example.com dig +short CNAME ms2._domainkey.example.com
After DNS resolves, send a fresh message and inspect the receiving server's Authentication-Results header. DKIM must show pass, and its d= signing domain must match the visible From domain under the DMARC record's adkim setting. The selector s= identifies which key signed the message; both keys do not need to sign each message.
Check Return-Path and DMARC alignment
SPF checks the SMTP MAIL FROM (envelope-from) domain, shown in Return-Path after delivery. It does not check Reply-To. Publishing MailerSend's root-domain SPF include does not replace its custom Return-Path CNAME.
Illustrative headers with relaxed SPF matchingtext
From: Billing <billing@example.com> Return-Path: <bounce-id@mta.example.com> Authentication-Results: receiver.example; spf=pass smtp.mailfrom=mta.example.com; dkim=pass header.d=example.com header.s=ms1; dmarc=pass header.from=example.com
With the default aspf=r, mta.example.com and example.com share an organizational domain, so an SPF pass satisfies DMARC's SPF requirement. With aspf=s, these domains do not match. DMARC can still pass through DKIM when d=example.com passes and meets the adkim setting. Keep an existing strict policy unless its owner approves a change.
Set up DMARC
DMARC belongs at _dmarc on the visible From domain. It checks identifier alignment, publishes receiver handling policy, and requests aggregate reports.
- Check for an existing record: Query _dmarc.example.com before publishing anything. There must be only one DMARC policy record at that hostname, shared by all services sending with that From domain.
- Preserve enforcement: If the existing policy is quarantine or reject, keep it. Do not weaken a working policy just to add MailerSend.
- Start monitoring safely: When no DMARC record exists, begin with p=none and a monitored aggregate-report mailbox.
- Publish at _dmarc: Create one TXT record using the value below after replacing the example report address with a monitored mailbox or the reporting address supplied by Suped.
- Check matching modes: The default relaxed modes, aspf=r and adkim=r, allow an organizational-domain match. Check existing strict settings before changing them; the default mta Return-Path differs from the visible From domain.
Use the DMARC record generator when you need to add reporting addresses or policy controls without hand-editing tag syntax.
Initial DMARC recordDNS
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Publish the value as TXT at _dmarc. Some DNS panels require only _dmarc in the host field, while others require the full hostname. If rua points outside your organizational domain, the report destination's operator must publish the required external-report authorization in its DNS.
DMARC checker
Look up a domain's DMARC record and catch policy issues.
?/7tests passed
Check the exact visible From domain, including a sending subdomain when used, and verify any policy inherited from its parent domain. Do not use the mta Return-Path hostname for this check. Confirm the effective policy and aggregate-report destination.

MailerSend DNS panel showing a _dmarc TXT record with p=none
Verify authentication and troubleshoot DNS errors
Verification has two layers. First, MailerSend must see every required DNS record. Second, a delivered message must pass DMARC through SPF or DKIM with a domain that matches the visible From domain under the configured matching rules.
- Wait for DNS: Most changes appear within minutes, but resolver caches can keep old data for the record's prior TTL. MailerSend advises allowing up to 48 hours.
- Re-check in MailerSend: Open Email > Domains, select the domain, open DNS records, toggle the confirmation again, and select Re-check now.
- Send a new message: Do not inspect a message sent before the DNS change. Send a fresh transactional email through the verified MailerSend domain.
- Inspect Authentication-Results: Inspect the receiving server's Authentication-Results header, such as Gmail's Show original view. Look for dkim=pass, spf=pass, and dmarc=pass, then compare header.from, header.d, and smtp.mailfrom. DMARC requires one passing mechanism with a matching domain.
- Isolate the failed layer: A DNS verification failure points to record publication. A DMARC failure with SPF and DKIM passes points to domain mismatch.

MailerSend verification statuses for SPF, both DKIM records, and Return-Path
A verified badge confirms that MailerSend can resolve its required records. It does not prove that every message stream uses the expected From address or that downstream modifications preserve DKIM.
Test a real message sent by the same API or SMTP path used in production. That catches wrong sender domains, stale templates, forwarding changes, and Return-Path mismatches that a DNS-only check misses.
Email tester
Send a real email to this address. Suped shows a results button when the test is ready.
?/43tests passed
Send the requested test email through MailerSend. The resulting diagnosis should show SPF, DKIM, and DMARC results for the exact message received, along with the domains used by each mechanism. Forwarding often breaks SPF, so also test whether DKIM survives the forwarding paths your recipients use.
Fix the first failing dependency before retesting. For example, correct a missing DKIM CNAME before changing DMARC policy, because policy changes cannot repair a broken signature.
If DNS verification passes but messages still go to spam, investigate complaints and sending reputation separately. DMARC authenticates use of the From domain; it does not guarantee inbox placement. MailerSend manages reverse DNS for its sending IPs, so do not replace your existing inbound MX records to complete outbound authentication.
Healthy result
- SPF: One valid record authorizes MailerSend and stays within the ten-term DNS lookup limit.
- DKIM: Both CNAME records resolve and a fresh message has dkim=pass.
- DMARC: The message has dmarc=pass through at least one matching identifier.
What to fix
- SPF PermError: Merge duplicate records or reduce DNS-triggering mechanisms.
- DKIM missing: Correct host duplication, target text, record type, or DNS proxying.
- DMARC fail: Compare the visible From domain with DKIM d= and SPF mail-from domains.
Monitor MailerSend authentication with Suped
DNS checks prove the configuration at one moment. Suped, our DMARC reporting and email authentication platform, groups incoming reports by source so you can track MailerSend failures and investigate the affected domains. Aggregate reports usually arrive daily, so report-based alerts follow the reporting delay.
- Watch pass rates: Track SPF, DKIM, and DMARC results by source instead of relying on one test message.
- Set failure alerts: Notify the right owner when reported failures exceed the chosen threshold, and review unfamiliar sources before authorizing them.
- Separate sources: Keep MailerSend traffic distinct from other authorized senders before changing DNS or enforcement.
- Use guided fixes: Follow automated issue detection and source-specific repair steps instead of interpreting raw XML manually.
Connect the reporting destination
To use Suped for this workflow, add the domain and copy its supplied rua reporting address into your existing DMARC TXT record. Preserve the current policy and any reporting destinations you still need. Then review MailerSend traffic as reports arrive.
Use DMARC monitoring to establish a normal MailerSend baseline and catch regressions before a stricter policy turns them into rejected mail.
Secure your domain with p=reject
Move to p=reject only after legitimate senders pass DMARC consistently and remaining failures are understood. MailerSend should pass through its DKIM signature, its custom Return-Path, or both.
- Collect reports: Keep p=none long enough to observe routine traffic, billing runs, low-frequency automations, and forwarded messages.
- Inventory legitimate sources: Classify each source as authorized, unauthorized, or still under investigation. Do not approve a source only because its name looks familiar.
- Repair authentication: For MailerSend, confirm both DKIM records and the Return-Path CNAME, then retest a fresh production-path message.
- Apply quarantine: Change to p=quarantine after business owners confirm critical mail flows. Plan for the policy to apply to all DMARC-failing messages, and keep the previous record available for a controlled rollback.
- Review quarantine results: Review new aggregate reports and delivery errors before switching to reject. If failures affect legitimate mail, fix the sending configuration and retest it first.
- Move to reject: Set p=reject, keep aggregate reporting enabled, and continue watching for new senders or configuration drift.
- Cover subdomains: Set an explicit sp policy when subdomains need different treatment. A subdomain's own DMARC record takes precedence over an inherited sp policy. Test every active sending subdomain first.
Example enforcement stagesDNS
v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com v=DMARC1; p=reject; rua=mailto:dmarc@example.com
These examples are successive replacements for the same DMARC TXT record. Publish only one at a time and use your actual reporting address.
Suped's hosted DMARC supports policy staging without repeated direct TXT edits. Suped also keeps source identification, issue alerts, and remediation steps beside the policy workflow, which reduces the risk of enforcing against an overlooked sender.
Do not rely on pct for partial enforcement
RFC 9989 marks pct historic. Receivers using that specification ignore it, while older receivers handle it inconsistently. A record with p=quarantine; pct=10 can therefore affect all DMARC-failing messages.
MailerSend authentication FAQ
Use the live values in MailerSend's Domains area as the authority for your account. Reverse DNS names and known SPF includes help identify traffic, but they are not installation instructions by themselves.
A reverse DNS name under mailersend.net is a clue that a sending IP belongs to MailerSend. Confirm it against the DKIM signing domain and Return-Path in your reports, then cross-check the sending IP and your MailerSend activity log before classifying the source as authorized.
The SPF include _spf.mailersend.net is associated with MailerSend. Do not add it only because it appears in a report or lookup. Add the SPF value currently displayed for your verified domain in MailerSend, and merge it into the existing single SPF record when required.
Yes. A passing DKIM signature with a signing domain that matches under your adkim setting is enough for DMARC to pass. Investigate SPF failures separately: an incorrect Return-Path needs repair, while forwarding can break SPF even when the original MailerSend configuration is correct.
Common causes are duplicate SPF records, a host with the root domain appended twice, a proxied CNAME, an incorrect DKIM target, or only one of the two DKIM records. Correct the DNS, wait for caching, and select Re-check now. MailerSend advises allowing up to 48 hours.
No. Keep an existing quarantine or reject policy when it already works. For a new deployment, start at p=none, identify legitimate sources and repair authentication failures. Move to quarantine, review the results, and then consider p=reject. Do not depend on pct to limit enforcement.

