How to add an SPF TXT record in GoDaddy DNS

To add an SPF record in GoDaddy DNS, open Domain Portfolio, select the domain, and open DNS. Find the TXT record at @ that starts with v=spf1. Edit it if it exists. Add a new TXT record at @ only when no SPF record exists.

SPF (Sender Policy Framework) authorizes hosts to use a domain in the SMTP envelope sender. It does not authenticate the visible From address by itself. DMARC adds that identity check through SPF or DKIM alignment.

GoDaddy publishes SPF as a TXT record. The main risk is creating a second SPF record instead of updating the existing value.

We checked GoDaddy’s current SPF and Domain Portfolio documentation in August 2026. From the domains we review, duplicate SPF records and edits made at non-authoritative DNS are the two failures that recur.

This guide covers the current GoDaddy fields, GoDaddy email values, third-party senders, and verification.

Before you start

You’ll need access to your GoDaddy account with permission to edit DNS records. You also need to confirm that DNS is actually managed at GoDaddy. GoDaddy’s SPF help says the domain must use GoDaddy nameservers to add SPF in the GoDaddy account. If your nameservers point to Cloudflare, Wix, Squarespace, Route 53, or another provider, edit SPF there instead.

You also need to know which email services send mail as your domain.

List every service that uses the domain as its envelope sender. Examples include Google Workspace, Microsoft 365, Mailchimp, HubSpot, and SendGrid. Each authorized source must fit into the same SPF policy.

If your domain, DNS, and email are all in the same GoDaddy account, GoDaddy says it may add SPF for you. You should still check the DNS record before changing anything.

If the sender inventory is incomplete, start DMARC reporting before enforcing a policy. Aggregate reports identify the sources receivers see using the domain.

Step 1: build your SPF record

Before touching GoDaddy, you need to know what to put in the record.

Go to our SPF record generator. Select the email services you use, and the tool builds a valid SPF record for you. It also counts DNS lookups in real-time, which matters because SPF has a hard limit of 10 lookups before it breaks.

For a basic setup with Google Workspace, the generator outputs something like:

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

If you use Microsoft 365 directly from Microsoft:

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

If you use Microsoft 365 from GoDaddy, Professional Email, Linux Hosting, Gen 4 VPS or Dedicated Hosting, or Media Temple Mail, GoDaddy’s documented SPF value is:

v=spf1 include:secureserver.net -all

If you have Microsoft 365 from GoDaddy with the Advanced Email Security add-on, GoDaddy says to get the SPF value from the Email & Office Dashboard.

If you use both (which is unusual, but happens during migrations):

v=spf1 include:_spf.google.com include:spf.protection.outlook.com -all

Copy your generated or provider-supplied record. You’ll paste it into GoDaddy in Step 4.

Step 2: log into GoDaddy

Go to GoDaddy’s Domain Portfolio and sign in.

GoDaddy’s current SPF instructions use this path: select an individual domain to open the Domain Settings page, then select DNS to view records.

You may also get there through My Products: click your profile icon, select My Products, find your domain under Domains, and choose DNS next to the domain name.

Both paths land you at the same DNS management screen.

Step 3: check for existing SPF records

This step is important. You can only have one SPF record per domain. If you already have an SPF record and add another, both become invalid. Receiving servers see the conflict and return an error.

In your DNS records list, look for any TXT record that starts with v=spf1. It might look like this:

Type: TXT
Name: @
Value: v=spf1 include:some-service.com -all

If you find one, edit the existing record instead of creating a second one. For example, if you have v=spf1 include:_spf.google.com -all and Zendesk uses the same domain as its SPF identity, edit it to v=spf1 include:_spf.google.com include:mail.zendesk.com -all.

If you don’t have an existing SPF record, proceed to Step 4.

Step 4: add or edit the SPF TXT record

If you found an existing SPF record, edit it. If not, select Add New Record and choose TXT from the Type menu. Fill in these fields:

Field	Value
Type	TXT
Name / Host	@
Value / TXT Value	Your SPF record (from Step 1)
TTL	Leave as default

The Name field should be @ (the at symbol). In GoDaddy’s DNS, @ means the root of your domain. Your SPF record will apply to yourdomain.com.

For the Value field, paste your entire SPF record exactly as generated. Do not add quotes around it. GoDaddy handles quoting internally.

GoDaddy’s SPF help says the Value field must be ASCII and can be up to 512 characters. If your SPF record is approaching that length or using many include: mechanisms, you should simplify it before saving because SPF also has a DNS lookup limit.

Example of what you’re entering:

Type:  TXT
Name:  @
Value: v=spf1 include:_spf.google.com include:mail.zendesk.com -all

Step 5: save the record

Click Save.

If your domain has GoDaddy Domain Protection enabled, GoDaddy may require identity verification before the DNS change is saved. After saving, you should see one TXT record at @ whose value starts with v=spf1.

Step 6: verify it works

Run your domain through our SPF checker first: it queries live public DNS rather than reading your GoDaddy dashboard, so the record it shows is the one resolvers actually serve. If it still shows the old value, GoDaddy’s TTL has not expired and receivers are still evaluating the record you replaced.

GoDaddy says most DNS updates take effect within an hour but can take up to 48 hours globally.

To verify your SPF record is live, go to DMARCTrust’s domain checker, enter your domain name, and look at the SPF section.

You should see your record displayed. The checker also shows you how many DNS lookups your record requires. If you’re at 10 or above, you have a problem that needs fixing.

GoDaddy-specific pitfalls

GoDaddy’s DNS interface has a few details that trip people up.

SPF value length. GoDaddy’s SPF help lists a 512-character maximum for the SPF value and ASCII-only content. Long SPF records are often a sign that too many services are included. They are also more likely to hit SPF’s DNS lookup limit.

The @ symbol confusion. In GoDaddy, @ means your root domain. Don’t enter your full domain name in the Name field. If your domain is example.com, entering example.com creates a record for example.com.example.com. That’s wrong, and it’s a mistake we see constantly.

DNS hosted somewhere else. If your domain is registered at GoDaddy but uses another provider’s nameservers, GoDaddy’s DNS records are not authoritative. Add or edit SPF at the DNS provider your nameservers point to.

Propagation delays. GoDaddy says DNS updates usually take effect within an hour, but global propagation can take up to 48 hours. You can verify propagation using our domain checker or command-line tools like dig or nslookup.

Common SPF mistakes

Beyond GoDaddy-specific issues, here’s what we see go wrong most often.

Multiple SPF records. You can only have one SPF record per domain. Two v=spf1 TXT records invalidates both. Check your DNS for duplicates before adding anything new. For more on this, see our SPF documentation.

Exceeding 10 DNS lookups. Every include: starts another SPF evaluation and can add nested queries. More than 10 DNS-querying terms in one evaluation returns PermError. Our SPF generator shows the complete lookup count.

Forgetting services. Marketing, CRM, helpdesk, billing, and ticketing systems may all use the same visible From domain. Add a service to this SPF record only when it uses the domain as its envelope sender. Otherwise, configure the vendor’s aligned DKIM or custom return-path feature.

Using a random SPF value. If you use GoDaddy email products, use GoDaddy’s documented value or the value shown in the Email & Office Dashboard. If you use third-party providers, use their SPF includes and merge them into one record.

What about DMARC?

SPF alone isn’t enough. SPF tells receivers which servers are allowed to send your email, but it doesn’t tell them what to do when authentication fails. That’s what DMARC does.

DMARC adds alignment, policy, and reporting to SPF and DKIM. The policy requests how receivers handle messages that fail aligned authentication. Aggregate reports show which systems use the domain.

If you’re setting up SPF, you should set up DMARC too.

GoDaddy now automatically adds DMARC for some newer domains, so check for an existing _dmarc record before adding anything. The full walkthrough is in the GoDaddy DMARC setup guide.

v=DMARC1; p=none; rua=mailto:[email protected];

If there is no DMARC record yet, the independent setup is a TXT record named _dmarc with a value like the example above.

You get your unique reporting address when you sign up for DMARCTrust.

Alignment: why SPF isn’t always enough

Here’s something that trips people up. SPF can pass, but DMARC can still fail.

SPF checks the envelope sender (the Return-Path). DMARC checks whether that domain aligns with the From header. If they’re different (common with third-party senders), SPF passes but doesn’t help your DMARC result.

This is called SPF alignment. It’s why you need both SPF and DKIM properly configured. And it’s why monitoring matters.

Why monitoring matters

SPF is only the allowlist. It says which mail servers may send for your domain, but it does not tell you which services are actually sending, which ones are failing, or whether SPF is aligned for DMARC.

That is where DMARC monitoring helps. Aggregate reports show real traffic: source IPs, sending organizations, SPF pass/fail results, DKIM results, and whether either mechanism aligned with the visible From: domain.

DMARCTrust parses those reports automatically. You see which senders are covered by SPF, which ones need DKIM instead, and which GoDaddy TXT record changes are safe before moving DMARC toward enforcement.

Frequently asked questions

How do I add an SPF record in GoDaddy?

In GoDaddy DNS management, check whether a TXT record beginning with v=spf1 already exists. If it exists, edit it. If not, select Add New Record, choose TXT, enter @ in the Name field, paste your SPF value (for example, v=spf1 include:_spf.google.com -all), keep the default TTL, and save. Verify the record propagated using a DNS or DMARC checker.

Is a GoDaddy SPF record a TXT record?

Yes. Select TXT as the record type. Use @ as the Name for the root domain, and place the complete value beginning with v=spf1 in the Value field.

Does GoDaddy have an SPF record by default?

Sometimes. GoDaddy says that if your domain, DNS, and email are in the same GoDaddy account, they add the SPF record for you. Their broader email-authentication help also says SPF is automatically added for Professional Email or Professional Email powered by Titan. Always check DNS before adding another v=spf1 TXT record.

What is the SPF record value for GoDaddy email?

If you use Microsoft 365 from GoDaddy, Professional Email, Linux Hosting, Gen 4 VPS or Dedicated Hosting, or Media Temple Mail, GoDaddy documents v=spf1 include:secureserver.net -all. If you use Microsoft 365 from GoDaddy with Advanced Email Security, check the Email & Office Dashboard for the exact SPF value. Combine third-party senders into the same record and keep total DNS lookups under 10.

Can I have two SPF records on a GoDaddy domain?

No. A domain can have only one SPF record. Two v=spf1 TXT records invalidate each other. Edit the existing record to add new senders rather than creating a second one.

How long does GoDaddy take to publish an SPF record?

GoDaddy says most DNS updates take effect within an hour but can take up to 48 hours globally.

The path to enforcement

Use evidence instead of a fixed calendar:

1. Collect reports with p=none until normal and infrequent senders appear.
2. Fix each legitimate source that lacks aligned SPF or DKIM.
3. Test quarantine with p=quarantine; t=y.
4. Remove t=y only after the report data is clean.
5. Consider p=reject after evaluating forwarding and mailing-list traffic.

RFC 9989 made the older pct sampling tag historic. Our enforcement playbook covers the current rollout model.

Check your domain now

Enter your domain in our free checker. You’ll see whether your SPF record is configured correctly, how many DNS lookups it uses, and whether you have DMARC set up.

For SPF, the important checks are concrete: one TXT record at each SPF identity, no duplicate policies, and no more than 10 DNS-querying terms during evaluation. Represent each source that uses the domain as its SPF identity. Configure aligned DKIM or a custom return-path for the others.

GoDaddy gives you the DNS editor. DMARCTrust shows whether the SPF record actually covers the mail your domain sends.

Additional resources

For more details on GoDaddy’s DNS management, see their official documentation:

• Manage DNS records - GoDaddy’s guide to adding and editing DNS records
• Add a TXT record - Specific instructions for TXT records