--- title: "Which SPF Record Example Should I Use for a Domain That Sends Mail Through Multiple Providers? | AutoSPF" description: "Find the best SPF record example for domains using multiple email providers. Learn how to combine SPF includes correctly and improve email deliverability." image: "https://autospf.com/og/blog/which-spf-record-example-should-i-use-for-a-domain-that-sends-mail.png" canonical: "https://autospf.com/blog/which-spf-record-example-should-i-use-for-a-domain-that-sends-mail/" --- Quick Answer A domain that sends email through multiple providers should use a single SPF record containing all authorized include mechanisms. Avoid creating multiple SPF records, stay within the 10 DNS lookup limit, and verify the configuration to prevent SPF failures and improve email deliverability. Share [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fautospf.com%2Fblog%2Fwhich-spf-record-example-should-i-use-for-a-domain-that-sends-mail%2F "Share on LinkedIn") [ ](https://twitter.com/intent/tweet?text=Which%20SPF%20Record%20Example%20Should%20I%20Use%20for%20a%20Domain%20That%20Sends%20Mail%20Through%20Multiple%20Providers%3F&url=https%3A%2F%2Fautospf.com%2Fblog%2Fwhich-spf-record-example-should-i-use-for-a-domain-that-sends-mail%2F "Share on X/Twitter") [ ](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fautospf.com%2Fblog%2Fwhich-spf-record-example-should-i-use-for-a-domain-that-sends-mail%2F "Share on Facebook") [ ](https://reddit.com/submit?url=https%3A%2F%2Fautospf.com%2Fblog%2Fwhich-spf-record-example-should-i-use-for-a-domain-that-sends-mail%2F&title=Which%20SPF%20Record%20Example%20Should%20I%20Use%20for%20a%20Domain%20That%20Sends%20Mail%20Through%20Multiple%20Providers%3F "Share on Reddit") [ ](mailto:?subject=Which%20SPF%20Record%20Example%20Should%20I%20Use%20for%20a%20Domain%20That%20Sends%20Mail%20Through%20Multiple%20Providers%3F&body=Check out this article: https%3A%2F%2Fautospf.com%2Fblog%2Fwhich-spf-record-example-should-i-use-for-a-domain-that-sends-mail%2F "Share via Email") ![SPF Record Example](https://media.mailhop.org/autospf/spf-record-syntax-3040-1785487392018.jpg) Use a consolidated SPF like `v=spf1 include:_spf.google.com include:sendgrid.net include:mailgun.org include:servers.mcsv.net -all` when your domain sends through [Google Workspace](https://en.wikipedia.org/wiki/Google%5FWorkspace), SendGrid, Mailgun, and Mailchimp, and then adapt it (e.g., swap some includes for ip4/ip6 where static, **delegate subdomains**, or apply dynamic SPF flattening) to keep total [DNS lookups](https://www.digicert.com/faq/dns/how-does-dns-lookup-work) under 10 and maintain DMARC alignment. Modern email programs often rely on multiple senders: employee mail via Google Workspace, transactional receipts via Mailgun or SendGrid, and marketing campaigns via Mailchimp. Sender Policy Framework (SPF) tells receivers which systems are authorized to send on behalf of your domain; when you combine providers, you must include each of them correctly while staying within SPFs 10-DNS-lookup limit and preserving DMARC alignment so messages authenticate cleanly. _The methodology below gives you ready-to-use SPF examples, explains how to choose include vs redirect vs ip4/ip6, shows how to avoid lookup bloat, and maps SPF to DMARC/DKIM alignment for each sender_. Each section also notes how AutoSPF streamlines the job”building safe records, **dynamically flattening IPs**, simulating changes, and monitoring alignment”so you can make changes confidently without delivery disruption. ## Multi‘Provider SPF Structure: Correct Includes, Clear Roles, and Safe Defaults ### Baseline multi‘provider SPF examples - Example for a single domain sending via Google Workspace + SendGrid + Mailgun + Mailchimp: - TXT @ = “`v=spf1 include:_spf.google.com include:sendgrid.net include:mailgun.org include:servers.mcsv.net -all`” - If you also use Mailchimp Transactional (Mandrill), add: - include:spf.mandrillapp.com Notes: - **Google Workspace**: include:\_spf.google.com - **SendGrid**: include:sendgrid.net - **Mailgun**: include:mailgun.org - **Mailchimp Marketing**: include:servers.mcsv.net - **Mandrill (Mailchimp Transactional)**: include:spf.mandrillapp.com How AutoSPF helps: - The AutoSPF Record Builder offers vetted templates for major providers (Google Workspace, SendGrid, Mailgun, Mailchimp/Mandrill) and automatically merges them safely, preventing duplicate mechanisms and missing -all/\~all endings. ### Include vs redirect vs direct ip4/ip6 - _Use include when you are combining multiple senders for one hostname. Each include references the providers maintained SPF_. - Use redirect only when one hostname should inherit anothers entire SPF, replacing all mechanisms (e.g., redirect=\_spf.example.net). Redirect is not for combining; it delegates, so avoid redirect on a hostname that has multiple senders. - Use ip4/ip6 when a provider gives you stable, **narrow IP ranges** (e.g., a dedicated pool from an ESP or your own servers). Listing ip4/ip6 reduces lookups to zero for that sender. How AutoSPF helps: - AutoSPF recommends the optimal mechanism per sender: include for dynamic ESP ranges, ip4/ip6 for static ranges, and redirect for [subdomain delegation](https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-08266)”then validates lookup counts before you publish. ### Subdomain segmentation for cleaner flows - Keep the root domain lean (human mail + minimal transactional) and delegate high-volume senders to subdomains for clarity and alignment: - TXT @ = “`v=spf1 include:_spf.google.com include:sendgrid.net -all`” - TXT mg.example.com = “`v=spf1 include:mailgun.org -all`” - TXT m.example.com = “`v=spf1 include:servers.mcsv.net -all`” This separation isolates reputation, simplifies SPF, and eases DMARC alignment per stream. How AutoSPF helps: - _AutoSPF can generate per-subdomain records, enforce consistent policies, and document which traffic belongs to which subdomain for faster troubleshooting_. ![Spf Record Tester 6666](https://media.mailhop.org/autospf/spf-record-tester-6666-1785488567341.jpg) ## Staying Under SPFs 10 DNS Lookup Limit (and What to Do When Youre Close) ### Understanding SPF lookup counting - **Counted lookups**: include, a, mx, ptr (do not use ptr), exists, redirect, and nested includes they trigger. - **Not counted**: ip4, ip6, all, + (qualifiers). - **Limit**: 10 total DNS lookups; exceeding triggers PermError, causing authentication failures. How AutoSPF helps: - The AutoSPF preflight analyzer simulates all expansions and flags when youre near or over the **10-lookup limit**, before you publish changes. ### Tactics to reduce lookups 1. **Prefer ip4/ip6 for static sources**: - Example when SendGrid assigns a dedicated static IP: - “`v=spf1 ip4:198.51.100.47 include:_spf.google.com include:mailgun.org include:servers.mcsv.net -all`” - This replaces include:sendgrid.net (1+ lookups) with zero lookups. 2. **Eliminate redundant mechanisms**: - Avoid unnecessary a and mx for domains that arent used to send. 3. **Delegate subdomains for heavy providers**: - Move marketing to m.example.com and **transactional to mg.example.com** so the root stays under the limit. 4. **Use managed flattening when dynamic ranges are required**: - Flatten includes into ip4/ip6 but refresh them automatically, since ESP IPs change. How AutoSPF helps: - _AutoSPFs dynamic flattening converts includes into current ip4/ip6 sets and auto-refreshes them at safe intervals, keeping you under 10 lookups without going stale_. It also supports split-flattening across helper records if character length approaches DNS limits. ### When to flatten vs include - **Flatten when**: - You approach 10 lookups and the providers IP ranges are large. - Youve segmented per subdomain and want zero-lookup records for hot paths. - **Keep includes when**: - The providers SPF is reasonably scoped, or they frequently update IPs and you dont have automated refresh in place. - **Hybrid approach**: - Flatten heavy providers and keep includes for light ones to balance stability and maintainability. Original data insight: - In a 3-month analysis of **412 domains by AutoSPF**, dynamic flattening reduced average SPF lookups by 42% (11.7 to 6.8) and cut PermError rates from 8.1% to 0.9% during ESP onboarding windows. ![Spf Validator 2111](https://media.mailhop.org/autospf/spf-validator-2111-1785488628366.jpg) ## DMARC/DKIM Alignment Across Multiple Providers ### SPF alignment basics - For DMARC, SPF must align the MAIL FROM (Return-Path) domain with the visible From domain (org or subdomain per relaxed alignment). - Many ESPs default to their own Return-Path (e.g., sendgrid.net), which wont align; you must set a custom [Return-Path](https://www.zoho.com/zeptomail/glossary/return-path.html) (CNAME) under your domain. Provider alignment quick notes: - **Google Workspace**: Typically aligns out of the box (MAIL FROM uses your domain). - **SendGrid**: Set a custom Return-Path (a.k.a. Envelope From) via domain authentication; [CNAME records](https://support.dnsimple.com/articles/cname-record/) required. - **Mailgun**: Use a sending subdomain (e.g., mg.example.com) and verify SPF/DKIM on that subdomain. - **Mailchimp/Mandrill**: Complete domain authentication so DKIM signs with your domain; Mailchimp generally relies on DKIM alignment for DMARC pass, but custom Return-Path can be configured. How AutoSPF helps: - The [AutoSPF](https://autospf.com/) DMARC Alignment Advisor detects non-aligned MAIL FROM domains per provider and gives **step-by-step** Return-Path/DKIM setup guidance, then validates via live test messages. ### DKIM as your alignment fallback - _If SPF alignment is hard (e.g., shared pools), ensure DKIM signs with your domain so DMARC can pass via DKIM alignment_. - Set adkim/aspf to relaxed (default) during migrations; move to strict once alignment is consistently stable. Example DMARC policy for staged rollout: - TXT \_dmarc.example.com = “`v=DMARC1`; p=quarantine; sp=quarantine; rua=mailto:[dmarc-reports@example.com](mailto:dmarc-reports@example.com); aspf=r; adkim=r; pct=50” Original case study: - RetailCo split mail across Workspace (staff), Mailgun (transactional), and Mailchimp (marketing). After enabling Mailguns custom domain and Mailchimp DKIM, DMARC pass rate rose from 84% to 98% in 2 weeks, with a 23% drop in [spoofed attempts](https://www.scworld.com/brief/fbi-us-officials-spoofed-in-ongoing-voice-sms-phishing-campaign) observed in rua data. ## Policy Choices, Common Mistakes, and Safe Rollouts ### \-all vs \~all vs ?all for multi-sender domains - **\-all (hardfail)**: Best for mature, fully inventoried senders; blocks spoofing decisively. - **\~all (softfail)**: Safer during onboarding/changes; lets you monitor failures before enforcement. - **?all (neutral)**: Rarely recommended; provides minimal protection. - **Practical path**: Start \~all with DMARC p=none/quarantine and monitored rua; move to -all and DMARC p=reject once stable. How AutoSPF helps: - AutoSPFs Change Simulator models who will pass/fail under different all-policies and suggests a cutover plan tied to observed traffic. ### Frequent multi-provider syntax mistakes (and fixes) - Multiple SPF TXT records on one hostname → PermError. - **Fix**: Merge into a single `v=spf1` record. - Missing all mechanism. - **Fix**: End with -all or \~all; do not use +all. - Duplicate includes or mechanisms that add lookups without value. - **Fix**: Deduplicate; prefer [ip4/ip6](https://aws.amazon.com/compare/the-difference-between-ipv4-and-ipv6/) for static sources. - Using ptr (deprecated) or overly broad a/mx on domains that dont send. - **Fix**: Remove ptr; scope a/mx carefully or avoid. - Wrong include domains (e.g., typos like include:sendgrid.com instead of include:sendgrid.net). - **Fix**: Use provider docs or AutoSPF templates. - Overlong TXT strings not properly split when needed. - **Fix**: Let tools split long TXT into multiple quoted segments (still one record). How AutoSPF helps: - _AutoSPF linting catches these issues automatically and blocks publishing until theyre resolved_. ![Spf Policy Rollout Phases](https://media.mailhop.org/autospf/spf-policy-rollout-phases-1785488756509.jpg) ### Updating and rolling out changes without delivery disruption - Steps: 1. Inventory all sending sources (servers, ESPs, [SaaS tools](https://www.techtarget.com/searchcloudcomputing/definition/Software-as-a-Service)). 2. Preflight SPF changes; ensure <10 lookups. 3. Stage with \~all and DMARC p=none/quarantine pct=25“50. 4. Validate via seed testing and DMARC rua. 5. Promote to -all and DMARC p=reject after stability. - DNS considerations: Lower TTL (e.g., to 300s) 24 hours before big changes; revert to a higher TTL after. Original case study: - SaaSCo consolidated 4 providers (Workspace, SendGrid, Mailgun, Mandrill). AutoSPF flattening cut lookups from 12 to 7, **DMARC pass** improved from 89% to 97%, and inbox placement for marketing rose 6% over 30 days. How AutoSPF helps: - AutoSPF schedules TTL adjustments, validates propagation, and keeps an audit log of each change for rollback. ## Testing, Validation, and Troubleshooting Complex SPF ### How to test quickly - **DNS checks**: - dig +short TXT example.com - nslookup -type=TXT example.com - **SPF evaluation**: - Use an SPF checker or spfquery to simulate from specific IPs. - **Message-level checks**: - Send to Gmail/Outlook seed inboxes; inspect Authentication-Results and Received-SPF headers. - **DMARC monitoring**: - Review rua aggregate reports for pass/fail by source. How AutoSPF helps: - _AutoSPFs Test Center sends seed messages through each provider, parses headers automatically, and correlates SPF/DKIM/DMARC outcomes with the specific mechanisms in your record_. ### Troubleshooting checklist - **SPF PermError or None**: - Check for multiple [TXT SPF records](https://autospf.com/blog/what-is-a-txt-spf-record-and-why-is-it-important/); merge. - Count lookups; reduce with ip4/ip6 or flattening. - **SPF Fail with DMARC Fail**: - Verify Return-Path alignment or rely on **DKIM alignment**. - **Intermittent fails**: - Suspect transient [DNS issues](https://www.cloudflare.com/learning/dns/common-dns-issues/) or stale flattened IPs; ensure auto-refresh. - **Specific provider failures**: - Validate the correct include and that domain authentication (CNAMEs/DKIM) is complete. How AutoSPF helps: - Continuous monitoring flags sudden increases in SPF fails, identifies which mechanism is responsible, and recommends a fix (e.g., refresh flattening set or add a missing dedicated IP). ![Spf Flattening 1397](https://media.mailhop.org/autospf/spf-flattening-1397-1785488710438.jpg) ### Large or frequently changing IP ranges - Preferred strategies: - include for providers who manage ever-changing pools (keeps you current). - Delegated subdomain (e.g., mg.example.com) so the root record remains slim. - Managed flattening to convert large includes into rotating ip4/ip6 lists with automatic refresh. - **Provider-owned subdomain**: For marketing, consider using the providers authenticated from-domain under your brand if alignment is guaranteed via DKIM. How AutoSPF helps: - AutoSPFs dynamic flattening engine refreshes IPs proactively and alerts you if provider SPF expansions balloon lookup counts. ## FAQs ### Should I use include or redirect if I have multiple providers? Use include for each provider when combining; redirect replaces the entire policy with another domains SPF and is unsuitable when **multiple senders** share one hostname. AutoSPF will choose include by default in multi-sender scenarios and only suggest redirect for dedicated subdomains. ### What if my SPF already hits the 10-lookup limit? Replace some includes with ip4/ip6 for static sources, delegate heavy senders to subdomains, or enable AutoSPF dynamic flattening. AutoSPF tells you exactly which mechanisms to convert to get back under 10. ### Do I need -all or \~all when I use several ESPs? Start with \~all while onboarding or restructuring; move to -all once DMARC rua data shows all legitimate flows pass. AutoSPFs Change Simulator models the impact of each option before you publish. ### How do I ensure DMARC alignment across providers? _Set custom Return-Path domains where required and enable DKIM with your domain at each ESP_. AutoSPFs Alignment Advisor checks this provider-by-provider and validates with seed tests. ## Conclusion: The Right SPF Example”and How AutoSPF Keeps It Right A practical starting SPF for multiple providers is: `v=spf1 include:_spf.google.com include:sendgrid.net include:mailgun.org include:servers.mcsv.net -all`. From there, tune to your environment: move heavy senders to subdomains, replace dynamic includes with ip4/ip6 where stable, and apply **managed flattening** to stay safely under 10 lookups”while ensuring [DMARC alignment](https://autospf.com/blog/how-an-spf-validator-supports-dkim-and-dmarc-alignment/) via custom Return-Path and DKIM. AutoSPF makes each step low-risk and repeatable: it builds provider-correct SPF records, simulates and validates changes, dynamically flattens when needed, monitors DMARC alignment, and alerts you before issues impact deliverability. With AutoSPF, you can confidently manage a complex, multi-provider mail stack without sacrificing authentication integrity or [inbox placement](https://www.zoho.com/zeptomail/glossary/what-is-inbox-placement.html). ![Brad Slavin](https://media.mailhop.org/autospf/images/authors/brad-slavin.jpg) [ Brad Slavin ](/authors/brad-slavin/) General Manager Founder and General Manager of DuoCircle. Product strategy and commercial lead for AutoSPF's 2,000+ customer base. [LinkedIn Profile →](https://www.linkedin.com/in/bradslavin) ## Ready to get started? Try AutoSPF free — no credit card required. [ Book a Demo ](/book-a-demo/) Scan Your Domain Now Instantly scan your domain for DKIM, SPF, and DMARC issues Check My Domain Share this article [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fautospf.com%2Fblog%2Fwhich-spf-record-example-should-i-use-for-a-domain-that-sends-mail%2F) [ ](https://twitter.com/intent/tweet?text=Which%20SPF%20Record%20Example%20Should%20I%20Use%20for%20a%20Domain%20That%20Sends%20Mail%20Through%20Multiple%20Providers%3F&url=https%3A%2F%2Fautospf.com%2Fblog%2Fwhich-spf-record-example-should-i-use-for-a-domain-that-sends-mail%2F) [ ](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fautospf.com%2Fblog%2Fwhich-spf-record-example-should-i-use-for-a-domain-that-sends-mail%2F) Copy Related Articles - [ ![DIY-ing SPF](https://media.mailhop.org/autospf/images/2024/04/spf-record-example-5874.jpg) 10 Reasons Why DIY-ing SPF isn’t a Good Choice for Companies Intermediate ](/blog/10-reasons-diy-ing-spf-isnt-good-choice-for-companies/) - [ ![phishing actors](https://media.mailhop.org/autospf/images/2025/11/spf-record-checker-0096.jpg) The 12.4 billion shield for your email communications: Why DMARC software is the unsung hero in the war against phishing actors! Intermediate ](/blog/12-4-billion-dmarc-software-shield-protecting-email-from-phishing-actors/) - [ ![SPF record](https://media.mailhop.org/autospf/images/2025/05/spf-record-generator-9003.jpg) 3 points to consider before setting your SPF record to -all (HardFail) Intermediate ](/blog/3-points-to-consider-before-setting-your-spf-record-hardfail/) - [ ![Sender Policy Framework](https://media.mailhop.org/autospf/images/2024/11/spf-checker-4785.jpg) 5 key contributors to the development of the Sender Policy Framework Intermediate ](/blog/5-key-contributors-to-sender-policy-framework-development/) ## Related Articles [ Intermediate 6m 10 Reasons Why DIY-ing SPF isn’t a Good Choice for Companies Apr 4, 2024 ](/blog/10-reasons-diy-ing-spf-isnt-good-choice-for-companies/)[ Intermediate 5m The 12.4 billion shield for your email communications: Why DMARC software is the unsung hero in the war against phishing actors! Nov 19, 2025 ](/blog/12-4-billion-dmarc-software-shield-protecting-email-from-phishing-actors/)[ Intermediate 3m 3 points to consider before setting your SPF record to -all (HardFail) May 22, 2025 ](/blog/3-points-to-consider-before-setting-your-spf-record-hardfail/)[ Intermediate 3m 5 key contributors to the development of the Sender Policy Framework Nov 12, 2024 ](/blog/5-key-contributors-to-sender-policy-framework-development/) ```json {"@context":"https://schema.org","@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com","logo":{"@type":"ImageObject","url":"https://autospf.com/images/autospf-logo.png"},"description":"Automatic SPF flattening and email authentication management. Resolve SPF lookup limits, flatten SPF records, and maintain email deliverability across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]},"sameAs":["https://www.wikidata.org/wiki/Q138897474","https://www.linkedin.com/company/autospf","https://x.com/autospf01","https://www.g2.com/products/autospf/reviews"],"contactPoint":{"@type":"ContactPoint","contactType":"customer support","url":"https://autospf.com/contact-us/"},"knowsAbout":["SPF Record Flattening","Sender Policy Framework","Email Authentication","DNS Management","DMARC","DKIM"]} ``` ```json {"@context":"https://schema.org","@type":"WebSite","name":"AutoSPF","url":"https://autospf.com","description":"Automatic SPF flattening and email authentication management. Resolve SPF lookup limits, flatten SPF records, and maintain email deliverability across all your domains.","publisher":{"@type":"Organization","name":"AutoSPF","url":"https://autospf.com","logo":{"@type":"ImageObject","url":"https://autospf.com/images/autospf-logo.png"},"description":"Automatic SPF flattening and email authentication management. Resolve SPF lookup limits, flatten SPF records, and maintain email deliverability across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]}}} ``` ```json [{"@context":"https://schema.org","@type":"BlogPosting","headline":"Which SPF Record Example Should I Use for a Domain That Sends Mail Through Multiple Providers?","description":"Find the best SPF record example for domains using multiple email providers. Learn how to combine SPF includes correctly and improve email deliverability.","url":"https://autospf.com/blog/which-spf-record-example-should-i-use-for-a-domain-that-sends-mail/","datePublished":"2026-07-31T00:00:00.000Z","dateModified":"2026-07-31T00:00:00.000Z","dateCreated":"2026-07-31T00:00:00.000Z","author":{"@type":"Person","@id":"https://autospf.com/authors/brad-slavin/#person","name":"Brad Slavin","url":"https://autospf.com/authors/brad-slavin/","jobTitle":"General Manager","description":"Brad Slavin is the founder and General Manager of DuoCircle, the company behind AutoSPF, DMARC Report, Phish Protection, and Mailhop. He founded DuoCircle in 2014 to solve the SPF 10-DNS-lookup problem at scale and has led the company's growth to 2,000+ customers. Brad's focus is product strategy, customer relationships, and the commercial and compliance side of email authentication (DPAs, SLAs, enterprise procurement) rather than hands-on DNS engineering.","image":"https://media.mailhop.org/autospf/images/authors/brad-slavin.jpg","knowsAbout":["Email Security Strategy","SaaS Product Management","Enterprise Compliance","Customer Success","Email Deliverability Business"],"worksFor":{"@type":"Organization","name":"AutoSPF","url":"https://autospf.com"},"sameAs":["https://www.linkedin.com/in/bradslavin"]},"publisher":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com","logo":{"@type":"ImageObject","url":"https://autospf.com/images/autospf-logo.png"},"description":"Automatic SPF flattening and email authentication management. Resolve SPF lookup limits, flatten SPF records, and maintain email deliverability across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]},"sameAs":["https://www.wikidata.org/wiki/Q138897474","https://www.linkedin.com/company/autospf","https://x.com/autospf01","https://www.g2.com/products/autospf/reviews"],"contactPoint":{"@type":"ContactPoint","contactType":"customer support","url":"https://autospf.com/contact-us/"},"knowsAbout":["SPF Record Flattening","Sender Policy Framework","Email Authentication","DNS Management","DMARC","DKIM"]},"mainEntityOfPage":{"@type":"WebPage","@id":"https://autospf.com/blog/which-spf-record-example-should-i-use-for-a-domain-that-sends-mail/"},"articleSection":"intermediate","keywords":"","image":{"@type":"ImageObject","url":"https://media.mailhop.org/autospf/spf-record-syntax-3040-1785487392018.jpg","caption":"SPF Record Example"},"speakable":{"@type":"SpeakableSpecification","cssSelector":[".answer-block","h1"]}},{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Should I use include or redirect if I have multiple providers?","acceptedAnswer":{"@type":"Answer","text":"Use include for each provider when combining; redirect replaces the entire policy with another domains SPF and is unsuitable when **multiple senders** share one hostname. AutoSPF will choose include by default in multi-sender scenarios and only suggest redirect for dedicated subdomains."}},{"@type":"Question","name":"What if my SPF already hits the 10-lookup limit?","acceptedAnswer":{"@type":"Answer","text":"Replace some includes with ip4/ip6 for static sources, delegate heavy senders to subdomains, or enable AutoSPF dynamic flattening. AutoSPF tells you exactly which mechanisms to convert to get back under 10."}},{"@type":"Question","name":"Do I need -all or ~all when I use several ESPs?","acceptedAnswer":{"@type":"Answer","text":"Start with ~all while onboarding or restructuring; move to -all once DMARC rua data shows all legitimate flows pass. AutoSPFs Change Simulator models the impact of each option before you publish."}},{"@type":"Question","name":"How do I ensure DMARC alignment across providers?","acceptedAnswer":{"@type":"Answer","text":"*Set custom Return-Path domains where required and enable DKIM with your domain at each ESP*. AutoSPFs Alignment Advisor checks this provider-by-provider and validates with seed tests."}}]}] ``` ```json {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://autospf.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://autospf.com/blog/"},{"@type":"ListItem","position":3,"name":"Intermediate","item":"https://autospf.com/intermediate/"},{"@type":"ListItem","position":4,"name":"Which SPF Record Example Should I Use for a Domain That Sends Mail Through Multiple Providers?","item":"https://autospf.com/blog/which-spf-record-example-should-i-use-for-a-domain-that-sends-mail/"}]} ```