SPF Record Checker (Free) – Validate SPF Syntax & Lookups

Validate your SPF record in seconds. We check syntax, includes, lookup count, and surface permerror or temperror so you can fix issues before they affect deliverability.

What we check

  • Syntax — Valid mechanisms and modifiers (include, a, mx, ip4, etc.).
  • Includes — Resolved include: domains and that they don’t exceed lookup limits. How include works.
  • Lookup count — Total DNS lookups (SPF allows max 10). Why 10 and how to fix.
  • Permerror / Temperror — Permanent or temporary errors that can cause rejections or retries.

Common SPF failures

  • More than 10 DNS lookups (too many includes or mechanisms).
  • Invalid syntax (typos, malformed mechanisms).
  • Missing or incorrect include for your ESP (e.g. SendGrid, Mailchimp).
  • Multiple SPF records (only one is allowed per domain).
  • Permerror left unfixed so receivers treat SPF as fail or softfail.

Check my SPF record

Get SPF, DMARC, and key headers checked in one go. No signup required.

Check my SPF recordView pricing

FAQ

What does an SPF record checker actually validate?

A good checker validates syntax (mechanisms, modifiers), resolves all includes and counts DNS lookups (max 10), and flags permanent or temporary errors so you can fix them before sending.

Why do I get 'too many DNS lookups'?

SPF allows at most 10 DNS lookups when a recipient evaluates your record. Each include, a, mx, or ptr can consume lookups. Consolidate includes or use subdomains to stay under the limit.

What's the difference between permerror and temperror?

Permerror means the record is invalid (e.g. syntax error, over lookup limit) and may cause rejections. Temperror is a temporary DNS failure; some receivers will retry or allow the message.

Is checking SPF read-only?

Yes. We only read your domain's DNS. We don't send email or modify any records.

Related reading

Read-only checks. We don't send email or modify DNS. How we check