One bad send costs weeks of inbox placement. Send Check reads the HTML before it goes and fails the build on the mistakes that get you filtered.
Send Check is a pre-send lint for self-hosted newsletters. Point it at the HTML body (paste, file or URL) and it checks link domains against your allowlist, confirms unsubscribe tags and headers, counts links and promo mix, reports tracking state, and flags images hotlinked from hosts you haven't cleared. Rules live in a file you edit. Runs as a command-line tool or a small web page on your server. Sold by A2 Digital as a one-time purchase.
A single tracking or affiliate domain the mailbox providers dislike can tank a send. Allowlist your domains once; anything else fails the check.
Hotlinked images, a missing unsubscribe merge tag, tracking left on for a plain-text-style send: visible in the report, invisible in the preview.
Run it in the terminal or paste into the page. Pass or fail with reasons. Make it a habit, or make it a gate in your send script.
Allowed link domains, allowed image hosts, max links, promo ratio, required tags and headers. One file, plain text.
CLI: point it at the HTML file. Web: paste the body. Either way, seven checks in a second.
Failures name the exact link or image. Fix, run again, send when it's green.
Prices in USD. Requires PHP 8 on any host, or runs locally. Send Check checks the HTML you give it; it does not test spam scores, authentication (SPF, DKIM, DMARC) or sender reputation, which are separate concerns.
No; it's the step before them. Those test a sent sample for spam score and placement. Send Check enforces your own link and content rules on the HTML before anything is sent, every time, in a second.
Link domains against your allowlist, unsubscribe merge tag and List-Unsubscribe header, link count and promotional ratio, click-tracking state, image hosts against your allowlist, and text-to-image ratio.
No. It reads HTML you give it (file, paste or URL). That keeps it safe to run anywhere and means it works with any sender, including hand-built ones.
Yes. The CLI returns a non-zero exit code on failure, so a send script can refuse to proceed until the check passes.
Your allowlists are yours. The optional updates tier refreshes the default thresholds and adds checks as mailbox-provider rules change.
No. Those are DNS and sending-infrastructure concerns; Send Check is about the content of the message.
Seven checks, your rules, one second.
Get Send Check