DMARC for HubSpot and Google Workspace: the setup that passes
Publish one SPF record with Google's include and set up Google DKIM. In HubSpot, connect your sending domain and add its two DKIM CNAME records. On HubSpot's shared sending, DMARC passes through DKIM, not SPF, so those CNAMEs are the part you can't skip.
Who sends what
It helps to be clear about which tool sends which email, because they authenticate differently:
- Google Workspace sends everything your team writes by hand. It also sends HubSpot sales emails and sequences that go through a connected inbox, because those leave through your Google mailbox.
- HubSpot sends marketing emails and automated marketing emails from its own servers. This is the part that needs the HubSpot setup below.
Part 1: Google Workspace
SPF
Your root domain needs one SPF record that includes Google:
v=spf1 include:_spf.google.com ~all
One record, not two. If you already have an SPF record for another tool, add Google's include to it rather than publishing a second one. Two SPF records make SPF fail for everything.
DKIM
- In the Google Admin console, open Apps → Google Workspace → Gmail → Authenticate email.
- Generate a new record with a 2048-bit key. Google gives you a TXT record named
google._domainkey. - Add it at your DNS provider, wait a little, then click Start authentication.
If the generate button isn't available yet, Google sometimes needs 24 to 72 hours after Gmail is first switched on.
Part 2: HubSpot
Connect your sending domain
In HubSpot, go to Settings → Content → Domains & URLs → Email Sending and choose Connect sending domain. HubSpot will give you two DKIM records, both CNAMEs, that look like this:
hs1-ACCOUNTID._domainkey CNAME (value from HubSpot)
hs2-ACCOUNTID._domainkey CNAME (value from HubSpot)
Copy the exact values from your account. They're unique to it.
On Cloudflare, set both records to DNS only (grey cloud). Proxied CNAMEs break DKIM lookups.
Why DKIM matters more than SPF here
On HubSpot's standard shared sending, the hidden bounce address (the Return-Path) is HubSpot's domain, not yours. SPF is checked against that address, so SPF can pass without lining up with your From domain. DMARC passes through DKIM instead. That's why the two CNAME records are the part you can't skip.
HubSpot's setup screen may also show SPF data to add. If it does, copy exactly what your account shows into your single SPF record. Guides online quote different values for HubSpot's include, so trust your own screen over any article, this one included.
Can SPF align with HubSpot at all?
Only with a custom return-path, which HubSpot currently offers for eligible Marketing Hub Enterprise accounts. It also requires sending from a subdomain. For everyone else, aligned DKIM is the way, and it's enough.
Part 3: DMARC
Once both tools are signing with DKIM on your domain, publish DMARC in monitoring mode first:
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
Watch the reports, catch any other senders you forgot, then move to enforcement. I've written up the whole rollout in how to move DMARC from p=none to quarantine safely.
Check it worked
Send a test marketing email from HubSpot to a Gmail address. Open it, choose Show original, and look for:
dkim=passwithheader.d=yourdomain.comdmarc=pass
Do the same with an email sent from Gmail itself. If both pass, the two biggest senders on your domain are covered.
Common mistakes
- A second SPF record added for HubSpot instead of editing the existing one.
- Doubled hostnames. Many DNS providers add your domain automatically, so
hs1-123._domainkey.yourdomain.combecomes...yourdomain.com.yourdomain.com. Enter only the part before your domain. - Proxied CNAMEs on Cloudflare.
- Forgetting the other tools. Support desks, billing systems and product email services send as your domain too. DMARC reports will show them.
Quick questions
Do I need to add HubSpot to my SPF record?
Add whatever SPF data your HubSpot setup screen shows. Just know that on shared sending it doesn't make SPF align with your domain. DKIM does that job.
Do HubSpot sequences need the same setup?
Sequences sent through a connected Gmail inbox leave through Google Workspace, so they're covered by your Google SPF and DKIM.
Why does HubSpot say my domain isn't connected?
Usually a typo in the CNAME values, a doubled hostname, or a proxied record on Cloudflare. Check each record with a DNS lookup tool.
Want me to check your domain?
Run the live check on my homepage, or send me your domain and get a one-page report within one business day. Free.
Run the live check →