SPF for Multiple Email Services
Learn how to combine multiple email services in one SPF record. Manage DNS lookup limits, prioritize providers, and avoid breaking your email authentication.
You Use Five Email Services and Your SPF Record Is Broken
Your company sends email through Google Workspace for corporate mail, SendGrid for transactional alerts, Mailchimp for marketing newsletters, HubSpot for sales outreach, and Zendesk for support tickets. Each one told you to "add their SPF include." You added them all. And now your SPF record exceeds the DNS lookup limit, silently failing for every email you send.
The Multiple Sender Problem
SPF has a hard limit: 10 DNS lookups per record. Each include: mechanism triggers at least one lookup, and many providers chain additional lookups behind the scenes. Google Workspace alone uses 3-4 lookups. Add a few more services and you blow past the limit without any warning in your DNS.
Here's what goes wrong:
- Too many includes exceed the 10-lookup limit, causing a
permerror— receiving servers treat this as an SPF failure - You can only have one SPF TXT record per domain — creating separate records for each service breaks all of them
- There's no error message when you exceed the limit. Your DNS provider accepts the record just fine. You only find out when emails start bouncing or landing in spam.
The 10-lookup limit is defined in RFC 7208 and is strictly enforced by most mail servers. There's no way to request an exception. If your record exceeds 10 lookups, SPF evaluation stops and returns permerror.
How SPF Creator Helps
Live lookup counter
As you add providers, SPF Creator counts the total DNS lookups in real time. You see exactly when you're approaching the limit — before you publish anything.
Multi-provider merge
Select all your services from one interface. SPF Creator combines them into a single, valid record with proper syntax.
Provider library
Common providers are pre-configured with the correct include values. No more hunting through documentation for the right string.
Validation before publishing
SPF Creator checks for duplicate includes, syntax errors, and lookup overflows before you copy the record.
Keep your multi-service SPF record healthy
Monitor all your email authentication records daily and get alerts when something breaks.
Managing Multiple Providers Step by Step
List all your sending services
Inventory every system that sends email from your domain. Include corporate email (Google Workspace, Microsoft 365), transactional services (SendGrid, Postmark), marketing platforms (Mailchimp, Klaviyo), CRM (HubSpot, Salesforce), and support tools (Zendesk, Freshdesk).
Add each to SPF Creator
Select each provider from the dropdown or enter custom includes manually. Watch the lookup counter as you add each one.
Check the lookup count
If you're at or under 10 lookups, you're good. If you're over, you need to optimize (see strategies below).
Copy and publish
Copy the generated record and add it as a single TXT record on your root domain in your DNS provider.
Test thoroughly
Send test emails from each service and verify SPF passes in the email headers. Check the Authentication-Results header for spf=pass. Use SPF Record Check to validate your merged record before testing.
When You Hit the 10-Lookup Limit
If your providers require more than 10 lookups combined, you have several options:
Use subdomains for some services
Move specific services to send from subdomains like mail.yourdomain.com or marketing.yourdomain.com. Each subdomain gets its own SPF record with its own 10-lookup budget.
Replace includes with IP addresses
If a service sends from a small, stable set of IPs, you can use ip4: or ip6: mechanisms instead of include:. IP mechanisms don't count toward the lookup limit.
Which services have stable IPs?
Self-hosted servers and some dedicated-IP plans from services like SendGrid or Postmark have stable IPs. Shared-IP services change frequently — stick with include: for those.
Prioritize your providers
If you truly can't fit everything, prioritize the services that send the most email or the most critical email. Corporate email (Google Workspace, Microsoft 365) should always be included. Secondary marketing tools can potentially move to a subdomain.
Common Multi-Service Combinations
| Combination | Lookups (approx.) | Record |
|---|---|---|
| Google + SendGrid | 5-6 | v=spf1 include:_spf.google.com include:sendgrid.net ~all |
| Google + Mailchimp | 5-6 | v=spf1 include:_spf.google.com include:servers.mcsv.net ~all |
| M365 + SendGrid | 4-5 | v=spf1 include:spf.protection.outlook.com include:sendgrid.net ~all |
| M365 + Mailchimp + SendGrid | 6-7 | v=spf1 include:spf.protection.outlook.com include:servers.mcsv.net include:sendgrid.net ~all |
| Google + SendGrid + Mailchimp + HubSpot | 8-10 | v=spf1 include:_spf.google.com include:sendgrid.net include:servers.mcsv.net include:spf.hubspot.com ~all |
Lookup counts are approximate because providers sometimes add or remove chained lookups from their SPF records. Always verify the actual count with SPF Creator before publishing.
Once your combined SPF record is live, don't stop at SPF. Set up DKIM for each sending service and create a DMARC policy to tie everything together. Each service that sends on your behalf should have both SPF and DKIM configured.
Related Articles
Monitor Your New SPF Record
You've created your SPF record — now make sure it keeps working. The Email Deliverability Suite watches your SPF, DKIM, DMARC, and MX records daily and alerts you when something breaks.
Never miss an SPF issue
Monitor your SPF, DKIM, DMARC and MX records daily. Get alerts when something breaks.
Start Monitoring