GoDaddy
GoDaddy SPF record: how to add or edit it in DNS
Add or edit a GoDaddy SPF record: one TXT record at Name @, the Edit DNS path, what goes in Value and how to confirm it works.
Before you start
A GoDaddy SPF record is one TXT record with Name @ and a Value that starts with v=spf1. You add or edit it on the domain's Edit DNS screen.
Check three things first:
- You can sign in to the GoDaddy account that holds the domain. The record is created there. Microsoft 365, for one, has no portal for managing SPF.
- GoDaddy hosts the domain's DNS. Your registrar and your DNS host can be different companies. Enter the domain at ICANN Lookup (
lookup.icann.org) and read Nameservers under Domain Information. If they belong to another company, make this change there. - You know every service that sends as your domain. A domain can have only one SPF record, so they all share it.
Microsoft 365 uses this value. The Add DNS records page in its admin center shows the records to add:
v=spf1 include:spf.protection.outlook.com -all
Google Workspace uses this one:
v=spf1 include:_spf.google.com ~all
For a GoDaddy email plan, ask GoDaddy which value applies to your plan. For any other service, use the value in its documentation.
Steps
Microsoft documents this path in its GoDaddy article, and GoDaddy can rename these labels.
-
Sign in to GoDaddy. Select your login name in the upper right, then My Products.
-
Under Domains, in the Portfolio tab, select the three dots (...) next to the domain, then Edit DNS.
-
Under DNS Records, look for a TXT record with Name
@whose Value starts withv=spf1. Other TXT records at@, such as anMS=verification value, are separate. Leave them alone. -
If you find one, edit it and do not add another. Keep the existing values and add each new
include:before the finalall. Deleting aninclude:can make that service's mail fail SPF. -
If you find none, select Add New Record, choose TXT and enter:
Type Name Value TTL TXT @Your SPF value 1 hour -
Paste the value instead of typing it, so the spacing stays correct. Then select Save.
For example, a domain that already publishes v=spf1 include:secureserver.net -all and starts sending through Google Workspace keeps one record:
v=spf1 include:secureserver.net include:_spf.google.com -all
Be careful with the ending. -all says unlisted servers are not authorized, and a receiving server can reject their mail. ~all is softer: receivers should not reject on that result alone. List every sender before you publish -all.
Microsoft 365 can also add its records through Domain Connect. You sign in at GoDaddy and select Authorize. Microsoft points to that route when the domain is not already set up with another email service provider. If another service sends as your domain, use the steps above so you end up with a single combined record.
Confirm it worked
Microsoft says DNS changes typically take about 15 minutes, and occasionally longer. Google allows up to 48 hours for SPF authentication to start working.
- Run the domain through the SPF checker. You want one record, valid syntax and no more than 10 DNS lookups.
- Run
nslookup -type=TXT example.com 1.1.1.1with your domain. Exactly one line should start withv=spf1. - Send a message to a mailbox you control and open its headers. Look for
spf=passinAuthentication-Results.
If you edited a record and still see the old value, wait for the TTL to run out. The TTL is how long resolvers may cache a record.
Continue with DKIM at GoDaddy and DMARC at GoDaddy.
Common problems
Two SPF records at @
Microsoft's GoDaddy article warns against creating a second SPF record, but its numbered steps show only Add New Record. Using those steps on a domain that already has SPF creates a duplicate. RFC 7208 makes that a permerror. Merge both values into one record, save it, then delete the other. See multiple SPF records.
Saved at GoDaddy but missing from lookups
Check the nameservers again. If they point to another company, receiving servers read that company's DNS, so add the record there.
Two different values for Microsoft 365
Microsoft's GoDaddy article prints v=spf1 include:secureserver.net -all. Its general DNS article and SPF guide print v=spf1 include:spf.protection.outlook.com -all. On 9 November 2026, secureserver.net led to spf-0.secureserver.net, a list of IP ranges that ends by including spf.protection.outlook.com. So the first value also reaches Microsoft, but it costs 3 DNS lookups instead of 1. Add what your admin center shows.
Too many DNS lookups
RFC 7208 allows 10 lookup terms per check, and going over returns permerror. Nested includes count, so include:secureserver.net alone used 3 on that date. See SPF permerror.
A subdomain sends mail
@ covers only its own SPF domain. If news.example.com is used as SMTP MAIL FROM or HELO, it needs its own SPF record, with Name news. A visible From subdomain alone does not decide where SPF is checked.