June 28, 2011

Block Known Comment Spammers in WordPress

Filed under: Anti-Spam,Wordpress — Jack @ 11:55 am

A short while back, I did an article on blocking spammers in WordPress. After spending the past three hours going through our network of blogs and blocking the latest wave of spam poo, I have decided to post all of the IPs and stop-words we are blocking. This list can not possibly cover all of the spam nazis across the net, but it can save you some considerable time by eliminating all of the ones that have spammed us.

Just download the file below then select all, copy and paste the list into your WordPress comment blacklist (WP Admin -> Settings -> Discussion -> Comment Blacklist).  Enjoy!

Master-Spam-Block-List

3 Responses to “Block Known Comment Spammers in WordPress”

  1. Daytona Web Design
    5:43 pm on October 8th, 2011

    Thanks! I’m seeing less spam only a short time after importing your list.

  2. james white
    6:28 pm on January 30th, 2012

    To be honest Internet site owners ought to have a look at simple ways of ending spam by being significantly less of a target, rather compared to fighting the spam programs when they are banging at your web-site

    The trouble with open source engines just like Joomla,Wordpress etc is bot users scanning for somewhat insecure internet sites for spamming comments or security risks to input malware they are able do that since every single one of opensources automatically leave a digital foot print on main search engines just like Google and yahoo, I’ve written and published a short article relating to this on my web page you should check it out, its definitely ideal for blocking spam and viruses, stop being detected as a target!

    Way to stop comment spam

    james white
    Web Design Bournemouth

  3. Jack
    12:07 pm on February 6th, 2012

    James,

    Thanks for adding to the discussion. You make a great point about removing the footprints left behind by the CMS or blogging system of choice. The sad truth is that these minor details often get tabled as a result of time or budget constraints. Although it may not be necessary, it would certainly be a good idea to implement.

    Best,
    Jack