Octeth v6.0.7 Now Available! See What's New
Free Deliverability Tool

SPF Record Validator

Ensure your email deliverability and security with our comprehensive SPF Record Validator. Validate your domain's SPF record against the latest standards to prevent spoofing and improve email authentication.

Enter your domain without http:// or www

Understanding SPF and How Our Validator Works

Sender Policy Framework (SPF) is an email authentication protocol designed to detect and prevent email spoofing. By specifying which mail servers are permitted to send emails on behalf of your domain, SPF helps protect your domain from being used for sending spam or phishing emails.

Our SPF Record Validator tool checks the SPF record of your domain against the latest standards and requirements. It ensures that your SPF record is correctly configured to enhance your email security and deliverability.

The tool validates the syntax of your SPF record, checks for the number of DNS lookups, and verifies the validity of included domains and IP addresses. By using our validator, you can identify and resolve potential issues, ensuring your emails reach their intended recipients securely.

Syntax Validation

Checks for proper SPF record syntax and formatting

DNS Lookup Count

Ensures you're within the 10 DNS lookup limit

IP Verification

Validates included IP addresses and ranges

Include Check

Verifies all included domains are valid

How to Check an SPF Record and Read the Result

What an SPF Check Does

A receiving server looks up the v=spf1 record on the envelope sender domain (the Return-Path) and checks whether the connecting IP is on the list. This validator fetches the SPF record for the domain you enter, splits it into mechanisms, checks the syntax of each one, and counts the mechanisms that cost a DNS lookup. Enter the domain your mail uses in the Return-Path, which is often a bounce subdomain of your email service rather than your main domain.

Reading the Result

1

Status

Green means the syntax is valid and nothing needs attention. Amber means the record works but has warnings, such as a neutral ?all, a deprecated ptr, or more than 7 lookups. Red means a mechanism is invalid, the record uses +all, or it needs more than 10 lookups. "No SPF Record Found" means receivers have nothing to check against.

2

Summary counts

Mechanisms is the number of terms after v=spf1. DNS Lookups counts the include, a, mx, ptr, exists and redirect terms in your record. Each included record can add lookups of its own, so treat this number as the minimum.

3

Validation details, warnings and recommendations

Each mechanism gets its own verdict. Fix the warnings first. Recommendations are optional.

Common Mistakes

  • More than 10 DNS lookups. RFC 7208 caps evaluation at 10 lookups, including the ones inside every include. Past that, receivers return a permanent error and SPF fails. Remove unused includes and list your own servers with ip4 and ip6.
  • Two SPF records on one domain. A domain may publish only one v=spf1 record. Two records cause a permanent error. This validator shows the first record it finds, so check the full TXT list in your DNS provider and merge any second record into the first.
  • Using +all or no all at all. +all authorizes every server on the internet. A record without an all term or a redirect ends in a neutral result. End the record with ~all or -all.

Example SPF Record

v=spf1 ip4:203.0.113.10 include:_spf.google.com ~all

This record authorizes one self-hosted sending server at 203.0.113.10, authorizes Google Workspace through its include, and soft-fails everything else. The validator would report 3 mechanisms, 1 DNS lookup, 1 IP range and 1 include. To build a record for your own senders, use the SPF record generator.

Frequently asked questions

What does an SPF validator check?

It fetches the TXT record that starts with v=spf1 on the domain you enter, checks the syntax of every mechanism, counts the mechanisms that need a DNS lookup, and flags risky settings such as +all, ?all, a missing all term or the deprecated ptr mechanism.

Why does my SPF record fail with too many DNS lookups?

RFC 7208 allows at most 10 DNS lookups while a receiver evaluates SPF. The include, a, mx, ptr and exists mechanisms and the redirect modifier each use one, and the lookups inside every included record count too. Past 10, the result is a permanent error and SPF fails. Remove unused includes and list your own servers with ip4 and ip6, which use no lookups.

Can a domain have two SPF records?

No. A domain must publish exactly one TXT record that starts with v=spf1. Two records cause a permanent error and receivers treat SPF as failed. Merge the mechanisms from both into a single record.

My record is valid here. Why does SPF still fail on received mail?

SPF is checked against the envelope sender domain (the Return-Path), which may differ from your From domain. Check the Return-Path in a received message header and validate that domain. The sending IP also has to match one of the mechanisms, so a service you never added to the record will fail.

Should my SPF record end with ~all or -all?

Use ~all (SoftFail) while you confirm every service that sends for your domain is listed. Switch to -all (Fail) once the list is complete if you want the stricter policy. With a DMARC policy in place, DMARC decides what happens to failing mail, so many domains keep ~all.

Need Enterprise Email Infrastructure?

Octeth provides self-hosted email marketing software with built-in deliverability tools. Own your infrastructure and save on SaaS fees.