How to Add an SPF Record in GoDaddy

GoDaddy is one of the largest domain registrars in the world, which means millions of domains rely on its DNS manager for email authentication. If your domain is registered with GoDaddy -- or you're using GoDaddy's nameservers -- adding an SPF record is something you need to get right. One wrong field and your email authentication silently breaks.

This guide walks you through adding, editing, and troubleshooting SPF records in GoDaddy's DNS manager.

Why You Need SPF With GoDaddy Domains

Every domain that sends email needs an SPF record. It tells receiving mail servers which IP addresses and services are authorized to send email on behalf of your domain. Without one, Gmail, Outlook, and other providers have no way to distinguish your legitimate email from spoofed messages.

GoDaddy domains are no exception. Whether you use GoDaddy's own workspace email, Google Workspace, Microsoft 365, or any other email service, you need an SPF record published in your domain's DNS.

Step-by-Step: Adding an SPF Record in GoDaddy

A Note on the Host Field

GoDaddy's DNS manager uses "Name" or "Host" for the record name. For your root domain SPF record, this value should be @. Don't enter your full domain name (like example.com) -- GoDaddy appends the domain automatically. Entering the full domain would create a record for example.com.example.com, which won't work.

GoDaddy Workspace Email and secureserver.net

If you use GoDaddy's built-in workspace email (sometimes called GoDaddy Email or Professional Email), your email is routed through GoDaddy's secureserver.net infrastructure. This means your SPF record must include secureserver.net to authorize those servers.

A basic SPF record for GoDaddy workspace email only:

v=spf1 include:secureserver.net -all

GoDaddy may have already added this record when you activated workspace email. The problem arises when you add a second email service and create a new SPF record instead of updating the existing one.

Combining SPF Records in GoDaddy

Most GoDaddy users run into this scenario: they already have an SPF record for GoDaddy workspace email, and now they need to add Google Workspace, Office 365, or a marketing platform. The solution is always the same -- merge everything into one record.

GoDaddy Workspace + Google Workspace

v=spf1 include:secureserver.net include:_spf.google.com -all

This authorizes both GoDaddy's email servers and Google's sending infrastructure.

GoDaddy Workspace + Microsoft 365

v=spf1 include:secureserver.net include:spf.protection.outlook.com -all

GoDaddy Workspace + SendGrid

v=spf1 include:secureserver.net include:sendgrid.net -all

Google Workspace Only (no GoDaddy email)

If you've moved completely to Google Workspace and don't use GoDaddy's email at all, you can drop the secureserver.net include:

v=spf1 include:_spf.google.com -all

Common GoDaddy SPF Mistakes

GoDaddy's DNS manager is straightforward, but there are several mistakes that trip people up consistently.

Using the Wrong Host Field

The most common mistake is typing your domain name in the Host field instead of @. In GoDaddy's DNS manager, @ represents the root domain. If you enter example.com in the Host field, GoDaddy creates the record at example.com.example.com -- a subdomain that doesn't exist and won't authenticate your email.

Creating Duplicate SPF Records

When you add a new email service, it's tempting to just add a new TXT record with the new SPF value. But a domain can only have one SPF record. If GoDaddy workspace email already created v=spf1 include:secureserver.net -all and you add v=spf1 include:_spf.google.com -all as a second record, both break.

Fix: Edit the existing record and add the new include to it. Delete the old record only after you've saved the new combined version.

Forgetting secureserver.net

If you activated GoDaddy workspace email at any point -- even if you mainly use another email provider -- GoDaddy's servers may still send email for your domain (password resets, forwarding, auto-replies). Removing include:secureserver.net from your SPF record can cause those messages to fail authentication.

Fix: Only remove secureserver.net if you've fully deactivated GoDaddy workspace email and confirmed no email flows through GoDaddy's servers.

Not Saving After Editing

GoDaddy's DNS manager requires you to click Save after making changes. It's not uncommon to edit a record, get distracted, and navigate away without saving. Always confirm your changes were saved by refreshing the DNS page and checking the record value.

Editing an Existing SPF Record in GoDaddy

If you need to update your SPF record (to add a new service, remove an old one, or fix a mistake):

Verifying Your GoDaddy SPF Record

After adding or editing your SPF record, you should always verify it's live and correct. Go to SPF Record Check and enter your domain. The tool will:

• Confirm your SPF record is published
• Check for syntax errors
• Count your DNS lookups (must be 10 or fewer)
• Flag duplicate SPF records
• Show you exactly what receiving servers will see

If you see any errors, go back to GoDaddy's DNS manager and fix them before relying on the record.

Complete Your Email Authentication

SPF is one piece of the email authentication puzzle. For full protection, you need all three protocols working together:

• DKIM adds a cryptographic signature to your outgoing emails, proving they haven't been tampered with in transit. Use DKIM Creator to generate your DKIM keys and add the records in GoDaddy the same way you added your SPF record.
• DMARC ties SPF and DKIM together and tells receiving servers what to do when authentication fails. Use DMARC Creator to build your DMARC policy.

With all three records published in GoDaddy's DNS, mailbox providers can fully verify that your email is legitimate.

Monitor Your New SPF Record

You've created your SPF record — now make sure it keeps working. The Email Deliverability Suite watches your SPF, DKIM, DMARC, and MX records daily and alerts you when something breaks.