Call (703) Book ↗
On this page
SPF · RFC 7208 PermError

SPF PermError (Permanent Error)

Getting 550 5.7.1 SPF PermError? Discover the 5 root causes—too many lookups, syntax errors, void lookups, multiple records—and how to fix them cleanly.

Bouncing With 550 5.7.1 SPF PermError?

Run your domain through our Free Email Deliverability Scanner to pinpoint the exact failing mechanism, or walk through the five root causes and command-line checks below.

What is an SPF PermError?

Under RFC 7208, an SPF PermError (Permanent Error) occurs when a receiving server cannot legally evaluate your domain's SPF DNS record. Unlike a TempError caused by a momentary authoritative DNS timeout, a PermError never heals on its own—it requires an explicit DNS fix.

When Gmail or Microsoft 365 hits a PermError, you will see spf=permerror inside the message's Authentication-Results header (via Gmail's Show original or Outlook's View message details), or an immediate NDR bounce containing 550 5.7.1.

Five common causes of SPF PermError

  1. Multiple SPF RecordsPublishing two or more TXT records starting with v=spf1 throws an immediate PermError. Follow our Multiple SPF Records Merge Guide to combine them cleanly.
  2. Exceeding the 10-DNS-Lookup LimitRFC 7208 caps recursive lookups (include, a, mx, ptr, exists, redirect) at 10 per check. Crossing 10 stops evaluation immediately—see our SPF 10-Lookup Limit Guide.
  3. Invalid Syntax & TyposMisspelled mechanisms (inlcude: instead of include:), missing spaces, extra spaces after colons (ip4: 192.0.2.1), smart quotes copied from Word, or invalid CIDR masks invalidate the entire record.
  4. Exceeding the Void Lookup Limit (>2)Under RFC 7208 Section 4.6.4, if an include: or a mechanism points to a retired vendor domain returning NXDOMAIN or zero records, it counts as a void lookup. Exceeding 2 void lookups triggers a PermError even if total lookups are under 10.
  5. Deprecated Mechanisms (ptr) & Circular LoopsUsing ptr is explicitly deprecated by RFC 7208, and accidentally referencing your own domain inside include:yourdomain.com creates an infinite recursion loop that immediately errors out.
Why PermError Hurts Worse Than Missing SPF

Under DMARC alignment rules, an SPF PermError causes SPF to fail completely—meaning unless 2048-bit DKIM signing is independently aligned, Gmail, Yahoo, and Microsoft 365 treat your invoices as indistinguishable from spoofed mail.

Real troubleshooting examples: broken syntax vs. fixed DNS

Broken SPF RecordRoot CauseCorrected Record
v=spf1 inlcude:spf.protection.outlook.com -all Typo in include: mechanism v=spf1 include:spf.protection.outlook.com -all
v=spf1 ip4: 203.0.113.10 include:_spf.google.com ~all Illegal space after ip4: colon v=spf1 ip4:203.0.113.10 include:_spf.google.com ~all
v=spf1 include:spf.oldvendor.invalid include:deadcrm.net include:badhost.org include:spf.protection.outlook.com ~all 3 void lookups (NXDOMAIN / empty TXT > 2 limit) v=spf1 include:spf.protection.outlook.com -all
v=spf1 include:yourdomain.com include:_spf.google.com -all Self-referencing recursion loop v=spf1 include:_spf.google.com -all

Diagnosing SPF PermError with dig and nslookup

Before editing DNS, query both your root TXT record and every nested include: target so you spot duplicate rows, typos, or dead vendor domains immediately:

INSPECT ROOT RECORD & TRACE NESTED INCLUDES
# 1. Fetch every TXT record on your root domain (macOS / Linux)
dig +short TXT yourdomain.com

# 2. Test each vendor include to verify it resolves (not NXDOMAIN / empty)
dig +short TXT spf.protection.outlook.com
dig +short TXT _spf.google.com

# 3. Windows PowerShell / CMD equivalent
nslookup -q=txt yourdomain.com 8.8.8.8
nslookup -q=txt spf.protection.outlook.com 8.8.8.8

Provider-specific DNS gotchas

  • Cloudflare: Never rely on bare a or mx mechanisms if your root A record is orange-cloud proxied through Cloudflare—the a lookup resolves to Cloudflare's web proxy IPs rather than your real mail server, wasting a lookup and authorizing the wrong addresses. Also check for stray double quotes pasted inside Cloudflare's TXT editor.
  • GoDaddy: GoDaddy enforces 255 characters per TXT string and frequently leaves a legacy include:secureserver.net record in place on migrated domains. Copying records from Microsoft Word or email threads can also introduce curly smart quotes (“ / ”) that break syntax silently.
  • Microsoft 365 & Google Workspace: Although both include:spf.protection.outlook.com (1 lookup) and include:_spf.google.com (1 lookup) currently publish flat IP lists, leaving a retired suite's include—or redundant a and mx mechanisms (1 lookup each toward RFC 7208 Section 4.6.4's 10-lookup limit, with RFC 7208 Section 4.6.4 also applying a separate 10-hostname per-mechanism A/AAAA resolution cap on mx)—permanently in DNS erodes headroom alongside multi-lookup senders such as include:sendgrid.net (2 lookups) and include:_spf.salesforce.com (2 lookups), and leaves your domain exposed if a vendor later restructures its includes. Remove the retired suite's include once cutover is complete.

Common pitfalls after you think it's fixed

  • Fixing root DNS while an internal DNS server serves stale records: Split-horizon offices running Active Directory DNS sometimes publish a broken copy internally while fixing only Cloudflare/GoDaddy publicly. Verify against both 1.1.1.1 and your local resolver.
  • Forgetting trailing spaces or uppercase V=SPF1 edge cases: While SPF tags are case-insensitive in RFC 7208, legacy filters expect clean lowercase v=spf1 with single ASCII spaces and no trailing control characters.
  • Ignoring DMARC alignment during repair: Always check that 2048-bit custom DKIM signing is enabled on Microsoft 365 or Google Workspace so messages stay authenticated even during DNS TTL propagation windows.

A clean repair strategy: subdomain delegation

When legitimate CRM, ticketing, and marketing platforms push your root domain past 10 lookups, move high-volume third-party senders to a subdomain (for example, notify.yourdomain.com). SPF is evaluated on the exact envelope domain sending each email, giving every subdomain an independent 10-lookup budget while keeping your primary Microsoft 365 or Google Workspace domain lean.

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.