Most incidents start with one domain, not all domains.
You see a sudden dip in inbox placement for one sender, or a teammate says "I think we changed DNS yesterday." In those moments, broad dashboards are useful, but you need depth on one domain quickly.
gives you that focused view.
Why single-domain detail matters
A dedicated monitor detail read lets you:
- confirm whether monitoring is active
- verify current check interval
- see latest status and score before taking action
- avoid guessing before triggering a run-now check
It's the "show me the truth for this one domain" endpoint.
Endpoint
cURL example
What to pay attention to
When you're investigating quickly, you don't need every field. You need the ones that drive the next action:
: are you actually monitoring, or is it paused?: how frequently should you expect fresh data?- latest status/score: is this a current failure or a stale one?
- domain identity: are you looking at the right environment or the right sender domain?
If the monitor shows that scheduling is paused or the interval is long, a run-now check is usually the next step.
Where this fits in a workflow
A common operational sequence:
- Find a risky domain in the list view.
- Open monitor detail with this endpoint.
- Validate schedule and last status.
- Run a manual check if needed.
- Review run history and trends.
Investigate faster
Deliverability incidents are won or lost in the first few minutes of investigation. Getting accurate single-domain state fast helps your team make better decisions under pressure.