Google Workspace
SPF Google Workspace Setup: The TXT Record and How to Add It
The SPF record for Google Workspace is one TXT entry at your domain host. Exact value, the steps, how to confirm it passes and Google-specific problems.
Before you start
SPF Google Workspace setup takes one DNS TXT record on your domain, with the value v=spf1 include:_spf.google.com ~all when Google is your only sender. SPF (Sender Policy Framework) lists the servers allowed to send mail for your domain.
Google says "You don't need to do anything in your Google Admin console to set up SPF." You publish the record at your domain host, the service that runs your DNS. Whoever holds that login makes the change.
Google says you can skip setup if your domain already has SPF by default, or if you bought it from a Google partner when you signed up for Workspace. Confirm with the SPF checker that the record contains include:_spf.google.com.
SPF for Gmail addresses
There is no Gmail SPF record to publish for a personal @gmail.com address. Google owns that domain, and its record reads v=spf1 redirect=_spf.google.com. An outside tool cannot be added to it, so send from a domain you control.
Steps
-
List every sender. Google names web servers, on-premise servers, outbound gateways, "Contact us" forms and third-party services. Caution: a sender you leave out might fail SPF and be rejected or sent to spam.
-
See what is published. Run
nslookup -type=TXT example.com 1.1.1.1and look for a line beginning withv=spf1. -
Build one value. For Google Workspace alone (each term explained):
TXTv=spf1 include:_spf.google.com ~all
Google says its addresses change often, so keep the
include:term and avoid pasting IP ranges. For each other sender, add itsinclude:before~all, using that sender's current documentation. Google publishes this example for Workspace and Zendesk:TXTv=spf1 include:_spf.google.com include:mail.zendesk.com ~all
-
Open your domain host, typically where you bought the domain, and find the page for DNS TXT records.
-
Add or update the record. Type
TXT. Host@, or blank if your panel uses that. Value: your line from step 3. Some hosts require quotes around the value. Caution: if av=spf1record already exists, edit it and placeinclude:_spf.google.combefore itsall. A second SPF record breaks the check (permerror). If you already have two, merge them into one. -
Repeat for each domain. Google says each domain must have its own SPF record, and each subdomain you use needs one.
-
Keep
~all. Google recommends it and says a hyphen can cause delivery issues for legitimate email. Caution: with-all, receivers may reject a sender you forgot, so switch only after DMARC reports show every sender passing.
Confirm it worked
- Wait. Google says SPF can take up to 48 hours to start working.
- Run the SPF checker again. You want exactly one
v=spf1record containinginclude:_spf.google.com, with 10 lookups or fewer. Check MX in the Google Admin Toolbox also counts them. - From a Workspace account, email a mailbox outside your domain, such as a personal Gmail account. In Gmail, next to Reply, click More, then Show original.
- Find the header that starts with
Authentication-Results. The text afterspf=should bepass. Repeat from every other sender.
A pass counts for DMARC only when the domain of the envelope sender, the address used during delivery, aligns with your From domain. Add DKIM too, since Google says forwarded messages often fail SPF.
Common problems
- The alert
SPF record doesn’t include Google servers (likely impact to email delivery). Google means the SPF record for your primary domain lacks Google's servers. Addinclude:_spf.google.comto the existing record. best guess recordin thespfentry. Google lists three causes: SPF is missing, SPF is set up wrong, or your domain provider has a DNS issue.- A warning that you have no SPF record when you do. Google says more than 10 DNS lookups can cause this, and nested includes count. As of 2026-11-09,
_spf.google.comlisted only IP ranges, so Google's term used one lookup. See too many DNS lookups. - Contact form mail is rejected. Google counts a form that sends automatically as a sender for your domain. In Email Log Search, this error can mean your record omits one:
550-5.7.26 Unauthenticated email from domain-name is not accepted due to domain-name's DMARC policy - Forwarded mail fails SPF. Google says this can happen with a correct record. Leave out hostnames ending in
unverified-forwarding.1e100.net. Google warns that adding them puts your domain at risk of forged mail.