GoDaddy's DNS management interface is one of the most-searched for SPF setup guides - likely because the interface changes frequently and the field names are not intuitive. Here is the current step-by-step process.
Step 1: Access DNS Management
Log in to GoDaddy → click your account icon → "My Products" → find your domain → click "DNS" or "Manage DNS." If you use GoDaddy's website builder, you may need to navigate to "Domains" → click the three dots next to your domain → "Manage DNS."
Step 2: Look for Existing TXT / SPF Records
Scroll to the TXT Records section. GoDaddy historically showed a separate "SPF" record type, but now stores SPF as a TXT record. Look for any TXT record at the @ host that contains "v=spf1." If one exists, click the pencil icon to edit it rather than adding a new one.
Step 3: Add the SPF TXT Record
Click "Add" in the TXT Records section. Fill in these fields:
- Type: TXT
- Name:
@ - Value: For Google Workspace:
v=spf1 include:_spf.google.com ~all - TTL: 1 Hour (or 3600 seconds)
Click Save. GoDaddy will show a warning that DNS changes can take up to 48 hours - in practice, GoDaddy DNS propagates within 15–30 minutes for most records.
SPF Values for Common Email Providers
- Google Workspace:
v=spf1 include:_spf.google.com ~all - Microsoft 365:
v=spf1 include:spf.protection.outlook.com ~all - Both Google + M365:
v=spf1 include:_spf.google.com include:spf.protection.outlook.com ~all
Common GoDaddy SPF Mistakes
- Adding a record instead of editing: If a TXT record with v=spf1 already exists, adding a second one breaks SPF. Always edit the existing record.
- Wrong host field: Use @ for the root domain. Using "www" or leaving it blank creates the record in the wrong place.
- Missing include: If GoDaddy is also your email host (via GoDaddy Email Essentials), add
include:secureserver.netto your record alongside your ESP's include.
Verify the Record
After saving, use MXToolbox SPF Lookup or Google Admin Toolbox (toolbox.googleapps.com) to verify the record is live and parsing correctly. The MXToolbox result should show your ESP's IP ranges as "authorized senders" for your domain.
Ready to reach the inbox every time?
Automated email warmup across real peer mailboxes. Live inbox placement monitoring. Free 7-day trial - no credit card required.
Start free trialFrequently asked questions
How long does an SPF record take to work on GoDaddy?
GoDaddy usually publishes DNS changes within an hour, but resolvers cache the old record for as long as its TTL says. If the previous record had a 1-hour TTL, allow up to an hour after GoDaddy shows the change before testing, and longer if the TTL was set higher.
Can I have two SPF records on one domain?
No. A domain must publish exactly one SPF record. Two TXT records starting v=spf1 is a permerror, and the result is that SPF fails entirely rather than one record winning. If you need to authorise several senders, merge them into a single record using multiple include: entries.
What is the 10-lookup limit and why does it break SPF?
Every include:, a, mx, ptr and redirect in your record costs a DNS lookup, and the limit is 10 in total including nested lookups inside the providers you include. Exceeding it produces a permerror, which means SPF stops protecting you silently - nothing errors, mail just starts being treated as unauthenticated.
Do I still need DKIM and DMARC if SPF passes?
Yes. SPF alone authorises servers; it says nothing about whether the message was altered, and it validates the Return-Path rather than the From address your recipient sees. DMARC is what ties authentication back to the visible From domain, and without DKIM you have no second mechanism when mail is forwarded.