Off the blocklist before your email bounces.

Blocklistings fail silently: your app works, your mail just stops arriving. UptimeStatus checks the lists so your customers do not have to.

The outage nothing else can see.

A blocklisted IP breaks nothing you monitor. HTTP checks pass, the mail server accepts connections, and every password reset you send quietly lands in spam or vanishes. The first report is usually a customer asking why they never got their receipt, days in.

UptimeStatus checks your IP against Spamhaus ZEN, Barracuda, SORBS, and SpamCop on every run, using the same DNS lookup receiving mail servers use. If a list knows about you, so do you.

mail.yourcompany.com Degraded
Spamhaus ZEN
zen.spamhaus.org
Clean
Barracuda
b.barracudacentral.org
Clean
SORBS
dnsbl.sorbs.net
Listed
SpamCop
bl.spamcop.net
Clean

Alerted on the change, not the state.

Each check is compared with the previous one. The moment your IP shows up on a list it was clean on before, an incident opens naming the IP and the exact blocklists, and your channels fire. That is the moment worth interrupting someone for: a fresh listing usually means something on that host just started spamming, or a shared IP neighbor did.

While you work the delisting, the monitor shows degraded rather than down, and every subsequent check records whether you are still listed. When the list drops you, the history shows that too.

Incident timeline Investigating
Newly listed on dnsbl.sorbs.net
203.0.113.7
09:14
Still listed
delisting requested
11:40
Not listed on any checked blocklist
back to clean
16:02

What blocklist monitoring includes.

Reputation checks you can read the source of.

UptimeStatus is MIT licensed. The blocklist check is a short job you can audit, extend with your own zones, and run inside your own network. Or use the hosted version and start checking in minutes.

git clone https://github.com/stacksjs/status
FAQ

Blocklist monitoring, answered.

Which blocklists are checked?

Four widely used public DNS blocklists: Spamhaus ZEN, Barracuda, SORBS, and SpamCop. These are among the lists that receiving mail servers commonly query when deciding whether to accept or junk your mail.

How does the check work?

It resolves your monitor's hostname to its IPv4 address and performs the standard DNSBL query against each zone: the IP's octets reversed and prefixed onto the blocklist domain. An answer means listed, no answer means clean. It is the same lookup a mail server does before accepting your message.

When do I get alerted?

When your IP appears on a blocklist it was not on at the previous check. Each new listing opens an incident naming the IP and the specific lists, and notifies your channels. Staying listed does not re-alert you every few minutes, so the signal stays meaningful.

What should I do when I get listed?

First find the cause: a compromised account or form sending spam, a misconfigured mailer, or a neighbor on a shared IP. Then request delisting through the blocklist's own process. Your check history shows exactly when the listing appeared and confirms when the delisting takes effect.

My mail goes through SendGrid or SES. Do I still need this?

Your provider manages its own sending IPs, but the reputation of your domain and of anything that sends directly, like a transactional relay or a legacy cron job on a VPS, is still yours. Monitoring the hosts you control catches the listings your provider will not tell you about.

Start monitoring in under 2 minutes.

No credit card required for the self-hosted, open-source version.