To let Forward Email send as you, add include:spf.forwardemail.net to your SPF.
On the root; Forward Email says to add include:_spf.google.com too if you send through Gmail “Send mail as”. It covers Forward Email’s outbound servers. Measured on 5 Nov 2026, the include costs 5 of your 10 SPF lookups, leaving 5 for everything else.
- Include
- spf.forwardemail.net
- Vendor’s record
- v=spf1 a include:spf.forwardemail.net -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
- 7 ip4 · 7 ip6
- Category
- Forwarding
What include:spf.forwardemail.net expands to live, 5 Nov 2026
v=spf1 a:forwardemail.net include:mx1.forwardemail.net include:mx2.forwardemail.net include:smtp.forwardemail.net -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:spf.forwardemail.net ~all
How it affects DMARC
DMARC passes when SPF or DKIM passes for a domain aligned with your From address. With Forward Email 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 forwarding services
Sources
- Forward Email: FAQ (DNS setup) · checked 5 Oct 2026
- RFC 7208 §4.6.4: DNS lookup limits · checked 5 Oct 2026
peekip isn’t affiliated with Forward Email; follow the vendor’s own setup page, which shows the exact values for your account.