{"id":2902,"date":"2026-04-27T11:11:49","date_gmt":"2026-04-27T11:11:49","guid":{"rendered":"https:\/\/www.trulyinbox.com\/blog\/?p=2902"},"modified":"2026-04-28T05:41:58","modified_gmt":"2026-04-28T05:41:58","slug":"what-is-an-spf-record","status":"publish","type":"post","link":"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/","title":{"rendered":"What Is an SPF Record? A Complete Guide for Email Senders (With Examples)"},"content":{"rendered":"\n<p>Most email senders know they need SPF. Very few understand what it actually does or how it protects their domain.<\/p>\n\n\n\n<p>The result is predictable. Broken records, failed authentication, and emails landing in spam for reasons nobody can diagnose.<\/p>\n\n\n\n<p>I run TrulyInbox, an email warm-up tool. I have seen hundreds of domains with misconfigured SPF records. The patterns are always the same.<\/p>\n\n\n\n<p>This is not a DNS tutorial written by a security vendor. It is a practical guide for people who send email for a living.<\/p>\n\n\n\n<p>In this blog, I will cover what SPF is, how it works, how to create your record, the 10-lookup limit, and common mistakes. I will also explain how SPF fits with DKIM and DMARC.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">TL;DR: What SPF Is and Why It Matters<\/h2>\n\n\n\n<p>SPF stands for Sender Policy Framework. It is a DNS TXT record that lists which servers can send email on behalf of your domain.<\/p>\n\n\n\n<p>When someone receives an email from your domain, their server checks your SPF record. It compares the sending server&#8217;s IP against your authorized list. If it matches, SPF passes. If not, the email gets flagged or rejected.<\/p>\n\n\n\n<p>Without SPF, anyone can spoof your domain. That opens the door to phishing, spam complaints, and serious deliverability damage.<\/p>\n\n\n\n<p>Here is what a basic SPF record looks like:<\/p>\n\n\n\n<p>v=spf1 include:_spf.google.com ~all<\/p>\n\n\n\n<p>Two constraints you need to know right away. You can only have one SPF record per domain. And SPF allows a maximum of 10 DNS lookups before it breaks.<\/p>\n\n\n\n<p>SPF alone does not cover everything. DKIM and DMARC complete the authentication stack. But for cold emailers and marketers, SPF is not optional. It is the bare minimum.<\/p>\n\n\n\n<p>Below, I will break down exactly how SPF works, show you how to build your record, and walk through the mistakes I see most often.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What Is an SPF Record?<\/h2>\n\n\n\n<p>SPF stands for Sender Policy Framework. It is a DNS TXT record published on your domain that tells receiving servers which IP addresses and servers you authorize to send email on your behalf.<\/p>\n\n\n\n<p>Think of it as a guest list for your domain. Only servers on that list get permission to send email as you.<\/p>\n\n\n\n<p>Every major inbox provider checks SPF. Gmail, Outlook, Yahoo, and others all verify SPF before deciding where to place your email.<\/p>\n\n\n\n<p>The standard was formalized as RFC 7208. But you do not need to read the RFC to use SPF correctly.<\/p>\n\n\n\n<p>Here is what matters for email senders:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>SPF is a TXT record you add to your domain&#8217;s DNS settings<\/li>\n\n\n\n<li>It lists every server and IP authorized to send email from your domain<\/li>\n\n\n\n<li>Receiving servers query your DNS to verify the sender is legitimate<\/li>\n\n\n\n<li><em>If the sending server is not on the list, the email fails SPF<\/em><\/li>\n<\/ul>\n\n\n\n<p>Most guides explain SPF from the DNS admin&#8217;s perspective. That is not who this blog is for. <strong>If you send cold emails, marketing campaigns, or transactional messages, SPF directly affects whether your emails reach the inbox.<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How Does SPF Authentication Work?<\/h2>\n\n\n\n<p>SPF authentication follows a straightforward process. Every time you send an email, the receiving server runs a quick check behind the scenes.<\/p>\n\n\n\n<p>Here is the step-by-step flow:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>You send an email from your domain<\/li>\n\n\n\n<li>The receiving server extracts the domain from the return-path header<\/li>\n\n\n\n<li>It performs a DNS lookup on that domain for an SPF record<\/li>\n\n\n\n<li>It compares the sending server&#8217;s IP address against the authorized list in the SPF record<\/li>\n\n\n\n<li>It returns a result: Pass, Fail, SoftFail, Neutral, or None<\/li>\n<\/ol>\n\n\n\n<p>One critical misconception trips up most senders. <strong>SPF checks the return-path domain, not the visible &#8220;From&#8221; address.<\/strong> These are often different, and this distinction causes most SPF confusion.<\/p>\n\n\n\n<p>The return-path is a hidden <a href=\"https:\/\/www.trulyinbox.com\/blog\/email-headers\/\" target=\"_blank\" rel=\"noreferrer noopener\"><u>email header<\/u><\/a> that tells servers where to send bounce notifications. Your recipients never see it. But SPF only cares about this header.<\/p>\n\n\n\n<p>So if your return-path domain does not have SPF set up, authentication fails. It does not matter what your &#8220;From&#8221; address says.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">SPF Results Explained (Pass, Fail, SoftFail, Neutral, None)<\/h3>\n\n\n\n<p>After the SPF check runs, the receiving server gets one of five results. Each one triggers a different response.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Pass:<\/strong> The sending IP is authorized. The email is delivered normally.<\/li>\n\n\n\n<li><strong>Fail (HardFail):<\/strong> The sending IP is not authorized. The receiving server typically rejects the email outright.<\/li>\n\n\n\n<li><strong>SoftFail:<\/strong> The sending IP is not authorized, but the domain owner has not set a strict policy. The email may land in spam with a warning.<\/li>\n\n\n\n<li><strong>Neutral:<\/strong> The domain owner has made no statement about the sending IP. The server treats it as unverified.<\/li>\n\n\n\n<li><strong>None:<\/strong> No SPF record exists for the domain. The server has nothing to check against.<\/li>\n<\/ul>\n\n\n\n<p>For deliverability, <em>Pass and Fail matter most.<\/em> SoftFail is a gray zone that Gmail and Outlook increasingly treat like a Fail.<\/p>\n\n\n\n<p>When SPF fails on Gmail, the email does not always bounce. It often lands in spam with a warning banner. That is worse than a bounce because your sender reputation takes the hit silently.<\/p>\n\n\n\n<p>If you are seeing <a href=\"https:\/\/www.trulyinbox.com\/blog\/bounced-emails\/\" target=\"_blank\" rel=\"noreferrer noopener\"><u>bounced emails<\/u><\/a> or unexplained spam placement, check your SPF result first. It is the fastest diagnostic step.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">SPF Record Syntax: Breaking Down Each Component<\/h2>\n\n\n\n<p>An SPF record looks intimidating at first glance. But once you break it down, every piece has a clear purpose.<\/p>\n\n\n\n<p>Here is an example:<\/p>\n\n\n\n<p>v=spf1 ip4:192.0.2.1 include:_spf.google.com ~all<\/p>\n\n\n\n<p>Let me walk through each component:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>v=spf1 \u2014 This is the version tag. Every SPF record starts with this. It tells the server this is an SPF record.<\/li>\n\n\n\n<li>ip4: \u2014 Authorizes a specific IPv4 address. Use this when you know the exact IP of your sending server.<\/li>\n\n\n\n<li>ip6: \u2014 Same as above, but for IPv6 addresses.<\/li>\n\n\n\n<li>include: \u2014 Delegates authorization to another domain&#8217;s SPF record. You use this for third-party services like Google Workspace or SendGrid.<\/li>\n\n\n\n<li>a \u2014 Authorizes the IP address that your domain&#8217;s A record points to.<\/li>\n\n\n\n<li>mx \u2014 Authorizes the IP addresses of your domain&#8217;s MX (mail exchange) servers.<\/li>\n\n\n\n<li>redirect= \u2014 Points to another domain&#8217;s SPF record entirely. Replaces your current record with theirs.<\/li>\n<\/ul>\n\n\n\n<p>The last part of the record is the &#8220;all&#8221; mechanism. It tells servers what to do with senders not listed in the record:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>~all (SoftFail) \u2014 Flag unauthorized senders but still deliver. Use this during initial setup.<\/li>\n\n\n\n<li>-all (HardFail) \u2014 Reject unauthorized senders outright. <strong>Use this for established domains.<\/strong><\/li>\n\n\n\n<li>?all (Neutral) \u2014 Take no position on unauthorized senders. Not recommended.<\/li>\n\n\n\n<li>+all \u2014 Authorize everyone. <em>Never use this.<\/em> It disables SPF entirely.<\/li>\n<\/ul>\n\n\n\n<p>You can use the <a href=\"https:\/\/www.trulyinbox.com\/free-tools\/spf-generator\/\" target=\"_blank\" rel=\"noreferrer noopener\"><u>SPF record generator<\/u><\/a> on TrulyInbox to build your record without memorizing this syntax.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Real-World SPF Record Examples<\/h3>\n\n\n\n<p>No SERP competitor provides ready-to-use SPF records for common email stacks. Here are the ones I use and recommend.<\/p>\n\n\n\n<p><strong>Google Workspace only:<\/strong><\/p>\n\n\n\n<p>v=spf1 include:_spf.google.com -all<\/p>\n\n\n\n<p><strong>Microsoft 365 only:<\/strong><\/p>\n\n\n\n<p>v=spf1 include:spf.protection.outlook.com -all<\/p>\n\n\n\n<p><strong>Google Workspace + a cold email tool (e.g., SendGrid):<\/strong><\/p>\n\n\n\n<p>v=spf1 include:_spf.google.com include:sendgrid.net -all<\/p>\n\n\n\n<p><strong>Multi-service stack (Google Workspace + Brevo + Help Scout):<\/strong><\/p>\n\n\n\n<p>v=spf1 include:_spf.google.com include:spf.brevo.com include:helpscoutemail.com -all<\/p>\n\n\n\n<p>Notice each record uses -all at the end. I recommend HardFail for any domain that has verified all its sending services. Start with ~all only if you are still testing.<\/p>\n\n\n\n<p>Also notice that every record is a single line. You cannot split SPF across multiple TXT records. One domain, one SPF record.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to Create an SPF Record for Your Domain<\/h2>\n\n\n\n<p>Creating an SPF record is not complicated. But you need to be methodical. Miss one sending service and those emails fail authentication.<\/p>\n\n\n\n<p>Here is the step-by-step process:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>List every service that sends email from your domain.<\/strong> Include your email provider (Google Workspace, Microsoft 365), CRM, helpdesk, marketing platform, transactional email service, and any cold email tools.<\/li>\n\n\n\n<li><strong>Collect the include values from each service&#8217;s documentation.<\/strong> Every email provider publishes the SPF include string you need. Search for &#8220;[provider name] SPF record&#8221; to find it.<\/li>\n\n\n\n<li><strong>Combine all include values into a single SPF record.<\/strong> Use the format: v=spf1 include:service1 include:service2 -all<\/li>\n\n\n\n<li><strong>Log into your DNS provider and create a TXT record.<\/strong> Set the Host\/Name field to @ (or leave blank, depending on your registrar). Paste your full SPF record as the value.<\/li>\n\n\n\n<li><strong>Save the record and wait for DNS propagation.<\/strong> This can take up to 48 hours, but it usually resolves within 30 minutes.<\/li>\n\n\n\n<li><strong>Verify your record using a lookup tool.<\/strong> Send a test email and check the headers for &#8220;spf=pass.&#8221;<\/li>\n<\/ol>\n\n\n\n<p>I recommend verifying immediately after publishing. If your record has a syntax error, you will catch it faster.<\/p>\n\n\n\n<p>For the complete setup process including DKIM and DMARC, check out this guide on how to <a href=\"https:\/\/www.trulyinbox.com\/blog\/how-to-set-up-spf-dkim-and-dmarc\/\" target=\"_blank\" rel=\"noreferrer noopener\"><u>set up SPF, DKIM, and DMARC<\/u><\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How to Check If You Already Have an SPF Record<\/h3>\n\n\n\n<p>Before you create a new SPF record, check whether one already exists. Having two SPF records on the same domain causes both to fail with a PermError.<\/p>\n\n\n\n<p>You can check using these methods:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>MXToolbox:<\/strong> Go to mxtoolbox.com, enter your domain, and run an SPF lookup. It shows your current record and flags errors. For a deeper look at MXToolbox, read this <a href=\"https:\/\/www.trulyinbox.com\/blog\/mxtoolbox-reviews\/\" target=\"_blank\" rel=\"noreferrer noopener\"><u>MXToolbox review<\/u><\/a>.<\/li>\n\n\n\n<li><strong>Google Admin Toolbox:<\/strong> Use the Check MX tool to verify your SPF, DKIM, and DMARC setup.<\/li>\n\n\n\n<li><strong>TrulyInbox Header Analyzer:<\/strong> Send a test email, grab the raw headers, and paste them into the <a href=\"https:\/\/www.trulyinbox.com\/free-tools\/header-analyzer\/\" target=\"_blank\" rel=\"noreferrer noopener\"><u>email header analyzer<\/u><\/a>. It shows your SPF result instantly.<\/li>\n<\/ul>\n\n\n\n<p><em>If a record already exists, modify it.<\/em> Do not create a second one. Add your new include values to the existing record.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The 10 DNS Lookup Limit: Why SPF Records Break<\/h2>\n\n\n\n<p>This is the most under-discussed SPF issue for email senders. And it is the #1 reason SPF records break silently at scale.<\/p>\n\n\n\n<p>SPF allows a maximum of 10 DNS lookups per record. The RFC 7208 specification enforces this limit to prevent DNS abuse.<\/p>\n\n\n\n<p>Here is what counts toward the limit:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Every include: mechanism triggers one lookup<\/li>\n\n\n\n<li>a and mx mechanisms each trigger one lookup<\/li>\n\n\n\n<li>redirect= triggers one lookup<\/li>\n\n\n\n<li>Nested includes also count (if an included record has its own includes, those add to your total)<\/li>\n<\/ul>\n\n\n\n<p>Here is what does not count:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ip4: and ip6: mechanisms are direct and skip DNS lookups entirely<\/li>\n\n\n\n<li>The all mechanism does not count<\/li>\n<\/ul>\n\n\n\n<p><strong>If your record exceeds 10 lookups, SPF returns a PermError.<\/strong> That means SPF fails for every single email you send. Not just some. All of them.<\/p>\n\n\n\n<p>The tricky part is that your SPF record can look perfectly correct on paper. But if the nested includes push you past 10, it breaks without warning.<\/p>\n\n\n\n<p>I have seen domains running 4 to 5 email tools blow past the 10-lookup limit without realizing it. Their SPF looked correct in the DNS panel. But every email was failing authentication silently.<\/p>\n\n\n\n<p>If you are using multiple sending services, this is worth checking today. Especially if you run a <a href=\"https:\/\/www.trulyinbox.com\/blog\/shared-ip-vs-dedicated-ip\/\" target=\"_blank\" rel=\"noreferrer noopener\"><u>shared IP vs dedicated IP<\/u><\/a> setup with several tools.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How to Reduce DNS Lookups in Your SPF Record<\/h3>\n\n\n\n<p>If you are hitting the 10-lookup limit, here are practical ways to bring the count down:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Replace include: with direct ip4: addresses where possible.<\/strong> If a service uses a fixed set of IPs, add them directly instead of using their include string.<\/li>\n\n\n\n<li><strong>Remove old services you no longer use.<\/strong> Audit your SPF record quarterly. If you switched from Mailchimp to Brevo six months ago, remove the Mailchimp include.<\/li>\n\n\n\n<li><strong>Use SPF flattening tools.<\/strong> These tools resolve all your includes into direct IP addresses and maintain the flattened record automatically. Options include AutoSPF and SPF Ninja.<\/li>\n\n\n\n<li><strong>Consider hosted SPF for complex setups.<\/strong> Services like Valimail or dmarcian offer managed SPF that handles lookup limits for you.<\/li>\n<\/ol>\n\n\n\n<p><em>The simplest fix is usually the second one.<\/em> Most senders have at least one outdated include from a tool they stopped using months ago.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Common SPF Record Mistakes (And How to Fix Them)<\/h2>\n\n\n\n<p>I have audited hundreds of domains through running TrulyInbox. These seven mistakes show up again and again.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1. Creating multiple SPF records<\/h3>\n\n\n\n<p>DNS allows only one SPF record per domain. If you add a second one, both fail with a PermError. Combine all your senders into a single record.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Using +all<\/h3>\n\n\n\n<p>This tells receiving servers to accept email from any IP. It completely disables SPF protection. Never use +all under any circumstances.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Forgetting to include all sending services<\/h3>\n\n\n\n<p>Your CRM, helpdesk, transactional service, etc., all send email.<\/p>\n\n\n\n<p>If any of these are missing from your SPF record, those emails fail authentication.<\/p>\n\n\n\n<p>Take 10 minutes to list every tool that sends from your domain. Cross-reference that list with your SPF record.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4. Exceeding the 10-lookup limit<\/h3>\n\n\n\n<p>I covered this in detail above. But it belongs on this list because it is the most common silent failure. Check your lookup count using an SPF lookup tool.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">5. Not updating SPF when switching tools<\/h3>\n\n\n\n<p>If you moved from one email tool to another, update your SPF record. The old include is a security risk. The new tool&#8217;s emails will fail without its include.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6. Adding SPF to the wrong domain<\/h3>\n\n\n\n<p>SPF checks the return-path domain. If your return-path uses a different domain than your From address, you need SPF on the return-path domain. Verify which domain your sending tools actually use for the return-path.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">7. Expecting SPF to authenticate the &#8220;From&#8221; address<\/h3>\n\n\n\n<p>SPF only validates the return-path domain. It does not verify the visible From header. Full &#8220;From&#8221; address protection requires DMARC alignment on top of SPF.<\/p>\n\n\n\n<p>If you want protection against spoofing, you also need to watch for <a href=\"https:\/\/www.trulyinbox.com\/blog\/email-blacklist\/\" target=\"_blank\" rel=\"noreferrer noopener\"><u>email blacklist<\/u><\/a> issues.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">SPF Alone Isn&#8217;t Enough: How It Works with DKIM and DMARC<\/h2>\n\n\n\n<p>SPF validates the sending server. It does not validate the email content or the visible From address. And it breaks completely on forwarding.<\/p>\n\n\n\n<p>That is why SPF is just one piece of the authentication stack. DKIM and DMARC fill the gaps SPF leaves open.<\/p>\n\n\n\n<p>Here is how the three work together:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>SPF<\/strong> checks whether the sending server&#8217;s IP is authorized for the return-path domain<\/li>\n\n\n\n<li><strong>DKIM<\/strong> adds a cryptographic signature to the email. This signature survives forwarding and proves the content was not altered in transit.<\/li>\n\n\n\n<li><strong>DMARC<\/strong> ties SPF and DKIM together. It checks alignment between the return-path, DKIM domain, and the visible From address. It also tells receiving servers what to do when checks fail.<\/li>\n<\/ul>\n\n\n\n<p>The major inbox providers now require all three:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Google and Yahoo made SPF + DKIM mandatory for all senders in February 2024. Bulk senders also need DMARC.<\/li>\n\n\n\n<li>Microsoft Outlook made all three mandatory starting May 2025.<\/li>\n<\/ul>\n\n\n\n<p><strong>SPF is step one, not the whole solution.<\/strong> Without DKIM, your emails have no integrity verification. Without DMARC, you have no policy enforcement or reporting.<\/p>\n\n\n\n<p>If you do not have DMARC set up yet, read this guide on what happens when you have <a href=\"https:\/\/www.trulyinbox.com\/blog\/no-dmarc-record-found\/\" target=\"_blank\" rel=\"noreferrer noopener\"><u>no DMARC record found<\/u><\/a> on your domain.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">SPF vs DKIM vs DMARC: Quick Comparison<\/h3>\n\n\n\n<p>Here is a side-by-side breakdown of what each protocol does:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><br><\/td><td><strong>SPF<\/strong><\/td><td><strong>DKIM<\/strong><\/td><td><strong>DMARC<\/strong><\/td><\/tr><tr><td><strong>What it validates<\/strong><\/td><td>Sending server IP<\/td><td>Email content integrity<\/td><td>Alignment between SPF, DKIM, and From address<\/td><\/tr><tr><td><strong>What it checks<\/strong><\/td><td>Return-path domain<\/td><td>Cryptographic signature in email header<\/td><td>Whether SPF or DKIM aligns with the From domain<\/td><\/tr><tr><td><strong>Survives forwarding?<\/strong><\/td><td>No<\/td><td>Yes<\/td><td>Depends on SPF\/DKIM results<\/td><\/tr><tr><td><strong>Provides reporting?<\/strong><\/td><td>No<\/td><td>No<\/td><td>Yes (aggregate and forensic reports)<\/td><\/tr><tr><td><strong>Policy enforcement?<\/strong><\/td><td>No<\/td><td>No<\/td><td>Yes (none, quarantine, reject)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p><em>The key takeaway is simple.<\/em> SPF tells servers who is allowed to send. DKIM proves the email is genuine. DMARC enforces the rules and gives you visibility into failures.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How SPF Affects Your Email Deliverability<\/h2>\n\n\n\n<p>SPF is the first gate in <a href=\"https:\/\/www.trulyinbox.com\/blog\/email-deliverability\/\" target=\"_blank\" rel=\"noreferrer noopener\"><u>email deliverability<\/u><\/a>. If it fails, nothing else matters.<\/p>\n\n\n\n<p>A consistent SPF pass sends a trust signal to inbox providers. Over time, that trust builds your sender reputation. Gmail, Outlook, and Yahoo all factor SPF results into their placement decisions.<\/p>\n\n\n\n<p>When SPF fails, the consequences vary:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Gmail often places the email in spam with a warning banner<\/li>\n\n\n\n<li>Outlook may reject the email outright or add a junk header<\/li>\n\n\n\n<li>Yahoo flags the email and weighs SPF failure against other signals<\/li>\n<\/ul>\n\n\n\n<p>For cold emailers, this is especially critical. You are emailing people who did not opt in.<\/p>\n\n\n\n<p>Inbox providers already scrutinize your messages more heavily. A failed SPF check gives them one more reason to filter you.<\/p>\n\n\n\n<p><strong>Here is the connection most guides miss.<\/strong> If your SPF is broken and you are running <a href=\"https:\/\/www.trulyinbox.com\/blog\/email-warmup\/\" target=\"_blank\" rel=\"noreferrer noopener\"><u>email warm-up<\/u><\/a>, those warm-up emails also fail authentication.<\/p>\n\n\n\n<p>Instead of building trust, they train inbox providers to distrust your domain.<\/p>\n\n\n\n<p>SPF is the first checkpoint. If it fails, warm-up emails damage your reputation instead of building it.<\/p>\n\n\n\n<p>Once your SPF, DKIM, and DMARC are all passing, the next step is to warm up your email accounts before you start outreach. TrulyInbox automates this process and helps you build sender reputation before you scale.<\/p>\n\n\n\n<p>You can monitor your SPF status and domain reputation through <a href=\"https:\/\/www.trulyinbox.com\/blog\/google-postmaster-tools\/\" target=\"_blank\" rel=\"noreferrer noopener\"><u>Google Postmaster Tools<\/u><\/a>. It shows authentication results and reputation scores directly from Google&#8217;s data.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">FAQs About SPF Records<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. What Is an SPF Record in Simple Terms?<\/h3>\n\n\n\n<p>An SPF record is a guest list for your domain. It is a DNS entry that tells receiving servers which mail servers you have authorized to send email on your behalf. If a server is not on the list, the email gets flagged or rejected.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Can I Have More Than One SPF Record?<\/h3>\n\n\n\n<p>No. DNS allows only one SPF record per domain. If you add a second record, both fail with a PermError. Combine all your sending services into a single record using multiple include: mechanisms.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. What Is the Difference Between ~all and -all?<\/h3>\n\n\n\n<p>~all is a SoftFail. It flags unauthorized senders but may still deliver the email. -all is a HardFail. It tells receiving servers to reject unauthorized senders outright.<\/p>\n\n\n\n<p>Start with ~all during initial setup and testing. Switch to -all once you have verified all your sending services are included.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4. Does SPF Prevent Phishing?<\/h3>\n\n\n\n<p>Partially. SPF validates the return-path domain, not the visible From address. An attacker can still spoof your From header if you only have SPF.<\/p>\n\n\n\n<p>Full phishing protection requires SPF + DKIM + DMARC working together with proper alignment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">5. What Happens if My SPF Record Is Missing?<\/h3>\n\n\n\n<p>Without an SPF record, receiving servers cannot verify your sending authorization. Your emails become more likely to land in spam or get rejected entirely. This is especially true with Gmail, Yahoo, and Outlook, which now require SPF for all senders.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6. How Do I Check if My SPF Record Is Working?<\/h3>\n\n\n\n<p>Send a test email to yourself and view the original message or headers. Look for &#8220;spf=pass&#8221; in the authentication results. You can also use MXToolbox or the TrulyInbox <a href=\"https:\/\/www.trulyinbox.com\/free-tools\/header-analyzer\/\" target=\"_blank\" rel=\"noreferrer noopener\"><u>email header analyzer<\/u><\/a> to check your SPF status.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">7. Does SPF Work if I Forward Emails?<\/h3>\n\n\n\n<p>No. When an email gets forwarded, the forwarding server&#8217;s IP replaces the original sending IP. That new IP is not in your SPF record, so the check fails.<\/p>\n\n\n\n<p>DKIM survives forwarding because it validates the email content, not the server IP. DMARC handles the fallback by checking whether either SPF or DKIM passes with proper alignment.<\/p>\n\n\n\n<script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What is an SPF record in simple terms?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"An SPF record is a guest list for your domain. It is a DNS entry that tells receiving servers which mail servers you have authorized to send email on your behalf. If a server is not on the list, the email gets flagged or rejected.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Can I have more than one SPF record?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"No. DNS allows only one SPF record per domain. If you add a second record, both fail with a PermError. Combine all your sending services into a single record using multiple include: mechanisms.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What is the difference between ~all and -all?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"~all is a SoftFail. It flags unauthorized senders but may still deliver the email. -all is a HardFail. It tells receiving servers to reject unauthorized senders outright. Start with ~all during initial setup and testing. Switch to -all once you have verified all your sending services are included.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Does SPF prevent phishing?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Partially. SPF validates the return-path domain, not the visible From address. An attacker can still spoof your From header if you only have SPF. Full phishing protection requires SPF + DKIM + DMARC working together with proper alignment.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What happens if my SPF record is missing?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Without an SPF record, receiving servers cannot verify your sending authorization. Your emails become more likely to land in spam or get rejected entirely. This is especially true with Gmail, Yahoo, and Outlook, which now require SPF for all senders.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How do I check if my SPF record is working?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Send a test email to yourself and view the original message or headers. Look for spf=pass in the authentication results. You can also use MXToolbox or the TrulyInbox email header analyzer to check your SPF status.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Does SPF work if I forward emails?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"No. When an email gets forwarded, the forwarding server's IP replaces the original sending IP. That new IP is not in your SPF record, so the check fails. DKIM survives forwarding because it validates the email content, not the server IP. DMARC handles the fallback by checking whether either SPF or DKIM passes with proper alignment.\"\n      }\n    }\n  ]\n}\n<\/script>\n\n\n","protected":false},"excerpt":{"rendered":"<p>Most email senders know they need SPF. Very few understand what it actually does or how it protects their domain. The result is predictable. Broken records, failed authentication, and emails landing in spam for reasons nobody can diagnose. I run TrulyInbox, an email warm-up tool. I have seen hundreds of domains with misconfigured SPF records. [&hellip;]<\/p>\n","protected":false},"author":7,"featured_media":2903,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-2902","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-email-deliverability-hub"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v25.6 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>What is SPF Record?<\/title>\n<meta name=\"description\" content=\"I&#039;ve audited hundreds of SPF setups. Here&#039;s how SPF works, how to build your record, and the common mistakes most senders never catch.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"What is SPF Record?\" \/>\n<meta property=\"og:description\" content=\"I&#039;ve audited hundreds of SPF setups. Here&#039;s how SPF works, how to build your record, and the common mistakes most senders never catch.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/\" \/>\n<meta property=\"og:site_name\" content=\"TrulyinboxBlog\" \/>\n<meta property=\"article:published_time\" content=\"2026-04-27T11:11:49+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-04-28T05:41:58+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2026\/04\/What-is-SPF-Complete-Guide-to-Sender-Policy-Framework.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"2400\" \/>\n\t<meta property=\"og:image:height\" content=\"1350\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"author\" content=\"Vatsal Shah\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Vatsal Shah\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"14 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/\"},\"author\":{\"name\":\"Vatsal Shah\",\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/#\/schema\/person\/badcb20e2c136c3f8ff70ced3bfa86ee\"},\"headline\":\"What Is an SPF Record? A Complete Guide for Email Senders (With Examples)\",\"datePublished\":\"2026-04-27T11:11:49+00:00\",\"dateModified\":\"2026-04-28T05:41:58+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/\"},\"wordCount\":3147,\"publisher\":{\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2026\/04\/What-is-SPF-Complete-Guide-to-Sender-Policy-Framework.webp\",\"articleSection\":[\"Email Deliverability\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/\",\"url\":\"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/\",\"name\":\"What is SPF Record?\",\"isPartOf\":{\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2026\/04\/What-is-SPF-Complete-Guide-to-Sender-Policy-Framework.webp\",\"datePublished\":\"2026-04-27T11:11:49+00:00\",\"dateModified\":\"2026-04-28T05:41:58+00:00\",\"description\":\"I've audited hundreds of SPF setups. Here's how SPF works, how to build your record, and the common mistakes most senders never catch.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/#primaryimage\",\"url\":\"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2026\/04\/What-is-SPF-Complete-Guide-to-Sender-Policy-Framework.webp\",\"contentUrl\":\"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2026\/04\/What-is-SPF-Complete-Guide-to-Sender-Policy-Framework.webp\",\"width\":2400,\"height\":1350,\"caption\":\"I've audited hundreds of SPF setups. Here's how SPF works, how to build your record, and the common mistakes most senders never catch.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.trulyinbox.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"What Is an SPF Record? A Complete Guide for Email Senders (With Examples)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/#website\",\"url\":\"https:\/\/www.trulyinbox.com\/blog\/\",\"name\":\"TrulyinboxBlog\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.trulyinbox.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/#organization\",\"name\":\"TrulyinboxBlog\",\"url\":\"https:\/\/www.trulyinbox.com\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2025\/02\/logo.svg\",\"contentUrl\":\"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2025\/02\/logo.svg\",\"width\":138,\"height\":36,\"caption\":\"TrulyinboxBlog\"},\"image\":{\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/#\/schema\/person\/badcb20e2c136c3f8ff70ced3bfa86ee\",\"name\":\"Vatsal Shah\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.trulyinbox.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2025\/03\/Vatsal-Shah-96x96.webp\",\"contentUrl\":\"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2025\/03\/Vatsal-Shah-96x96.webp\",\"caption\":\"Vatsal Shah\"},\"description\":\"Vatsal is a deliverability expert who believes numbers don\u2019t matter if emails never reach the inbox. While working in outbound sales, he noticed that many focused on sending large volumes of emails but overlooked inbox placement. He knew this wasn\u2019t an efficient approach, so he took it upon himself to find ways to improve deliverability. After years of experimenting, he became an expert in inbox placement. Today, Vatsal helps TrulyInbox with growth strategies and shares his expertise on deliverability through blogs.\",\"sameAs\":[\"https:\/\/www.linkedin.com\/in\/vatsaas\/\"],\"url\":\"https:\/\/www.trulyinbox.com\/blog\/author\/vatsal\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"What is SPF Record?","description":"I've audited hundreds of SPF setups. Here's how SPF works, how to build your record, and the common mistakes most senders never catch.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/","og_locale":"en_US","og_type":"article","og_title":"What is SPF Record?","og_description":"I've audited hundreds of SPF setups. Here's how SPF works, how to build your record, and the common mistakes most senders never catch.","og_url":"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/","og_site_name":"TrulyinboxBlog","article_published_time":"2026-04-27T11:11:49+00:00","article_modified_time":"2026-04-28T05:41:58+00:00","og_image":[{"width":2400,"height":1350,"url":"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2026\/04\/What-is-SPF-Complete-Guide-to-Sender-Policy-Framework.webp","type":"image\/webp"}],"author":"Vatsal Shah","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Vatsal Shah","Est. reading time":"14 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/#article","isPartOf":{"@id":"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/"},"author":{"name":"Vatsal Shah","@id":"https:\/\/www.trulyinbox.com\/blog\/#\/schema\/person\/badcb20e2c136c3f8ff70ced3bfa86ee"},"headline":"What Is an SPF Record? A Complete Guide for Email Senders (With Examples)","datePublished":"2026-04-27T11:11:49+00:00","dateModified":"2026-04-28T05:41:58+00:00","mainEntityOfPage":{"@id":"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/"},"wordCount":3147,"publisher":{"@id":"https:\/\/www.trulyinbox.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/#primaryimage"},"thumbnailUrl":"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2026\/04\/What-is-SPF-Complete-Guide-to-Sender-Policy-Framework.webp","articleSection":["Email Deliverability"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/","url":"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/","name":"What is SPF Record?","isPartOf":{"@id":"https:\/\/www.trulyinbox.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/#primaryimage"},"image":{"@id":"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/#primaryimage"},"thumbnailUrl":"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2026\/04\/What-is-SPF-Complete-Guide-to-Sender-Policy-Framework.webp","datePublished":"2026-04-27T11:11:49+00:00","dateModified":"2026-04-28T05:41:58+00:00","description":"I've audited hundreds of SPF setups. Here's how SPF works, how to build your record, and the common mistakes most senders never catch.","breadcrumb":{"@id":"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/#primaryimage","url":"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2026\/04\/What-is-SPF-Complete-Guide-to-Sender-Policy-Framework.webp","contentUrl":"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2026\/04\/What-is-SPF-Complete-Guide-to-Sender-Policy-Framework.webp","width":2400,"height":1350,"caption":"I've audited hundreds of SPF setups. Here's how SPF works, how to build your record, and the common mistakes most senders never catch."},{"@type":"BreadcrumbList","@id":"https:\/\/www.trulyinbox.com\/blog\/what-is-an-spf-record\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.trulyinbox.com\/blog\/"},{"@type":"ListItem","position":2,"name":"What Is an SPF Record? A Complete Guide for Email Senders (With Examples)"}]},{"@type":"WebSite","@id":"https:\/\/www.trulyinbox.com\/blog\/#website","url":"https:\/\/www.trulyinbox.com\/blog\/","name":"TrulyinboxBlog","description":"","publisher":{"@id":"https:\/\/www.trulyinbox.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.trulyinbox.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.trulyinbox.com\/blog\/#organization","name":"TrulyinboxBlog","url":"https:\/\/www.trulyinbox.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.trulyinbox.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2025\/02\/logo.svg","contentUrl":"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2025\/02\/logo.svg","width":138,"height":36,"caption":"TrulyinboxBlog"},"image":{"@id":"https:\/\/www.trulyinbox.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.trulyinbox.com\/blog\/#\/schema\/person\/badcb20e2c136c3f8ff70ced3bfa86ee","name":"Vatsal Shah","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.trulyinbox.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2025\/03\/Vatsal-Shah-96x96.webp","contentUrl":"https:\/\/www.trulyinbox.com\/blog\/wp-content\/uploads\/2025\/03\/Vatsal-Shah-96x96.webp","caption":"Vatsal Shah"},"description":"Vatsal is a deliverability expert who believes numbers don\u2019t matter if emails never reach the inbox. While working in outbound sales, he noticed that many focused on sending large volumes of emails but overlooked inbox placement. He knew this wasn\u2019t an efficient approach, so he took it upon himself to find ways to improve deliverability. After years of experimenting, he became an expert in inbox placement. Today, Vatsal helps TrulyInbox with growth strategies and shares his expertise on deliverability through blogs.","sameAs":["https:\/\/www.linkedin.com\/in\/vatsaas\/"],"url":"https:\/\/www.trulyinbox.com\/blog\/author\/vatsal\/"}]}},"_links":{"self":[{"href":"https:\/\/www.trulyinbox.com\/blog\/wp-json\/wp\/v2\/posts\/2902","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.trulyinbox.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.trulyinbox.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.trulyinbox.com\/blog\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.trulyinbox.com\/blog\/wp-json\/wp\/v2\/comments?post=2902"}],"version-history":[{"count":2,"href":"https:\/\/www.trulyinbox.com\/blog\/wp-json\/wp\/v2\/posts\/2902\/revisions"}],"predecessor-version":[{"id":2905,"href":"https:\/\/www.trulyinbox.com\/blog\/wp-json\/wp\/v2\/posts\/2902\/revisions\/2905"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.trulyinbox.com\/blog\/wp-json\/wp\/v2\/media\/2903"}],"wp:attachment":[{"href":"https:\/\/www.trulyinbox.com\/blog\/wp-json\/wp\/v2\/media?parent=2902"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.trulyinbox.com\/blog\/wp-json\/wp\/v2\/categories?post=2902"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.trulyinbox.com\/blog\/wp-json\/wp\/v2\/tags?post=2902"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}