Skip to content
Domains & URLs

Connect your email sending domain

Last updated: August 13, 2021

Applies to:

Marketing Hub Starter, Professional, Enterprise
Service Hub Professional, Enterprise
Legacy Marketing Hub Basic

If you want to send marketing emails from your own domain, such as info@yourdomain.com, you can connect your email sending domain to HubSpot. This will give HubSpot permission to send emails on your behalf by connecting an email sending domain for DKIM (Domain Keys Identified Mail) email authentication. 

Connecting your email sending domain will help prevent your marketing emails from getting caught in spam filters, and will also remove the via HubSpot text that appears in the sender information at the top of your marketing emails. You can connect multiple email sending domains, as long as you own and have access to each domain.

To watch an overview of this process, check out the video below:


If you have any trouble after following the steps below, check out our troubleshooting guide.

Please note:

  • If you're using Cloudflare to configure your email sending domain, to verify DNS records:
    • Domain-wide CNAME flattening must not be enabled.
    • Proxy settings must not be enabled. In your DNS records under Proxy status, check that the Cloudflare logo is grey rather than orange.
  • You can connect a subdomain, like info.domain.com, as your email sending domain. The subdomain you connect should match the domain in the From email address you're using to send marketing emails in HubSpot.

 

To start the domain connection process:

  • In your HubSpot account, click the settings icon settings in the main navigation bar.

  • In the left sidebar menu, navigate to Website > Domains & URLs.

  • Click Connect a domain.

  • In the dialog box, select Email Sending, then click Connect. You'll then be directed to the domain connection screen.

connect-email-sending-domain

Select domain

  • On the domain connection screen, enter the email address you use to send marketing emails from this domain, then click Next
  • On the next screen, verify that the email sending domain is correct, then click Next

Verify URLs

The final step involves setting up hosting with your DNS provider:

  • In a separate tab, log in to your DNS provider. Then select the I'm logged in checkbox in HubSpot. 
  • In the main navigation menu of your DNS provider, go to DNS > DNS settings. If you're not sure where to locate your DNS settings, reference the steps below for general instructions, or reach out directly to your DNS provider. If you are uncomfortable making these changes yourself, send this article to your IT team. When you're in your DNS settings, select the I'm there checkbox in HubSpot. 
  • In the Update your DNS records section in HubSpot, click Copy next to the value in the Host (Name) column and paste it into the corresponding field in your DNS provider account. Then click Copy next to the value in the Value column and paste it into the corresponding field.
    • If you're connecting a subdomain you should append it to _domainkey

Please note: some providers, such as Network Solutions or GoDaddy, will add your brand domain and top level domain to the end of these DNS records automatically. For example, if you enter {hsdomainkey}.yourdomain.com, it will turn that value to {hsdomainkey}.yourdomain.com.yourdomain.com, which will result in a DNS error. Instead, copy the value but remove the .yourdomain.com part into the corresponding field in your DNS provider account.


  • When you're done updating the values in your DNS provider, select the Done checkbox in HubSpot. new-update-cname-records-section
  • If your DNS records are set up correctly, you'll see a Verified message letting you know your email sending domain is verified. This can take up to 24 hours to take effect everywhere in the world. Once you see the Verified message, click Done
  • If your DNS records still need to be set up or are still processing, you'll see a Record invalid error displayed to the right of one or all of your records. Click check them again to see if the changes have propagated.
new-verify-cname-records-section