To let GoDaddy email and hosting send as you, add include:secureserver.net to your SPF.
On the domain (GoDaddy’s article covers its email, Linux hosting, VPS and Media Temple mail). GoDaddy says mail from these products needs this include for SPF to work. Measured on 5 Nov 2026, the include costs 3 of your 10 SPF lookups, leaving 7 for everything else.
- Include
- secureserver.net
- Vendor’s record
- v=spf1 include:secureserver.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)
- 3 of 10
- Ranges published
- 39 ip4 · 5 ip6
- Category
- Mailbox provider
What include:secureserver.net expands to live, 5 Nov 2026
v=spf1 include:spf-0.secureserver.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:secureserver.net ~all
How it affects DMARC
DMARC passes when SPF or DKIM passes for a domain aligned with your From address. With GoDaddy email and hosting 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 mailbox provider services
Sources
- GoDaddy: Add an SPF record · checked 5 Oct 2026
- RFC 7208 §4.6.4: DNS lookup limits · checked 5 Oct 2026
peekip isn’t affiliated with GoDaddy email and hosting; follow the vendor’s own setup page, which shows the exact values for your account.