Free tool · Deliverability

Find what is eating
your SPF budget.

Walk your include chain and count against the 10-lookup limit.

Runs entirely in your browser. No signup, nothing stored.
Record
DNS lookups

Each include:, a, mx, ptr, exists: and redirect= costs one lookup — including those nested inside records you include. exists: containing an %{i} macro is counted but cannot be expanded here, because the sender IP is unknown. Every SPF tool has that limitation.

How this works

The method, not the marketing.

SPF permits a maximum of ten DNS lookups when a record is evaluated. Every include, a, mx, ptr, exists and redirect counts — including the ones nested inside records you include. Exceed ten and the result is permerror, which most receivers treat as a failure.

This is the failure mode that bites in practice, because each provider you add costs one to three lookups. A company using an ESP, a CRM, a helpdesk and a payroll tool can quietly pass the limit and find out months later.

Flattening — replacing includes with raw IP addresses — is sold as a paid service almost everywhere. It works, and it goes stale the moment your provider rotates IPs, which is precisely why it is sold as a hosted subscription rather than a one-off. Fixing the chain is usually better than flattening it.

One limitation, shared by every SPF tool: an exists: mechanism containing an %{i} macro is counted but cannot be expanded, because the sender IP is unknown outside a real delivery.

Bring your provider.
Keep your brands distinct.
Start today.

Set up your first workspace, connect a provider, and publish a workflow — free, in test mode, before you pay a thing.