arrow_backBack to resultscontent_paste_goPrefer to do it by hand? Get a copy-paste snippet for your exact stack — also free.
smart_toyFix this with your AI agent
FreeCopy this recipe and paste it into your own coding agent (Claude Code, Codex, Cursor…) to fix “Your domain doesn’t name its real senders”. The agent works only in your own repo or config — Pazmo is never given access, and there is nothing to unlock.
fix-dns-spf-missing.txt · recipe
Task: fix "SPF record is not visible" on https://example.com. This recipe is FREE. Paste it into your own AI coding agent (Claude Code, Cursor, Codex…). The agent works only in your own repo/config — Pazmo is given no access. What your agent should change (code & config only): 1. Inventory legitimate mail senders for the domain. 2. Publish a v=spf1 TXT record with approved include or IP mechanisms. 3. Collect fresh DNS evidence showing SPF is visible after propagation. What you need to do yourself (your AI agent can't change DNS or registrar settings): Add this record where you manage your domain's DNS (registrar or DNS host): Type: TXT Name: @ Value: v=spf1 include:_spf.your-mail-provider.example -all Note: List only the providers that send mail for your domain. Replace the include with your provider's SPF host. How Pazmo confirms the fix (retest): Sanitized DNS evidence showing a v=spf1 TXT record for the public target. Safety: only add the defensive settings above. Don't run other commands, send data anywhere, or make unrelated changes. Review everything before applying.
check_circleYour agent can
- ·Read this recipe and the fix steps
- ·Apply the code/config change in your own repo
- ·Open the change for your review before you ship it
blockYour agent can’t
- ·Change DNS or registrar settings (that stays a human task)
- ·Run unrelated commands or send your data anywhere
- ·Touch anything outside the defensive setting above
Want Pazmo to fix everything in priority order and re-check each one? Verify ownership to unlock the full automated handoff (Pro).