Who runs on it

We run our own companies
on it first.

Three businesses we operate send their production email through BlacklistGuard. That is where the roadmap comes from. We hit the rough edges before anyone else does, and we fix them because we are the ones being paged.

What it gets used for

Five jobs it does every day.

TX
Transactional
REST or SMTP
587 / 465submission ports

Point your app at it and forget about it.

Password resets, receipts, notifications. Send them over the REST API, or change the SMTP settings you already have and send them that way. Both routes land in the same delivery log.

Works with WordPress, Laravel, or anything that speaks SMTP
DM
Deliverability
DMARC and blocklists
15blocklists watched

Read your DMARC reports as something other than XML.

Aggregate reports come in compressed and unreadable. We parse them and show you which reporter saw what, with the source IP behind every pass and every failure.

Scheduled blacklist checks on your domains and IPs
CM
Campaigns
lists and segments
5step builder

Build the segment, watch the count, then send.

Conditions are built from the same field catalogue the query engine validates against, so a rule you can build is a rule that will run. The subscriber count updates as you narrow it down.

Suppression lists are checked before anything queues
IN
Inbound
on your own domain
HMACsigned deliveries

Take delivery of the replies yourself.

Point MX at us and send each address wherever it belongs. A real mailbox, a forward that fans out to several people, or a signed POST straight to your endpoint.

SHA-256 signature and timestamp on every webhook
MT
Agencies
many clients, one login
1:1workspace per client

One workspace per client, no shared fate.

Every list, domain, key and sending IP belongs to exactly one workspace. Switch between them from the top bar without logging out and back in.

Isolation is enforced on the query, not by convention

Ready to see your sending?

Spin up a workspace in 5 minutes. Free plan, no credit card required.