If your team's mailboxes are on Google Workspace or Microsoft 365, the domain's SPF record has to include that provider. Here are the includes, a record that covers both, and how to add other senders to the same record.
Google Workspace
v=spf1 include:_spf.google.com ~allPublish it as a TXT record on the root domain, the name some DNS hosts show as @. Google's include covers Gmail's sending servers for your domain. It uses several of your 10 lookups, because _spf.google.com includes other records of its own.
Microsoft 365
v=spf1 include:spf.protection.outlook.com -allThis is the record Microsoft documents for Exchange Online. Microsoft suggests -all. ~all is also valid while you are still finding every sender. Government and regional clouds use different hosts, so check the admin center if your tenant is not on the standard service.
Both at once
During a migration, or when some mailboxes are on each, put both includes in one record:
v=spf1 include:_spf.google.com include:spf.protection.outlook.com ~allDo not publish one record for each. Two v=spf1 records on the same name is a permerror, and both providers fail. Multiple SPF records shows how to merge them. Remove the old provider's include once its mailboxes are gone.
Adding an app, CRM or newsletter tool
Most services that send as your domain give you an include. Add it to the existing record, before all:
v=spf1 include:_spf.google.com include:sendgrid.net ~allEach include adds lookups, and SPF stops at 10. Google Workspace plus three or four other services can cross that line. The SPF checker counts the total. If you are over, SPF too many DNS lookups covers what to remove.
Services that use their own return-path
Some senders do not need a place in your root record at all. SPF checks the return-path domain, and a service that sends with its own return-path subdomain publishes SPF there. SendPanda works this way: the domain screen shows a return-path name and an SPF value for that name. Your Google Workspace or Microsoft 365 record on the root domain stays as it is, and its lookup count does not change. DMARC still passes because the DKIM signature aligns with your domain. See the domain setup guide.
Check the result
Look the domain up with the SPF checker, then test a sending IP from a message header to confirm the right path passes. Add DKIM in the Google or Microsoft admin console as well, and publish a DMARC record. SPF alone does not protect the From address people see.
Next steps
- Quickstart for the full first-send walkthrough.
- Verify webhooks to learn when an email is delivered or bounces.
- Pricing: 3,000 emails a month free, no card.