Built for the people who run email.
Most platforms bury the parts that matter: bounces, blocklists, queue depth. We put them on the front page, along with the controls to do something about them.
Operator-grade infrastructure
Multi-tenant SMTP queues, per-IP throttling, automatic VMTA pool warmup, RFC-compliant bounce parsing.
- Direct MX delivery
- DKIM signing (RSA, ECDSA, Ed25519)
- MTA-STS policy hosting + ARC
Visibility, not vibes
Real-time dashboards for queues, IPs, and reputation. DMARC aggregate reports parsed and humanized.
- Live throughput graphs
- DMARC aggregate viewer
- Per-domain reputation
Built like a developer tool
A REST API that reaches every part of the platform, SMTP relay for the apps you already run, and signed webhooks on inbound mail.
- REST API with scoped keys
- SMTP relay on 587 and 465
- Webhooks for everything
Everything in one place.
This is more than an MTA. Lists, campaigns, validation, deliverability and blacklist monitoring all live in the same place, on the same data.
Less spreadsheet. More signal.
Queue depth, retries, deferrals and reputation, across every tenant, in one view.
Every transactional email the platform sends goes through BlacklistGuard. The DMARC viewer turned up two subdomains we had forgotten were still sending, which our previous provider had no way of telling us.
An API that feels like infrastructure.
Send over REST or plain SMTP, scope every key to what it needs, and read the delivery record back for any message you sent.
- REST API over the whole platform, not only sending
- Inbound mail delivered to your endpoint, signed with HMAC-SHA256
- SMTP submission on 587 and 465 for WordPress, Laravel, anything
- Per-message delivery log with the SMTP response we got back
curl -X POST https://app.blacklistguard.com/api/v1/emails/send \
-H "X-API-Key: $BLACKLISTGUARD_KEY" \
-H "Content-Type: application/json" \
-d '{
"from_email": "ops@yourdomain.com",
"from_name": "Ops",
"to": "ada@example.com",
"subject": "Welcome aboard",
"body": "<p>Glad to have you.</p>"
}'