HubSpot: authenticate your email sending domain
What this guide is for
HubSpot sends your marketing emails from its own servers. Until your domain is connected, the DKIM signature uses a HubSpot domain: messages are not aligned with your From address for DMARC, and Gmail, Yahoo or Outlook may treat them with suspicion. Connecting your email sending domain lets HubSpot sign your emails with your own domain.
This guide summarizes the procedure from HubSpot's official documentation. Exact labels may vary with your subscription and account language.
Expected records
HubSpot generates values that are specific to your account. Always copy them from HubSpot: never reuse values from another account.
| Type | Name (host) | Value |
|---|---|---|
| CNAME | hs1-<Hub ID>._domainkey |
provided by HubSpot, ends with dkim.hubspotemail.net |
| CNAME | hs2-<Hub ID>._domainkey |
provided by HubSpot, ends with dkim.hubspotemail.net |
| TXT (SPF) | your domain (@) |
your existing SPF record, with the include shown by HubSpot (form include:<Hub ID>.spf0X.hubspotemail.net) |
| TXT (DMARC) | _dmarc |
v=DMARC1; p=none; rua=mailto:[email protected] |
<Hub ID>is the numeric ID of your HubSpot account, for examplehs1-123456._domainkey.- Both DKIM CNAME records are required: HubSpot uses them for key rotation.
- Each sending domain or subdomain gets its own pair of CNAME records.
SPF: a single record
The domain must have only one SPF record. If you already have one, add HubSpot's include to the existing record instead of creating a second one, for example:
v=spf1 include:_spf.google.com include:123456.spf03.hubspotemail.net ~all
Keep your current qualifier (~all) and watch the SPF limit of 10 DNS lookups. According to HubSpot's documentation, the include is not required in every case: DMARC alignment of marketing emails relies first on the DKIM signature.
Steps in HubSpot
- In HubSpot, click the settings icon (gear) in the navigation bar.
- In the left sidebar, open Content > Domains & URLs. In older accounts, the menu may be named Website > Domains & URLs.
- Open the Email Sending tab and click Connect an email sending domain.
- Enter the From address you use in your emails. The connected domain must match the part after the
@: if you send from[email protected], connectnews.example.com. - HubSpot displays the records to create. Add them at your DNS host (see the precautions below), then return to HubSpot.
- Click Verify. DNS updates usually take 10 to 70 minutes, but can take up to 48 hours. The domain is authenticated once every record is validated.
DNS host precautions
- Domain added twice: some hosts (GoDaddy, Network Solutions...) automatically append your domain to the name. In that case, enter only
hs1-123456._domainkey, noths1-123456._domainkey.example.com. The same issue can affect the value: remove the extra domain. - Cloudflare: turn off the proxy (orange cloud) on the CNAME records and domain-wide CNAME flattening, otherwise HubSpot cannot see the records.
- Website subdomain: a subdomain that already hosts HubSpot content (e.g.
www) cannot be connected as an email sending domain.
Link tracking subdomain
- Marketing emails: by default, the click tracking domain is your connected email sending domain. With the Brands add-on, each brand can have its own tracking domain, set in the marketing email tracking settings. A change only applies to emails not yet sent.
- Sales and service (one-to-one) emails: tracked links use a HubSpot domain unless you connect a custom tracking domain (one per account). HubSpot then provides a CNAME record to create for that subdomain.
The exact menus for these two settings are not repeated here: follow the HubSpot documentation linked at the bottom of this page.
Check the setup
- In Settings > Content > Domains & URLs > Email Sending, the domain should show as connected and authenticated.
- Send a test email to a Gmail address, open Show original and check for
DKIM: PASSwith your domain (header.d=example.com). - Run a new scan in this tool. Note that
hs1-<Hub ID>selectors contain the account ID: they cannot be guessed and are only found if the tool knows them.
DMARC
Publish a single TXT record at _dmarc.<your domain>, starting with monitoring:
v=DMARC1; p=none; rua=mailto:[email protected]
Read the reports for a few weeks and check that every tool sending on your behalf (HubSpot, mailbox provider, billing...) passes DKIM or SPF with your domain. Then move gradually to p=quarantine, then p=reject. Never tighten the policy in one step.