The results are in! Congrats to Fortinet – today’s top performer. Fortinet blocked about 98% of porn sites in the test site. Others blocked about 94-98% of porn sites, so the competition was pretty close.
The methodology and process was fairly simple. We googled 50 pornographic search terms and tested each product against each search term 100 links deep (The test is documented more in the presentation). Each product was graded against the site list qualified by humans. Each missed between 2% and 6% of porn – enough for a determined user to easily get around. In addition, there was usually about a 1% false positive rate, an annoying side effect for users.


How does one interpret these results? It depends on your view on web filtering. All products performed within a small range, probably within the margin of error. If you are expecting to block all porn, all these products will not be effective, however if you’re looking to control and monitor porn usage as much as possible these products make great candidates. Given the similar performance on this test set other aspects should play a larger role in which to choose, like price, performance, and features.
The full test set with human and vendor scores is available here (30meg). The scripts used to run the full tests and live tests are available here.
Many asked why untangle was not included in the test. We felt including untangle itself in the test would not be fair, as we know the test set and methodology ahead of time. We also apologize to the vendors (netsweeper, besafe) who requested to be in the test but time didn’t allow. Other popular vendors did not have a offering that suitably fit our market (small business)
I hope this serves to educate the market as to what one can expect of web filtering and also provide a small help to web filter providers. Thanks to all those who joined us and the vendors!
16 Responses on Deep Throat Fightclub Results!
It sounds that the event was a success…
Congratulations!!
Darn, I was at RSA launching Microsoft Forefront Stirling as part of my day job at Microsoft, and was so busy with that I didn’t know this was going on, or I would have gone. I’ve added this test to my table of filter tests here: http://filteringfacts.files.wordpress.com/2008/04/table_of_filter_tests.pdf
David Burt, http://www.filteringfacts.org
So the obvious question:
How does Untangle filtering compare to Fortinet, WatchGuard, Bess?
As a potential customer investigating this stuff, It would be nice to know.
Wait, you sponsor the fight, put in all your competitors, but didn’t participate? This is the internet, so this will come off much more assholeish than it is meant too, but considering you put yourself in the last round of testing… Can you just explain that? Also, in the SMB category, there is http://www.opendns.com, set and forget : )
Oh, ahem, speaking of which shy not offer a copy opendns’s search page trick and make some money off of non-support clients? I mean I could just set my untangle DNS to OpenDNS, but then they would be making money, instead of you…
-Z
I really do not understand where is Untangle’s part in this test? I tried to find some good reason for not participating but I really couldn’t.
Why is ScanSafe in the ppt introduction but not in the test results?
One thing intrigues me. Why you are so proud of blocking pornography since you are promoting it yourself ? Here’s the proof : http://fileforum.betanews.com/detail/KLite_Mega_Codec_Pack/1080441198/1
This is not sexual, but it’s pornography anyway.
all for your site
thank you
Thank you very much açıköğretim hakkında herşey
Thank you sex ürünleri
Wait, you sponsor the fight, put in all your competitors, but didn’t participate? This is the internet, so this will come off much more assholeish than it is meant too, but considering you put yourself in the last round of testing… Can you just explain that? Also, in the SMB category, there is http://www.onlyporno.ucoz.ru, set and forget : )
Thanks very good
Thank Administrator
?????????! ???
Leave a comment on Deep Throat Fightclub Results!
RSS feed for comments on this post · TrackBack URI