To let Marketo Engage (Adobe) send as you, add include:mktomail.com to your SPF.
On your From domain; if you already have SPF, add include:mktomail.com to it. Adobe’s setup steps list it for sending from your own domain. Measured on 5 Nov 2026, the include costs 1 of your 10 SPF lookups, leaving 9 for everything else.
- Include
- mktomail.com
- Vendor’s record
- v=spf1 mx ip4:[Corporate IP(s)] include:mktomail.com ~all
- Where it goes
- Your domain’s SPF record (@)
- Needed on your root?
- Yes, if you send through it from your domain
- Lookups (measured)
- 1 of 10
- Ranges published
- 12 ip4 · 0 ip6
- Category
- Marketing automation
What include:mktomail.com expands to live, 5 Nov 2026
v=spf1 ip4:199.15.212.0/22 ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24 ip4:72.32.243.0/24 ip4:94.236.119.0/26 ip4:37.188.97.188/32 ip4:185.28.196.0/22 ip4:192.28.128.0/18 ip4:103.237.104.0/22 ip4:130.248.172.0/24 ip4:130.248.173.0/24 ~all
Counted as RFC 7208 §4.6.4 does: the include itself plus every nested include, a, mx, ptr, exists and redirect. Includes can change at any time; this page re-measures daily.
Adding it next to another service
A domain has exactly one SPF record, so add the include to the record you already have. With Google Workspace, for example:
v=spf1 include:_spf.google.com include:mktomail.com ~all
How it affects DMARC
DMARC passes when SPF or DKIM passes for a domain aligned with your From address. With Marketo Engage (Adobe) sending from your domain, its include lets SPF pass and align; DKIM signing with your domain gives you a second, forwarding-proof way to pass.
Sources
- Adobe Experience League: Marketo setup steps · checked 5 Oct 2026
- RFC 7208 §4.6.4: DNS lookup limits · checked 5 Oct 2026
peekip isn’t affiliated with Marketo Engage; follow the vendor’s own setup page, which shows the exact values for your account.