Guide per mail provider

Set up the SPF record for Google Workspace

For receivers to accept mail from Google Workspace with your domain as sender, the domain’s SPF record has to name the Google Workspace sending servers. This guide shows the value Google Workspace specifies and what to watch when publishing it.

Google Workspace: all records at a glance

The SPF value for Google Workspace

For Google Workspace the SPF record consists of a single include. Google explicitly recommends ~all, the soft fail: mail not coming through Google is then marked as suspicious instead of being rejected outright.

If further services send on behalf of the domain, such as a newsletter tool or the CRM, their include mechanisms go into the same record. There must be only one TXT record with v=spf1. According to Google it can take up to 48 hours for the record to take effect.

DNS
v=spf1 include:_spf.google.com ~all

How to set up SPF for Google Workspace

The SPF record is created at the domain’s DNS host:

  • Check at the DNS host whether a TXT record with v=spf1 already exists for the apex domain.
  • If there is none: create a TXT record for the apex domain (@) with the value above.
  • If there is one: add include:_spf.google.com before the all mechanism instead of creating a second record.
  • Use the SPF checker to verify that the record is read and stays under ten DNS lookups.

Publishing at the DNS host

The SPF record is a TXT record on the apex domain. Where you create it depends on who manages the domain’s DNS zone; the name server part of the domain check shows that. The guides per host below walk through the respective DNS editor.

Verify and keep an eye on it

The SPF checker below resolves the record completely, counts the DNS lookups and shows whether Google Workspace is included. DomainWarn keeps checking the record afterwards and alerts you when it changes, becomes invalid or breaks the lookup limit.

Frequently asked questions

Should I use ~all or -all for Google Workspace?
Google recommends ~all. With DKIM and a DMARC policy of quarantine or reject the protection is the same, because DMARC decides what happens to a message that passes neither SPF nor DKIM.
Is SPF alone enough for mail to reach Gmail?
For small senders Google requires SPF or DKIM. Anyone sending around 5,000 messages or more a day to Gmail accounts needs SPF, DKIM and DMARC.
What happens if there are two SPF records?
Then SPF is invalid for the domain and receivers evaluate neither record. All senders belong in a single TXT record with v=spf1.
Check now

Free SPF record check and lookup: syntax, includes, the 10 DNS lookup limit and the closing qualifier. Shows whether your domain blocks forged senders.

DomainWarn checks SPF, DKIM, DMARC, DNS and certificates of all client domains regularly and reports changes before mail lands in spam.

Monitor this domain continuously14-day free trial, no credit card.

Publishing at your host

The mail provider specifies the value; it is created at the domain’s DNS host. Pick your host for the way to the DNS editor.

All hosts at a glance

The same guide for other mail providers

All mail providers at a glance