Home / Businesses / One-Click Unsubscribe Header Check
One-Click Unsubscribe Header Check
Check an email's List-Unsubscribe and List-Unsubscribe-Post headers and DKIM h= list against RFC 8058 one-click unsubscribe, each problem named by its rule, with a signed record.
Testing
- What it does
- Check an email's List-Unsubscribe and List-Unsubscribe-Post headers and DKIM h= list against RFC 8058 one-click unsubscribe, each problem named by its rule, with a signed record.
- Who it is for
- Businesses.
- Start in one step
- Ask your agent to call
one_click_unsubscribe_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
One-Click Unsubscribe Header Check is for agents that send marketing or bulk email for a business and must make every message one-click unsubscribable the way RFC 8058 and the big mailbox providers expect. Check a marketing or bulk email's one-click unsubscribe headers against RFC 8058 before sending (large mailbox providers ask bulk senders for one-click unsubscribe). Send the List-Unsubscribe header value, the List-Unsubscribe-Post header value and, if you have it, the DKIM-Signature header value. Get back whether the message is one-click ready: the HTTPS address found (its host only), each other address (mailto and so on), whether the Post header is exactly the one key/value pair, whether the DKIM h= list covers both headers, and each problem by its RFC rule. It is one of the Email department tools LLPRO builds for the work agents do across business software (Mailchimp, Klaviyo, HubSpot, Salesforce, Gmail). 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 send marketing or bulk email for a business and must make every message one-click unsubscribable the way RFC 8058 and the big mailbox providers expect.
- 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. Does not fetch the URL or send the POST (no network): it cannot check that the address answers a POST without a redirect (RFC 8058 3.1 MUST NOT redirect), that the unsubscribe works, or that the identifier is hard to forge. Does not verify the DKIM signature itself (needs the whole message and the sender's DNS key): it reads only the h= list; the receiving system's Authentication-Results decide. Takes one value per header: RFC 8058 wants exactly one List-Unsubscribe and one List-Unsubscribe-Post field, and RFC 2369 no more than one of each, so a message with two fails whatever this says. Does not check mailbox providers' own sender rules or CAN-SPAM (see can-spam-footer-check). Addresses in the URIs are never echoed in full: only the HTTPS host and each URI's scheme. Nothing is stored.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "one_click_unsubscribe_check", "arguments": {"list_unsubscribe": "<https://example.com/unsubscribe/opaquepart>", "list_unsubscribe_post": "List-Unsubscribe=One-Click", "dkim_signature": "v=1; a=rsa-sha256; c=relaxed/relaxed; d=example.com; s=s1; h=From:To:Subject:Date:List-Unsubscribe:List-Unsubscribe-Post; bh=abc=; b=def="}}}For agents
Tool one_click_unsubscribe_check on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:kw4yptmwsmsuw7gmgbamhswtby): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): 4D9mZVApcrK7+Vr1Gzt7LxgxCEgBDGdM1CjB7aOtOCY=
For agents that search MCP registries for one-click unsubscribe, RFC 8058, List-Unsubscribe 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: Checking unsubscribe headers is one step of sending a campaign. Tell the Hub the whole job; it routes you to the right signed tools.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card