Email Deliverability Tools: Monitoring and Improvement
Seed testing, reputation monitoring and DMARC reporting, plus what to do with the reports once they arrive.
On this page
The short version
- The free tools from the mailbox providers themselves are the most meaningful data available, because they reflect the actual decision-maker.
- Paid platforms buy aggregation and alerting, not better data. That is a real product for a programme large enough to need watching daily.
- DMARC reports are the one source that shows you something nothing else can: everyone sending as your domain, including services you forgot about.
Deliverability tooling divides into three kinds: seed testing that estimates placement, reputation monitoring that reports what providers think of you, and DMARC reporting that shows who is sending as you.
The second and third are largely free and underused. The first is the one people buy and the one with the most important caveat attached.
What each source shows, and cannot
| Source | Shows | Cannot show | Cost |
|---|---|---|---|
| Provider postmaster tools | Reputation and spam rate at that provider | Anything about other providers | Free |
| DMARC aggregate reports | Every source sending as your domain | Where the mail landed | Free |
| Seed list testing | Placement across accounts you control | Placement for real subscribers | Paid |
| Blocklist monitoring | Listings on the lists that matter | Provider-internal filtering | Free or cheap |
| Open rate by receiving domain | Relative performance across providers | Absolute placement | Already have it |
DMARC reports are the underused one
Publishing a DMARC record with a reporting address produces daily XML from every major receiver, listing which sources sent mail claiming to be your domain and whether each passed authentication.
That answers a question nothing else does: who is sending as you. It routinely surfaces forgotten services — an old CRM, a support desk, an invoicing tool — that have been failing authentication for months, plus any actual spoofing.
The reports are unpleasant to read by hand, which is why a parser or a hosted service is worth the modest cost. It is the cheapest genuinely new information available in this category.
What to do with the reports
Postmaster spam rate is a leading indicator — it moves before placement does. Treat a spike as an incident rather than noise, and check what changed in the preceding fortnight.
DMARC failures split into two kinds. A legitimate service failing authentication needs fixing, usually by adding it to SPF or setting up DKIM for it. Unknown sources sending as you need investigating, and are the reason to move the policy past monitoring once everything legitimate passes.
Blocklist alerts need triage before action. Most lists affect nothing; a small number matter. Check whether the listing is on one that major receivers actually consult before spending an afternoon on a delisting request.
When a paid platform is worth it
When someone needs to be told within hours rather than finding out at the monthly review. Aggregation across providers, alerting on thresholds, and one dashboard instead of four sources is a genuine product.
It is not worth it when nobody would act on an alert within a day, which describes most small programmes. In that case the free sources checked monthly deliver the same information at the speed you can use it.
The honest test is what would happen if an alert fired on a Friday afternoon. If the answer is that it would be read on Monday, monthly checks are the right cadence and the subscription is buying nothing.
Deliverability tooling check
- Postmaster tools connected for the sending domain
- DMARC published with a reporting address someone reads
- Reports parsed rather than left as XML nobody opens
- Every legitimate sending service passes authentication
- Blocklist monitoring covers the lists that matter and ignores the rest
- Seed addresses are not in the main list
- Seed results are compared against their own history
- Someone would act on an alert within a day, or the alerting is not needed
Frequently asked questions
How often should placement be tested?
On change — a new template, domain, provider or a significant volume increase. Testing an unchanged setup repeatedly tells you nothing new, because the seed panel does not change between sends.
Are third-party reputation scores meaningful?
They are proxies built from limited data. Provider postmaster tools reflect the actual decision-maker and are free, which makes them the better place to start.
What if I cannot see any placement data at all?
Open rate broken down by receiving domain, watched against its own history, is available in every platform and is a sensitive early indicator. One provider diverging from the others is the pattern to look for.