This reads the same public DNS records any spammer can read — your SPF and DMARC — then tells you which line to change. Runs entirely in your browser. Nothing is stored, nothing is sent to you.
Example: outdoorvoices.com · gymshark.com — one fails, one passes. That contrast is the whole point.
Changing p=none to p=reject in one afternoon breaks your transactional mail if you skip the ramp. The Deliverability Rescue Kit is the checklist, the warm-up schedule and the rollback plan for that change — $47, one-time. All packs →
v=spf1 on the root domain) — tells receivers which servers may send for you. More than one record, or more than 10 lookups, and the whole record is invalid per RFC 7208._dmarc.yourdomain) — p=none means receivers report but never block. A forged sender still lands. p=quarantine or p=reject is what actually stops it.rua=) — without it you never see who is sending as you, so you cannot tell an attack from your own ESP.DKIM is deliberately not scored. Most senders sign with an ESP-specific selector, so probing default._domainkey produces false alarms on healthy domains. A checker that cries wolf is worse than no checker.
The order matters more than the edit. Publish DMARC at p=none with rua= first, read two weeks of reports to find every legitimate sender, get them into SPF/DKIM, and only then move to quarantine and reject. Skipping to reject on day one is how order confirmations and password resets start bouncing.