Preview an SPF change.

See the rule changes and lookup impact before adding or removing a sending service.

Free. No account required. Your DNS is never changed.

Sending domain (optional for a pasted record)

Pasted records are processed in this browser. “Load published SPF” and “Check lookup impact” query Google Public DNS, which receives the queried names and your IP address. Records and edits are not saved. Privacy details.

Current SPF record

Paste the current record or load it from public DNS. Include the v=spf1 prefix. Quoted DNS TXT chunks are accepted on one line.

Add an email provider

Select only services you use. Confirm the required record and sending domain in each provider’s instructions.

Add or remove rules and change the final result

Add other rules (optional)

One include:, ip4: or ip6: rule per line. Replace example values with the addresses supplied by your provider.

Remove exact rules (optional)

Copy the complete rule from the current record. Remove it only after confirming the service is no longer used.

When no sender rule matches

A different final rule changes the result for unmatched senders. This tool blocks open +all policies and rules that need a manual review.

Example: add a second sender

A domain currently allows one fixed sending IP. Adding a second IP keeps the existing final rule and adds no DNS-querying terms. These documentation addresses are examples, not values to publish.

Before	Proposed
`v=spf1 ip4:192.0.2.10 ~all`	`v=spf1 ip4:192.0.2.10 ip4:198.51.100.20 ~all`

The proposed example has 0 DNS-querying terms. Real provider includes can add nested dependencies, so their lookup impact must be checked separately.

Before publishing

SPF applies to the SMTP return-path domain, which can differ from the visible From address. Confirm the services you use and their setup instructions, then publish one SPF TXT record at the correct name. Recheck it after saving.

This planner handles static, pass-qualified include, IP, a and mx rules. It preserves their order and does not rewrite redirects, modifiers, macros, ptr, exists or non-pass rules. Lookup counts are potential DNS-querying terms, not a test of a particular message or a guarantee of delivery.

Rule handling follows RFC 7208.