The categories, and what each one really covers
Deliverability tooling splits into four categories that solve genuinely different problems. Most frustration with these tools comes from expecting one category to answer a question that belongs to another.
Tool categories
what each solves, and what it will not tell youMonitoring is the category that earns its cost
Point-in-time checkers are useful when you are debugging something specific. Continuous monitoring is what actually prevents incidents, because deliverability failures are almost always gradual, and the useful moment is while a trend is forming rather than after placement has collapsed.
Kam built our trends layer around exactly that: spam-rate and per-provider placement trends, plus DNSBL monitoring using Spamhaus DQS. The paid reputation layer grades a domain's spam rate against Gmail's 0.30% block threshold so you can see headroom rather than only seeing the breach.
He also made a design decision I think is right, which is that the system shows the whole sending machine and every limit on it, measured through the same doors users would use. Tools that report a curated version of the truth are worse than no tool, because they replace uncertainty with false confidence.
What to buy, and what should already be in your stack
My honest position after a decade of this: most of what teams buy as separate deliverability tooling should be part of the sending platform. Preflight checks belong before the send, not in a separate tab. Suppression inspection should be an API call, not an export. Our REST API lists active suppressions directly so you can see hard bounces, soft-bounce accumulations and complaints without leaving your own code.
Buy monitoring if your volume justifies it. Connect the free provider tools regardless, because Google and Microsoft are telling you their own view for nothing. And treat any tool that promises to move mail from Promotions to Primary as a red flag rather than a feature, because that is a filter to be earned, not gamed.
If you are choosing tools because placement is already bad, tooling is not the first move. Work the order: authentication, then listings, then list hygiene, then warmup, and use a test to confirm each fix.
Some of what people buy tooling for is better solved in the send path itself: address checking through the validation API, and delivery events through webhooks rather than a polling dashboard.
Go deeper
References
The primary sources behind the rules on this page. Provider policy and the underlying standards, not vendor marketing.
Common questions
At minimum an authentication checker, a blacklist monitor and a seed placement test. Postmaster tools from Google and Microsoft are free and worth connecting.
The monitoring ones are, once you send enough that a placement drop costs real money. Below that volume, free provider tools plus a seed test cover most of it.
Google Postmaster Tools, because it reports Gmail's own view of your domain reputation and spam rate, which is the read that matters most for consumer mail.