Back to Tools

Bulk SPF Extractor

Complete SPF record analysis with TYPE 99 HEX decoding support.

Email Security Tool

Manual Input

Enter one domain per line. Don't include protocols (http://) or subdomains unless needed.

CSV Upload

Upload CSV with domains column. Supports large files.

Processing Settings

SPF Analysis: Choose 'Includes Only' for supply chain analysis, or 'Full Records' for complete SPF policies.

Extraction Mode

Record Type

Processing Domains
00:00
0
Total
0
Processed
0
With SPF
0
TXT SPF
0
Type 99
0
Failed
0
Unique
0
Batch
Ready to start...

Analysis Summary

0
Unique Items
0
Total Occurrences
0
From TXT
0
From Type 99
-
Most Common

SPF Records Found

0 records
Sort by:

Failed Domains

0 errors

Error Summary

The Complete Technical Guide to SPF Records

Methodology: How SPF Validation Actually Works

SPF (Sender Policy Framework) is evaluated by the receiving Mail Transfer Agent (MTA). When an email arrives, the MTA checks the "Return-Path" domain, queries its DNS for a TXT record beginning with v=spf1, and evaluates the sender's IP against the declared mechanisms. The evaluation returns one of several results:

  • Pass: The sender IP matches a definitive mechanism (e.g., ip4:192.168.0.1).
  • Fail (-all): The IP does not match, and the policy is strict. The email is usually rejected outright.
  • SoftFail (~all): The IP does not match, but the policy is lenient. The email is accepted but often marked as spam.
  • PermError: A syntax error or DNS limit violation occurred (e.g., >10 lookups). The SPF check completely fails.

Real-World Use Cases

Scenario 1: Diagnosing Deliverability Drops

The Problem: A company's marketing emails suddenly start landing in spam. Nothing changed in their ESP (e.g., Mailchimp).

The Solution: Using our Bulk Extractor, the IT team inputs their domain. They discover that their parent company recently added a new include: to the shared SPF, pushing the total DNS lookups to 12. This triggers a PermError across all outgoing mail. They flatten the record to fix it.

Scenario 2: Competitor SaaS Stack Analysis

The Problem: A B2B sales team wants to know which CRM and Support ticket software their competitors use to tailor their sales pitch.

The Solution: They feed a competitor list into the Extractor. By extracting the include: statements, they map out the exact infrastructure (e.g., finding include:servers.mcsv.net reveals Mailchimp; include:zendesk.com reveals Zendesk).

Technical Limits & RFC 7208 Benchmarks

SPF records are incredibly fragile due to strict limits imposed by RFC 7208 to prevent Denial of Service (DoS) attacks against DNS infrastructure.

Constraint Maximum Limit Mechanisms Affected
DNS Lookup Limit 10 Lookups include:, a, mx, ptr, exists
Void Lookout Limit 2 Void Lookups Any mechanisms that return an empty response
String Length Limit 255 Characters per string Must split longer records into multiple quoted strings "part1" "part2"
UDP Packet Size 512 Bytes (Historically) Records exceeding 512 bytes may force TCP fallback, slowing delivery

Frequently Asked Questions

What is the difference between ~all vs -all?

~all (soft fail) instructs the receiver that the message might not be authorized but to accept it anyway (usually moving it to the spam folder). -all (hard fail) instructs the receiver to reject unauthorized emails immediately. -all is highly recommended, but only after mapping all legitimate sending sources.

What is a Type 99 (SPF) record?

Originally, SPF had its own dedicated DNS Resource Record type (Type 99). However, this was officially deprecated in 2014 by RFC 7208 in favor of formatting SPF as standard TXT records. Our tool still supports decoding Type 99 for forensic investigation of legacy architectures.

How do I fix the "Too many DNS lookups" PermError?

If you exceed the 10-lookup limit, you must use a technique called "SPF Flattening." This involves resolving the subsequent a, mx, and include: domains down into their raw IPv4/IPv6 addresses (since `ip4` and `ip6` mechanisms do not count toward the 10-lookup limit) and deploying them directly in your record.

About the Author: Nicola Selenu

Nicola is a Lead Developer and Digital Marketing Technologist with years of hands-on experience in technical SEO, web analytics, and deliverability. He builds tools to bridge the gap between complex marketing technicalities and easy-to-use solutions.