How to Create an SPF Record for HubSpot
Learn how to create an SPF record for HubSpot. Step-by-step guide to adding the correct SPF include for marketing and sales email delivery.
HubSpot is an all-in-one CRM platform that sends a lot of email on your behalf -- marketing campaigns, sales sequences, automated workflows, and CRM notifications. If you're using HubSpot to reach customers and prospects, those emails need to pass authentication checks. Without an SPF record authorizing HubSpot, receiving mail servers may flag your messages as suspicious and route them to spam.
This guide walks you through creating the correct SPF record for HubSpot so every email -- whether it's a marketing blast or a one-to-one sales email -- lands in the inbox.
The SPF Include Value for HubSpot
Here's the include you need for HubSpot:
include:spf.hubspot.com
A complete SPF record with only HubSpot looks like this:
v=spf1 include:spf.hubspot.com -all
This single include covers all HubSpot email sending -- marketing emails, sales sequences, ticket notifications, and workflow-triggered messages. You don't need separate includes for different HubSpot hubs. See HubSpot's domain authentication guide for details.
Step-by-Step: Creating Your HubSpot SPF Record
Connect your sending domain in HubSpot
In your HubSpot account, go to Settings > Website > Domains & URLs (or Settings > Email > Configuration depending on your HubSpot version). Add your sending domain and follow the prompts. HubSpot will display the DNS records you need to add, including SPF and DKIM.
Generate your SPF record
Use the free SPF record generator to build your SPF record. Select HubSpot from the provider list and add any other services that send email from your domain -- most HubSpot users also have Google Workspace or Microsoft 365 for team email.
Log in to your DNS provider
Go to the DNS management dashboard for your domain. This might be your registrar (like GoDaddy, Namecheap, or Cloudflare) or a separate DNS host.
Check for an existing SPF record
Look through your TXT records for any entry starting with v=spf1. If one exists, you need to edit it -- not create a second one. A domain must have exactly one SPF record.
Add or update the TXT record
If you don't have an SPF record, create a new TXT record with the Name set to @ (your root domain) and the Value set to your SPF record. If you already have one, edit it and add include:spf.hubspot.com before the all mechanism.
Save and wait for propagation
Save the record. DNS changes typically take a few minutes to 48 hours to propagate depending on your provider. Cloudflare propagates in seconds; others may take longer.
Common SPF Record Combinations With HubSpot
Most HubSpot users also have a primary email provider for day-to-day communication. Here are the most common setups:
| Setup | SPF Record | Est. Lookups |
|---|---|---|
| HubSpot only | v=spf1 include:spf.hubspot.com -all | ~2 |
| HubSpot + Google Workspace | v=spf1 include:_spf.google.com include:spf.hubspot.com -all | ~5 |
| HubSpot + Microsoft 365 | v=spf1 include:spf.protection.outlook.com include:spf.hubspot.com -all | ~4 |
| HubSpot + Google + SendGrid | v=spf1 include:_spf.google.com include:spf.hubspot.com include:sendgrid.net -all | ~7 |
| HubSpot + Google + Mailchimp | v=spf1 include:_spf.google.com include:spf.hubspot.com include:spf.mandrillapp.com -all | ~7 |
SPF has a 10-lookup limit. Each include uses at least one lookup, and nested includes add more. If you're combining multiple providers, use SPF Record Check to count your total lookups and make sure you're within the limit.
Build your SPF record in seconds
Select your email providers and generate a valid SPF record -- no DNS expertise needed.
Verifying Your HubSpot SPF Record
Once DNS changes have propagated, verify that everything is working correctly.
Go to SPF Record Check and enter your domain. The tool will show your published SPF record, validate the syntax, check for duplicate records, and count DNS lookups. Confirm that include:spf.hubspot.com appears in the record and that no errors are flagged.
You can also check the status inside HubSpot. After adding DNS records, go back to your domain settings in HubSpot and click the verification button. HubSpot will check your DNS and confirm whether the SPF record (and DKIM records) are correctly published. If something is wrong, HubSpot will tell you what's missing.
For a hands-on test, send a marketing email or sales sequence message from HubSpot and inspect the email headers on the receiving end. Look for Authentication-Results: spf=pass to confirm everything is working.
Common HubSpot SPF Mistakes
Confusing HubSpot's SPF Include With Other HubSpot Domains
HubSpot uses many domains for different purposes -- tracking links, landing pages, forms, and more. The correct SPF include is spf.hubspot.com. Don't use hubspot.com, hubspot.net, or any tracking domain you might see in email headers. Only spf.hubspot.com authorizes HubSpot's mail servers.
Creating a Second SPF Record
This is the most common DNS mistake across all email providers. If you already have an SPF record for Google Workspace or Microsoft 365, don't create a new TXT record for HubSpot. Two SPF records on the same domain cause a permerror that breaks SPF entirely. Edit your existing record and add the HubSpot include alongside your other providers.
Not Connecting Your Domain in HubSpot
Adding the SPF record to your DNS is only half the setup. You also need to connect and verify your sending domain inside HubSpot's settings. Without this step, HubSpot may send emails using a shared HubSpot domain, which means your SPF record won't apply to those messages. Make sure you complete the domain connection process in HubSpot so emails go out as your domain.
Forgetting About Sales Email
HubSpot's sales tools -- sequences, one-to-one emails sent through the CRM -- also send email on behalf of your domain. The same spf.hubspot.com include covers these. But if your sales team connects their personal email accounts (like Gmail) to HubSpot, those emails may route through Google's servers instead. Check how your sales team's email is configured to make sure SPF covers the right sending path.
Complete Your Email Authentication
SPF tells receiving servers which IP addresses can send email for your domain, but it's only one layer of protection. For full email authentication, you need all three protocols working together:
- DKIM adds a cryptographic signature to each outgoing message. HubSpot supports custom DKIM by having you add CNAME records to your DNS. Use DKIM Creator to generate your DKIM configuration.
- DMARC ties SPF and DKIM together and tells receiving servers what to do when a message fails authentication. Use DMARC Creator to build your DMARC policy.
Setting up all three protocols is the best way to protect your domain from spoofing and maximize your inbox placement rates.
Related Articles
Never miss an SPF issue
Monitor your SPF, DKIM, DMARC and MX records daily. Get alerts when something breaks.
Start Monitoring