Free tools · Email domain setup
Google Workspace SPF Record: Setup and Check
Google publishes an SPF include for Workspace senders. Use the Google-only example only when Google is your only sending service for that domain. Support, marketing and transactional systems may need their own entries.
Real public DNS lookup. No signup, mailbox connection or API key needed.
Check your published SPF record
Enter your own public domain. The illustrated examples below are not preloaded and no lookup runs until you submit.
Look up your public SPF record.
Enter your domain to see the published record and any issues found. Results appear here after a real DNS lookup.
SPF record generator
Create a TXT record from the settings you choose. This builder runs in your browser and produces text for you to review. It does not update DNS.
Your TXT record
Add the settings you intend to publish, then generate the text. Compare it with your existing record before making changes with your DNS provider.
What to do next
1. Inventory your senders
List every service sending for the domain. Include devices and applications that send notifications, not just people's Gmail accounts.
2. Inspect the current policy
Check the public sending domain below. Review any existing SPF policy before adding a record; a second separate policy is not the way to add Google.
3. Use Google's current instructions
For Google-only sending, the example below is Google's published starting policy. If you use other services, prepare a single policy that covers their confirmed requirements too.
4. Publish and test each source
Add the reviewed TXT value through your DNS host. Recheck public DNS, then inspect received test messages from each sending service for authentication results.
Google-only sending example
v=spf1 include:_spf.google.com ~all
This is the Google-only example from Google's setup guide. It is not a universal replacement for a domain that also sends through other providers. The checker does not change DNS.
The DNS host holds the policy
SPF is published in your domain's DNS. Signing in to Gmail or connecting Gmail to AskQuokka does not publish an SPF record.
Use DKIM and DMARC alongside SPF
Review a real message's signing domain and alignment as well. An SPF DNS result alone cannot prove that a particular message passed authentication or reached the Inbox.
Questions
Should I use gmail.com in the checker?
Enter your business sending domain. Checking gmail.com inspects Google's public domain rather than your Workspace domain's own configuration.
Can the builder discover every service for me?
No. Enter the authorised sources you have confirmed with your providers. Leave out example domains and do not add a service just because an old record mentions it.
Checking sends your public domain to AskQuokka. Record generation and copying run in this tab. No DNS settings are changed and no email is sent. Domain inputs and lookup results are not included in tool analytics.
Official references
References checked 23 October 2026. Use your provider's current domain-specific values.
More setup and troubleshooting guides
SPF Too Many DNS Lookups: Find the Cause
Review SPF lookup-limit findings, understand nested includes and plan a change using your actual sending services. Includes a free DNS checker.
Multiple SPF Records: How to Review and Fix Them
Understand duplicate SPF policies, distinguish TXT chunks from separate records and prepare one policy from confirmed senders. Free checker included.