Spam protection, AntiSpam, FireWall by CleanTalk

СleanTalk <> Free   Connect to feed
Max power, all-in-one, no Captcha, premium anti-spam plugin. No comment spam, no registration spam, no contact spam, protects any WordPress forms.

No CAPTCHA, no questions, no animal counting, no puzzles, no math and no spam bots. Universal AntiSpam plugin.

AntiSpam features

  1. Stops spam comments.
  2. Stops spam registrations.
  3. Stops spam contact emails.
  4. Stops spam orders.
  5. Stops spam bookings.
  6. Stops spam subscriptions.
  7. Stops spam surveys, polls.
  8. Stops spam in widgets.
  9. Stops spam in WooCommerce.
  10. Checks and removes the existing spam comments and spam users.
  11. Compatible with mobile users and devices.
  12. Compatible with General Data Protection Regulation (GDPR) (EU).
  13. Real-time email validation. Is email real or Not.
  14. Blocking disposable & temporary emails.
  15. No Spam - No Google Penalties. Give your SEO boost.
  16. Mobile friendly Anti Spam & FireWall.
  17. Stops spam in Search Form.
  18. Disable comments.
  19. Spam FireWall: Anti-Flood
  20. Spam FireWall: Anti-Crawler
  21. Hide «Website» field for comments
  22. Block messages by languages, countries, networks.
  23. Email Address Encoder

Free trial then $8 per year

CleanTalk is an anti-spam plugin which works with the premium Cloud Anti-Spam service This plugin as a service

Public reviews

CleanTalk - Cloud-Based Anti-Spam Service to Keep Your Site Bot-Free. NewsWatch Review.

Using CleanTalk on WPLift was a great test as we receive huge amounts of spam. Oliver Dale,

I know you have heard of a number of anti-spam plugins. But you must know, the cloud-based ones are the best regarding detection rate. They compare all the content in forms with their own algorithm to find out the legibility.

The key selling point of CleanTalk for me is not simply its effectiveness. It's the fact that CleanTalk works in the background. It does not make users jump through hoops in order to submit a comment or complete a form.

AntiSpam protection for comments

Native spam protection for WordPress, JetPack comments and any other comment plugins. The plugin moves spam comments to SPAM folder or you can set the option to ban spam comments silently. You can also enable the option in the plugin settings to auto-delete comments from SPAM folder.

Spam bots registrations filter

Spam filter for contact forms

Contact Form by WPForms spam filter

Plugin extends Contact Form by WPForms to provide spam protection. It filters spam submissions for each type of forms - simple contact form, marketing form, request a quote and etc.

Elementor Website Builder filter

Plugin extends spam protection for Elementor Website Builder. It filters spam submisssions and tested for contact form type.

Gravity forms spam filter

Plugin extends spam protection for Gravity forms. It filters spam submisssions for any type of forms.

Formidable Form Builder spam filter

Plugin extends spam protection for Formidable Form Builder. It filters spam submisssions for any type of forms - Contact Form, Survey & Quiz Forms.

Contact Form 7 spam filter

Plugin extends spam protection for Contact Form 7 (CF7). It can be used with any other third-party spam filters. How to protect your Contact Form 7 using CleanTalk Anti-Spam plugin

Ninja forms contact form spam filter

WooCommerce spam filter

Anti-spam by CleanTalk filters spam registrations and spam reviews for WooCommerce. The plugin is fully compatible with WooCommerce 2.1 and higher.

Newsletters antispam filter

Spam filter for theme contact forms

The plugin blocks spam emails via any theme (built-in ones included) contact forms. The plugin filters spam emails silently (without any error notices on WordPress frontend) in AJAX forms as well.

bbPress spam filter

Spam protection for everything about bbPress: logins, registrations, forums, topics and replies.

Other spam filters

  • WordPress Landing Pages.
  • WP User Frontend, UserPro.
  • Any WordPress form (checkbox 'Custom contact forms').
  • Any submission to the site (checkbox 'Check all POST data')

Compatible with WordPress cache plugins

Check existing comments for spam. Bulk spam comments removal. Spam comment Cleaner

With the help of anti-spam by CleanTalk you can inspect through existing comments to find and quickly delete spam comments at once. To use this function, go to WP Console → Comments → Find spam comments.

Check existing users for spam. Bulk spam accounts removal. Spam users cleaner

With the help of anti-spam by CleanTalk you can inspect through existing accounts to find and quickly delete spam users at once. For use this function, go to WP Console → Users → Check for spam. Also, you can export a list of spam users to the CSV.

Blocking users by country

Automatically block comments and registrations from the countries you have set a ban for. This option is useful in cases of manual spam protection and for protection enhancement. If your site is not intended for international audience and you do not expect comments/users from other countries.

Blocking comments by "stop words"

You can block comments which contain "stop words" to enhance spam protection and messages with obscene words blocking. You can add particular words or phrases.

Private black lists for anti-spam service

Automatically block comments and registrations from your private black IP/email address list. This option helps to strengthen the spam protection from a manual spam or block unwanted comments from users. You can add not only the certain IP addresses, but also a separate subnet to your personal black list.

Private black list for Spam FireWall

It allows you to add individual IP addresses and subnets to Spam FireWall. It blocks the spam attacks from IP addresses which are not included in the SFW base yet. This option can help to block HTTP/HTTPS DDoS, SQL, brute force attacks and any others that made it through the HTTP/HTTPS. You can add not only the certain IP addresses, but also a separate subnet to your personal black list.

Hide «Website» field for comments

This option hides the «Website» field from standard WordPress comments forms. After that spammers won't be able to send spam links using «Website» field in the bottom of the comments form. This option is disabled by default and can be enabled in plugin Settings in your WordPress dashboard.

Low false/positive rate

This plugin uses multiple anti-spam tests to filter spam bots having as low false/positive rate as possible. Multiple anti-spam tests help to avoid false/positive blocks of the real website visitors even if one of the tests failed.

How effective is CleanTalk?

Accurately blocking spam is not an easy thing to do, but CleanTalk has a very low proven False/Positive rate. Here is actual statistics on false positives for all customers.

  • Registrations - 0.004%
  • Comments - 0.004%
  • Contact forms - 0.006%
  • Orders (WooCommerce) - 0.016%
  • Site search - 0.001%

The statistic was calculated on August 28 2020 for 2.5 million requests.

How CleanTalk improves SEO for your website?

So, you already know that the speed of the site has a direct impact on SEO.

CleanTalk works faster than most of the other anti-spam plugins. It is common knowledge that the faster your site loads, the better your customer experience is, the better your SEO will be, and the better your site will convert. Speed is becoming increasingly important in SEO, 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.

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.

Among anti-spam plugins CleanTalk AntiSpam is one of the fastest. Despite the large plugin functionality, the developers have optimized the performance of the plugin so that AntiSpam by 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.

How CleanTalk works?

  • A visitor writes a comment or registers
  • Anti-Spam by CleanTalk plugin sends action parameters into the CleanTalk cloud
  • Service analyzes the parameters
  • If this is a visitor, the comment will be published. If it's a spam bot, then CleanTalk blocks this comment or registration.
  • Parameters are written to the spam log which can be viewed in the service Dashboard.

CleanTalk team has been developing a cloud antispam system for five years and has created a truly reliable anti-spam service designed for you to guarantee your safety.

Spam attacks log

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.

Spam FireWall

CleanTalk has an advanced option "Spam FireWall". Spam FireWall allows blocking the most active spam bots before they get access to your website. It prevents 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 website by spam bots. Therefore Spam FireWall significantly reduces the load on your web server. 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 checks all other requests on the website in the moment of submitting comments/registers etc.

Spam FireWall is fully compatible with the most popular VPN services. Also, Spam FireWall supports all search engines Google, Bing, Yahoo, Baidu, MSN, Yandex and etc.

How Spam FireWall works?

  • The visitor enters to your web site.
  • HTTP request data are being checked in the nearly 5.8 million of the identified spam bot IPs.
  • If it is an active spam bot, the bot gets a blank page, if it is a visitor then he receives a normal page. This process is completely transparent for the visitors.

All the CleanTalk Spam FireWall activity is being logged in the process of filtering.

Spam FireWall DDoS Protection

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 the description of DDoS rejection instead of the website pages. Therefore Spam FireWall helps to reduce CPU usage of your server.

Spam FireWall: Anti-Flood & Anti-Crawler

Spam FireWall: Anti-Flood and Anti-Crawler options are intended for blocking unwanted bots, content parsing, shop goods prices parsing or aggressive website scanning bots. Learn more

No spam comments, no spam registrations, no spam contact emails, no spam trackbacks. CAPTCHA-free anti-spam for WordPress

Spam is one of the most irritating things. Spam rates are increasing every year and conventional anti-spam can no longer handle all spam bots. CleanTalk prevents and automatically blocks spam. You'll be surprised how effective CleanTalk is in protecting from spam.

AntiSpam plugin info

CleanTalk is an all-in-one antispam solution for WordPress that protects login, comment, contact and WooCommerce forms at once. You don't need to install separate antispam plugins for each form. It 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.

CleanTalk is a transparent antispam tool, we provide detailed stats of all incoming comments and logins. You can always be sure that there are no errors. We have developed a mobile app for you to see antispam stats wherever you want.

We have developed the antispam for WordPress that protects you from spam bots at the maximum level 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. The anti-spam method offered by CleanTalk avoids inconvenient for communication methods (CAPTCHA, question-answer etc.), and offers to your site visitors a more comfortable one.

CleanTalk is a premium anti-spam service for WordPress, the plugin works with our own CleanTalk Cloud Service. Anti Spam by CleanTalk offers a free trial, 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 the providing anti-spam protection. Paying for a year of anti-spam service, you save a lot more and receive:

  • Up to 99.998% protection from spam bots.
  • Time and resources saving.
  • More registrations/comments/visitors.
  • Spam protection of the several websites at once in different CMS.
  • Ease in installation and using.
  • Traffic increase and loyalty to the users.
  • 24/7 technical support.
  • Clear stats.
  • Spam FireWall.
  • No captcha (reCaptcha), puzzles, etc.
  • Free mobile app to control anti-spam protection on your website.

Additional features

  • Daily and weekly detailed anti-spam reports: traffic VS spam.
  • AntiSpam apps for most popular CMS on

How to protect sites from spam bots without CAPTCHA?

The most popular anti spam method is CAPTCHA - the annoying picture with curved and sloping symbols, which are presented to the visitor to decipher and fill in. In 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. 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 spam both from bots and visitors. CAPTCHA is not a panacea from spam. Doubts concerning the Need for CAPTCHA?

"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

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.

CleanTalk's features

Anti-Spam by CleanTalk with Spam FireWall is one of the fastest plugins that allows you to lower the server load. One of the important parameters for each webmaster is the speed of the site, so we make sure that our plugin consumes as few server resources as possible. The Cloud Service provides the advantage: all data processing takes place in the Cloud.

CleanTalk team has developed unique anti spam algorithms to assess visitors behavior. CleanTalk analyzes user behavior and the parameters of the filled forms. Our anti-spam module, being installed in your website, sends the behavior parameters of either a visitor or a spam bot. When these parameters are estimated, the anti spam service makes a decision - to post a message or to define it as spam and reject it. Based on these checks, the service forms its own list of email addresses used by spam bots.

The registrations of visitors are being checked in a similar manner. The service adds to the blacklist not just email addresses, but also IP addresses and domains of websites that promote themselves through spam mailing. All of this happens automatically and requires no action from the administration of the website. In 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 the figures over time.

All-in-one. CleanTalk protects form spam all forms instantaneously - comments, registrations, feedback, contacts. No need to install additional plugins for each form. You save resources and increase performance of your website.

Spam attacks log. Anti-Spam by CleanTalk records all filtered comments, registrations 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.

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. The existing comments and users checking process is performed in a database of the nearly 2 million identified spam bots. Detailed spam stats allows CleanTalk customers to fully control it.

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 unloads you website pages when an attempt attack was made, so your web server won't run unnecessary scripts on these pages. Also it prevents any scanning of website pages by spam bots. Subsequently Spam FireWall significantly reduces your webserver load. 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 the CPU usage of your server because of this reason.

"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".

White Label Mode

To switch the plugin work in the white-label mode you should set up a few settings on your main site in Wordpress Multisite Network:

  1. Check setting "Enable White Label Mode".
  2. Fill "Hoster API Key" field with key from CleanTalk's hoster panel.
  3. Fill "Plugin name" field. It could be any name you want for the plugin.
  4. Save settings.

The plugin will do everything rest.

Auto-Update CleanTalk AntiSpam

CleanTalk Dashboard allows you to set auto-update plugin and select several websites and update the plugin at once on all sites by one click or you can setup auto-update for all websites or separate websites.

Note: there is 24 hours delay before auto-update will do. This delay allows needing to avoid any issues. All updates that made through CleanTalk Dashboard manually will do immediately.

Auto-updating system will work from CleanTalk AntiSpam version 5.88

Real-time email validation. Is email real or Not.

It is very important to be sure that the user used his real email address. Spambots very often use fake email addresses, i.e. which addresses do not exist.

CleanTalk will check email addresses for existence in real time.

Non-existing email addresses also entail several other problems for website owners.

  • You can never contact them by email,
  • the client will never receive any notifications from you (account activation letter, password recovery, email distribution, notifications, etc.),
  • if you use email marketing for your clients, then a large number of nonexistent emails in the mailing list may result in your IP address being added to various blacklists of email servers.

Improve your email list with email validation without fake emails.

Blocking disposable & temporary emails

Block fake and suspicious users with disposable & temporary emails to improve email delivery. So, it also prevents malicious activity, spam bots, and internet trolls.

Stops Spam in Search Form

Spam bots can use your search form to make a GET request with spam text. CleanTalk Anti-Spam has the option to protect your website search form from spam bots. Each time, the search generates a new page and if there are many requests, this can create additional load. So, under some conditions, spam searches can be indexed, which affects SEO,

  • Spam FireWall blocks access to all website pages for the most active spambots. It lowers your web server load and traffic just by doing this.
  • Anti-Spam protection for website search forms repels spambots.
  • If your search form gets data too often the CleanTalk Anti-Spam plugin will add a pause and increase it with each new attempt to send data. It saves your web server processor time.
  • Spam protection allows you to not forbid indexation for the crawler bots if you really need it but simultaneously you will get protection from spambots.

You will always know what users were looking for on your site.

Disable comments

This option disables comments on your site. You can choose one or several options:

  • Disable comments for posts
  • Disable comments for pages
  • Disable comments for media

When using Disables comments, existing comments will not be deleted and will remain on the pages.

Email Address Encoder

CleanTalk Anti-Spam offers a feature called "Encode contact data" that is designed to encode all email addresses on the website pages. Encoding the email addresses increases the level of protection of contact data from being abused, parsed, getting spammed and used in spam mailing lists by bots and online criminals. To reveal the encoded email address simply click on it and it will be decoded instantly.



WordPress 3.0 at least. PHP 5 with CURL or file_get_contents() function and enabled 'allow_url_fopen' setting. The plugin is fully compatible with PHP 7.

Max power, all-in-one, premium anti-spam WordPress plugin. No comments & registrations spam, no contact spam, protects any forms. Just install and forget spam.

Why are they spamming me?

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.

Is the anti-spam protection safe for mobile visitors?

Yes, it is. The plugin doesn't block mobile visitors as well as desktop website visitors. It uses several independent anti-spam tests to decrease the number of false outcomes and to have as low false-positive rate as possible. Multiple anti-spam tests help to avoid false/positive blocks for real website visitors even if one of the tests failed.

What does the plugin do with spam comments?

Spam comments are being moved to SPAM folder by default or you can set the option to ban spam comments silently.

How can I test the anti-spam protection?

Please use the email for comments, contacts or signups to see how the anti-spam protection works. Also, you can see the logs for the last 7 days in the Dashboard or look at the folder "Spam" for banned comments.

Is the plugin effective against spam bots?

The plugin Anti-Spam by CleanTalk stops up to 99.998% of spam comments, spam signups (registrations), spam contact emails, spam subscriptions, spam bookings or spam orders.

Does the plugin protect from brute force, DoS attacks and spam attacks?

Yes, it does. Please turn the option 'Spam FireWall' on in the plugin settings to protect your website from DoS/DDoS, XML-RPC attacks.

How does the plugin stop spam?

Please, note - administrator's actions are NOT being checked.

The plugin uses several simple tests to stop spammers:

  1. JavaScript anti-spam test. 99% of spam bots don't have full JavaScript functions support. So, the plugin has the code which can be run by normal visitor and can't be run by the spam bot.
  2. Email, IP, domain spam activity list entries check. The plugin uses spam activity database online at, consisting of more than 20 billion spam activity records of IPs, Emails, Domains and ASN. If the sender's IP or Email is in the database, the sender gets some spam scores. To reduce false/positive rate the plugin not only uses the blacklist test to ban spammers, the sender will be banned when and only when multiple spam tests have been failed.
  3. Comment submit time. Spam bots usually submit the info immediately after the page has been loaded, this happens because spam bots don't actually fill the web form, they just send $_POST data to the blog. The normal visitor sends the data after several seconds or minutes.

Will the anti-spam plugin protect my theme?

Yes, it will. The Anti-spam by CleanTalk is compatible with any WordPress theme.

What about pingback, trackback spam?

The plugin passes pingbacks without any checks by default. All trackbacks will be blocked if the sender had spam activity.

Can I use CleanTalk with Akismet?

Sure, you can use CleanTalk with Akismet. In this case you will probably have higher false/positive rate (when legitimate comments/signups are being denied), but you will have stronger anti-spam protection on your website.

Is CleanTalk better than Akismet?

Please look at this features comparison here

Can I use CleanTalk to remove pending spam comments?

Yes, you can. The plugin has the option to test all pending comments via database of spam active IP/Email, found spam comments will be moved to Trash folder.

How does the plugin find spam in pending comments or registered accounts?

The plugin checks all non-spam comments in the blacklist database and shows you those senders who have spam activity on other websites. There are some differences between blacklist database and API to protect you from spam bot registrations/comments online. Blacklists show all history of spam activity, but our API (which is used in spam tests) relies on other parameters too: last day of activity, number of spam attacks during the last days etc. These mechanisms help us to reduce the number of false outcomes. So, there is nothing strange, if some emails/IPs are not found by bulk comments/accounts test.

To check comments please go here:

WordPress console → Comments → Find spam comments

To check users please go here:

WordPress console → Users → Find spam users

Should I use other anti-spam tools (Captcha, reCaptcha and etc.)?

CleanTalk stops up to 99.998% of spam bots, so you can disable other anti-spam plugins (especially CAPTCHA-type anti-spam plugins). In some cases several anti-spam plugins could conflict with each other, so it would be better to use just one plugin.

Is the plugin compatible with WordPress MultiUser (WPMU or WordPress network)?

Yes, the plugin is compatible with WordPress MultiUser. Each blog in multisite environment has individual anti-spam options for the protection from spam bots.

After the installation I noticed that the number of spam attacks has been increased in the stats

There are a few reasons for this:

  • With the indexing of your web-site by the search systems, appearance of external links and better search results position, your web-site attracts more and more spambots.
  • Non-transparent protection systems like CAPTCHA or question/answer, that don't have spam attacks stats, don't let you see the whole picture, or the picture is incomplete.
  • Counting methods for spam attacks and spam bots are different for different systems, thus the diversity appears. We seek to provide detailed stats.

Why my dummy "spam" comment passed to the WordPress?

The plugin has several options to detect spam bots and humans. If you just post spammy text like this:

"I want to sell something", "Buy something here.." and etc

the comments will be passed, because the plugin detects sender as a human. So, use special email to test the anti-spam functionality or wait a few days to see how the plugin works.

Is it free or paid?

The plugin is free and distributed under the GPLv2 license.

CleanTalk anti-spam plugin works with a cloud base anti-spam service and this plugin is a Software as a service (SaaS). CleanTalk it’s a free plugin that works with premium Cloud Anti-Spam service.

The fact that the plugin works with a premium type service is mentioned in the plugin annotation and in its WordPress catalog description.

We are ready to help you with any issue regarding CleanTalk. There are hundreds of environment compositions and we do our best to cover as many as possible.

Can I use CleanTalk with cache plugins?

Anti-spam by CleanTalk doesn't use static HTML code in its templates, so all anti-spam functions work correctly with any WordPress cache plugins.

Does the plugin protect from spam bots if I use forms with third-party services?

Yes, it does. Plugin protects web-forms on your websites which send data to third-party servers (like MailChimp). To enable this protection set the option 'Protect external forms' in the plugin settings.

Does CleanTalk compatible with Cloudflare?

CleanTalk is fully compatible with CloudFlare. Service doesn't filter CloudFlares IP's (AS13335) through blacklists database, so in this case plugin/service filters spam bots using other anti-spam tests.

Is CleanTalk compatible with a content delivery network (CDN)?

Yes, it is. CleanTalk works with any CDN system, i.e. CloudFlare, MaxCDN, Akamai.

Can I use CleanTalk functionality in my plugins?

Yes, you can. Just use following snippet:

	include_once( ABSPATH . '/wp-content/plugins/cleantalk-spam-protect/cleantalk.php' );
//for registration test:
$res=ct_test_registration("nickname", "", "");
//or for some other messages (contact forms, comments etc.)
$res=ct_test_message("nickname", "", "", "test message");

$res now contents array with two parameters:

  • $res['allow'] - is request allowed (1) or not (0)
  • $res['comment'] - comment for our server's decision.

I see two loads of script cleantalk_nocache.js. Why do you use it twice?

This script is used for AJAX JavaScript checking. Different themes use different mechanisms of loading, so we use two methods for loading our script. If you absolutely know what you are doing, you can switch one of the methods off by defining constants in your wp-config.php file:

define('CLEANTALK_AJAX_USE_BUFFER', false); //false - don't use output buffering to include AJAX script, true - use it


define('CLEANTALK_AJAX_USE_FOOTER_HEADER', false); //false - don't use wp_footer() and wp_header() for including AJAX script, true - use it

Can I add exclusions for some pages of my site?

Yes, you can. There is a special setting in plugin settings. You could use this guide to learn more:

Can I not send my personal data to CleanTalk servers?

Yes, you can exclude your data. There is a special setting in plugin settings. You could use this guide to learn more:

How to test Spam FireWall?

Use special IP in URL to test Spam FireWall. For example,

Attention! The incognito mode should be enabled in your browser when you do a test. To enable incognito mode press Ctrl+Shift+N for Chrome, Opera и Safari browsers; press Ctrl+Shift+P for Firefox, Internet Explorer and Microsoft Edge. A full guide to enable Incognito mode is here:

How can I enter access key in WPMU version?

To set up global CleanTalk access key for all websites in WPMU, define constant in your wp-config.php file before defining database constants:

define('CLEANTALK_ACCESS_KEY', 'place your key here');

Now, all subsites will have this access key.

Why is CleanTalk faster and more reliable than stand-alone solutions?

All anti-spam checks are held in the cloud and don't overload the web server. The cloud solutions have a huge advantage since the parameters are being compared with information from more than 100,000 websites.

I see a lot of blocked messages with the reason "Forbidden. Please enable JavaScript. Spam sender name." in my logs

A lot of spam bots can't perform JavaScript code, so it is one of the important checks and most of the spam bots will be blocked with the reason "Forbidden. Please enable JavaScript. Spam sender name." All browsers can perform JS code, so real visitors won't be blocked.

If you or some of your visitors have the error "Forbidden. Enable JavaScript." please check JavaScript support in your browser and do this JavaScript test at this page:

If you think that there is something wrong in the messages blocking, let us know about it. Please submit a support request here:

Does the plugin work with Varnish?

CleanTalk works with Varnish, it protects WordPress against spam, but by default the plugin generates a few cookies for the protection from spam bots and it also disables Varnish cache on pages where CleanTalk's cookies have been stored. To get rid of the issue with cache turn off the option 'Set cookies' in the plugin settings.

WordPress console -> Settings -> CleanTalk -> Advanced settings

Now the plugin will protect WordPress comments, registrations and most of popular contact forms, but will not protect some of rarely used contact forms.

Does the anti-spam plugin work with Accelerated Mobile Pages (AMP)?

Yes, it does. But you have to turn off the SpamFireWall and the option 'Use AJAX for JavaScript check' in Advanced settigns of the plugin to be fully compatible with Accelerated Mobile Pages.

How to close renewal or trial notice in the WordPress backend?

To close the notice please save the plugin settings again or it will be closed automatically within 60 minutes after the renewal.

I'm using PHP 4.2 version and i'm getting errors related with JSON. Why does it happens?

СleanTalk is no longer supports PHP lower than 5.2 version because the support code have incompatibility with PHP 7 version. Please, upgrade your PHP. If you couldn't perform that, let us know about it via support ticket here:

Should I change anything in the plugin's settings or in my CleanTalk Dashboard when I switch my website from HTTP to HTTPS or vice versa?

No. You don't need to change anything in the plugin's settings or in your CleanTalk Dashboard. The plugin will work regardless of the protocol.

How to use Anti-Spam Log?

The following possibilities are available for you in the Anti-Spam Log:

  • Time period for all spam records you want to see.

  • Filter spam records by their status: Any status, Denied, Approved.

  • Filter spam records by your websites.

  • Filter spam records by country they came from.

  • Filter spam records by IP address, e-mail address or username.

  • Available options for a specific record:

    • Details - see item 4 below.
    • Spam/Not Spam - press this string if our system made wrong decision and blocked or approved a registration, a comment ot a contact form submission. More about it here:
    • Delete - delete a record permanently.
    • Personal blacklists - go to your website Black&White Lists page.
    • Record details: block reason, body of the message, additional caught data.

Spam FireWall and AntiSpam - Networks Blocking

Anti-Spam - will blocks users from selected IP or network from using contacts/messages/registrations/comments forms. Spam FireWall - will blocks users from selected IP or network from entering the website.

Please, read more here

Spam Comment Management

By default, all spam comments are placed in the spam folder, now you can change the way the plugin deals with spam comments:

  1. Move to the Spam folder. All spam comments will be placed to the folder "Spam" in the WordPress Comments section except comments with Stop-Words. Stop-Word comments will be always stored in the "Pending" folder.

You can prevent the proliferation of Spam folder. It can be cleaned automatically using the option "Keep spam comments for 15 days." Enable this option in the settings of the plugin: WordPress Admin Page → Settings → Antispam by CleanTalk → Advanced settings → enable "Keep spam comments for 15 days" → Save Changes.

  1. Move to Trash. All spam comments will be placed to the folder "Trash" in the WordPress Comments section except comments with Stop-Words. Stop-Word comments will be always stored in the "Pending" folder.

  2. Ban comments without moving to WordPress backend. All spam comments will be deleted permanently without going to the WordPress backend except comments with Stop-Words. Stop-Word comments will be always stored in the "Pending" folder.

What comments were blocked and banned can be seen in the Anti-Spam Log here:

To manage the actions with spam comments, go to the Control Panel, select the website you want to change the actions for and go to "Settings" under the name of the website.

Please, read more here:

How do I report a missed spam bot or incorrect filter?

If you think the service has missed a spam bot or improperly filtered visitor to the website, you may notify us via the Anti-spam control panel. To do this, Log in to Control panel Click the line "Log" under the name of your website. When you mark a record as "SPAM", its e-mail and IP-address will be added to your personal blacklist for your website. When you mark a record as "Not SPAM", its e-mail and IP-address will be added to your personal white list for your website.

Please, read more here

Is the plugin fast?

We develop plugin to do it as optimized as possible, CleanTalk doesn't downgrade response time in backend or frontend. The plugin proccess only POST requests to WordPress core, it tackes less than 1 second to return results.

Is the plugin EU GDPR compatible?

Yes, it is. Please read this article,

Check external forms

If your website has forms that send data to external sources, you can enable option to "Protect external forms". In this case, if plugin determinates that the current message is spam, your form action will be temporary replaced to your current hostname to prevent sending false data to an external source.

5.182.2 Aug 08 2022

Server variables sanitizing fixed, js key getting fixed, internal forms catching fixed.

  • Fix: removed & in getAndSanitize()
  • Fix: ct_add_hidden_fields() - the data in the locale storage is added in json format
  • Fix: Excluded wp-comments-post.php form from internal scripts
  • Fix. Server variables. ServerVariables::sanitizeDefault() method is abstract now.
  • Fix. Server variables. Common\Variables* classes are abstract now.
  • Fix. Server variables. Default sanitizing method implementation added to ApbctWP\Variables* classes.
  • Fix. Server variables. Client code fixed.
  • Fix: FluentForm integration fixed
  • Fix. Server variables. Url decoding removed.

5.182.1 Aug 04 2022

Server variables getting fixed.

  • New. Server variables. Sanitizing logic added.
  • Upd. Server variables. Getting variables logic updated.
  • Upd. Server variables. Default sanitize added for ApbctWP\Variables* classes.
  • Upd. Server variables. Client code updated - using ApbctWP\Variables* classes.
  • Upd. Server variables. Sanitizing array nesting increased.
  • Fix. External forms. Form draw fixed.
  • Fix. Common. Set check JS value fixed.
  • Fix. Common. Custom ajax forms catching logic fixed.
  • Fix: added styles to hide the honeypot field in the plugin Ultimate Member

5.182 Jul 28 2022

Email encoder improved, internal and external forms protection fixed, code quality improved and some minor issues fixed.

  • New. Email encoder. Encoding exclusions implemented.
  • New. Alternative cookies AJAX calls reduce. Use browser localStorage to keep check_js value instead of CTSetCookie()
  • Upd. External forms. integration added.
  • Upd. Internal forms. Internal forms protection logic updated.
  • Fix. GetFieldsAny.php Take visible fields from POST if apbct_visible_fields cookie is not detected.
  • Fix. Integrations. WPUserMeta. Added case of user-meta-pro
  • Fix. Email encoder. Divi contact forms exclusions added.
  • Fix. public.js. Handle exception if backend returns invalid JSON.
  • Fix: External Forms. Match action with action, method with method.
  • Fix: Restore JS for internal form protection.
  • Fix: JS localize. Add blog_home to ctPublic object.
  • Fix: Honeypot. Delete redundant style.
  • Code: Internal forms. Fix action detection.
  • Code: Internal forms. Added exclusion for native WordPress action scripts.
  • Fix: SpamFirewall. Ignore warning from gzdecode() in ApbctWP/Firewall/SFW::updateWriteToDb().
  • Fix: Internal forms protection. Now is controlled by settings.
  • Fix: External forms protection. Now is controlled by settings.
  • Fix. Common. Prevent JS async loaded by CF.
  • Fix: Protect external. Sort callback params.
  • Fix. Code. Code quality improved.
  • Fix. Variables. Filter variables contains arrays fixed.
  • Fix: Honeypot field. Make filed invisible.
  • Fix: GiveWP integration.
  • Fix: ApbctWP/Variables/Cookie::setNativeCookie(). Adjust the detection of the default 'secure' flag logic.
  • Fix. Variables. Getting empty variables fixed.
  • Fix. External/Internal. General contact form option dependence fixed.

5.181 Jul 14 2022

One integration added, SFW testing page updated, code quality improved and some minor issues fixed.

  • New. Integrations. WP User Meta integration.
  • Upd. SFW. Testing page updated.
  • Fix. WP discuzz integration. Check for spam if comment is edited.
  • Fix. WP discuzz integration. Remove unnecessary data when check on comment edition.
  • Fix. Admin banner. Security attention mark fixed.
  • Fix. Code. Sanitizing incoming data.
  • Fix. CSS. Fix stylesheet source name and minifed name.
  • Fix. apcbt-public-bundle. New detection method for mailerlite classes to prevent default submit clicks.
  • Fix. HTTP lib. Multi request error handling fixed.
  • Fix: setting page JS key validating.
  • Fix: Replace array_* function implemented on State properties.
  • Mod: ApbctWP/State to use the direct equation on properties.
  • Fix. Integrations. WPUserMeta. Added case of user-meta-pro

5.180.2 Jul 04 2022

SpamFireWall working fixed.

  • Fix. Updater. Updater actions moved from the hook "upgrader_process_complete"
  • Fix. SFW. JS errors on the block pages fixed.
  • Fix. SFW. Skiping block hyperlink fixed.
  • Fix. SFW. Additional redundant blocking by AC fixed.

5.180.1 Jul 01 2022

  • Fix. Common. Undefined class fixed.

5.180 Jun 30 2022

Getting api key from the CleanTalk Dashboard implemented, SFW updating improved, code quality improved and some minor issues fixed.

  • New. API key length extended to 30 symbols.
  • New. Remote call. RC post_api_key implemented.
  • New: Option 'cleantalk_debug' now outputs in 'debug' remote call.
  • Upd. SFW. Direct update during fallback.
  • Fix. Honeypot fields for search. Search forms with GET method now handles correct.
  • Fix. Ajax. Prevent JS errors on ajax general contact forms.
  • Fix. apbct_need_to_process_unknown_post_request() Add Divi themes exclusion to proceed them to contact_form_validate().
  • Fix. General contact form catching fixed.
  • Fix. cleantalk-pluggable.php. Skip service requests of enable-jquery-migrate-helper
  • Added notice_review banner
  • Fix. cleantalk_external.js. Exclude mewtwo flight forms.
  • Fix. Code. Compressing JS gulp task updated.
  • Fix. Request.php. Extend CURL timeout and low-speed detection limit.
  • Fix. Cleantalk.php. Exclude timestamp refreshing via template_rediret hook for alternative cookies mode.
  • Fix. External forms JS error fixed.
  • Fix. cleantalk-public-integrations.php-> apbct_form_search__add_fields(). Force to run pregmatch search if DOM content is broken.
  • Fix. Honeypot. Styles moved to the separated file.

5.179.1 Jun 21 2022

General contact form catching fixed

  • Revert "Integration before common aa (#129)"

5.179 Jun 16 2022

Email Encoder functionality improved, SFW updating process improved and some minor issues fixed.

  • New. EmailEncoder.php->modifyContent. Admins and logged in exclusions.
  • Fix. Email encoder. Prevent encoding data for logged in users.
  • Fix. Queue. Return statement from executeStage() method added.
  • Fix. SFW. Updating process fixed.
  • Fix. SFW. SFW update worker fixed.
  • Mod: Using the shutdown hook to call a function ct_contact_form_validate().
  • Fix. apbct_sfw_update__worker. Clear errors if stage is finished.
  • Fix. HTTP lib. Useragent for WP HTTP API requests fixed.
  • Fix. cleantalk_external. Exclusion for booking forms.
  • Fix. cleantalk_external. Exclusion for flodesk forms.
  • Mod: Replace apbct_update_actions() to upgrader_process_complete hook
  • Fix. cleantalk_external.js->ct_protect_external(). Exclusion for booking forms.
  • Fix. RemoteCalls. No cache parameter added.
  • Fix. apbct_remove_upd_folder(). Force unknown file deletion ('.last.jpegoptim')
  • Fix. apbct_remove_upd_folder(). Add chek if a strange file is a file and exists.
  • Fix. GetFieldsAny.php. Decode email if it is urlencoded.
  • Fix. cleantalk-public-validate.php. Add JS check to public forms.
  • Mod: Refactoring User Scanner
  • Fixed apbct_cookies_test cookie
  • Upd. JS. Cookies has_scrolling and mouse_moved optimized.
  • Upd. Email encoder. Links mailto: processed.

5.178 Jun 02 2022

Comment moderation option added, cookies prefix added, RemoteCalls stability improved and some minor issues fixed.

  • New. Options. Comment moderation option added on discussion page.
  • New. Settings. Encode contact data long description added.
  • New. Cookies. Getting prefix function implemented.
  • New. Cookies. Get and set cookies with prefix.
  • New. Cookies. Using cookie prefix on client code.
  • Mod: Created RemoteCallsCounter::class to limit remote calls
  • Mod: Created RemoteCallsLogger::class for logging last remote calls
  • Upd. Comments. Comment moderation logic modified.
  • Fix: extended form
  • Fix. SFW. Statistics fixed.
  • Fix: external
  • Fix: external
  • Fix: fixed test for wpforms
  • Fix. Pluggable. Getting REST url fixed.
  • Fix: Formidable Pro Multistep Fixed
  • Fix: Formidable Form Pro ajax response - fixed
  • Fix. Settings. Alternative cookies option renamed.
  • Fix. Common. Cookies test function fixed.
  • Fix. External forms. JS logic fixed.
  • Fix. External forms. Force ajax check action handler added.
  • Fix. cleantalk.php. VisualFormBuilder hook change.
  • Delete RC update plugin
  • Fix. cleantalk.php. Visual Form Builder integration: add legacy support.
  • Fix. Helper. Fatal error (Call to private method) fixed.
  • Fix. WooCommerce. WC checking order hook changed.
  • Fix. Settings. Validate URL exclusions.
  • Fix. cleantalk-public-integrations.php->apbct_form__gravityForms__testSpam. Gravity forms multiple email fields fix.
  • Fix. SFW updating. Writing update errors fixed.
  • Fix. cleantalk.php-> apbct_sfw_update__worker() Convert errors array to a string if set in a stage.

5.177.2 May 27 2022

  • Fix. EmailEncoder.php. Fix accident encoding.

5.177.1 May 19 2022

  • Fix. Pluggable. Getting REST url fixed.

5.177 May 12 2022

WP 6.0 compatibility, Email Encoder added, Common HTTP API implemented, Honeypot fields improved and some minor issues fixed.

  • New. Email Encode functionality added.
  • New. cleantalk-common.php. Honeypot field value and source now sends in sender_info.
  • New. ct_preprocess_comment(). Honeypot field source now sends in sender_info.
  • New. HTTP API. Common CleanTalk http library added.
  • New. Public integrations. Honeypot field for search form.
  • New. WP 6.0 compatibility.
  • Fix: EZ Form Calculator - clearing the message
  • Fix. Common. Checking all post data fixed.
  • Imp. Settings. "Hide website" field moved to "different" section.
  • Imp. Settings. "Hide website" type changed to checkbox from radio.
  • Imp. Settings. "Honeypot field" state changed to enabled by defaults.
  • Mod: Integration for Advanced Classifieds & Directory Pro - registration form
  • Fix. Custom ajax. Custom ajax handler usage removed completely.
  • Fix: Excluded the addition of visible fields in filter of The Events Calendar
  • Fix. cleantalk-common.php. Added search honeypot field signature to potential honeypot fields post values
  • Fix: MultiStep Checkout for WooCommerce - skipped step validation
  • Ref. cleantalk-public-integrations.php. Empty string converts to false - comparison removed.
  • fix: apbct_get_rest_url - returns the result of a get_rest_url() function if it exists
  • Mod: modified getting pixel_url.
  • Fix. apbct_init. Reduce multiple direct calls of apbct_get_pixel_url__ajax.
  • Fix: Cleantalk\Common\HTTP\Request. Timeout error while async request.
  • Fix. HTTP API. Process exception passed from WordPress \Requests class.
  • Fix. Cleantalk. Antispam class fixed.
  • Fix. API. Common API class fixed.
  • Fix. Comments checker. Pagination fixed.
  • Fix. Common. CleanTalk service request excluded.

5.176 Apr 28 2022

New integration added, honeypot fields added and some minor issues fixed.

  • New. Integration. NextendSocialLogin integration implemented.
  • New: Exclusions validation in apbct_settings__sanitize__exclusions().
  • New. WPDiscuz integration. Now sends sender_url. Integrations.php now ready to process sender_url.
  • New. Common. Headless parameter added.
  • Upd. Integration. A honeypot field was added for the CF7 integration.
  • Upd. Integration. A honeypot field was added for the WPForms integration.
  • Fix. Common. Prevent double json encoding for source_url.
  • Fix. SFW. SFW results priority depends by network mask.
  • Fix: Excluded visible fields for AvadaFormBuilder
  • Fix: honeypot fixed
  • Fix. Forms. Prevent generating a honeypot field if such option is disabled.
  • Fix: Fixed external forms
  • Exclusion fields descritpions update.
  • Fields exclusion input changed to textarea to keep visual identity with URL exclusion.
  • Fix. After review. Removed condition on exclusions array slicing. Functions order changed.
  • Fix. WPDiscuz integration. Now tries to get email, nick and message directly from POST. If unsuccessful then runs get_fields_any.
  • Fix: Optimize and fixed user scanner
  • Fix. JS. Using ajax for getting JS key is disabled by default.
  • Fix. Common. Custom ajax logic removed.
  • Fix. Settings. Now templated settings applies to sub-sites on the first save.
  • Fix: FixTeam integration - removed visible fields
  • Fix. apbct_settings__sanitize__exclusions(). Checking input params types.
  • Fix. Settings. Url/fields exclusion validating fixed.
  • Fix: Fusion Avada Form Builder Fixed
  • Fix: External form fix for infusionsoft

5.175 Apr 14 2022

Integration added, typos fixed, user scanner improved and minor issues fixed.

  • New. Integration. Events Manager plugin integration implemented.
  • New. Code. New validate classes.
  • New. Code. New validate sub-classes in ApbctWP.
  • Upd. Readme. One more AntiSpam feature added.
  • Mod: PlansoFormBuilder integration
  • Fix. External forms. Capturing buffer fixed.
  • Fix. Integration. Simple Ajax Chat sending fixed.
  • Fix. Exclusions. Special flag to prevent exclusions implemented.
  • Fix. Getting key errors handle.
  • Fix. Getting key error output fixed.
  • Fix: Added VFB_Pro integration
  • Fix. Settings api. Long description for text fields implemented.
  • Fix. Settings. Long description for hoster api key removed.
  • Fix. Settings. Long descriptions UTM marks fixed.
  • Fix. Comments checker. Dates ranges fixed.
  • Fix. Code. Core based JqueryUI use on users/comments checking page.
  • Fix. Code. Moderate API answer fixed.
  • Fix. Code. Including assets fixed.
  • Fix. Text. Typos on company brand terms fixed.
  • Fix: Glitched redirect after plugin activation.
  • Fix. Settings. Hoster Access Key long description mark removed.
  • Fix: Filter visible fields for AvadaFormBuilder
  • Fix. Code. Using wrappers for calling global variables.
  • Fix. Code. Cookie secure attribute fixed.
  • Fix. Code. Refactoring the user scanning engine.
  • Fix. Cookie. Getting cookies fixed.
  • Upd. Settings. SFW long description added.
  • Upd. Localization. SFW, AC, AF titles is not localized now.
  • Fix. Common. Collecting visited urls fixed.
  • Fix. Integration. JP contact form checking JS fixed.
  • Fix. Integration. CF7 form checking JS fixed.

5.174.1 Mar 25 2022

  • Fix: Comments/Users scanner fixed.

5.174 Mar 25 2022

Minor issues fixed.

  • Fix. URLs storing fixed.
  • Fix. Visible fields. Do not add hidden field for logged-in users if the protection was deactivated.
  • Fix. Integration. CF7 native spam protection fixed.
  • Fix. Integration. Formidable integration fixed.
  • Fix. Integration. Skipping elementor pro action fixed.
  • Fix. Scanners. Users and comments scanners fixed.

5.173 Mar 03 2022

Honeypot field implemented for improving antispam protection, new integrations added, performance improved and minor issues fixed.

  • New. Honeypot field for the registration form.
  • New. Integration. Added Visual Form Builder Integration without Ajax.
  • New. Integration. GiveWP integration implemented.
  • Upd. Code. Helper::ipGet() improved.
  • Upd. Settings. Honeypot setting modified.
  • Fix: Formidable Integration Refactoring.
  • Fix. Integration. Fusion Avada Form Builder output fixed.
  • Fix. Settings. Honeypot setting descriptions fixed.
  • Fix: Skipped WP Booking System Premius service requests
  • Fix. Exclusion. Checkout For WC - service requests skip.
  • Fix. Comments checker. Found comments displaying optimized.
  • Fix: visible fields was excluded form custom form.

5.172 Feb 17 2022

Updating system modified, settings long descriptions added and minor issues fixed.

  • Fix: Fixed Fusion Builder Avada Form integration
  • Fix: Fixed CF7 visible fields
  • New. Updating system modified.
  • Fix: Fixed apbct_store__urls()
  • Fix. Updating system. Source url template fixed.
  • Fix. Updating system. Redundant errors handling removed.
  • New. Integration. WS-Forms integration implemented.
  • Fix. Settings. Long description mark fixed.
  • Upd. Settings. Set cookies setting long description added.
  • Upd. Settings. Hide website field setting long description added.
  • Upd. Settings. Anti-Crawler setting long description added.
  • Fix. Settings. Long description mark for checkboxes fixed.
  • Upd. Settings. Anti-Flood setting long description added.
  • Upd. Settings. CleanTalk Pixel setting long description added.
  • Mod: Replaced the is_super_admin() function with its own apbct_is_super_admin(
  • Fix. Settings. Settings hints fixed.
  • Upd. Ajax. Nonce lifetime constant added.
  • Fix. Integration. Elementor pro forms integration fixed #2.
  • Fix: Formidable Forms - fixed spam protection without JS
  • Fix. Settings. Hints links contain UTM marks.

5.171.2 Feb 09 2022

Minor issue fixed.

  • Fix. Comments/Users checker. Date ranges validation fixed.

5.171.1 Feb 09 2022

XML-RPC requests excluded and minor issues fixed.

  • Fix: Excluded standard WordPress search form from apbct-public.min.js
  • Fix. Common. ct_contact_form_validate moved to the init hook.
  • Fix. Exclusions. XML-RPC request removed from the filtering.
  • Fix. Comments/users checker. Values for dates range validating.
  • Fix. Comments/users checker. Values of dates range for resuming scanner validating.

5.171 Feb 03 2022

Visible fields processing modified, many excepted requests are skipped, SFW compatibility with a cache fixed and minor issues fixed.

  • New. Exclusions. Excluded some service requests from checking but log them with exception flag.
  • Upd. Visible fields. Storing visible fields into an input.
  • Upd. Visible fields. Visible fields processing modified.
  • Upd. Visible fields. Replacing redundant service field.
  • Fix: SFW. Caching block page prevented.
  • Fix: Skip. Entry Views plugin service requests.
  • Fix: Antispam. Ajax checking moved to the plugins_loaded hook.
  • Fix: Skip. APBCT plugin service requests.
  • Fix: Skip. Vault Press (JetPack) plugin service requests.
  • Fix: Skip. GridBuilder plugin service requests.
  • Fix: Skip. Woo Gift Wrapper plugin service requests.
  • Fix: Skip. iThemes Security plugin service requests.
  • Fix: Settings. Using new API key when sending local settings to the cloud.
  • Fix. Integration. Registration form of eMember plugin.
  • Fix. Exception action. Xmlrpc requests skipped.
  • Fix. Integration. Elementor pro forms integration fixed.
  • Fix: Excluded from the test the standard check for Formidable Form Plugin in some situations
  • Fix: Skip. Microsoft Azure Storage plugin service requests.
  • Fix: Skip. AdRotate plugin service requests.
  • Fix: Skip. Super admin requests.
  • Fix: Fixed the block message for HappyForms
  • Fix: Excluded the form of WP Time Slots Booking Form from apbct_ready()

5.170 Jan 13 2022

One integration added, CleanTalk pixel functionality fixed and minor issues fixed.

  • Mod: Added Ova Login Integration. Registrations under protection
  • Fix. Common. is_trackback() notice fixed.
  • Fix: Removed the exeption for Quick Contact Form from ct_contact_form_validate()
  • Fix: Moved the function apbct_settings__get_ajax_type() to cleantalk-pluggable.php to fix the plugin activation error via the CLI
  • Fix: Fixed errors in apbct-public.js
  • Fix: Cleared notice_incompatibility if SFW disabled
  • Fix. AC. Antibot cookie fixed.
  • Fix. Pixel. Auto mode fixed.
  • Fix. JS. Checking JS via ajax fixed.
  • Fix. Pixel. Getting pixel url from backend fixed.

Early changelogs look in changelog.txt


Spam Antispam Anti Spam Comments Firewall

More information