To let Mailgun send as you, add include:mailgun.org to your SPF.
On the sending domain you added in Mailgun (that can be your root or a subdomain you send from). Mailgun’s control panel (Domain Verification & DNS) shows the exact records for the domain you added. Measured on 4 Nov 2026, the include costs 5 of your 10 SPF lookups, leaving 5 for everything else.
- Include
- mailgun.org
- Vendor’s record
- v=spf1 include:mailgun.org ~all
- Where it goes
- Your domain’s SPF record (@)
- Needed on your root?
- Yes, if you send through it from your domain
- Lookups (measured)
- 5 of 10
- Ranges published
- 22 ip4 · 0 ip6
- Category
- Transactional email
What include:mailgun.org expands to live, 4 Nov 2026
v=spf1 include:_spf.mailgun.org include:_spf.eu.mailgun.org -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:mailgun.org ~all
DKIM for Mailgun
A TXT key Mailgun generates for the sending domain (shown in Domain Verification & DNS).
How it affects DMARC
DMARC passes when SPF or DKIM passes for a domain aligned with your From address. With Mailgun 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.
Other transactional email services
Sources
- Mailgun: Verify your domain · checked 5 Oct 2026
- RFC 7208 §4.6.4: DNS lookup limits · checked 5 Oct 2026
peekip isn’t affiliated with Mailgun; follow the vendor’s own setup page, which shows the exact values for your account.