Verify before the send, not after the bounce.
Six checks run against every recipient before your provider ever sees the address. Bad recipients are blocked with a reason recorded in the route log — the bounce you would have paid for never happens.
You paid your provider to bounce a bad address.
A campaign ships on Wednesday morning. Two hours later the bounce dashboard fills up — recycled addresses, obvious typos, three role accounts that unsubscribed a year ago, and a handful of disposable domains from last month’s signup form. Every one of them counted against your monthly volume. Every one of them nudged your sender reputation the wrong way. And every one of them was knowable in advance.
sendrules screens each recipient before your provider sees the address. The ones that would have bounced are blocked with a reason attached to the route log; the ones that pass reach a provider you weren’t going to regret sending through.
Six checks. One pass. Nothing to change in your application.
Every rejection writes a block reason to the recipient’s route log so you can audit list decay over time and tune policy per Grid.
- Standards-conformant syntax — international domains and the harder edge cases handled correctly, not just the common shapes.
- Tenant suppression — your workspace list plus your bounce history, updated automatically on every provider event.
- Disposable-domain screening — a corpus refreshed daily against curated and community feeds; junk signups get filtered, not delivered.
- Role-address policy — configurable per Grid; flag info@ and sales@ on cold campaigns, allow them on transactional receipts.
- Typo correction — gmial.com becomes gmail.com when confidence is high enough; the original is logged for review.
- Live mailbox check — a live check against the recipient’s mail server, routed through our secure probe network; the mailbox either exists or it doesn’t.
In the send path, not a separate verification product.
Most send-time platforms treat verification as a separate product you have to remember to call — a batch job that runs on last night’s list, or an API you invoke from the same code path. sendrules runs the checks inline: no separate service to integrate, no separate quota to reconcile, no rejected recipient counted against your monthly volume.