Teams usually don't need more raw data. They need clearer answers.
Is the domain stable? Is risk increasing? What should we fix first?
is designed to answer those questions in a compact summary.
What an email deliverability report should do
"Deliverability report" can mean a few different things. Some reports focus on inbox placement testing. Others focus on authentication and domain posture. This endpoint is in the second category: it helps you summarize the domain health signals that typically cause deliverability to drift.
A useful deliverability report should:
- be readable by non-specialists (operators, product leads, marketing leads)
- highlight changes over time (not just current state)
- name the top 1 to 3 fixes that will reduce risk fastest
- separate urgent failures from background improvements
When you treat deliverability like an operational surface area, the report becomes part of your weekly cadence rather than an emergency artifact.
What makes this endpoint useful
It combines multiple runs into higher-signal indicators such as:
- success rate
- average health score
- healthy streak metrics
- positive and negative signals
- top findings to prioritize
That makes it ideal for weekly reviews, handoffs, and leadership updates.
Endpoint
cURL example
How to turn insights into a report people act on
If you already have dashboards, the main win is packaging. A good report tends to follow a consistent structure:
- Current risk summary (one sentence)
- Trend summary (what changed since last week)
- Top findings (prioritized)
- Recommended actions (what to do next)
- Evidence links (run history, raw DNS checks, tickets)
The point is to remove interpretation work. Your audience should be able to answer "what should we fix first?" without opening five tools.
Example report outline (weekly)
Use this as a template for a weekly deliverability report meeting:
- Overall status: Healthy, Degraded, or Critical
- Auth posture: SPF status, DMARC policy strength, MX stability
- Trend highlights: improving, stable, deteriorating
- Top findings:
- finding 1 (impact + suggested fix)
- finding 2 (impact + suggested fix)
- finding 3 (impact + suggested fix)
- Action plan:
- owner, due date, and verification step (run-now or next scheduled run)
If you keep the outline consistent, stakeholders learn to read it quickly and the report becomes a reliable decision input.
Where this fits in UI
- Summary cards above trend charts.
- "Needs attention" callouts for operators.
- Executive-friendly snapshot blocks for status meetings.
Make it actionable
If run history is the evidence, insights are the narrative. This endpoint helps teams understand and communicate domain health without manual interpretation work.