Blocklist monitoring checks one thing: does the internet trust your sending IP. Not server availability, not SSL, not DNS. Reputation. WatchCron runs your IPs against 40+ DNS blocklists using standard DNS queries, no third-party API, and alerts you the same day an IP gets listed. Blocklist monitors are unlimited on every plan and don't count toward your check quota.
01 — Reputation, not whether the server is up#
Being listed doesn't mean your server is down or compromised. It means a mailbox provider or spam filter has decided mail from your IP is suspect. The reason often has little to do with you: a noisy neighbour on a shared host, the previous owner of a recycled IP, or one compromised account that sent a spam burst before you caught it. The machine keeps running perfectly. The email just stops arriving.
That's why this is its own check rather than a footnote to uptime. An availability monitor tells you whether the server is reachable. A blocklist tells you whether the internet still trusts what it sends. Different questions, different tools.
02 — What a DNSBL lookup looks like#
Under the hood it's an ordinary DNS query. The IP gets reversed by octet and appended to the list's hostname:

$ dig +short 34.216.184.93.zen.spamhaus.org
127.0.0.2
A response like 127.0.0.x means listed. Silence means clean. You can run this by hand for one IP and one list. For three IPs across forty lists every day, you won't. That's the automation that pays for itself: not in theory, but the morning a client asks why your emails aren't arriving.
03 — How WatchCron runs the check#
Give it an IP directly, or a domain (it resolves to an IP first). On each run, WatchCron sends a DNS query to every list in the set and records which ones, if any, answered. No third-party reputation API in between. Just the standard DNSBL protocol over DNS.


Every IP and mail host you monitor sits in one view: a Clean or Listed badge and a count of how many lists flagged it. A server leaking reputation stands out before the support tickets start.
04 — 40+ blocklists, led by Spamhaus#
WatchCron checks over 40 DNS blocklists on every run. The full set covers the lists that actually move email deliverability. Here are the ones that matter most:
Blocklist | What it flags |
|---|---|
| Spamhaus Zen: the most-consulted list (spam sources, exploited hosts, dynamic IPs) |
| SpamCop: driven by user spam reports |
| Barracuda's reputation list |
| SORBS: open relays and proxies |
| UCEPROTECT Level 1: individual IPs |
| CBL: botnet and infected hosts |
| Spamrats: confirmed spam sources |
| s5h: aggregate spam list |
The remaining 30+ lists in the set cover regional providers, secondary aggregators, and niche reputation sources. The full set is fixed, so you can't add a private list, but it covers what the major inbox providers actually defer to.
05 — Alerts: listed and cleared#
A monitor reads as Clean, Listed, Error, or New. When an IP gets listed, the detail page shows exactly which blocklists flagged it. That's the first thing you need before requesting removal.

Two alerts fire on changes: one the moment an IP becomes Listed (naming the lists), a second when it clears all of them. So you know a delisting actually took. Both send only on the state change, through the channels that monitor uses.
Free includes 3 alert channels (pick from email, Slack, Telegram, webhooks, or any other supported type); Starter raises that to 10, Pro to 25, Business removes the cap. SMS opens on Pro, voice calls and WhatsApp on Business.
Every check is logged, so you can tell a spotless IP from one that keeps bouncing on and off a list. Set the interval anywhere from hourly to weekly. The Check Now button is for right after you've requested removal and want to confirm it worked.
06 — Who needs blocklist monitoring#
SaaS companies sending transactional email from their own servers: password resets, confirmations, invoices. One listing and all of it lands in spam. The customer doesn't complain the email is in spam. The customer complains it never arrived. You find out days later.
Agencies and hosting providers on shared IPs: your client is clean, but a neighbour on the same server was spamming. The whole IP gets listed. Monitoring catches it before the first client notices.
E-commerce with in-house sending: order confirmations, shipping updates, marketing emails. When the sending IP hits Spamhaus, that's not an abstract problem. That's lost sales, one per undelivered email.
DevOps teams running mail servers (Postfix, Exim): IP reputation is infrastructure, like uptime and SSL. It's just not visible in conventional monitoring tools.
07 — Where the check stops#
The check covers IPv4 reputation, and its boundaries follow from that.
No IPv6 support: the DNSBL reverse-lookup scheme is built around IPv4 addresses. It checks IP-based blocklists, not the domain- and URL-based families (URIBL, SURBL) that judge links inside a message rather than the sending IP.
It tells you that an IP is listed and on which lists, not why. That detail lives on each blocklist's own site. A domain resolves to a single IP for the check, so a hostname with several A records is judged on the first one.
And it stops at telling you: the delisting itself is a manual request you make on each blocklist. WatchCron reports the result but doesn't automate the process. Most blocklists have a self-service removal form. Spamhaus and SpamCop clear automatically once the underlying problem is fixed, usually within 24-48 hours.
Blocklist monitoring sits in the same dashboard as your uptime and cron job checks, so the IP reputation that decides whether your email arrives lives next to the checks that decide whether your site answers.
Watch every IP you send from against 40+ blocklists and hear about a listing the same day, not the week sales asks why nobody is replying. Free plan: 3 alert channels, unlimited blocklist monitors, no credit card.08 — Add your first sending IP#
Paste an IP or domain and the check runs against every list automatically. See what each plan includes on the pricing page, or create an account and know the moment your reputation changes.
09 — FAQFrequently asked#
It means a spam filter or mailbox provider treats mail from that IP as suspect, so your messages may be delayed or filed as spam. It doesn't mean your server is down or hacked. It's a reputation problem, not a security breach.
Twelve major DNSBLs, including Spamhaus Zen, SpamCop, Barracuda, SORBS, CBL, UCEPROTECT, and Spamrats. The set is fixed.
Both. Give it an IP directly, or a domain, and it resolves the domain to an IP before running the check.
No. It tells you which lists flagged the IP and alerts you when it's cleared, but the delisting itself is a manual request you make on each blocklist's own site.
Not currently. The DNSBL checks are IPv4 only.