Now stop using dsbl.org blacklisting: it’s offline

Want to help support this blog? Try out Oh Dear, the best all-in-one monitoring tool for your entire website, co-founded by me (the guy that wrote this blogpost). Start with a 10-day trial, no strings attached.

We offer uptime monitoring, SSL checks, broken links checking, performance & cronjob monitoring, branded status pages & so much more. Try us out today!

Profile image of Mattias Geniar

Mattias Geniar, August 10, 2012

Follow me on Twitter as @mattiasgeniar

It seems a lot of Blacklist filters still use the old DSBL DNS Blacklist, but it’s been dead for few years already. Since March 2009, to be exact. However, something changed in the last 24 hours that actually made them go offline.

The result is that any system still using that blacklist sends out bounce messages such as this.

The following recipient(s) cannot be reached: xxx
Service unavailable; Client host [x.x.x.x] blocked using list.dsbl.org

If you still have legacy systems running that use the list.dsbl.org blacklist, you may want to remove any references to the DSBL in your configs and stop using that blacklist.



Want to subscribe to the cron.weekly newsletter?

I write a weekly-ish newsletter on Linux, open source & webdevelopment called cron.weekly.

It features the latest news, guides & tutorials and new open source projects. You can sign up via email below.

No spam. Just some good, practical Linux & open source content.