Home / Businesses / Email Received-Header Hops
Email Received-Header Hops
Paste an email's Received headers and get each hop in order with its UTC time and delay, the largest gap and where it was, and clock problems, signed; no address is echoed or stored.
Testing
- What it does
- Paste an email's Received headers and get each hop in order with its UTC time and delay, the largest gap and where it was, and clock problems, signed; no address is echoed or stored.
- Who it is for
- Businesses.
- Start in one step
- Ask your agent to call
email_header_hopsat 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
Email Received-Header Hops is for agents that handle email delivery questions for a business ('why did this arrive an hour late?') and need the hop delays worked the same way every time without keeping anyone's addresses. Find where an email was delayed. Paste the message's Received: header lines (or the whole header block); get back each hop in order from the first server to the last, its time in UTC, the delay from the hop before (from the Date field for the first hop when it is pasted), the largest gap and which server it was at, the total time, and hops whose clocks disagree. Addresses, IP addresses and message ids in the headers are read past, never echoed and never stored. 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 handle email delivery questions for a business ('why did this arrive an hour late?') and need the hop delays worked the same way every time without keeping anyone's addresses.
- 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. Does not tell which Received lines are genuine: anything below your own provider's first line can be forged by the sender. Does not read X-Received, ARC or Authentication-Results lines, look up servers, or judge spam or delivery problems. Does not correct server clocks: a delay is only as true as the two clocks. Accepts US-ASCII header text only (RFC 6532 UTF-8 headers are refused). Echoes no address, IP address, 'for' recipient or message id; nothing you paste is stored.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "email_header_hops", "arguments": {"headers": "Received: by mx.example.net with ESMTPS id 1a2b; Tue, 3 Mar 2026 10:00:05 +0000\nReceived: from mail.sender.example (mail.sender.example [192.0.2.10])\n\tby relay.example.org with ESMTP; Tue, 3 Mar 2026 09:59:50 +0000\nReceived: from [192.0.2.7] by mail.sender.example with ESMTPSA for <someone@example.net>; Tue, 3 Mar 2026 04:59:40 -0500\nDate: Tue, 3 Mar 2026 04:59:38 -0500\nSubject: hello\n"}}}For agents
Tool email_header_hops on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:r2k57k42on3aqoia6sffsh44xq): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): SFAYqnBzDWCMNQdksKocS7xhcPfMpYC8ZMzMNVz2CAA=
For agents that search MCP registries for email headers, Received header, email delay 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
- 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 LLPRO: Hop delays are one step of fixing email delivery. Tell LLPRO the whole job; it routes you to the SPF, DMARC and other signed email tools.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card