Spam protection, AntiSpam, FireWall by CleanTalk - Version 5.36.1

Version Description

2016-02-05 = * Fixed bug, when users receive error after logging in

Download this release

Release Info

Developer shagimuratov
Plugin Icon 128x128 Spam protection, AntiSpam, FireWall by CleanTalk
Version 5.36.1
Comparing to
See all releases

Code changes from version 5.36 to 5.36.1

Files changed (3) hide show
  1. cleantalk.php +2 -2
  2. inc/cleantalk-common.php +4 -4
  3. readme.txt +70 -551
cleantalk.php CHANGED
@@ -3,11 +3,11 @@
3
  Plugin Name: Anti-Spam by CleanTalk
4
  Plugin URI: http://cleantalk.org
5
  Description: Max power, all-in-one, captcha less, premium anti-spam plugin. No comment spam, no registration spam, no contact spam, protects any WordPress forms.
6
- Version: 5.36
7
  Author: СleanTalk <welcome@cleantalk.org>
8
  Author URI: http://cleantalk.org
9
  */
10
- $cleantalk_plugin_version='5.36';
11
  $cleantalk_executed=false;
12
 
13
  if(defined('CLEANTALK_AJAX_USE_BUFFER'))
3
  Plugin Name: Anti-Spam by CleanTalk
4
  Plugin URI: http://cleantalk.org
5
  Description: Max power, all-in-one, captcha less, premium anti-spam plugin. No comment spam, no registration spam, no contact spam, protects any WordPress forms.
6
+ Version: 5.36.1
7
  Author: СleanTalk <welcome@cleantalk.org>
8
  Author URI: http://cleantalk.org
9
  */
10
+ $cleantalk_plugin_version='5.36.1';
11
  $cleantalk_executed=false;
12
 
13
  if(defined('CLEANTALK_AJAX_USE_BUFFER'))
inc/cleantalk-common.php CHANGED
@@ -1,6 +1,6 @@
1
  <?php
2
 
3
- $ct_agent_version = 'wordpress-536';
4
  $ct_plugin_name = 'Anti-spam by CleanTalk';
5
  $ct_checkjs_frm = 'ct_checkjs_frm';
6
  $ct_checkjs_register_form = 'ct_checkjs_register_form';
@@ -297,8 +297,8 @@ function get_sender_info() {
297
  {
298
  $ct_first_referer = 'null';
299
  }
300
- $post_id=url_to_postid($_SERVER['HTTP_ORIGIN'].@$_SERVER['REQUEST_URI']);
301
- $post_type=get_post_type($post_id);
302
 
303
  return $sender_info = array(
304
  'page_url' => htmlspecialchars(@$_SERVER['SERVER_NAME'].@$_SERVER['REQUEST_URI']),
@@ -314,7 +314,7 @@ $post_type=get_post_type($post_id);
314
  'fields_number' => sizeof($_POST),
315
  'js_info' => $js_info,
316
  'ct_first_referer' => $ct_first_referer,
317
- 'post_type' => $post_type,
318
  );
319
  }
320
 
1
  <?php
2
 
3
+ $ct_agent_version = 'wordpress-5361';
4
  $ct_plugin_name = 'Anti-spam by CleanTalk';
5
  $ct_checkjs_frm = 'ct_checkjs_frm';
6
  $ct_checkjs_register_form = 'ct_checkjs_register_form';
297
  {
298
  $ct_first_referer = 'null';
299
  }
300
+ //$post_id=url_to_postid($_SERVER['HTTP_ORIGIN'].@$_SERVER['REQUEST_URI']);
301
+ //$post_type=get_post_type($post_id);
302
 
303
  return $sender_info = array(
304
  'page_url' => htmlspecialchars(@$_SERVER['SERVER_NAME'].@$_SERVER['REQUEST_URI']),
314
  'fields_number' => sizeof($_POST),
315
  'js_info' => $js_info,
316
  'ct_first_referer' => $ct_first_referer,
317
+ //'post_type' => $post_type,
318
  );
319
  }
320
 
readme.txt CHANGED
@@ -1,9 +1,9 @@
1
  === Anti-Spam by CleanTalk - No Captcha, no comments & registrations spam ===
2
  Contributors: znaeff, shagimuratov, vlad-cleantalk
3
- Tags: anti-spam, antispam, bbpress, buddypress, captcha, capcha, captha, catcha, cf7 spam, comments, contact form spam, signup, spam, spammers, spammy, woocommerce, wordpress spam, booking, order, subscription, gravity spam, jetpack, bots, contact form 7, contact form, registrations, ninja, Fast Secure Contact, Gravity forms, formidable, mailchimp, s2member, protection, protect, email, akismet, plugin, contact, recaptcha, google captcha, google recaptcha, math, security, login, blacklist, prevent spam comments, wordpress, User Frontend, bulk delete, bulk remove, cloudflare, widget, review, auth forms, firewall, ddos, cleantalk, mailpoet, profile builder, comment spam, registration spam, spam comments, comment moderation, spam bots, block spam, signup spam, spam blocker, spam filter, user registration spam,pingback,trackback, spam trackbacks, anti-spam plugin
4
  Requires at least: 3.0
5
  Tested up to: 4.4.2
6
- Stable tag: 5.36
7
  License: GPLv2
8
  License URI: http://www.gnu.org/licenses/gpl-2.0.html
9
 
@@ -23,98 +23,100 @@ No CAPTCHA, no questions, no counting animals, no puzzles, no math and no spam b
23
  1. Check existing comments for spam.
24
 
25
  = Public reviews =
26
- > Using on WPLift was a great test as we receive huge amounts of spam.
27
- > *Oliver Dale. <a href="http://wplift.com/wordpress-anti-spam-plugin" target="_blank">WPLift.com</a>.*
28
 
29
  = Comments spam protection =
30
- Supports native WordPress, JetPack comments and any other comments plugins. Plugin moves spam comments to SPAM folder or set option to silent ban spam comments. You can enable option in plugin settings to auto delete comments from SPAM folder.
31
 
32
  = Spam bots registrations filter =
33
- Filers spam bots on registrations forms WordPress, BuddyPress, bbPress, S2Member, WooCommerce, Profile builder and any other registrations plugins.
34
 
35
- = Protection against contact forms spam =
36
  Plugin is tested and ready to protect against spam emails via Formidable forms, Contact form 7, JetPack Contact form, Fast Secure Contact form, Ninja forms, Landing pages, Gravity forms and any themes/custom contact forms.
37
 
38
  = WooCommerce spam filter =
39
- Anti-spam by CleanTalk filters spam registrations and spam reviews for WooCommerce. Plugin is fully compatible with WooCommerce 2.1 and upper.
40
 
41
  = Newsletters filter =
42
- Anti-spam by CleanTalk filters spam subsciptions for MailPoet and many other newsletters plugins.
43
 
44
  = Spam filter for themes contact forms =
45
- Plugin blocks spam emails via any themes (built-in) contact forms. With AJAX forms plugin silent (without any error notices on WordPress frontend) filters spam emails.
46
 
47
  = Other spam filters =
48
  * WordPress Landing Pages.
49
  * WP User Frontend.
50
- * Any WordPress form (option 'Custom contact forms'). 
51
- * Any submission to site (option 'Check all POST data')
52
 
53
  = Compatible with WordPress cache plugins =
54
  * W3 Total Cache, Quick Cache, WP Fastest Cache, Hyper Cache, WP Super cache and any other cache plugins.
55
 
56
- = Check existing comments for spam. Bulk comments removal =
57
- With the help of anti-spam by CleanTalk you can check existing comments, to find and quickly delete spam comments at once. For use this function, go to WP Console->Comments->Find spam comments.
58
 
59
- = Check existing users for spam. Bulk accounts removal =
60
- With the help of anti-spam by CleanTalk you can check existing comments, to find and quickly delete spam users at once. For use this function, go to WP Console->Users->Check for spam.
61
 
62
  = Low false/positive rate =
63
- This plugin uses multiple anti-spam tests to filter spam bots with lower false/positive rate as possible. Multiple anti-spam tests avoid false/positive blocks for real website visitors even if one of the tests failed.
64
 
65
  = CleanTalk works faster than most of the other anti-spam plugins =
66
- Everyone knows about why the faster your site loads, the better your customer experience is, the higher your Pagerank will be, and the higher your site will convert. Speed is becoming increasingly important in Search Engine Optimization , conversion and user experience. Today, site speed is one of the most important ranking factors on Google. A site that loads slowly will lose visitors and potential revenue.
67
 
68
- There are different ways of improving your site's loading performance, an important parameter for the performance site to install well-developed plugins from a reputable source.
69
 
70
- Among anti spam plugins CleanTalk Anti Spam is one of the fastest. Despite the large plug-in functionality, the developers manage to optimize the performance of the plugin so that CleanTalk faster than most analogs. This contributes to the cloud service architecture, as all calculations take place in the cloud, not on the server, the server receives the finished result for further action.
71
 
72
  https://s.w.org/plugins/cleantalk-spam-protect/screenshot-5.png?r=1288723
73
 
74
  = How CleanTalk works? =
75
- * A visitor writes a comment or registers.
76
  * CleanTalk plugin sends action parameters into the CleanTalk cloud
77
- * Service analyzes the parameters.
78
- * If this is a visitor, the comment will be published. If it’s a spam bot, then CleanTalk blocks this comment or registering.
79
  * Parameters are written to the log which can be viewed in the Control Panel service.
80
 
81
- The team CleanTalk has been developing a cloud spam protection system for 5 years and has created a truly reliable anti spam service designed for you to ensure your safety.
82
 
83
  = Spam attacks log =
84
- Service CleanTalk (this plugin is a client application for CleanTalk anti-spam service) records all filtered comments, registration and other spam attacks in the "Log of spam attacks" and stores the data in the log up to 45 days. Using the log, you can ensure reliable protection of your website from spam and no false/positive filtering.
85
 
86
  = Spam FireWall =
87
- CleanTalk has got an advanced option "Spam FireWall", this option allows blocking the most active spam bots before they get access to web site. It prevents loading of pages of the web site by spam bots, so your web server doesn't need perform all scripts on these pages. Also it prevents scanning of pages of the web site spam bots.
88
- Therefore Spam FireWall significantly can reduce the load on your web server.
89
-
90
- Spam FireWall also makes CleanTalk the two-step protection from spam bots. Spam FireWall is the first step and it blocks the most active spam bots, CleanTalk Anti-Spam is the second step and it checks all other requests on the web site in the moment before submit comments/registers and etc.
 
 
91
 
92
  = How Spam FireWall works? =
93
  * The visitor enters to your web site.
94
- * HTTP request data is checked of the nearly 5,8 million of certain IP spam bots.
95
- * If it is an active spam bot, it gets a blank page, if it is a visitor then it gets a site page. This is completely transparent to the visitors.
96
 
97
  All the CleanTalk Spam FireWall activity is being logged in the process of filtering.
98
 
99
- = Spam FireWall DDos Protection (Experimentally option) =
100
- Spam FireWall can mitigate HTTP/HTTPS DDoS attacks. When an intruder makes GET requests to attack your website. Spam FireWall blocks all requests from bad IP addresses. Your website gives infringer a special page with description of DDoS rejection instead of the website pages. Therefore Spam FireWall can help to reduce of CPU usage on your server.
101
 
102
  = XML-RPC brute force protection =
103
- Spam FireWall can mitigate XML-RPC brute force attacks. It blocks XML-RPC attacks from bad IP addresses. That helps to prevent bruteforce attacks by a Remote Procedure Call.
104
 
105
- = No spam comments, no spam registrations, no spam contact emails, no spam trackbacks. CAPTCHA less anti-spam for WordPress =
106
- Spam is one of the most irritating factors. Spam become every year more and conventional anti-spam can no longer handle all the spam bots. CleanTalk prevents spam and automatically blocks it. You'll be surprised of effective protection against spam.
107
 
108
  = Anti-spam plugin info =
109
- CleanTalk is an anti-spam solution **all in 1 for WordPress** that protects login, comments, contact and WooCommerce forms all at once. You don't need to install separate anti-spam plugins for each form. This allows your blog to work faster and save resources. After installation **you will forget about spam**, CleanTalk plugin will do all the work. You won't have to deal with spam, CleanTalk will do this for you automatically. 
110
 
111
  CleanTalk is a transparent anti-spam tool, we provide detailed statistics of all entering comments and logins. You can always be sure that **there are no errors**. We have developed a mobile app for you to see anti-spam statistics wherever.
112
 
113
- We have developed antispam for WordPress that would provide **maximum protection from spam bots** and you can provide for your visitors **a simple and convenient form of comments/registrations without annoying CAPTCHAs and puzzles**. Used to detect spam multistage test that allows us to block up to 99.998% of spam bots.
114
 
115
- The anti-spam method offered by CleanTalk allows to switch from the methods that trouble the communication (CAPTCHA, question-answer etc.) to a more convenient one.
116
 
117
- CleanTalk is premium anti-spam service for WordPress, please look at the <a href="http://cleantalk.org/price">pricing</a>. The plugin works with cloud anti spam service CleanTalk. CleanTalk has free trial. We try to provide anti-spam service at the highest level and we can not afford to offer a free version of our service, as this will immediately affect the quality of providing anti-spam protection. Paying for a year of anti-spam service, you save a lot more and get:
118
 
119
  * Up to 99.998% protection against spam bots.
120
  * Time and resources saving.
@@ -129,36 +131,37 @@ CleanTalk is premium anti-spam service for WordPress, please look at the <a href
129
 
130
  = Additional features =
131
  * Online, daily and weekly anti-spam reports traffic VS spam.
132
- * Apps for iPhone, Android to control anti-spam service, comments, signups, contacts. With traffic and spam statistics for last 7 days.
133
  * Anti-spam apps for most popular CMS on cleantalk.org.
134
 
135
  = How to protect sites from spam bots without CAPTCHA? =
136
- The most popular method is CAPTCHA - the annoying picture with curved and sloping symbols, which are offered to the visitor to fill in. It is supposed that spam bots won't discern these CAPTCHA, but a visitor will. CAPTCHA provokes great irritation, but if one wants to speak out, he has to fill in these symbols time after time, making mistakes and starting once again.
137
- Sometimes CAPTCHA reminds doodle 2x year old child. For users with vision problems captcha is just an insurmountable obstacle. Users hate captcha. Captcha for users means "hate". Unreadable CAPTCHA stops about 80% of site visitors. After 2 failed attempts to bring it up to 95% reject further attempts.
138
- At the sight of CAPTCHA and after input errors, many visitors leave the resource. Thus, CAPTCHA helps to protect the resource both from bots and visitors. CAPTCHA is not a panacea from spam. Doubts Concerning the Need for CAPTCHA?
139
 
140
- *“Ultimately, Captchas are useless for spam because they’re designed to tell you if someone is ‘human’ or not, but not whether something is spam or not.” Matt Mullenweg*
141
 
142
- You do not have to work in IT to know what spam is. Besides piles of unwanted e-mail, there are spam bots, or special software programs designed to act as human Web site visitors that are posting unwelcome messages over the Internet to advertise dubious services, while more often spammer messages do not even make much sense. Similarly to bacteria and viruses mutations developing antibiotic resistance in real world, spam bots are becoming more resilient penetrating Internet firewalls and security layers.
143
 
144
  *Why are they spamming me?*
145
 
146
  Spammers want to get backlinks from your site to improve their site's PageRank or redirect your visitors to malicious sites.This level of spam can damage your reputation with readers and commentators if you fail to tackle it. It is not uncommon for some WordPress websites to receive hundreds or even thousands of comments every week. However, by using a CleanTalk plugin, spam can be easily handled by your WordPress website.
147
 
148
  = CleanTalk's features =
149
- CleanTalk one of the fastest plug-in that allows you to lower the server load. One of the important parameters for each Web master is the speed of the site, so we make sure that our plug-in to consume as little as possible of server resources. Cloud service provides the advantage that all the checks take place in the cloud.
 
 
150
 
151
- The CleanTalk company developed unique algorithms to assess the behavior of the visitor. CleanTalk analyzes user behavior and parameter of the filled out form. Anti spam module, installed on the website, sends the behaviour parameters of the visitor or spam bot. These parameters are estimated, and service makes a decision – to post a message or to define it as spam and reject. On the basis of such checks, the service forms its own list of email addresses used by spam bots. Likewise the registrations of visitors are checked. The service adds not only email addresses to the blacklist, but also IP addresses and domains of the websites that are promoted through spam mailout. All of this happens automatically and requires no action from the administration of the website. At 2.5 million queries the service makes a mistake in 40-45 cases, i.e. CleanTalk detects spam with 99.9982% accuracy. We constantly monitor these errors and make adjustments to our algorithms”, so the team is aiming to improve those figures over time.
152
 
153
- All-in-one. CleanTalk immediately protects all forms – comments, registration, feedback, contacts. No need to install additional plug-ins for each form. You get save resources and increase performance of your website.
154
 
155
- Spam attacks log. Service CleanTalk records all filtered comments, registration and other spam attacks in the “Log of spam attacks” and stores the data in the log up to 45 days. Using the log, you can ensure reliable protection of your website from spam and no false/positive filtering.
156
 
157
- With the help of anti-spam by CleanTalk you can check existing comments and users, to find and quickly delete spam comments at once. This allows administrators of the Web sites automatically to check and identify spam bots, comments and users, which were not detected by conventional anti-spam tools. Checking existing comments and users is made on the basis of the nearly 2 million of certain spam bots. Detailed statistic allows CleanTalk customers to control the whole process.
158
 
159
- CleanTalk has got an advanced option “Spam FireWall”, this option allows blocking the most active spam bots before they get access to web site. It prevents loading of pages of the web site by spam bots, so your web server doesn’t need perform all scripts on these pages. Also it prevents scanning of pages of the web site spam bots. Therefore Spam FireWall significantly can reduce the load on your web server. Spam FireWall can mitigate HTTP/HTTPS DDoS attacks. When an intruder makes GET requests to attack your website. Spam FireWall blocks all requests from bad IP addresses. Your website gives infringer a special page with description of DDoS rejection instead of the website pages. Therefore Spam FireWall can help to reduce of CPU usage on your server.
160
 
161
- “CleanTalk team has been developing a cloud spam protection system for four years and has created a truly reliable anti-spam service designed for you to guarantee your safety”.
162
 
163
  = We recommend =
164
  Audience engagement plugin <a href="http://wordpress.org/plugins/feedweb/">Feedweb</a>
@@ -177,7 +180,10 @@ Audience engagement plugin <a href="http://wordpress.org/plugins/feedweb/">Feedw
177
 
178
  > *** Forbidden. Sender blacklisted. ***
179
 
180
- Done!
 
 
 
181
 
182
  = How can setup plugin in WPMU version? =
183
  In WordPress multisite version you can switch the plugin to use Global Access key. In this way the plugin doesn't show any options to enter Access key in plugin settings and doesn't show Trial banner in WordPress backend. To setup global CleanTalk access key for all websites in WPMU, define constant in your wp-config.php file before defining database constants:
@@ -329,6 +335,9 @@ If you think that message was blocked wrong, let us know about it.
329
 
330
  If you or someone from your visitors have error "Forbidden. Enable JavaScript." please check JavaScript support in your browser and do JavaScript test at this page <a href="https://cleantalk.org/checkout-javascript-support">Check out JavaScript support</a>.
331
 
 
 
 
332
  == Other notes ==
333
 
334
  = Troubleshooting Guide =
@@ -410,24 +419,17 @@ We develop plugin to do it as optimized as possible, CleanTalk doesn't downgrade
410
  = Requirements =
411
  WordPress 3.0 at least. PHP 5 with CURL or file_get_contents() function and enabled 'allow_url_fopen' setting. <a href="http://cleantalk.org/register?platform=wordpress">Sign up</a> to get an Access key.
412
 
413
- = Translations =
414
- * Danish (da_DK)
415
- * French (fr_FR) - thanks to Gilles Santacreu <a href="http://net-ik.net">http://net-ik.net</a>
416
- * German (de_DE)
417
- * Italian (it_IT)
418
- * Polish (pl_PL)
419
- * Portuguese (pt_PT)
420
- * Spanish (es_ES) - thanks to Andrew Kurtis and <a href="http://www.webhostinghub.com/index-c.html">WebHostingHub</a>
421
- * Russian (ru_RU)
422
-
423
  == Screenshots ==
424
  1. Anti-spam plugin settings.
425
  1. Anti-spam stopped spam bot at the CAPTCHA less registration form. The plugin provide explanation to visitor and websites about eache rejected comment/registration or contact message.
426
  1. Use anti-spam analytics tool for each website in service Dashboard to have information about spam/legitimate statistics.
427
  1. Use anti-spam log to control anti-spam plugin.
428
- 1. CleanTalk works faster than most of the other anti-spam plugins.
429
 
430
  == Changelog ==
 
 
 
431
  = 5.36 2016-02-04 =
432
  * Improved JavaScript anti spam protection
433
  * Improvements for avoiding blocking requests from payment systems
@@ -659,310 +661,10 @@ WordPress 3.0 at least. PHP 5 with CURL or file_get_contents() function and enab
659
  * Trimmed API key in admin panel.
660
  * Added current options to array sended to CleanTalk servers.
661
 
662
- = 4.13 2014-12-29 =
663
- * Fixed bug with autimatically aprovement not spam comments. Now this option disabled and do not override local WordPress policy.
664
-
665
- = 4.12 2014-12-29 =
666
- * Fixed bug with 'Wrong Access key...' notice in WordPress dashboard.
667
- * Fixed filtration bug in WordPress dashboard login form.
668
-
669
- = 4.11 2014-12-22 =
670
- * Improved anti-spam protection for custom contact/registration/subscribe forms.
671
- * Improved anti-spam protection for comments.
672
- * Accelerated plugin speed for comments, regirstrations and contacts.
673
- * Added translation to French.
674
-
675
- = 4.10 2014-12-10 =
676
- * Improved anti-spam protection for custom contact/registration/subscribe forms.
677
- * Option 'Custom contact forms' enabled by default for new setups.
678
- * Removed settings "Publish relevant comments", "Use encrypted (SSL) connection".
679
- * Added translation to Danish (thank you for Mikkel at KreativJul.dk).
680
-
681
- = 4.9 2014-11-24 =
682
- * Fixed spam test for Contact Form 7.
683
-
684
- = 4.8 2014-11-19 =
685
- * Improved anti-spam protection for BuddyPress registrations and custom contact forms.
686
-
687
- = 4.7 2014-11-16 =
688
- * Fixed JavaScript spam test for FastSecure contact form.
689
-
690
- = 4.6 2014-11-11 =
691
- * Improved anti-spam protection on BuddyPress registrations.
692
- * Improved anti-spam protection on contact forms.
693
- * Removed plugin sign from pending, spam comments. To get details about a comment please use Dashboard at cleantalk.org.
694
- * Improved Access key validation function.
695
- * Added protection for bbPress comments via stop list. Stop list function is a list to reject comments by prefiled words. To fill the list please use Dashboard at cleantalk.org.
696
-
697
- = 4.5 2014-11-04 =
698
- * Fixed CF7 JavaScript bug.
699
- * Fixed rejects in bbPress guests comments.
700
-
701
- = 4.4 2014-10-29 =
702
- * Improved anti-spam JS test for CF7.
703
- * Fixed 'noscript' text in FaceBook Like preview in Valenti theme.
704
-
705
- = 4.2 2014-10-20 =
706
- * Fixed double checks issue for BuddyPress registrations.
707
- * Increased timeout limits to find the work server.
708
-
709
- = 4.1 2014-10-13 =
710
- * Optimized code for manual moderation feedback sending.
711
- * Optimized anti-spam algorithms for comments, contacts and signups.
712
-
713
- = 4.0 2014-10-06 =
714
- * Improved anti-spam protection for custom contact forms.
715
- * Improved anti-spam protection for registration forms.
716
-
717
- = 3.9 2014-10-01 =
718
- * Did exception to do not break to create new user in WordPress backend.
719
-
720
- = 3.8 2014-09-19 =
721
- * Fixed json_encode() + malformed characters.
722
- * Fixed JavaScript issue with wpautop().
723
-
724
- = 3.6 2014-09-15 =
725
- * Fixed preg_match() issue for Formidable forms and Custom contact forms.
726
- * Improved anti-spam protection for Custom contact forms.
727
-
728
- = 3.4 2014-09-04 =
729
- * We've added anti-spam for themes contact forms and any untested contact forms plugins. To use this test enable option "Custom contact forms" in plugin settings.
730
- * We've added auto rotation for spam comments. Now the plugin removes comments in SPAM folder older then 15 days. This option is enabled by default.
731
-
732
- = 3.2 2014-08-27 =
733
- * Fixed submit_time() logic for failed submits (comments/registrations). Now form fill time resets after every failed submit.
734
-
735
- = 3.1 2014-08-19 =
736
- * Added anti-spam test over senders Cookies.
737
- * Improved form fill anti-spam test.
738
- * Improved speed selection of the nearest server to website.
739
- * Improved anti-spam speed for comments.
740
- * Relevance anti-spam test disabled by default. To enable test should be used option 'relevance_test'.
741
-
742
- = 2.58 2014-08-06 =
743
- * Added anti-spam protection for signups posted via WooCommerce order form.
744
- * Improved anti-spam protection for Contact Form 7.
745
- * Improved anti-spam protection for registrations. Now the plugin looking for JavaScript anti spam test results not only in POST array, but in COOKIES array too. This improvement allows protect signup forms for any untested signups plugins and themes.
746
- * Updated PHP API. Now the plugin can resolve sender IP for websites behind proxy servers. If the proxy servers uses private IP address.
747
-
748
- = 2.57 2014-07-29 =
749
- * Improved anti-spam protection for comments. The plugin now proccessing website url in the comments form.
750
- * Fixed sign remove logic for approved comments. Previous version doesn't cut sign for comments approved via AJAX call in WordPress backend.
751
- * Fixed switching to SSL for comments. Previous version doesn't use secured connection for comments.
752
-
753
- = 2.56 2014-07-21 =
754
- * Fixed account status check logic. Previous version makes unnecessary test API calls when the plugin asks account status check.
755
-
756
- = 2.55 2014-07-11 =
757
- * Fixed bug with account status function. In backend the plugin showed notice 'Please don’t forget to disable CAPTCHA if you have it!' on every page.
758
-
759
- = 2.54 2014-07-11 =
760
- * Fixed signup anti-spam protection logic for BuddyPress registrations.
761
- * Fixed anti-spam protection for JetPack contact form.
762
- * Changed account status check logic.
763
-
764
- = 2.53 2014-06-27 =
765
- * Fixed anit-spam protection bug for signups.
766
- * Changed anti-spam functions (comments and signups) priority.
767
-
768
- = 2.52 2014-06-25 =
769
- * Fixed 'Fatal error: Call to a member function get_error_code()' issue with signups via BuddyPress.
770
-
771
- = 2.51 2014-06-23 =
772
- * Added spam protection for registrations via plugin New User Approve by Josh Harrison. If the CleanTalk matched signup as spam this signup will be denied to placing in pending queue.
773
- * Added option "Use secure (SSL) connection to CleanTalk cloud". If the option enabled plugin will communicate with CleanTalk severs via 128bit encrypted data channel. So, if you have SSL protected webforms on website you can use this option to be sure that visitors personal data safely transmits to CleanTalk servers.
774
- * Fixed minor bug with loading backend functions.
775
-
776
- = 2.49 2014-06-10 =
777
- * Added spam protection for S2Member Auth.net forms.
778
- * Added spam protection for multisite signup form.
779
- * Optimized account status check function.
780
-
781
- = 2.46 2014-05-19 =
782
- * Added: HTML notice about the need to enable JavaScript.
783
- * Fixed: Fixed pingbacks anti-spam test.
784
-
785
- = 2.44 2014-05-12 =
786
- * Added: Anti-spam protection for S2Member framework. 
787
- * Improved: JavaScript anti-spam test. 
788
- * Improved: Plugin load time for backend and frontend.
789
- * Fixed: PHP warning mb_convert_encoding()
790
-
791
- = 2.42 2014-04-29 =
792
- * Fixed: JavaScript anti-spam test for comments. 
793
-
794
- = 2.40 2014-04-25 =
795
- * New: Fast Secure Contact form support.
796
- * New: WordPress Landing Pages support
797
-
798
- = 2.38 2014-03-27 =
799
- * Fixed: Registraion form submit time spam test.
800
-
801
- = 2.36 2014-03-12 =
802
- * Reversed to patches from old revisions.
803
-
804
- = 2.35 2014-03-12 =
805
- * New: Notifications about disabled account
806
- * New: Improved JavaScript spam test.
807
- * Fixed: Code optimization
808
- * Fixed: JavaScript test for signups.
809
-
810
- = 2.33 2014-02-12 =
811
- * Fixed: CURLOPT_FOLLOWLOCATION bug at admin notice
812
-
813
- = 2.32 2014-02-04 =
814
- * New: Added notice about automatically approved comment. The notice shows only for first approved comment and only for new commentators (without approved comments) of the blog.
815
- * New: At WordPress console added banner for notices.
816
- * Changed: Screenshots updated.
817
-
818
- = 2.31 2014-01-24 =
819
- * New: Added spam protection for JetPack comments
820
- * Fixed: cURL connection issue "Expect: 100-continue"
821
-
822
- = 2.30 2014-01-13 =
823
- * Changed: Improved servers connection logic.
824
- * Fixed: Antispam test for Fomidable forms.
825
-
826
- = 2.28 2013-12-19 =
827
- * New: Added protection against spam bots for WooCommerce review form.
828
- * Fixed: JavaScript anti-spam logic for WooCommerce review form.
829
-
830
- = 2.27 2013-12-06 =
831
- * New: Added protection against spam bots for JetPack Contact form.
832
- * Fixed: JavaScript anti-spam logic for registrations and Contact form 7.
833
-
834
- = 2.25 2013-11-27 =
835
- * New: Added protection against spam bots for BuddyPress registrations.
836
- * New: Added protection against spam bots for Contact form 7.
837
- * New: Added Spanish (es_ES) translation.
838
-
839
- = 2.23 2013-11-20 =
840
- * New: Added automatic training blacklists on spam bot account deletion.
841
- * New: Added URL to project homepage at plugin options.
842
- * Changed: Improved anti-spam logic.
843
-
844
- = 2.21 2013-11-13 =
845
- * Changed: WordPress blacklists settings get priority over plugin's anti-spam settings
846
- * Changed: Disabled management approval comments for regular commentators of the blog. Automatically approved for publication only the comments of the new blog authors.
847
- * Changed: Removed form submit time test. Imporved JavaScript spam test.
848
- * Changed: PHP code optimizations
849
-
850
- = 2.19 2013-11-08 =
851
- * New: Antispam protection from spam bots at the registration form
852
- * Changed: Russian localization for admin panel
853
- * Changed: PHP code optimizations
854
-
855
- = 2.5.18 2013-11-01 =
856
- * Fixed: Bug with selection of the last comments for post
857
- * New: Antispam protection for Formiadble feedback forms
858
- * New: Automatic deletion of outdated spam comments
859
- * New: On/Off option for comments spam filtration
860
- * Tested with WordPress 3.7.1
861
-
862
- = 2.4.15 2013-09-26 =
863
- * Fixed: Bug with mass comments deletion
864
- * Changed: Russian localization for admin panel
865
- * Tested with mulitsite setup (WordPress network or WPMU)
866
-
867
- = 2.4.14 2013-08-29 =
868
- * Changed: Removed feedback requests to the servers for banned (spam) comments.
869
-
870
- = 2.4.13 2013-08-19 =
871
- * Changed: Switched HTTP requests from file_get_contents() to CURL. Added file_get_contens() as backup connection to the servers.
872
- * Changed: Removed feedback requests for comments moved to trash.
873
- * Fixed: "Fail connect to servers..." error on hostings with disabled 'allow_url_fopen' PHP option.
874
-
875
- = 2.4.12 2013-08-12 =
876
- * Removed RPC::XML library from plugin.
877
- * Switched plugin to HTTP+JSON connection with servers.
878
- * Fixed bug with comments anti-spam tests with non UTF8 codepage.
879
-
880
- = 2.4.11 2013-08-02 =
881
- * Removed spam tests for self-made pingbacks
882
- * Tested up to WP 3.6
883
-
884
- = 2.4.10 2013-07-24 =
885
- * Fixed warning in PHP 5.4
886
- * Fixed bug with disabling comments test for Administrators, Authors and Editors
887
- * "Stop words" settings moved to <a href="http://cleantalk.org/my">Control panel</a> of the service
888
- * "Response language" settings moved <a href="http://cleantalk.org/my">Control panel</a> of the service
889
-
890
- = 2.4.9 =
891
- * Fixed extra debugging in base class
892
-
893
- = 2.4.8 =
894
- * Enabled convertion to UTF8 for comment and example text
895
- * Optimized PHP code
896
-
897
- = 2.3.8 =
898
- * Enabled selection the fastest server in the pool
899
- * Fixed work server in plugin's config
900
-
901
- = 2.2.3 =
902
- * Secured md5 string for JavaScript test
903
- * Added requests's timestamp to calculate request work time
904
- * Update base CleanTalk's PHP class
905
-
906
- = 2.1.2 =
907
- * Improved perfomance for processing large comments (over 32kb size)
908
- * Improved perfomance for bulk operations with comments in Comments panel
909
- * Added feedback request with URL to approved comment
910
-
911
- = 2.0.2 =
912
- * Fixed bug with JavaScript test and WordPress cache plugins
913
-
914
- = 2.0.1 =
915
- * Added option "Publicate relevant comments" to plugin's options.
916
- * Added descriptions to plugin options
917
-
918
- = 1.5.4 =
919
- * Fixed HTTP_REFERER transmission to the servers
920
- * Improved JavaScript spam test
921
- * Optimized PHP code
922
-
923
- = 1.4.4 =
924
- * Pingback, trackback comments has moved to manual moderataion
925
- * Added transmission to the serves comment type and URL
926
- * Post title, body and comments separated into individual data elements
927
- * Added priority for matched words in the comment with post title
928
- * Enabled stop words filtration as default option
929
-
930
- = 1.3.4 =
931
- * Removed PHP debugging.
932
-
933
- = 1.3.3 =
934
- * Added notice at admin panel about empty Access key in plugin settings
935
- * Removed HTTP link to the site project from post page
936
- * Removed unused options from settings page
937
- * Tested up to WordPress 3.5
938
-
939
- = 1.2.3 =
940
- * Fixed bug with session_start.
941
-
942
- = 1.2.2 =
943
- * Plugin rename to CleanTalk. Spam prevent plugin
944
- * Integration Base Class version 0.7
945
- * Added fast submit check
946
- * Added check website in form
947
- * Added feedbacks for change comment status (Not spam, unapprove)
948
- * Added function move comment in spam folder if CleanTalk say is spam
949
- * Disable checking for user groups Administrator, Author, Editor
950
- * Marked red color bad words
951
-
952
- = 1.1.2 =
953
- * Addition: Title of the post attached to the example text in auto publication tool.
954
- * Tested with WordPress 3.4.1.
955
-
956
- = 1.1.1 =
957
- * HTTP_REFERER bug fixed
958
-
959
- = 1.1.1 =
960
- * Added user locale support, tested up to WP 3.4
961
-
962
- = 1.1.0 =
963
- * First version
964
-
965
  == Upgrade Notice ==
 
 
 
966
  = 5.36 2016-02-04 =
967
  * Improved JavaScript anti spam protection
968
  * Improvements for avoiding blocking requests from payment systems
@@ -1179,186 +881,3 @@ Support of Contact Form 7 versions before 3.0.0, fixed global JS-vars and online
1179
 
1180
  = 4.14 2015-01-19 =
1181
  Removed deprecated option from comment approvement code.
1182
-
1183
- = 4.13 2014-12-29 =
1184
- Not spam comments auto approvement bug fix.
1185
-
1186
- = 4.12 2014-12-29 =
1187
- Plugin backend minfor bug fixes.
1188
-
1189
- = 4.11 2014-12-22 =
1190
- Major changes in spam protection algorithms.
1191
-
1192
- = 4.10 2014-12-10 =
1193
- Minor improvements for custom contact/registration/subscribe forms.
1194
-
1195
- = 4.9 2014-11-24 =
1196
- Minor bug fix for Contact form 7.
1197
-
1198
- = 4.8 2014-11-19 =
1199
- Improved anti-spam protection for BuddyPress registrations and custom contact forms.
1200
-
1201
- = 4.7 2014-11-16 =
1202
- Fixed JavaScript antispam test for FastSecure contact form.
1203
-
1204
- = 4.6 2014-11-11 =
1205
- Minor changes in anti-spam logic for BuddyPress registrations, contact forms and bbPress guest posting.
1206
-
1207
- = 4.5 2014-11-04 =
1208
- Bug fixes for Contact form 7 and bbPress guests posting.
1209
-
1210
- = 4.4 2014-10-29 =
1211
- Improved JS checking for CF7.
1212
-
1213
- = 4.2 2014-10-20 =
1214
- Increased plugin perfomance for BuddyPress registrations.
1215
-
1216
- = 4.1 2014-10-13 =
1217
- Minor anti-spam improvements for contacts, registration and contact forms.
1218
-
1219
- = 4.0 2014-10-06 =
1220
- Major anti-spam improvements for registration and contact forms.
1221
-
1222
- = 3.9 2014-10-01 =
1223
- Did exception to do not break to create new user in WordPress backend.
1224
-
1225
- = 3.8 2014-09-19 =
1226
- Bug fix release. Minor fixes in API class and JavaScript anti-spam test.
1227
-
1228
- = 3.6 2014-09-15 =
1229
- Minor fixes in anti-spam protection for Formidable and custom contact forms.
1230
-
1231
- = 3.4 2014-09-04 =
1232
- Spam comments rotation. Custom (themes) contact forms support.
1233
-
1234
- = 3.2 2014-08-27 =
1235
- Minor changes in spam filtration logic.
1236
-
1237
- = 3.1 2014-08-19 =
1238
- Major changes for comments antispam logic. Improved plugin speed.
1239
-
1240
- = 2.59 2014-08-14 =
1241
- Antispam protection for bbPress guests posts. Improvement for JetPack comments and PHP API update.
1242
-
1243
- = 2.58 2014-08-06 =
1244
- * Added anti-spam protection for signups posted via WooCommerce order form.
1245
- * Improved anti-spam protection for Contact Form 7.
1246
- * Improved anti-spam protection for registrations. Now the plugin looking for JavaScript antispam test results not only in POST array, but in COOKIES array too. This improvement allows protect signup forms for any untested signups plugins and themes.
1247
- * Updated PHP API. No the plugin can resolve sender IP for websites behind proxy servers. If the proxy servers uses private IP address.
1248
-
1249
- = 2.57 2014-07-29 =
1250
- * Improved anti-spam protection for comments. The plugin now proccessing website url in the comments form.
1251
- * Fixed sign remove logic for approved comments. Previous version doesn't cut sign for comments approved via AJAX call in WordPress backend.
1252
- * Fixed switching to SSL for comments. Previous version doesn't use secured connection for comments.
1253
-
1254
- = 2.56 2014-07-21 =
1255
- * Fixed account status check logic. Previous version makes unnecessary test API calls when the plugin asks account status check.
1256
-
1257
- = 2.55 2014-07-11 =
1258
- * Fixed bug with account status function. In backend the plugin showed notice 'Please don’t forget to disable CAPTCHA if you have it!' on every page.
1259
-
1260
- = 2.54 2014-07-11 =
1261
- * Fixed signup anti-spam protection logic for BuddyPress registrations.
1262
- * Fixed anti-spam protection for JetPack contact form.
1263
- * Changed account status check logic.
1264
-
1265
- = 2.53 2014-06-27 =
1266
- * Fixed anit-spam protection bug for signups.
1267
- * Changed anti-spam functions (comments and signups) priority.
1268
-
1269
- = 2.52 2014-06-25 =
1270
- * Fixed 'Fatal error: Call to a member function get_error_code()' issue with signups via BuddyPress.
1271
-
1272
- = 2.51 2014-06-23 =
1273
- * Added spam protection for registrations via plugin New User Approve by Josh Harrison. If the CleanTalk matched signup as spam this signup will be denied to placing in pending queue.
1274
- * Added option "Use secure (SSL) connection to CleanTalk cloud". If the option enabled plugin will communicate with CleanTalk severs via 128bit encrypted data channel. So, if you have SSL protected webforms on website you can use this option to be sure that visitors personal data safely transmits to CleanTalk servers.
1275
- * Fixed minor bug with loading backend functions.
1276
-
1277
- = 2.49 2014-06-10 =
1278
- * Added spam protection for S2Member Auth.net forms.
1279
- * Added spam protection for multisite signup form.
1280
- * Optimized account status check function.
1281
-
1282
- = 2.46 2014-05-19 =
1283
- * Added: HTML notice about the need to enable JavaScript.
1284
- * Fixed: Fixed pingbacks anti-spam test.
1285
-
1286
- = 2.44 2014-05-12 =
1287
- * Added: Anti-spam protection for S2Member framework. 
1288
- * Improved: Plugin load time for backend and frontend.
1289
- * Improved: JavaScript anti-spam test. 
1290
- * Fixed: PHP warning mb_convert_encoding()
1291
-
1292
- = 2.42 2014-04-29 =
1293
- * Fixed: JavaScript anti-spam test for comments.
1294
-  
1295
- = 2.38 2014-03-27 =
1296
- * Fixed: Registraion form submit time spam test.
1297
-
1298
- = 2.36 2014-03-12 =
1299
- * Reversed to patches from old revisions.
1300
-
1301
- = 2.35 2014-03-12 =
1302
- * New: Notifications about disabled account
1303
- * New: Improved JavaScript spam test.
1304
- * Fixed: Code optimization
1305
- * Fixed: JavaScript test for signups.
1306
-
1307
- = 2.33 2014-02-12 =
1308
- * Fixed: CURLOPT_FOLLOWLOCATION bug at admin notice
1309
-
1310
- = 2.32 2014-02-04 =
1311
- * New: Added notice about automatically approved comment. The notice shows only for first approved comment and only for new commentators (without approved comments) of the blog.
1312
- * New: At WordPress console added banner for notices.
1313
- * Changed: Screenshots updated.
1314
-
1315
- = 2.31 2014-01-24 =
1316
- * New: Added spam protection for JetPack comments
1317
- * Fixed: CURL connection issue "Expect: 100-continue"
1318
-
1319
- = 2.30 2014-01-13 =
1320
- * Changed: Improved servers connection logic.
1321
- * Fixed: Antispam test for Fomidable forms.
1322
-
1323
- = 2.27 2013-12-06 =
1324
- * New: Added protection against spam bots for JetPack Contact form.
1325
- * Fixed: JavaScript anti-spam logic for registrations and Contact form 7.
1326
-
1327
- = 2.25 2013-11-27 =
1328
- * New: Added protection against spam bots for BuddyPress registrations.
1329
- * New: Added protection against spam bots for Contact form 7.
1330
- * New: Added Spanish (es_ES) translation.
1331
-
1332
- = 2.23 2013-11-20 =
1333
- * New: Added automatic training blacklists on spam bot account deletion.
1334
- * New: Added URL to project homepage at plugin options.
1335
- * Changed: Improved anti-spam logic.
1336
-
1337
- = 2.21 2013-11-13 =
1338
- * Changed: WordPress blacklists settings get priority over plugin's anti-spam settings
1339
- * Changed: Disabled management approval comments for regular commentators of the blog. Automatically approved for publication only the comments of the new blog authors.
1340
- * Changed: PHP code optimizations
1341
-
1342
- = 2.19 2013-11-08 =
1343
- * New: Antispam protection from spam bots at the registration form
1344
- * Changed: Russian localization for admin panel
1345
- * Changed: PHP code optimizations
1346
-
1347
- = 2.5.18 2013-11-01 =
1348
- * Fixed: Bug with selection of the last comments for post
1349
- * New: Antispam protection for Formiadble feedback forms
1350
- * New: Automatic deletion of outdated spam comments
1351
- * New: On/Off option for comments spam filtration
1352
- * Tested with WordPress 3.7.1
1353
-
1354
- = 2.4.15 2013-09-26 =
1355
- * Fixed: Bug with mass comments deletion
1356
- * Changed: Russian localization for admin panel
1357
- * Tested with mulitsite setup (WordPress network or WPMU)
1358
-
1359
- = 2.4.14 2013-08-29 =
1360
- * Changed: Removed feedback requests to the servers for banned (spam) comments.
1361
-
1362
- = 2.4.13 2013-08-19 =
1363
- * Fixed: "Fail connect to servers..." error on hostings with disabled 'allow_url_fopen' PHP option.
1364
-
1
  === Anti-Spam by CleanTalk - No Captcha, no comments & registrations spam ===
2
  Contributors: znaeff, shagimuratov, vlad-cleantalk
3
+ Tags: anti-spam, antispam, bbpress, buddypress, captcha, cf7 spam, comments, contact form spam, signup, spam, spammers, spammy, woocommerce, wordpress spam, booking, order, subscription, gravity spam, jetpack, bots, contact form 7, contact form, registrations, ninja, Fast Secure Contact, Gravity forms, formidable, mailchimp, s2member, protection, protect, email, akismet, plugin, recaptcha, math, security, login, blacklist, prevent spam comments, wordpress, User Frontend, bulk delete, bulk remove, cloudflare, widget, review, auth forms, firewall, ddos, cleantalk, mailpoet, profile builder, comment spam, registration spam, spam comments, signup spam, filter, user registration spam,pingback,trackback,newsletter,puzzle,question
4
  Requires at least: 3.0
5
  Tested up to: 4.4.2
6
+ Stable tag: 5.36.1
7
  License: GPLv2
8
  License URI: http://www.gnu.org/licenses/gpl-2.0.html
9
 
23
  1. Check existing comments for spam.
24
 
25
  = Public reviews =
26
+ > Using CleanTalk on WPLift was a great test as we receive huge amounts of spam.
27
+ > *Oliver Dale, <a href="http://wplift.com/wordpress-anti-spam-plugin" target="_blank">WPLift.com</a>.*
28
 
29
  = Comments spam protection =
30
+ Supports native WordPress, JetPack comments and any other comments plugins. Plugin moves spam comments to SPAM folder or you can set options to silently ban spam comments. You can enable options in the plugin settings to auto delete comments from SPAM folder.
31
 
32
  = Spam bots registrations filter =
33
+ Filters spam bots on registration forms WordPress, BuddyPress, bbPress, S2Member, WooCommerce, Profile builder and any other registrations plugins.
34
 
35
+ = Protection against contact form spam =
36
  Plugin is tested and ready to protect against spam emails via Formidable forms, Contact form 7, JetPack Contact form, Fast Secure Contact form, Ninja forms, Landing pages, Gravity forms and any themes/custom contact forms.
37
 
38
  = WooCommerce spam filter =
39
+ Anti-spam by CleanTalk filters spam registrations and spam reviews for WooCommerce. Plugin is fully compatible with WooCommerce 2.1 and higher.
40
 
41
  = Newsletters filter =
42
+ Anti-spam by CleanTalk filters spam subscriptions for MailPoet and many other newsletters plugins.
43
 
44
  = Spam filter for themes contact forms =
45
+ Plugin blocks spam emails via any themes (built-in) contact forms. With AJAX forms plugin silently (without any error notices on WordPress frontend) filters spam emails.
46
 
47
  = Other spam filters =
48
  * WordPress Landing Pages.
49
  * WP User Frontend.
50
+ * Any WordPress form (options for 'Custom contact forms'). 
51
+ * Any submission to site (options for 'Check all POST data')
52
 
53
  = Compatible with WordPress cache plugins =
54
  * W3 Total Cache, Quick Cache, WP Fastest Cache, Hyper Cache, WP Super cache and any other cache plugins.
55
 
56
+ = Check existing comments for spam. Bulk comment removal =
57
+ With the help of anti-spam by CleanTalk you can check existing comments to find and quickly delete spam comments at once. To use this function, go to WP Console->Comments->Find spam comments.
58
 
59
+ = Check existing users for spam. Bulk account removal =
60
+ With the help of anti-spam by CleanTalk you can check existing accounts to find and quickly delete spam users at once. For use this function, go to WP Console->Users->Check for spam.
61
 
62
  = Low false/positive rate =
63
+ This plugin uses multiple anti-spam tests to filter spam bots with as lower false/positive rate as possible. Multiple anti-spam tests avoid false/positive blocks for real website visitors even if one of the tests fail.
64
 
65
  = CleanTalk works faster than most of the other anti-spam plugins =
66
+ It is common knowledge that the faster your site loads, the better your customer experience is, the higher your Pagerank will be, and the better your site will convert. Speed is becoming increasingly important in Search Engine Optimization, conversion and user experience. Today, site speed is one of the most important ranking factors on Google. A site that loads slowly will lose visitors and potential revenue.
67
 
68
+ There are different ways of improving your site's loading performance. One important parameter for site performance is to install well-developed plugins from a reputable source.
69
 
70
+ Among anti-spam plugins CleanTalk Anti-Spam is one of the fastest. Despite the large plug-in functionality, the developers have optimized the performance of the plugin so that CleanTalk is faster than most analogs. This contributes to the cloud service architecture, as all calculations take place in the cloud, not on the server, the server receives the finished result for further action.
71
 
72
  https://s.w.org/plugins/cleantalk-spam-protect/screenshot-5.png?r=1288723
73
 
74
  = How CleanTalk works? =
75
+ * A visitor writes a comment or registers
76
  * CleanTalk plugin sends action parameters into the CleanTalk cloud
77
+ * Service analyzes the parameters
78
+ * If this is a visitor, the comment will be published. If it’s a spam bot, then CleanTalk blocks this comment or registration.
79
  * Parameters are written to the log which can be viewed in the Control Panel service.
80
 
81
+ The CleanTalk team has been developing cloud-based spam protection for 5 years and has created a truly reliable anti-spam service designed for you to ensure your safety.
82
 
83
  = Spam attacks log =
84
+ Service CleanTalk (this plugin is a client application for CleanTalk anti-spam service) records all filtered comments, registration and other spam attacks in the "Log of spam attacks" and stores the data in the log for up to 45 days. Using the log, you can ensure reliable protection of your website from spam and no false/positive filtering.
85
 
86
  = Spam FireWall =
87
+ CleanTalk has an advanced option "Spam FireWall". This option allows blocking the most active spam bots before they get access to your website. It prevents
88
+ spam bots from loading website pages so your web server doesn't have to perform all scripts on these pages. Also it prevents scanning of pages of the
89
+ website by spam bots. Therefore Spam FireWall significantly reduces the load on your web server.
90
+ Spam FireWall also makes CleanTalk the two-step protection from spam bots.
91
+ Spam FireWall is the first step and it blocks the most active spam bots.
92
+ CleanTalk Anti-Spam is the second step and checks all other requests on the website in the moment of submitting comments/registers etc.
93
 
94
  = How Spam FireWall works? =
95
  * The visitor enters to your web site.
96
+ * HTTP request data is checked against the nearly 5.8 million identified IP spam bots.
97
+ * If it is an active spam bot, the bot gets a blank page, if it is a visitor then they receive the site page. This is completely transparent to the visitors.
98
 
99
  All the CleanTalk Spam FireWall activity is being logged in the process of filtering.
100
 
101
+ = Spam FireWall DDoS Protection (Experimentally option) =
102
+ Spam FireWall can mitigate HTTP/HTTPS DDoS attacks. When an intruder makes GET requests to attack your website, Spam FireWall blocks all requests from bad IP addresses. Your website gives the intruder a special page with description of DDoS rejection instead of the website pages. Therefore Spam FireWall can help to reduce CPU usage on your server.
103
 
104
  = XML-RPC brute force protection =
105
+ Spam FireWall can mitigate XML-RPC brute force attacks. It blocks XML-RPC attacks from bad IP addresses. This helps to prevent bruteforce attacks by a Remote Procedure Call.
106
 
107
+ = No spam comments, no spam registrations, no spam contact emails, no spam trackbacks. CAPTCHA-less anti-spam for WordPress =
108
+ Spam is one of the most irritating elements. Rates for spam increases every year and conventional anti-spam can no longer handle all the spam bots. CleanTalk prevents and automatically blocks spam. You'll be surprised how effective CleanTalk is in protecting against spam.
109
 
110
  = Anti-spam plugin info =
111
+ CleanTalk is an all-in-one anti-spam solution for WordPress that protects login, comments, contact and WooCommerce forms at once. You don't need to install separate anti-spam plugins for each form. This allows your blog to work faster and save resources. After installation you will forget about spam; your CleanTalk plugin will do all the work. You won't have to deal with spam as CleanTalk does this for you automatically.
112
 
113
  CleanTalk is a transparent anti-spam tool, we provide detailed statistics of all entering comments and logins. You can always be sure that **there are no errors**. We have developed a mobile app for you to see anti-spam statistics wherever.
114
 
115
+ We have developed anti-spam for WordPress that provides maximum protection from spam bots, allowing you to provide your visitors a simple and convenient form of comments/registrations without annoying CAPTCHAs and puzzles. CleanTalk detects spam in multistage tests allowing us to block up to 99.998% of spam bots.
116
 
117
+ The anti-spam method offered by CleanTalk avoids methods that inconvenience the communication (CAPTCHA, question-answer etc.), and offers your site visitors a more convenient one.
118
 
119
+ CleanTalk is a premium anti-spam service for WordPress and the plugin works with our cloud anti-spam CleanTalk Service. CleanTalk offers a free trial and you can look at the pricing here. We provide anti-spam services at the highest level. To maintain this level we cannot afford to offer a free version of our service, as this will immediately affect the quality of providing anti-spam protection. Paying for a year of anti-spam service, you save a lot more and receive:
120
 
121
  * Up to 99.998% protection against spam bots.
122
  * Time and resources saving.
131
 
132
  = Additional features =
133
  * Online, daily and weekly anti-spam reports traffic VS spam.
134
+ * Apps for iPhone, Android to control anti-spam service, comments, signups, contacts, with traffic and spam statistics for last 7 days.
135
  * Anti-spam apps for most popular CMS on cleantalk.org.
136
 
137
  = How to protect sites from spam bots without CAPTCHA? =
138
+ The most popular method is CAPTCHA - the annoying picture with curved and sloping symbols, which are presented to the visitor to decipher and fill in. It is supposed that spam bots won't discern these CAPTCHA, but a visitor will. CAPTCHA provokes great irritation, but if the visitor wants to comment, he has to fill in these symbols time after time, making mistakes and starting once again.
139
+ Sometimes CAPTCHA reminds us of the doodles of a two year old child. For users with vision problems CAPTCHA is an insurmountable obstacle. Users hate captcha. Captcha for users means "hate". Unreadable CAPTCHA stops about 80% of site visitors. After 2 failed attempts to decipher CAPTCHA 95% of visitors reject further attempts. At the sight of CAPTCHA and after input errors, many visitors leave the resource. Thus, CAPTCHA helps to protect the resource both from bots and visitors. CAPTCHA is not a panacea from spam. Doubts concerning the Need for CAPTCHA?
 
140
 
141
+ *“Ultimately, CAPTCHAs are useless for spam because they’re designed to tell you if someone is ‘human’ or not, but not whether something is spam or not.” Matt Mullenweg*
142
 
143
+ You do not have to work in IT to know what spam is. Besides piles of unwanted email, there are spam bots, or special software programs designed to act as human website visitors that post unwelcome messages over the Internet to advertise dubious services. More often than not spam messages do not even make sense. Similar to bacteria and virus mutations developing antibiotic resistance, spam bots are becoming more resilient in penetrating Internet firewalls and security layers.
144
 
145
  *Why are they spamming me?*
146
 
147
  Spammers want to get backlinks from your site to improve their site's PageRank or redirect your visitors to malicious sites.This level of spam can damage your reputation with readers and commentators if you fail to tackle it. It is not uncommon for some WordPress websites to receive hundreds or even thousands of comments every week. However, by using a CleanTalk plugin, spam can be easily handled by your WordPress website.
148
 
149
  = CleanTalk's features =
150
+ CleanTalk is one of the fastest plugins that allows you to lower the server load. One of the important parameters for each web master is the speed of the site, so we make sure that our plugin consumes as little as possible of server resources. Cloud service provides the advantage that all the checks take place in the cloud.
151
+
152
+ CleanTalk has developed unique algorithms to assess visitor behavior. CleanTalk analyzes user behavior and parameters of completed forms. Our anti-spam module, installed on your website, sends the behavior parameters of either a visitor or spam bot. These parameters are estimated, and the CleanTalk service makes a decision – to post a message or to define it as spam and reject. On the basis of such checks, the service forms its own list of email addresses used by spam bots.
153
 
154
+ The registrations of visitors are checked in a similar manner. The service adds not only email addresses to the blacklist, but also IP addresses and domains of websites that are promoted through spam mailout. All of this happens automatically and requires no action from the administration of the website. At 2.5 million queries the service makes a mistake in 40-45 cases, i.e. CleanTalk detects spam with 99.9982% accuracy. We constantly monitor these errors and make adjustments to our algorithms, Even with this exceptional accuracy our team is aiming to improve figures over time.
155
 
156
+ All-in-one. CleanTalk immediately protects all forms – comments, registration, feedback, contacts. No need to install additional plugins for each form. You save resources and increase performance of your website.
157
 
158
+ Spam attacks log. Service CleanTalk records all filtered comments, registration and other spam attacks in the “Log of spam attacks” and stores the data in the log for up to 45 days. Using the log, you can ensure reliable protection of your website from spam and experience no false/positive filtering.
159
 
160
+ With the help of anti-spam by CleanTalk you can check existing comments and users, to find and quickly delete spam comments at once. This allows administrators of websites to automatically check and identify spam bots, comments and users, which were not detected by conventional anti-spam tools. Checking existing comments and users is made against a database of the nearly 2 million certain spam bots. Detailed statistic allows CleanTalk customers to control the whole process.
161
 
162
+ CleanTalk has an advanced option “Spam FireWall”. This option allows you to block the most active spam bots before they get access to your website. It prevents website pages loading when attempted by by spam bots, so your web server doesn’t perform unnecessary scripts on these pages. Also it prevents scanning of website pages by spam bots. Subsequently Spam FireWall significantly reduces the load on your web server. Spam FireWall can mitigate HTTP/HTTPS DDoS attacks. When an intruder makes GET requests to attack your website, Spam FireWall will block requests from bad IP addresses. Your website gives the intruder a special page with a description of DDoS rejection instead of the website pages. Spam FireWall can help to reduce of CPU usage on your server for this reason.
163
 
164
+ “CleanTalk team has been developing a cloud spam protection system for five years and has created a truly reliable anti-spam service designed for you to guarantee your safety”.
165
 
166
  = We recommend =
167
  Audience engagement plugin <a href="http://wordpress.org/plugins/feedweb/">Feedweb</a>
180
 
181
  > *** Forbidden. Sender blacklisted. ***
182
 
183
+ **Important**
184
+ To test spam protection you must post a dummy submissions as website visitor (use must logged out from WordPress console), because the plugin doesn't filter submissions from WordPress administrators.
185
+
186
+ Done! The plugin is ready to use.
187
 
188
  = How can setup plugin in WPMU version? =
189
  In WordPress multisite version you can switch the plugin to use Global Access key. In this way the plugin doesn't show any options to enter Access key in plugin settings and doesn't show Trial banner in WordPress backend. To setup global CleanTalk access key for all websites in WPMU, define constant in your wp-config.php file before defining database constants:
335
 
336
  If you or someone from your visitors have error "Forbidden. Enable JavaScript." please check JavaScript support in your browser and do JavaScript test at this page <a href="https://cleantalk.org/checkout-javascript-support">Check out JavaScript support</a>.
337
 
338
+ = Does the plugin work with Varnish? =
339
+ CleanTalk works with Varnish, it protects WordPress against spam, but the plugin generates a few cookies that uses to protect against spam bots it disables Varnish cache on pages with cookies by CleanTalk. We are going to release a new version with option that turns cookies off. In that way plugin will protect WordPress comments, registrations and most of popular contact forms, but will not protect some of rarely used contact forms.
340
+
341
  == Other notes ==
342
 
343
  = Troubleshooting Guide =
419
  = Requirements =
420
  WordPress 3.0 at least. PHP 5 with CURL or file_get_contents() function and enabled 'allow_url_fopen' setting. <a href="http://cleantalk.org/register?platform=wordpress">Sign up</a> to get an Access key.
421
 
 
 
 
 
 
 
 
 
 
 
422
  == Screenshots ==
423
  1. Anti-spam plugin settings.
424
  1. Anti-spam stopped spam bot at the CAPTCHA less registration form. The plugin provide explanation to visitor and websites about eache rejected comment/registration or contact message.
425
  1. Use anti-spam analytics tool for each website in service Dashboard to have information about spam/legitimate statistics.
426
  1. Use anti-spam log to control anti-spam plugin.
427
+ 1. CleanTalk works faster than most of other anti-spam plugins.
428
 
429
  == Changelog ==
430
+ = 5.36.1 2016-02-05 =
431
+ * Fixed bug, when users receive error after logging in
432
+
433
  = 5.36 2016-02-04 =
434
  * Improved JavaScript anti spam protection
435
  * Improvements for avoiding blocking requests from payment systems
661
  * Trimmed API key in admin panel.
662
  * Added current options to array sended to CleanTalk servers.
663
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
664
  == Upgrade Notice ==
665
+ = 5.36.1 2016-02-05 =
666
+ * Fixed bug, when users receive error after logging in
667
+
668
  = 5.36 2016-02-04 =
669
  * Improved JavaScript anti spam protection
670
  * Improvements for avoiding blocking requests from payment systems
881
 
882
  = 4.14 2015-01-19 =
883
  Removed deprecated option from comment approvement code.