How to configure Google Workspace (Gmail) in your DNS
Follow these 4 straightforward steps to publish your authentication records on Cloudflare, GoDaddy, Namecheap, or AWS Route 53.
Check for Existing SPF Records
Never publish two SPF records for the same domain. If your DNS already contains a v=spf1 record, edit the existing TXT record instead of creating a second one.
Add Google Workspace Include
Add include:_spf.google.com to your SPF TXT record at the root domain (@). Finish the record with ~all (SoftFail).
v=spf1 include:_spf.google.com ~allGenerate and Publish DMARC Policy
Create a new DNS TXT record with Host _dmarc. Start with p=none for 7 days to collect diagnostic reports, then upgrade to p=quarantine.
v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@yourdomain.com; pct=100Verify DNS Propagation
Use our Live DNS Inspector tool below to confirm Google Workspace SPF and DMARC have propagated across global DNS resolvers.
Frequently Asked Questions for Google Workspace (Gmail)
Technical answers regarding lookup limits, multiple records, and delivery errors.
Why does Google Workspace consume 4 SPF lookups?▼
Can I have multiple SPF records if I use Google Workspace and SendGrid?▼
What happens if Google bulk sender rules are not met in 2026?▼
How do I configure DKIM for Google Workspace?▼
Common Providers Used with Google Workspace (Gmail)
Send marketing and transactional emails alongside your corporate inbox.
Microsoft 365 / Exchange Online
Outlook, Exchange, and Office 365 Enterprise Email
Twilio SendGrid
High-Volume Transactional & Marketing Email API
HubSpot
Inbound Marketing, Sales Automation & CRM Platform
Mailchimp
Global Email Marketing & Automated Audience Engagement
Need to combine multiple providers into one SPF record?
Our full in-browser engine merges SPF records, calculates RFC 7208 lookups in real-time, and generates custom DMARC policies.