Make Google Workspace DMARC-compliant
How to authenticate Google Workspace as a sender on your domain - so its mail passes SPF, DKIM and DMARC, and you can safely reach enforcement.
Three steps to authenticate Google Workspace
Google Workspace needs to pass SPF and DKIM, and align with your domain so DMARC passes. Here’s how – confirm the exact values against Google Workspace’s current documentation as you go.
Add Google Workspace to your SPF record
SPF lists the services allowed to send as your domain. Add Google Workspace’s include to your existing SPF record – don’t create a second SPF record, merge it into the one you have.
Watch the 10-lookup limit: every include counts, and going over makes SPF fail silently. Hosted SPF keeps you safely under it automatically.
Add this mechanism to your SPF record
include:_spf.google.com
Turn on DKIM signing
DKIM cryptographically signs each message so receivers can prove it really came from you and wasn’t tampered with. In the Google Admin console (Apps -> Google Workspace -> Gmail -> Authenticate email), turn on DKIM and publish the google._domainkey TXT record it generates.
DKIM is what keeps you authenticated even when a message is forwarded – so it’s worth getting right. More on how DKIM works →
- Enable DKIM inside Google Workspace
- Publish the DNS records it gives you
- Wait for it to verify, then send a test
Confirm alignment, then enforce
With SPF and DKIM set up, check that Google Workspace aligns – that the authenticated domain matches your visible From address. Once every legitimate sender aligns, you can move DMARC to p=reject safely.
DMARCER’s enforcement journey shows you exactly when it’s safe to advance – no guesswork.
Good to know
Gmail / Google Workspace sends as your domain once SPF, DKIM and DMARC alignment are all in place.
Check you got it right
Look up your records instantly, or run a full free check to confirm Google Workspace passes SPF, DKIM and DMARC – and get your score out of 100.
Check SPF Full free check