include:_spf.mailersend.net lists MailerSend’s sending servers. MailerSend asks for it on your domain together with a return-path CNAME — mta.yourdomain.com pointing to mailersend.net — and checks both when it verifies the domain. SPF for its mail is checked at that return-path, which aligns with your domain.
v=spf1 include:_spf.mailersend.net ~all
| Belongs to | MailerSend — email API and SMTP relay |
| Needed on your domain? | The service asks for it — though by default SPF checks a different domain for its mail |
What it costs, and is it in your record?
We measure include:_spf.mailersend.net as the page opens. Enter a domain: we read its SPF record, follow every include and say whether MailerSend’s is there and what it costs.
What it covers
MailerSend’s email API and SMTP relay.
Do you need it?
MailerSend’s verification checks the SPF include on your domain and the return-path CNAME separately, so it asks for both.
The return-path — “The address where bounces and other email feedback are sent to” — is mta.yourdomain.com by default, a CNAME to mailersend.net, whose own SPF record then covers MailerSend’s mail. MailerSend does not say whether the root include is still needed once that CNAME is in place.
Common mistakes
- “There cannot be more than 1 SPF record in a DNS zone” — the domain will not verify.
- On Wix, adding it in Wix’s separate SPF section instead of as a TXT record.
- spf.mailersend.net — without the underscore — does not exist.
Sources
Checked on 26 September 2026 against these official sources:
- How to Verify and Authenticate a Sending Domain — mailersend.com
- Merge Multiple SPF Records — mailersend.com
- Domains — MailerSend Developers — developers.mailersend.com