Adding another mail sender
Check whether an SPF record already exists before publishing a new one.
Look up a domain's Sender Policy Framework record and inspect the published sending policy.
SPF is a DNS-based policy that tells receiving systems which servers are allowed to send mail for a domain. It is one part of email authentication alongside DKIM and DMARC.
The tool reads public TXT records and identifies entries beginning with v=spf1. A published SPF record does not guarantee inbox placement, but missing or broken authentication can contribute to delivery problems.
The SPF checker reads the published TXT policy and flags a limited set of record issues. It does not recursively evaluate includes or determine whether a specific sending IP is authorised.

Use the domain for the policy you are investigating.
Look for duplicate records, permissive all mechanisms and reported top-level issues.
Inspect received message headers to see the receiver’s SPF result for an actual sender.
Illustrative scenarios, not live results for the addresses or records shown. Open a scenario to see the next action.
This can be intentional for a domain that sends no mail.
Next action Do not copy it onto an active sending domain.
Multiple SPF records need review; adding another record is not the way to add a sender.
Next action Follow your provider’s instructions for one combined policy.
An include may lead to more lookups. This tool counts only top-level lookup-causing terms.
Next action Use sender-aware evaluation for the entire chain.
Check whether an SPF record already exists before publishing a new one.
Look for supported policy mistakes before inspecting a message sent through the service.
No. Nested includes, macros and runtime sender-IP evaluation are outside this tool’s scope.
SPF evaluates an envelope or HELO identity. DMARC adds alignment with the visible author domain.
No. A pass or failure is determined for a particular message and sending host.
Technical reference: SPF specification.