SenderReady
$49 audit$49 audit

Will your SPF record survive a sender-readiness review?

Turn SPF lookup-count and include-chain risk into a shared action plan before the next campaign.

01$0Free scan

Check the public sender-auth records mailbox providers expect.

02$0Shareable action plan

Keep one URL with evidence, owner steps, and decisions.

03$49$49 fix plan

Add human review, provider context, and verification steps.

Optional. Most first scans can run with just the domain.
Checks Gmail, Yahoo, and Microsoft sender requirementsPublic DNS onlyNo mailbox login needed
Example result72/100Needs attention

Review DMARC policy strength before a high-volume send.

Public DNS evidence
DMARC/SPF/DKIM status and caveats are visible before you pay.
Owner-ready next step
The audit adds provider context and a verification checklist.
Get the exact fix plan for your domain.$49 readiness audit: prioritized owner actions, DNS evidence, and verification checks.
Get my $49 fix planView sample
Sender readiness cockpitExample action plan

Public DNS workspace

Overall sender readiness

72/100

Needs attention

Sample output: one warning and one fail mean this domain is not campaign-ready yet.

DMARCPass
SPFPass
DKIMPass
MXPass
BIMIWarning
MTA-STSFail

Fix workspace preview

The scan becomes a focused work surface: evidence, owner action, verification, and the paid context a public lookup cannot infer.

HighDMARC

Review DMARC policy strength before a high-volume send.

Evidence
Evidence: a monitoring-only policy can satisfy visibility needs, but enforcement requires aligned legitimate senders.
Verify after change
Re-scan _dmarc after DNS propagation and confirm aligned SPF or DKIM senders before enforcement.
Paid audit adds
Policy sequence, starter record review, alignment questions, and enforcement caveats.
Get my fix plan

What SPF readiness means

SPF lists the mail servers and platforms allowed to send for a domain. SenderReady reads the public SPF TXT record and flags common readiness issues to review before you send.

Official references

Google SPF setup guidanceMicrosoft email authentication overviewYahoo Sender Hub best practices

What this checker reviews

The scan looks for SPF TXT records at the domain root, follows public include and redirect chains, and reports lookup-count risk, duplicate records, loops, and missing include targets where public DNS exposes them.

Google describes SPF or DKIM as a requirement for all senders to personal Gmail accounts and lists SPF, DKIM, and DMARC for bulk senders. Yahoo similarly lists SPF or DKIM for all senders and stronger authentication for bulk senders. Public SPF recursion still does not prove every real sender, DKIM selector, provider account setting, or DMARC alignment outcome.

SPF FAQ

Can a domain have more than one SPF record?

Multiple SPF TXT records can cause validation problems. Keep one SPF policy at the domain root and include all approved senders inside it.

Does SPF alone satisfy bulk sender requirements?

No. Gmail and Yahoo describe SPF, DKIM, and DMARC as part of their bulk sender requirements. Microsoft also announced SPF, DKIM, and DMARC requirements for high-volume Outlook.com senders.

Why can forwarded mail fail SPF?

SPF checks the sending server in the SMTP path. Forwarding can change that path, which is why DKIM and DMARC alignment are also important to review.