Home / Businesses / SPF Record Check (RFC 7208)
SPF Record Check (RFC 7208)
Check an SPF record the RFC 7208 way: every term read, DNS lookups counted against the limit of 10 (nested records too when you send them), and each problem with its RFC section, signed.
Testing
- What it does
- Check an SPF record the RFC 7208 way: every term read, DNS lookups counted against the limit of 10 (nested records too when you send them), and each problem with its RFC section, signed.
- Who it is for
- Businesses.
- Start in one step
- Ask your agent to call
spf_record_checkat llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it. - What to expect
- Testing: open to try. Free
New to this? Start here.
What it does
SPF Record Check (RFC 7208) is for agents that set up or fix email sending for a business (domain records, new mail providers, deliverability problems) and need the SPF record checked before it goes into DNS. Check an SPF record before you publish it or when mail fails SPF. Send the TXT record text (for example 'v=spf1 include:_spf.example.net mx -all'). Get back every term read the RFC 7208 way (mechanism or modifier, qualifier, what a match returns, target, CIDR length, whether it costs a DNS lookup and whether it is ever evaluated), the DNS-lookup count against the limit of 10, the result when nothing matches, and each problem with its RFC section: syntax errors (permerror), more than 10 lookups, two redirect or exp modifiers, ptr, +all, terms after all, a redirect that all cancels, a missing all, a record too long for one string. The tool makes no DNS query: send the records of include and redirect targets in included_records to count the nested lookups too; any target you do not send is listed and the count is then a minimum. It is one of the Email department tools LLPRO builds for the work agents do across business software (Gmail, Outlook, Google Workspace, Microsoft 365, Sendgrid). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.
- Who it is for
- Agents that set up or fix email sending for a business (domain records, new mail providers, deliverability problems) and need the SPF record checked before it goes into DNS.
- Price
- Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
- Limits
- Up to 30,000 bytes per call, included_records up to 40 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Money takes up to 2 decimals unless a field says more, and every sum is exact (send amounts as numbers or strings; commas only as thousands separators, 1,234.56). Nothing you send is stored by the tool; no model and no network are used. Makes no DNS query: it does not fetch the record, find a second SPF record at the same name (two records are a permerror, 4.5), resolve include or redirect targets you do not send, expand macros, count MX or PTR host lookups (10 per mechanism, 4.6.4) or void lookups (limit 2), or test whether an IP address passes. The lookup count is the worst case for a sender that matches nothing; a real check stops at the first match. Does not check DKIM or DMARC (use the DMARC record check) or whether the senders listed are yours. Not legal or security advice.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "spf_record_check", "arguments": {"record": "v=spf1 ip4:192.0.2.0/24 mx include:_spf.example.net include:mail.example.org -all"}}}For agents
Tool spf_record_check on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:tc4jzxoustwhy5mksio743onpq): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): HbsNX3Qy0S/e34nzbBCIT0eocl1W2YUsTk45rnt3o3E=
For agents that search MCP registries for SPF record check, SPF lookup limit, email authentication tools (listed in MCP registries, served by the Campus gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Get your agent: No agent yet? Get one that asks first.
- Hand the whole job to the Hub: SPF is one record of email authentication. Tell the Hub the whole job; it routes you to the DMARC record check and other signed tools.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card