Call (703) Book ↗
On this page
SPF · Foundation Setup

Missing SPF Record

Fix missing SPF records for Microsoft 365, Google Workspace, and web hosts. Step-by-step TXT syntax examples to stop spam placement and spoofing.

Emails Landing in Spam or Bouncing?

Run your domain through our Free Email Deliverability Scanner to verify whether an SPF TXT record is visible in public DNS, then publish the exact template for your mail platform below.

Why missing SPF sends legitimate mail to spam

Your domain does not have a Sender Policy Framework (SPF) TXT record published. Think of SPF like an authorized guest list at the door: when an email arrives claiming to be from your company, the receiving server checks DNS to verify whether the sending server IP is actually allowed to send on your behalf.

When your SPF record is missing, the guest list is blank. Modern providers like Microsoft 365, Gmail, and Yahoo no longer give unauthenticated senders the benefit of the doubt—resulting in spam placement, bounced quotes, and easy domain impersonation.

Clean starting SPF TXT records by mail platform

First inventory every legitimate system that sends mail using your domain (primary email, accounting/invoicing like QuickBooks, CRM, website contact forms, or office scan-to-email relays). Publish strictly one TXT record on your root domain (@):

MICROSOFT 365 ONLY
@  300  IN  TXT  "v=spf1 include:spf.protection.outlook.com -all"
GOOGLE WORKSPACE ONLY
@  300  IN  TXT  "v=spf1 include:_spf.google.com -all"
MICROSOFT 365 + AMAZON SES / WEBSITE TRANSACTIONAL MAIL
@  300  IN  TXT  "v=spf1 include:spf.protection.outlook.com include:amazonses.com ~all"
PARKED / DEFENSIVE DOMAINS THAT NEVER SEND EMAIL
; Blocks spoofers from abusing unused brand or defensive domains
@  300  IN  TXT  "v=spf1 -all"

Choosing ~all (SoftFail) vs. -all (HardFail)

QualifierMeaningWhen to Use It
~all (SoftFail) Unauthorized senders fail SPF and are flagged for scoring/DMARC Best initial rollout setting for 14–30 days while auditing shadow senders (website forms, CRM, accounting) via DMARC reports.
-all (HardFail) Unauthorized senders fail SPF explicitly Recommended steady-state policy once every legitimate sender is inventoried and 2048-bit DKIM + DMARC are active.
?all / +all Neutral (?all) or allow the entire internet (+all) Never use +all—it explicitly authorizes every spammer on earth to send as your domain.
Never Publish Two SPF Records

If you also send from QuickBooks, Mailchimp, or a web host, combine all includes into that single TXT record (never create a second v=spf1 record, which causes a fatal Multiple SPF PermError). Start with ~all while verifying third-party senders, then tighten to -all alongside DMARC.

Provider-specific DNS publishing steps

  • Cloudflare: Open your domain → DNS → Records → Add record. Choose Type TXT, Name @ (your apex domain), TTL Auto (or 5 min), and paste v=spf1 include:... ~all into Content without extra surrounding quotes.
  • GoDaddy: Go to My Products → Domain → Manage DNS → Add New Record. Set Type to TXT, Name to @, Value to v=spf1 ..., and TTL to 600 seconds. Double-check first that GoDaddy did not already auto-create a secureserver.net TXT record—if one exists, edit it instead of adding a second row.
  • Microsoft 365 Admin Center: Check Settings → Domains → [your domain] → DNS records to confirm Microsoft recognizes your published include:spf.protection.outlook.com record. If an on-premise copier or scanner relays mail directly, add its static public IP via ip4:x.x.x.x.
  • Google Workspace Admin Console: Confirm SPF alongside custom DKIM under Apps → Google Workspace → Gmail → Authenticate email using include:_spf.google.com.

Verify your new SPF record live

After saving DNS, confirm your record resolves publicly and passes inside a real outbound test message:

VERIFY SPF TXT RECORD VIA DIG & NSLOOKUP
# macOS / Linux
dig +short TXT yourdomain.com

# Windows PowerShell / CMD
nslookup -type=txt yourdomain.com 1.1.1.1

Send a test email to a personal Gmail address, click the three-dot menu → Show original, and confirm you see SPF: PASS with your sending server IP.

Common first-time SPF pitfalls

  • Publishing on www instead of @: Email sent from [email protected] queries the apex (@), not www.yourdomain.com.
  • Using the deprecated DNS Type 99 (SPF) record: RFC 7208 Section 3.1 formally retired Type 99 records—always publish SPF strictly as a standard TXT record.
  • Stopping after SPF alone: SPF validates only the hidden Return-Path envelope and breaks during email forwarding. Pair your new SPF record with 2048-bit DKIM and a baseline DMARC policy for real anti-spoofing defense.
Want Our Engineers to Fix Your DNS Cleanly?

One stray character in SPF or DMARC can bounce every invoice your company sends. Let Enuclea audit your senders, flatten SPF safely, align 2048-bit DKIM, and configure DMARC cleanly starting at $250 flat. Test your domain free, book a 15-minute call (24-hr notice) ↗, or call (703) 239-4620.