Skip to content
  • There are no suggestions because the search field is empty.

HubSpot SPF, DKIM and DMARC setup

To pass DMARC on marketing email you send through HubSpot, connect your sending domain in HubSpot and publish the records it gives you: two DKIM CNAMEs, an SPF include added to your existing SPF record, an MX record and a DMARC record. DKIM is what makes the mail align on HubSpot's shared network. Then start DMARC at p=none with reports, and tighten the policy only after the reports show HubSpot mail passing with alignment.

One thing to settle first: this setup covers HubSpot marketing email (and transactional email if you use that add-on). One-to-one email and conversations inbox mail don't use the marketing sending domain; those streams use the address connected to those tools. Sales sequences often use a connected mailbox too. Test each stream on the path it actually takes.

What happens before you connect a domain

To send marketing email From an address on your domain, you have to connect that domain as a sending domain, and that needs a Starter subscription or higher. Until it's connected and the records resolve, HubSpot marketing mail has no DKIM signature aligned with your From domain. SPF won't help either, unless HubSpot is in your SPF record and the Return-Path domain lines up with your From domain (Identifier alignment for SPF and DKIM).

At p=none that only shows in reports. At p=quarantine or p=reject, receivers can filter or refuse the unaligned mail (What happens to failing mail under each policy).

Root domain or subdomain?

You can connect a subdomain or the root domain. Connect a subdomain when the root already hosts your website, because a domain that hosts the site shouldn't also be the email sending domain. The subdomain should match the domain in your From address: if you connect info.example.com, send from news@info.example.com. A sending subdomain also keeps marketing reputation apart from your main domain (Shared domains and multi-service setups).

HubSpot DKIM setup

In current HubSpot settings, go to Settings → Content → Domains & URLs, open the Email Sending tab, and choose Connect sending domain. You need permission to edit domain settings. Enter a From address you use for marketing email, and HubSpot shows the records to add. Some DNS hosts let you sign in from HubSpot and publish them for you; otherwise you add them by hand.

DKIM uses two CNAME records. HubSpot generates both host names and their values for your domain, so copy the Host and the required data from the portal exactly. In this guide they appear as placeholders:

[DKIM host 1 from your portal]   CNAME   [value 1 from your portal]
[DKIM host 2 from your portal]   CNAME   [value 2 from your portal]

Don't reuse names from another domain or a blog post. If HubSpot's own troubleshooting asks you to look up a specific selector, that's a check. You still publish the two CNAMEs exactly as the portal shows them.

HubSpot also gives you an MX record for the sending domain. Copy it from the portal and add it as shown. If the root already receives mail, connect a sending subdomain instead, so this MX doesn't collide with your mailbox platform.

Two DNS details catch people out:

  • Relative names. Many DNS hosts add your domain to whatever you type in the Name field. Enter the host the way your DNS host expects, often without the trailing domain, then check that the saved full name isn't doubled.
  • Cloudflare. If your DNS is on Cloudflare, HubSpot needs domain-wide CNAME flattening and proxy settings turned off, with the DKIM CNAMEs set to DNS-only. The steps are in Add SPF, DKIM and DMARC records in Cloudflare DNS Add SPF, DKIM and DMARC records in Cloudflare DNS.

Records often take 10 to 70 minutes to appear and can take up to 48 hours. Wait at least 20 minutes before you check the status in HubSpot. You'll see one of three:

  • Not authenticated.
  • Partially authenticated. DKIM is verified, but SPF or DMARC is still outstanding.
  • Authenticated.

A subdomain can show as authenticated for DMARC because a DMARC record already exists on the root domain, which the subdomain inherits (Subdomain policy (sp)). That status tells you the record exists. It doesn't tell you HubSpot mail passes DMARC. The reports do.

Add HubSpot to your SPF record

SPF is a TXT record, and a host name can have only one. If you already have an SPF record, add HubSpot to it. Don't create a second one, because two SPF records make SPF fail with a permanent error for all your mail (Two SPF records).

Copy the include value HubSpot shows for your domain. You may see more than one HubSpot include host mentioned in different places. Don't mix them or guess; use the exact value from your portal. Publish it at the host name the portal gives you, which may be your sending subdomain rather than the root.

Say your existing record covers Google Workspace. With HubSpot added, it reads:

TXT  "v=spf1 include:_spf.google.com include:[HubSpot include from your portal] ~all"

Keep v=spf1 at the start and the ~all at the end, once each. Every include costs DNS lookups, and SPF allows 10, so check your total after the change (The 10-lookup limit and SPF permerror).

HubSpot SPF alignment and the Return-Path

Adding the include authorizes HubSpot in your SPF record. Alignment is a separate question. SPF aligns only when the Return-Path domain matches your From domain, and on HubSpot's shared network you can't customize the Return-Path. So on the shared network, SPF may not align even with the include in place, and aligned DKIM is the route you rely on. That's enough for DMARC.

If you've bought the dedicated IP add-on or the transactional email add-on, the Return-Path can be customized, and SPF can align as well. Use the records HubSpot gives you for that setup. Why DKIM usually carries vendor mail is explained in SPF include vs DKIM from the vendor.

Your HubSpot DMARC record

Connecting a sending domain also asks for a DMARC TXT record. Publish it at your DNS host. It's a record on your domain, not a HubSpot switch.

If you don't have one yet, start with a monitoring policy and reports:

_dmarc.example.com.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"

Put the reporting address our platform gives you in rua, not the example address. The tags are explained in DMARC tags explained: p, sp, np, adkim, aspf, rua, ruf, fo, and t, report addresses in rua, ruf, and report authorization, and the full record on our DMARC setup page.

If you already have a DMARC record, keep it, including its rua. Don't add a second _dmarc TXT, because receivers ignore a domain's DMARC records when there's more than one. And don't paste whatever sample record HubSpot shows over your existing policy. If you're at enforcement, that would quietly take you back to p=none.

Confirm it in your reports

When HubSpot shows the domain as Authenticated, send a marketing email from that From domain and check two places.

The header of a received copy. Authentication-Results should show dkim=pass with header.d= on your domain, and dmarc=pass. The full test is in How to add a third-party sender without breaking DMARC.

Your aggregate reports. Over the next few days, HubSpot should appear as a source with DKIM passing and aligned. If you have a custom Return-Path through an add-on, look for aligned SPF as well. On the shared network, aligned DKIM is the pass you need, and SPF not aligning there is normal. In our reporting, each sending source has its own view, so HubSpot's results sit apart from your mailbox platform's.

If HubSpot mail fails alignment, Third-party mail fails alignment walks through the fixes.

Moving to enforcement

Move to p=quarantine, then p=reject, one domain at a time, and only after reports show HubSpot and every other legitimate source passing with alignment (A safe rollout: p=none to quarantine to reject, When you are ready for p=quarantine, When you are ready for p=reject). If staff also send from Microsoft 365 or Google Workspace on the same domain, confirm those streams too (DMARC for Microsoft 365, DMARC for Google Workspace). The same goes for HubSpot sales and inbox mail, which take a different path from marketing email.

Showing your logo (BIMI) after enforcement

BIMI is a DNS record on your domain, not a HubSpot setting, and nobody "certifies" a HubSpot domain. HubSpot's part is to keep signing marketing mail with aligned DKIM for your From domain. Everything else happens on the domain, and only once DMARC is at enforcement: p=quarantine or p=reject. That's the policy setting. It's separate from strict alignment, which is a different pair of tags (Relaxed vs strict alignment).

You'll need your logo as an SVG Tiny PS file (SVG Tiny PS logo requirements). Gmail requires a VMC or a CMC before it shows the logo, while Yahoo doesn't require a certificate. Display is always up to the mailbox provider, and Microsoft hasn't documented BIMI logo display in Outlook.com or Microsoft 365. A CMC can be based on prior use: the logo has appeared on your own website for at least 12 months, which is checked through the Internet Archive. The official requirements list other routes as well. A VMC is based on a registered trademark; see VMC certificate, and for choosing between them, is a VMC still worth it now that CMC exists.

For the HubSpot side of the story, read BIMI with HubSpot. The requirements are in BIMI requirements checklist, the move from enforcement to BIMI in How to move from DMARC enforcement to BIMI, why DMARC comes first in What is BIMI, and why DMARC comes first, and what to check when the logo doesn't appear in Why your BIMI logo is not showing.

Free DMARC account

Not sure which sender is failing?

Connect your domain's DMARC reports and see every service that sends as your domain, and whether each one passes SPF, DKIM and DMARC.

  • Every sending source in one dashboard
  • SPF, DKIM and alignment results per sender
  • No XML files to read

Create a free DMARC accountTalk to an expert

FAQ

How do I add HubSpot to my SPF record?

Edit your existing SPF TXT record and add the include value shown in your HubSpot portal, before the ~all. Don't create a second SPF record, and check you're still within 10 lookups.

Why is HubSpot SPF failing?

Common causes are a second SPF record, an include copied from somewhere other than your portal, or a record that now needs more than 10 lookups (Two SPF records, The 10-lookup limit and SPF permerror). If SPF passes but doesn't align, that's usually the shared-network Return-Path, and aligned DKIM covers it.

Can I customize the Return-Path in HubSpot?

Not on HubSpot's shared network. You can with the dedicated IP add-on or the transactional email add-on. DKIM still aligns without it.

HubSpot says the domain is Authenticated. Does DMARC pass?

Not automatically. Check your aggregate reports for HubSpot marketing mail passing DKIM with alignment.

Do sales emails use the same authentication?

Not necessarily. One-to-one and conversations inbox mail don't use the marketing sending domain. Sales sequences often use a connected mailbox. Check each of those streams on its own.

HubSpot asked me to add a DMARC record, and I already have one. What do I do?

Keep your existing record and its rua. A subdomain can inherit the root domain's policy, so you may not need a record on the subdomain at all. Don't add a second _dmarc TXT.