Home / Businesses / DMARC Record Check (RFC 9989 / RFC 7489)
DMARC Record Check (RFC 9989 / RFC 7489)
Check a DMARC record against RFC 9989: whether receivers read it, the policy for the domain and subdomains, alignment, report addresses' form and external-report records, each problem with its RFC section, signed.
Testing
- What it does
- Check a DMARC record against RFC 9989: whether receivers read it, the policy for the domain and subdomains, alignment, report addresses' form and external-report records, each problem with its RFC section, signed.
- Who it is for
- Businesses.
- Start in one step
- Ask your agent to call
dmarc_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
DMARC Record Check (RFC 9989 / RFC 7489) is for agents that set up or fix email authentication for a business (DMARC rollout, deliverability problems, missing reports) and need the DMARC record checked before it goes into DNS. Check a DMARC record before you publish it or when DMARC reports or enforcement do not behave as expected. Send the TXT record text (for example 'v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com') and, optionally, the domain it is published for. Get back whether receivers read it at all, the policy that applies to the domain, to existing subdomains and to non-existent subdomains (with test mode t=y applied), DKIM and SPF alignment, the form of each aggregate and failure report address (scheme, destination domain, whether it needs an external-report authorization record and that record's name), and each problem with its RFC section. Checked against RFC 9989 (May 2026, which replaced RFC 7489); the old pct, rf and ri tags are read and flagged as historic. No DNS query is made, and the mailbox part of a report address is never echoed back. 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 authentication for a business (DMARC rollout, deliverability problems, missing reports) and need the DMARC 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; 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, check that the external-report authorization record exists, find the Organizational Domain, or see a second DMARC record at the same name. Does not check SPF or DKIM records or whether your mail passes alignment (use the SPF record check for SPF). Does not send or read reports. Report addresses are checked for form only; the mailbox part is never echoed or stored. Receivers that still follow RFC 7489 may treat some cases differently (pct, tag order); differences are flagged. Not legal or security advice.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "dmarc_record_check", "arguments": {"record": "v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.com; adkim=s", "domain": "example.com"}}}For agents
Tool dmarc_record_check on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:k4ht33hv3w6k4nwwwi4ctu4fey): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): +ZwihTusvjRM3tg2VD1fEvJmN0GZqTvrXZ+bCAkr7I4=
For agents that search MCP registries for DMARC record check, DMARC policy, 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: DMARC is one record of email authentication. Tell the Hub the whole job; it routes you to the SPF record check and other signed tools.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card