Deliverability — how this works

In the app: /deliverability

How it works

The sending fleet mirrors Instantly's inboxes/domains (Instantly does the real SMTP + warmup). This page reads that model: per-domain SPF/DKIM/DMARC/MX authentication, the inboxes at risk (unhealthy or paused), and a rollup. It's read + display — pausing/suppression happen automatically from bounce/complaint handling (DELIVER-06), not from a button here.

Data source

src/lib/deliver/mailboxRepo.ts (Mailbox/SendingDomain) + src/lib/deliver/dnsHealth.ts (the display logic).

Troubleshooting

A domain shows unauthenticated? SPF/DKIM/DMARC/MX are read from Instantly / our own checks onto the SendingDomain row — a 'fail'/'unknown' means the DNS record needs fixing at the registrar, not a bug here. An inbox shows at-risk when its health isn't healthy or it's paused (often auto-paused by a complaint spike).

Vendors: instantly — check Tools for live/mocked status.

Who can see this: admin