# Find out why an email did not arrive

> Find out why an email did not arrive: 6 companies fully do it, 11 with a limit, 20 carry the tag. Every listing in Email delivery APIs with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/email.delivery-diagnosis/
- Markdown: https://www.anchorterminal.com/niches/email.delivery-diagnosis/index.md (~1,600 tokens)
- Slim: https://www.anchorterminal.com/niches/email.delivery-diagnosis/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/email.delivery-diagnosis/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Four or more companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 6 | 11 | 20 | 10 | 4 |

## What counts as done

A per-message status (delivered, bounced, deferred, suppressed) with the remote SMTP reason, for a message up to 7 days old.

Measured, for our own tests: it is found in at most 3 calls.

How agents ask for it: did the email go out; why didn't the customer get the reset email; check bounces for this address; is this provider down

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **AhaSend API + MCP (AhaSend B.V.)**: Get Message returns status, bounce_classification and delivery_attempts with each attempt's log line, in one call. Free keeps metadata up to 7 days, the default for new accounts.
- **Brevo API + MCP (Sendinblue SAS)**: GET /v3/smtp/statistics/events filters by messageId or email over up to 90 days and returns each event with the bounce reason, in one call. Limited to 2 requests a second per the context notes.
- **Cloudflare Email Service (Cloudflare, Inc.)**: The activity log and the emailSendingAdaptive GraphQL dataset give per-message status (delivered, delivery failed, dropped) with bounce reason codes over up to 30 days, in one query.
- **Groundmail API + MCP (Power Only Transit Inc. dba Groundmail)**: GET /emails/{id} gives status with bounce_reason, events are listed per email, and Free keeps logs 7 days (90 on pay as you go), so one or two calls answer a week-old message.
- **Mailchimp Transactional (Mandrill) (The Rocket Science Group LLC d/b/a Mailchimp)**: Search and messages/info return state with smtp_events and their SMTP diagnostic messages (smtp_events.diag); content is kept 30 days and bounce data 90 days, within the 7-day window.
- **Postmark API + MCP (AC PM, LLC)**: GET /messages/outbound/{id}/details returns the message with its Delivered, Transient or Bounced events, and messages are kept 45 days by default, so one call answers a week-old message.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Amazon SES (Amazon Web Services, Inc.)**: GetMessageInsights takes a MessageId and returns per-destination events with bounce type and DiagnosticCode, at one call a second. The reference page doesn't state how long insights are kept or whether Virtual Deliverability Manager must be on.
- **MailerSend (MailerSend, Inc.)**: GET /v1/email/{email_id} returns the email with its activity events and a suppression_reason when rejected, in one call; it is limited to 10 requests a minute, and retention per plan wasn't read this run.
- **Mailgun API + MCP (Mailgun Technologies, Inc.)**: The Events API filters by message id or recipient and returns delivery status with the remote SMTP message, but the Free plan keeps logs 1 day, short of the 7-day window; paid plans keep more.
- **Mailjet API + MCP (Mailjet SAS)**: GET /v3/REST/message/{id} gives the current status and messagehistory gives events, in two calls. The pages read show no remote SMTP reason field and no retention period.
- **MailPace (OhMySMTP Ltd)**: GET /api/v1/domains/:domain_id/emails/:id returns status and the remote bounce_reason in one call. The docs read give no log retention period.
- **Mailtrap Email API + MCP (Railsware Products Studio LLC)**: Email logs filter by status, event and provider with event history per message, reachable through the API and MCP. Retention depends on plan; the free plan keeps 3 days, short of the 7-day window.
- **Resend API + MCP (Plus Five Five, Inc.)**: GET /emails/{id} returns last_event and logs are kept 30 days, but the retrieve response shows no remote SMTP reason; bounce messages and subtypes come through webhooks or the dashboard.
- **Twilio SendGrid (Twilio Inc.)**: Email Logs filters by message id and returns every event with attempts and bounce or drop reason. The older Activity Feed API needs a purchased history add-on, and retention by plan wasn't stated on the pages read.
- **SendLayer (SendLayer, LLC)**: GET /events filters by MessageID, event and date, and the email log marks accepted, rejected or failed. The pages read give no remote SMTP reason field or retention period.
- **SMTP2GO API + MCP (Sand Dune Mail Ltd)**: One /email/search call filtered by recipient returns per-email status with smtpcode and the remote response. Retention wasn't stated on the reference page read.
- **Zoho CPaaS (formerly ZeptoMail) (Zoho Corporation)**: GET /email lists logs and GET /email/{id} returns one email's details, with bounce analytics in the product. The fields and retention weren't on the index page, and logs need an OAuth token rather than the send key.

- not this job: Loops API + MCP (Astrodon Corporation): No API endpoint looks up a sent message or its bounce reason; status is on the dashboard Metrics page and in email.delivered, softBounced and hardBounced webhooks. Suppression status can be checked by email.

## What stops agents finishing

- free plan keeps logs 1 to 3 days
- status page has no component for the API or MCP

## Around it

Before: email.transactional-send, support.triage-and-route. After: email.transactional-send.

## Where this comes from

Weight 10 of 100 in Email delivery APIs: 4 of 32 accounts: bounce logs (e27), body search for abuse (e22), a provider outage (e23) and an unverified domain found by an agent (e16)

As data: https://www.anchorterminal.com/api/v1/use-cases/email.delivery-diagnosis.json, or the MCP tool get_use_case with id email.delivery-diagnosis. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
