Email deliverability

Catch delivery problems before your agent sends.

Domani blocks preventable mistakes, watches real delivery outcomes, and keeps inbox evidence separate from provider receipts.

One status cannot tell the whole truth.

A perfect DNS setup does not guarantee Inbox placement. Domani reports three independent sources of evidence so humans and agents know what is proven.

Limited data

Authentication is ready. More delivery outcomes are needed.

4/4
configuration checks ready
Authentication

MX, SPF, DKIM, and DMARC are deterministic checks.

MX
SPF
DKIM
DMARC
Sending health

Bounces, complaints, suppressions, and volume create the observed history.

Confidence: limited
Low volume is reported as missing evidence, not a perfect score.
Inbox placement

Gmail, Outlook, and Yahoo are measured independently.

GmailNot tested
OutlookNot tested
YahooNot tested

Prevent the mistakes software can recognize.

The same policy engine protects every sending path. An agent cannot bypass a critical check by switching from the API to SMTP.

Localhost, private, test, and reserved links
Insecure or cross-domain authentication actions
Executable and script attachments
Duplicate authentication retries without idempotency
Suppressed recipients after hard bounces or complaints
Unsafe recipient fanout and sudden account-level risk

Delivered is not the same as Inbox.

A delivered event means the receiving server accepted the message. It does not reveal whether the message reached Inbox, Spam, or disappeared into a provider-specific filter.

Domani preserves that distinction in the dashboard and the API. When placement has not been tested, the result says “Not tested.”

Give every send a safety check.

Create an inbox for your agent. Domani applies the same protections across web, API, MCP, and SMTP.