DNSBL testing

[marcs]

http://mxtoolbox.com offers a nice service where it monitors your mx record and also does automatic checks and notification if your IP get's listed on some 150 known blacklists.

It would be nice to incorporate a test like this into host monitor. Would something like this be possible?

Thank you,
Marc
marcs@csgny.com

[KS-Soft]

MX check? Yes, we probably will implement that. Black List test? I think we will not implement such check.

Regards
Alex

[marcs]

Thanks for the response.

Any particular reason you couldn't implement blacklist checking? It's a great way to handle blacklists because it allows us to get clients removed from blacklists before we get emails from them that they are getting bounce backs.

Thanks again for the response.

Take care,
Marc
marcs@csgny.com

[KS-Soft]

Marc,
We can implement such option but we have a lot of tasks to do, these tasks probably more important for most of admins...
Ok, I have added another task into "to do" list. Low priority

Regards
Alex

[KS-Soft]

PS I don't think its a good idea to publish your e-mail address, spam robots can find it..
Better specify e-mail address in your profile. Forum allows to send e-mail to a member without showing address.

Regards
Alex

[plambrecht]

Can't you use that page as a test ?

If you create a HTML test, that checks that page.
http://mxtoolbox.com/blacklists.aspx?IP=<ip of the server to test>
Create a GET test, and in the advanced you can check if the contents contains a word like 'BAD' (I don't know what status a RBL listed server gets...)

If the word is in the page, then generate a BAD status...

Hope this helps

Pieter

[terje]

We created a folder called "Blacklist Tests". On the properties of this folder we go to the SPECIALS tab and turn on "Non-Simultaneous Test Execution".

In that folder we created a master test;

The test type is URL.
The target URL is: http://rbls.org:80/?q=127.0.0.2
Under advanced we set SHOULD CONTAIN: bgcolor=#ffc0c0

We then create a set of tests for each IP we want to test. For example;

The test type is URL.
The target URL is: http://rbls.org:80/?q=mail.tpg.com.au
Under advanced we set SHOULDN'T CONTAIN: bgcolor=#ffc0c0
We make this test dependent on the master test above.

In each case the URL changes so that part after the = sign names the relevant host.

The master test protects us in case the logic of the website ever changes.

[timn]

Yes, we also already use Host Monitor for some basic blacklist tests. Host Monitor is a thing of beauty....

For example, URL test calls:

http://www.dnsstuff.com:80/tools/ip4r.c ... 23.123.123

Contents should not contain "innerHTML += 'LISTED"

also

http://www.ordb.org:80/lookup/?host=123.123.123.123

Result should contain "host is not listed in ORDB"

We also perform test to RBLS.org is shown above.

Caution: The frequency of such tests should be fairly limited out of respect for the operators of these systems. We perform these tests once per day.

Also, I recommend a long timeout value to give these large pages a chance to fully load.