Setting Up Email Authentication for Google Workspace
Complete guide to configuring SPF, DKIM, and DMARC for Google Workspace (Gmail for Business). Step-by-step instructions for optimal deliverability.
Setting Up Email Authentication for Google Workspace
Google Workspace (formerly G Suite) requires proper email authentication for optimal deliverability, especially with Google's 2024 bulk sender requirements. This guide covers SPF, DKIM, and DMARC setup for Google Workspace.
Overview
Google Workspace provides automatic SPF configuration, but you need to:
- Verify SPF - Google adds itself automatically, but verify and add other services
- Enable DKIM - Must be manually enabled in Admin Console
- Configure DMARC - You publish this yourself in DNS
Prerequisites
- Google Workspace admin access
- Access to your domain's DNS settings
- Domain verified in Google Workspace
Step 1: Configure SPF for Google Workspace
Google's Default SPF
Google automatically adds itself to your SPF when you add a domain, but you should verify and potentially add other services.
Check Current SPF Record
- Go to Google Admin Console
- Navigate to Apps → Google Workspace → Gmail
- Click Authenticate email
- Select your domain
- View current SPF record
Or check DNS directly:
dig TXT yourdomain.comStandard Google Workspace SPF Record
v=spf1 include:_spf.google.com -allAdding Additional Services
If you use other email services alongside Google Workspace:
v=spf1 include:_spf.google.com include:sendgrid.net include:servers.mcsv.net -allImportant: Google's SPF includes multiple IP ranges. Don't try to flatten it manually.
Common Google Workspace SPF Includes
| Service | Include Statement |
|---|---|
| Google Workspace (default) | include:_spf.google.com |
| Gmail | Already included in above |
| Google Apps | Already included |
DNS Configuration
Add or update TXT record:
| Field | Value |
|---|---|
| Type | TXT |
| Host/Name | @ or leave blank |
| Value | v=spf1 include:_spf.google.com -all |
| TTL | 3600 |
Step 2: Enable DKIM for Google Workspace
Google Workspace uses TXT records for DKIM (unlike Microsoft's CNAME approach).
Enable DKIM in Admin Console
-
Go to Google Admin Console
- Navigate to: https://admin.google.com
- Apps → Google Workspace → Gmail
-
Click Authenticate email
-
Select your domain
-
Find DKIM authentication section
-
Click Generate new record
-
Google generates DKIM record with selector (usually
google)
Add TXT Record to DNS
Google provides a TXT record like:
google._domainkey.yourdomain.com TXT "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC..."
DNS Configuration:
| Field | Value |
|---|---|
| Type | TXT |
| Host/Name | google._domainkey |
| Value | The complete DKIM record (starts with v=DKIM1; k=rsa; p=...) |
| TTL | 3600 |
Important: Copy the entire value exactly as provided by Google, including v=DKIM1; k=rsa; p= prefix.
Verify DKIM Setup
Method 1: Google Admin Console
- Return to Authenticate email page
- Status should show "Authenticating email" or green checkmark
- May take up to 48 hours to fully activate
Method 2: Send Test Email
- Send email from Google Workspace account
- Open email → Click three dots → Show original
- Look for
DKIM-Signatureheader - Verify
d=matches your domain
Method 3: Online Tools
- Use MailSentinel to check DKIM records
- Use MXToolbox DKIM checker
- Use Google's own Postmaster Tools
DKIM Key Length
Google Workspace uses 1024-bit keys by default, which meets Google's requirements. For enhanced security, you can request 2048-bit keys, but 1024-bit is sufficient for compliance.
DKIM Key Rotation
Google automatically rotates DKIM keys periodically:
- Keys rotate every few months
- You'll need to update DNS record when rotated
- Google notifies you in Admin Console
- Old keys remain valid during transition period
Step 3: Configure DMARC for Google Workspace
Google doesn't configure DMARC automatically - you must do this yourself.
Get Your MailSentinel Report Address
- Log in to MailSentinel
- Go to Settings → DMARC Configuration
- Copy your report address:
your-org-id@reports.mailsentinel.io
Create DMARC Record
Starting with monitoring (recommended):
v=DMARC1; p=none; rua=mailto:your-org-id@reports.mailsentinel.io; ruf=mailto:your-org-id@forensic.mailsentinel.ioAfter monitoring period:
v=DMARC1; p=quarantine; rua=mailto:your-org-id@reports.mailsentinel.io; adkim=r; aspf=rFull enforcement:
v=DMARC1; p=reject; rua=mailto:your-org-id@reports.mailsentinel.io; ruf=mailto:your-org-id@forensic.mailsentinel.io; adkim=r; aspf=rAdd DMARC Record to DNS
| Field | Value |
|---|---|
| Type | TXT |
| Host/Name | _dmarc |
| Value | Your DMARC record |
| TTL | 3600 |
Verify DMARC Setup
- Use MailSentinel to check DNS
- Verify DMARC record is detected
- Wait 24-48 hours for first reports
- Monitor in MailSentinel dashboard
Google Workspace Specific Considerations
Gmail Routing
- Gmail routing uses Google's authentication
- No special configuration needed
- DMARC applies to all routed emails
Google Groups
- Google Groups emails use Google Workspace authentication
- No special SPF/DKIM needed
- Replies use the sender's authentication
Google Workspace Marketplace Apps
Third-party apps sending email:
- May need to be added to SPF
- Check app documentation for SPF includes
- Configure DKIM if app supports it
External Email Forwarding
If you forward emails externally:
-
Enable ARC (Authenticated Received Chain)
- Helps preserve authentication through forwarding
- Configure in Gmail settings
-
Update SPF if forwarding to external addresses
- May need to include forwarding server IPs
Google Workspace + Gmail Personal
If users have both:
- Workspace emails use Workspace authentication
- Personal Gmail uses Gmail authentication
- Separate DMARC policies if needed
Google's 2024 Bulk Sender Requirements
Google enforces strict requirements for bulk senders (5,000+ emails/day to Gmail):
Requirements
- SPF and DKIM - Both required (not just one)
- DMARC Policy - Must publish DMARC (minimum
p=none) - DMARC Alignment - From: domain must align with SPF or DKIM
- One-Click Unsubscribe - Required for marketing emails (RFC 8058)
- Spam Rate - Keep below 0.3% (monitor in Postmaster Tools)
- Valid PTR Records - Reverse DNS must be configured
- TLS Encryption - Required for transmission
Compliance Checklist
- SPF record includes
_spf.google.com - DKIM enabled and TXT record published
- DMARC record published (start with
p=none) - DMARC reports being received
- SPF alignment verified
- DKIM alignment verified
- List-Unsubscribe headers configured
- Spam complaint rate monitored in Postmaster Tools
- PTR records configured for sending IPs
Google Postmaster Tools
Set up Google Postmaster Tools to monitor:
- Go to https://postmaster.google.com
- Add and verify your domain
- Monitor key metrics:
- Spam Rate - Must stay below 0.3%
- IP Reputation - Track sender reputation
- Domain Reputation - Overall domain health
- Delivery Errors - Bounce and error rates
Troubleshooting Google Workspace Issues
Issue 1: SPF Too Permissive
Problem: Using +all or ?all instead of -all
Solution:
- Edit DNS TXT record
- Change to
-all - Verify in Google Admin Console
Issue 2: DKIM Not Signing
Symptoms:
- No DKIM signature in headers
- DKIM status shows "Not authenticated"
Solutions:
- Verify DKIM is enabled in Admin Console
- Check TXT record is published correctly
- Wait 24-48 hours for full activation
- Verify domain is fully configured in Google Workspace
- Check for typos in DNS record
Issue 3: DMARC Failures
Symptoms:
- DMARC reports show failures
- Emails going to spam
Common Causes:
-
SPF alignment issues
- Envelope sender doesn't match From: domain
- Check Return-Path header
-
DKIM alignment issues
- DKIM signing domain doesn't match From: domain
- Google signs with your domain, so this is usually fine
-
Third-party senders
- Services sending as your domain not in SPF
- Add missing services to SPF
Issue 4: Multiple SPF Records
Problem: Multiple SPF TXT records exist
Solution:
- Find all SPF records:
dig TXT yourdomain.com | grep "v=spf1" - Merge into single record
- Remove duplicates
Issue 5: DKIM Key Rotation
Symptoms:
- DKIM validation fails after Google rotates keys
- Need to update DNS record
Solution:
- Check Admin Console for new DKIM record
- Update DNS TXT record with new key
- Old key remains valid during transition
- Wait for DNS propagation
Issue 6: High Spam Rate
Symptoms:
- Spam rate above 0.3% in Postmaster Tools
- Emails going to spam folder
Solutions:
- Review email content and practices
- Ensure double opt-in for subscribers
- Make unsubscribe easy and prominent
- Remove inactive subscribers
- Honor unsubscribe requests immediately
- Segment lists for better engagement
Best Practices for Google Workspace
1. Start with Monitoring
Begin with p=none DMARC policy:
- Monitor for 2-4 weeks
- Identify all sending sources
- Fix alignment issues
- Then move to enforcement
2. Use MailSentinel for Monitoring
- Set up DMARC reporting to MailSentinel
- Monitor SPF/DKIM pass rates
- Get alerts for authentication failures
- Track progress toward enforcement
3. Monitor Postmaster Tools
Regularly check:
- Spam complaint rate (target: <0.3%)
- IP reputation
- Domain reputation
- Delivery errors
4. Regular Audits
Review quarterly:
- SPF record for unused services
- DKIM signing status
- DMARC report data
- Alignment issues
- Spam rates
5. Document Configuration
Keep records of:
- SPF includes and why
- DKIM selector and key rotation dates
- DMARC policy progression
- Any custom configurations
6. Test Before Changes
- Use test subdomain first
- Send test emails
- Verify headers
- Check DMARC reports
- Then apply to production
Common Google Workspace Configurations
Small Business (Google Workspace Only)
SPF:
v=spf1 include:_spf.google.com -allDKIM: Enable in Admin Console with google selector
DMARC:
v=DMARC1; p=none; rua=mailto:your-org-id@reports.mailsentinel.ioEnterprise (Google Workspace + Marketing Platform)
SPF:
v=spf1 include:_spf.google.com include:servers.mcsv.net -allDKIM: Enable Google Workspace DKIM + configure marketing platform DKIM
DMARC:
v=DMARC1; p=quarantine; rua=mailto:your-org-id@reports.mailsentinel.io; adkim=r; aspf=rDeveloper (Google Workspace + Transactional Email)
SPF:
v=spf1 include:_spf.google.com include:sendgrid.net include:spf.postmarkapp.com -allDKIM: Enable Google Workspace DKIM + configure transactional service DKIM
DMARC: Same as above, covers all sending sources
Next Steps
After configuring Google Workspace authentication:
- Monitor DMARC Reports - Track authentication status
- Set Up Alerts - Get notified of issues
- Review SPF Validation - Check lookup count
- Set Up Postmaster Tools - Monitor spam rates
- Progressive DMARC Enforcement - Move toward
p=reject
Additional Resources
- Google Workspace Email Authentication - Google's official guide
- DKIM Setup - DKIM configuration guide
- SPF Setup - SPF configuration
- Google Postmaster Tools - Deliverability monitoring
- Google's Bulk Sender Requirements - Official requirements