Start warming up today and get 20% off your first monthClaim offer

SPF Checker

Use this free SPF checker to look up your domain's SPF record, validate its syntax, and find errors that send your emails to spam.

10 checks remaining today
Examples:

Watch: SPF Checker: How to Check Your SPF Record and Fix 5 Common Errors (2026)

What is an SPF Record Checker?

An SPF record checker validates your domain's Sender Policy Framework configuration by querying DNS records and checking for proper syntax, multiple records, and authentication issues that could impact email deliverability.

Instant Validation

Quickly check if your domain has a valid SPF record and identify any configuration issues that could affect email delivery.

Detailed Reports

Get comprehensive analysis of your SPF record including syntax validation, duplicate detection, and specific error identification.

Improve Security

Properly configured SPF records help prevent email spoofing and improve your domain reputation with email providers.

How SPF Authentication Works

Email authentication through DNS records

1

DNS Lookup

When an email arrives, the receiving server checks the sender's domain DNS records for an SPF record that lists authorized mail servers.

2

Verification

The receiving server compares the sending server's IP address against the authorized servers listed in the SPF record.

3

Decision

Based on the SPF check result, the server decides whether to accept, flag, or reject the email according to your SPF policy.

Why SPF Records Matter

Critical for email deliverability and security

Prevent Email Spoofing

SPF records prevent attackers from sending emails that appear to come from your domain. This protects your brand reputation and prevents phishing attacks targeting your customers.

Improve Deliverability

Email providers like Gmail, Outlook, and Yahoo give preference to emails from domains with proper SPF authentication, significantly improving inbox placement rates.

Build Trust

Properly configured email authentication builds trust with email providers and recipients, establishing your domain as a legitimate sender and improving overall reputation.

Compliance

Many industries and email service providers now require SPF authentication as a baseline security standard for email communications.

Common SPF errors and how to fix them

If the SPF checker flags a problem, it's usually one of these. Rebuild a clean record with the SPF record generator.

Too many DNS lookups (the 10-lookup limit)

Each include, a, mx, ptr, exists and redirect costs a DNS lookup, and nested includes count too. Past 10, SPF returns a permerror. Fix: remove includes for services you no longer use, and replace static senders with ip4 or ip6 ranges.

Multiple SPF records

A domain can publish only one TXT record that starts with v=spf1. Two records cause a permerror, even if each is valid on its own. Fix: merge every include and IP range into a single record and delete the extra one.

+all or ?all at the end

+all authorizes every server on the internet to send as you, and ?all tells receivers to stay neutral. Both make SPF useless. Fix: end your record with ~all (soft fail) while testing, then move to -all (hard fail) once every sender is listed.

Missing include for your email provider

If your ESP, CRM or helpdesk sends mail as your domain but isn't in your record, its emails fail SPF. Fix: add the include your provider documents, such as include:_spf.google.com for Google Workspace or include:sendgrid.net for SendGrid.

permerror or softfail results

A permerror means the record is broken (syntax, duplicates or too many lookups), so receivers can't evaluate it. A softfail means the sending IP isn't authorized and you used ~all. Fix: correct the syntax for permerror, and add the missing sender for softfail.

SPF vs DKIM vs DMARC

Three records, one job: proving your email is really from you

SPF

Lists the servers allowed to send email for your domain. Receivers check the sending IP against it.

DKIM

Signs each message with a private key so receivers can verify it wasn't changed in transit. Test yours with theDKIM checker.

DMARC

Tells receivers what to do when SPF or DKIM fails, and reports who sends as your domain. Run aDMARC checknext.

Passing all three proves who you are, but mailbox providers also judge your sending history. A new or recovering domain still needs anemail warmup toolto build that reputation.

Related Resources

Learn more about SPF and email authentication

Related Email Authentication Tools

Enhance your email security and deliverability

Explore More Email Tools

Complete suite of free email tools

Frequently Asked Questions About SPF Records

Everything you need to know about SPF authentication

An SPF record is a DNS TXT record that lists the mail servers allowed to send email for your domain. SPF stands for Sender Policy Framework. Receiving servers compare the sending IP against this list, which helps stop spoofing and tells mailbox providers your messages are legitimate.

Enter your domain in the SPF checker above and run the check. The tool queries your DNS, finds the TXT record that starts with "v=spf1", and validates its syntax. You get a pass or fail result, the record itself, and a suggestion for anything that needs fixing.

Your email fails SPF when the server that sent it isn't listed in your SPF record, or when the record itself is broken. The usual causes are a missing include for your email provider, two SPF records on one domain, more than 10 DNS lookups, or a syntax error. Forwarded mail can also fail SPF.

An SPF record can trigger at most 10 DNS lookups. Every include, a, mx, ptr, exists and redirect counts toward that limit, including the lookups nested inside each include. Going over 10 returns a permerror, and many receivers treat that as an SPF failure. Remove unused includes or replace them with ip4 and ip6 ranges.

SPF, DKIM and DMARC are three email authentication standards that work together. SPF lists which servers may send for your domain. DKIM adds a cryptographic signature that proves the message wasn't altered. DMARC tells receivers what to do when SPF or DKIM fails, and sends you reports about who is sending as your domain.

A valid SPF record starts with "v=spf1", lists your authorized senders, and ends with an all mechanism. For example: "v=spf1 include:_spf.google.com ~all" authorizes Google Workspace and soft-fails everything else. Use ~all or -all at the end. Avoid +all, which lets any server send as your domain.

No, a domain can only have one SPF record. If a receiver finds two TXT records starting with "v=spf1", SPF returns a permerror and your email may fail authentication. To authorize several providers, merge them into a single record with multiple include mechanisms, for example "v=spf1 include:_spf.google.com include:sendgrid.net ~all".

Without an SPF record, receiving servers can't verify that your emails come from an authorized server. Gmail requires SPF or DKIM from every sender, so unauthenticated mail is more likely to land in spam or be rejected outright. Anyone can also spoof your domain more easily.

Improve Your Email Deliverability

Need help with email authentication and deliverability? Mailwarm helps you build sender reputation and ensure your emails reach the inbox. Want the full picture? Run a free email deliverability test.