LLPROBeta

Home / Businesses / DKIM Record Check (RFC 6376)

DKIM Record Check (RFC 6376)

Check a DKIM key record against RFC 6376: whether verifiers read it, key type and length in bits, revoked and testing flags, allowed hashes, each problem with its RFC, signed.

Testing

What it does
Check a DKIM key record against RFC 6376: whether verifiers read it, key type and length in bits, revoked and testing flags, allowed hashes, each problem with its RFC, signed.
Who it is for
Businesses.
Start in one step
Ask your agent to call dkim_record_check at 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

DKIM Record Check (RFC 6376) is for agents that set up or fix email authentication for a business (DKIM keys, selectors, deliverability problems) and need the key record checked before it goes into DNS. Check a DKIM public key record (the TXT record published at <selector>._domainkey.<domain>) before you publish it or when DKIM fails. Send the record text (for example 'v=DKIM1; k=rsa; p=MIIBIjANBg...'), and optionally the selector and domain. Get back whether verifiers read the record at all, the key type (rsa or ed25519), the key length in bits (read from the key itself), whether the key is revoked (empty p=) or in testing mode (t=y), the allowed hashes and service types, the strict-subdomain flag, the key's SHA-256 fingerprint, and each problem with its RFC: no p tag, a key under 1024 bits (cannot validate) or under 2048 (below the recommended size), a key that is not valid base64 or not a real key, a hash list with no SHA-256. No DNS query is made. 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 (DKIM keys, selectors, deliverability problems) and need the key 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. 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, see a second record at the same name, check that the private key matches, or check a mail signature. Does not test whether a key is strong beyond its length (it does not factor it or check the exponent), and does not check TXT string splitting (a 2048-bit key needs two strings of at most 255 characters; send them joined). Key rotation advice is outside it. Not legal or technical advice.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "dkim_record_check", "arguments": {"record": "v=DKIM1; k=ed25519; p=11qYAYKxCrfVS/7TyWQHOg7hcvPapiMlrwIaaPcHURo=", "selector": "brisbane", "domain": "football.example.com"}}}

For agents

Tool dkim_record_check on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:tujzcgigsjgvuos2jvotjprqwa): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): ZrVAisRmkHgsJ/x8T2s9O12Z7taBWs7h3fadKDsinwA=

For agents that search MCP registries for DKIM, DKIM record, DKIM selector tools (listed in MCP registries, served by the LLPRO gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.

Next

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card