Careers
Part of The honest guide to email deliverability
Email deliverability tools: what the good ones share
Email deliverability tools for 2027 should prove sender discovery, authentication, provider data, SMTP evidence, message tests, suppression, security, and export.
What to take away
- Buy against a written evidence and operating requirement, not a generic deliverability score.
- Test each tool with representative providers, identities, streams, failure cases, access roles, retention, and export needs.
- A useful pilot proves detection, diagnosis, correction, recovery, and controlled handover without one vendor holding all evidence.
Email deliverability tools should be chosen for specific evidence and controls, not a promised inbox score. This unpaid category guide is not a ranking or shortlist. Vendor claims need independent testing, and no tool replaces recipient permission, provider requirements, qualified technical work, or accountable operations.
Sender inventory and discovery
Look for domains, DNS, IPs, certificates, providers, signatures, traffic, ownership, change history, and unknown-sender alerts. Named examples include Valimail, dmarcian, EasyDMARC, and Agari (now Fortra); broader categories are DMARC monitoring, email security suites, and cloud asset inventory tools.
Authentication analysis
Test SPF authorization, live DKIM signatures, DMARC alignment, reports, policy, and vendor delegation. Require raw evidence and avoid treating a DNS lookup as full path validation. Named tools include dmarcian, Valimail, PowerDMARC, and EasyDMARC.
Provider postmaster data
Microsoft's services for external email senders describe provider-specific support, delisting, and abuse-reporting routes for senders to Microsoft 365. A tool should preserve the exact provider, message, response, IP, domain, timestamp, and case history needed to use such routes responsibly. Examples include Google Postmaster Tools, Microsoft SNDS, and Validity or 250ok postmaster data services.
SMTP and queue observability
Require exact responses, attempts, accepts, deferrals, rejections, bounces, retry behavior, queue age, route, stream, provider grouping, alerts, and safe rate control. Sending platforms with detailed logs include Amazon SES, Mailgun, Postmark, SendGrid, and SparkPost; analytics platforms include Datadog, Splunk, and Elastic.
Message and path testing
Evaluate headers, format, authentication, links, redirects, images, tracking, accessibility, destination security, and provider rendering. Tests should preserve the actual production route and limitations. Tools in this category include Litmus, Email on Acid, Mail-Tester, GlockApps, and Parcel.
Inbox placement diagnostics
Ask how seed accounts, panels, or other observations are selected and maintained. Review coverage, sample size, repeatability, privacy, confidence, and mismatch with real recipients. Named seed-list vendors include Validity Everest, Inbox Monster, GlockApps, and Mail-Tester.
Feedback and suppression
Check complaints, one-click requests, body-link withdrawal, hard failures, preferences, global suppression, propagation, queue cancellation, imports, audit evidence, downtime, and recovery. ESP and CRM suites with these controls include Mailchimp, Klaviyo, SendGrid, Braze, and Salesforce Marketing Cloud.
Security and incident response
Review roles, multifactor authentication, API scope, secrets, logs, anomaly alerts, pause controls, affected-recipient analysis, retention, deletion, vendor access, and notification support. Identity and access tools include Okta, Microsoft Entra ID, and Duo; secrets managers include AWS Secrets Manager and HashiCorp Vault.
Piloting and scoring a tool
Amazon SES's Virtual Deliverability Manager settings distinguish dashboard engagement tracking from optimized shared delivery and document configuration scope. Treat every product feature as a bounded mechanism: record what it observes or changes, where it applies, and how the team disables and exports it.
Test current provider requirements, a live message from each stream, known authentication failures, permanent and temporary responses, suppression propagation, a volume anomaly, and a full contract end. Score task accuracy, time, evidence, usability, support, total cost, false alarms, and portability. Pilot candidates include Amazon SES, Validity, Inbox Monster, dmarcian, and Litmus.
Write the buying decision before the demonstration: problems, required providers, data boundaries, integrations, controls, owners, acceptance tests, contract terms, and retirement plan. A useful tool shortens diagnosis and strengthens safe action; it does not hide definitions behind a proprietary health number.
Pilot scorecard
| Capability | Pilot test | Exit evidence |
|---|---|---|
| Discovery | Find a hidden sender | Domain and owner export |
| Diagnostics | Trace a provider failure | Raw response and IDs |
| Suppression | Reconcile a missed request | Portable audit record |
| Operations | Alert, pause, recover | Runbook and access map |
Total cost of ownership and vendor lock-in
The GOV.UK technology selection guidance recommends adaptable choices, data control, security review, and ownership-cost analysis. This section covers total cost of ownership and vendor lock-in, not just list price. Vendor categories include DMARC monitors, sending platforms, and placement services.
The GOV.UK open standards guidance links open standards with interoperability and reduced supplier dependence. Check export formats, API access, contract exit terms, and whether the vendor holds the only usable copy of your data.
Typical pricing and licensing models
Email deliverability tools use several pricing models. DMARC and sender-discovery platforms often include a free tier for one domain, then charge per domain per month. Typical small-portfolio plans run from about $10 to $100 per domain per month. Enterprise contracts are quoted per domain, per seat, per monitored message, or per sending IP, and usually require an annual commitment.
Sending platforms commonly charge per message or per monthly volume. Amazon SES lists $0.10 per 1,000 outbound emails. Mailgun, SendGrid, Postmark, and SparkPost use tiered monthly plans; typical entry plans range from about $15 to $50 per month for 10,000 to 50,000 emails.
Seed-list inbox placement tests typically cost $50 to $500 per month or per seed per test.
Open-source self-hosted tools remove license fees but add hosting, operations, and staff time. Vendor lock-in appears in per-domain or per-seat contracts, proprietary data formats, and API limits. Ask for written exit terms, data export formats, and any per-message overage rates before signing.
Common questions
Is one deliverability tool enough?
Usually not. Map provider data, DNS, message paths, application events, audience records, suppression, security, and business outcomes before choosing the smallest dependable stack.
Should an inbox placement seed test be the main KPI?
No. It can be one diagnostic observation with sampling limits. Pair it with provider, SMTP, audience, complaint, suppression, and outcome evidence.
What should a tool pilot prove?
It should prove a real workflow from detection through diagnosis, correction, recovery, access removal, and documented limits.
