Skip to content
BEAD

SPF / DKIM / DMARC Parser

Paste an email-auth TXT record and see it broken down, validated, and explained.

DiagnosticsNetworkSEO
Detected: spf
v=spf1SPF version 1.
include:_spf.google.comInclude policy of _spf.google.com. Pass.
~allMatch every sender. Qualifier: Soft fail (mark suspicious).

🔒 Records are parsed entirely in your browser.

</>Use this tool programmaticallycurl · JavaScript · MCP

Same tool, callable from any HTTP client or from Claude (via MCP). Anonymous: 100 req/day per IP. Sign up for 1,000 req/day.

curl
curl https://api.b-e-a-d.com/tools/email-auth-parser/run \
  -H "Content-Type: application/json" \
  -d '{
  "input": "your input here"
}'
JavaScript (fetch)
const res = await fetch("https://api.b-e-a-d.com/tools/email-auth-parser/run", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
  "input": "your input here"
}),
});
const data = await res.json();
console.log(data.result);
MCP (Claude Desktop / Claude Code)
# In Claude Desktop / Claude Code, add to your MCP config:
{
  "mcpServers": {
    "bead": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.b-e-a-d.com"]
    }
  }
}

# Then ask Claude to call:
mcp__bead__bead_email_auth_parser

Full reference: developer docs · OpenAPI spec

About these records

  • SPF (TXT at the domain root) lists the IPs / hosts allowed to send mail for the domain.
  • DKIM (TXT at selector._domainkey.example.com) carries the public key recipients use to verify message signatures.
  • DMARC (TXT at _dmarc.example.com) tells receivers what to do when SPF or DKIM fail, and where to report.

This tool just parses what you paste — it doesn't query DNS. For lookups, see the upcoming DNS Lookup tool.

You might also like

Used in these workflows