=== Anti-Spam by CleanTalk. Spam protection ===
Contributors: glomberg, alexandergull, sergefcleantalk, antonv1
Tags: antispam, honeypot, contact form spam, captcha, login
Requires at least: 4.7
Tested up to: 7.0
Requires PHP: 7.2
Stable tag: 6.81
License: GPLv2

Top-rated antispam plugin. For contact forms, orders, registration, login. No CAPTCHA, no puzzle, no bot anti-spam. Global spam detection network.

== Description ==

Top-rated ant-spam protection for WordPress. **No CAPTCHAs, no puzzles, and no visitor friction** — just automatic spam blocking for forms, comments, registrations, subscriptions, and fake orders. Powered by a **global spam detection network** that helps stop spam before it reaches your website. Easy to install and ready to protect your site in **less than 30 seconds**.

= Superpowers =
1. Stops spam comments.
2. Stops spam registrations and logins.
3. Stops spam contact emails.
4. Stops fake orders eCommerce sites and online stores.
5. Antispam for bookings.
6. Antispam subscriptions.
7. Stops spam surveys, polls.
9. Stops spam in WooCommerce.
17. Antispam for Search Form.
10. Real-time email validation. Check if an email is real or fake.
11. Checks and removes the existing spam comments and spam users.
14. Blocking  disposable & temporary emails.
22. Block messages by languages, countries, networks and stop words.

= Public reviews =
> It’s more than just a tool to combat spam; it’s an integral component that enhances the overall quality and performance of your website.
> <a href="https://www.techbusinessnews.com.au/embracing-a-spam-free-digital-experience-with-cleantalk-anti-spam-plugin/" target="_blank">techbusinessnews.com.au</a>

> Improve Your Security WordPress Spam Protection With CleanTalk Anti-Spam
> <a href="https://thehackernews.com/2023/07/improve-your-security-wordpress-spam.html" target="_blank">The Hacker News</a>.

> CleanTalk - Cloud-Based Anti-Spam Service to Keep Your Site Bot-Free.
> <a href="https://newswatchtv.com/2018/07/18/cleantalk-newswatch-review/" target="_blank">NewsWatch Review</a>.

> Compare reCAPTCHA & Akismet VS CleanTalk
> [CleanTalk vs Google reRECAPTCHA](https://cleantalk.org/recaptcha-alternative)
> [CleanTalk vs Akismet](https://cleantalk.org/help/cleantalk-vs-akismet)

>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.
>*<a href="https://www.techwibe.com/cleantalk-wordpress-plugin-review/" target="_blank">www.techwibe.com</a>*

> 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.
> <a href="https://www.kevinmuldoon.com/cleantalk-anti-spam-service/">www.kevinmuldoon.com</a>

= Free trial then $12 per year =
CleanTalk is an anti-spam plugin which works with the premium Cloud Anti-Spam service cleantalk.org. This plugin as a service <a href="https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/#6-software-as-a-service-is-permitted">https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/#6-software-as-a-service-is-permitted</a>

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

= Contact Form 7 Antispam =
Plugin extends spam protection for Contact Form 7 (CF7). It can be used with any other third-party spam filters.
<a href="https://blog.cleantalk.org/how-to-protect-your-contactform7-contact-form-using-cleantalk-anti-spam-plugin/">How to protect your Contact Form 7 using CleanTalk Anti-Spam plugin</a>

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

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

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

= Leaky Paywall subscription protection =
Plugin protects Leaky Paywall plugin (by ZEEN01) against spam subscriptions. It can be used with any other third-party spam filters.

= HubSpot protection for embedded forms =
Plugin protects HubSpot embedded forms against any spam submissions. Guide to start using embedded forms https://knowledge.hubspot.com/forms/how-can-i-share-a-hubspot-form-if-im-using-an-external-site

= Contact Form by WPForms Antispam =
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.

= Antispam for WooCommerce & fake orders filter =
Anti-spam by CleanTalk filters spam registrations, spam reviews, and fake orders for WooCommerce (any eCommerce plugin as well). The plugin is fully compatible with WooCommerce 2.1+ and online stores.

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

= Many other great contact, signups and all kind of forms that supported by CleanTalk =
* AWeber form builder <a href="https://wordpress.org/plugins/aweber-web-form-widget/">https://wordpress.org/plugins/aweber-web-form-widget/</a>
* Contact form by BestWebSoft <a href="https://wordpress.org/plugins/contact-form-plugin/">https://wordpress.org/plugins/contact-form-plugin/</a>
* Contact Form Plugin by Fluent Forms Ninja forms <a href="https://fluentforms.com/">https://fluentforms.com</a>
* Forminator contact from <a href="https://wpmudev.com/project/forminator-pro/">https://wpmudev.com/project/forminator-pro/</a>
* Ninja forms <a href="https://ninjaforms.com/">https://ninjaforms.com</a>
* Newsletters - MC4WP: Mailchimp for WordPress (<a href="https://www.mc4wp.com/">mc4wp.com</a>), MailPoet – emails and newsletters in WordPress (https://www.mailpoet.com/)
* WS Form Lite <a href="https://wordpress.org/plugins/ws-form/">https://wordpress.org/plugins/ws-form/</a>
* WP User Frontend, UserPro.
* WordPress Landing Pages.

Protection for the forms above works as a built-in feature of Anti-Spam by CleanTalk without requiring any additional actions from the user.

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

= Private black lists for anti-spam service =
Automatically block comments and registrations from your private black IP/email address 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.

= Low false/positive rate =
This plugin uses multiple anti-spam tests to filter spam bots having as low false/positive rate as possible.

= 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. How does it work?

 * 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: 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 https://cleantalk.org/help/anti-flood-and-anti-crawler

By default, well-known good bots — including AI crawlers such as GPTBot (ChatGPT), ClaudeBot (Claude), Google-Extended (Gemini), and Copilot — are allowed. You can choose which of these bots to block individually in your private lists. Blocking a bot will stop the corresponding AI service from accessing your content.

= How to protect sites from spam bots without CAPTCHA? =
CleanTalk Anti-Spam protects websites from spam bots without using traditional CAPTCHA, reCAPTCHA, or other visitor challenges. Instead of showing CAPTCHA puzzles, the service uses behavioral analysis, invisible JavaScript tests, and a global spam database to detect spam automatically in the background. This CAPTCHA-free anti-spam protection works for contact forms, comments, registrations, and WooCommerce checkouts without creating friction for real visitors. By replacing CAPTCHA with automated spam detection, CleanTalk helps improve usability, accessibility, and conversion rates while still blocking spam effectively.

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*

= 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,

* Anti-Spam protection for website search forms repels spam bots.
* 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 spam bots.

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, Phones 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 email, phontes 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.

= Honeypot field =
The option helps to block bots. The honeypot field option adds a hidden field to the form. When spambots come to a website form, they can fill out each input field. Enable this option to make the protection stronger on these forms. Learn more about supported forms here.


== Installation ==

= Installation instructions =

1. Download, install and activate 'Anti-spam by CleanTalk'.

2. Get Access key <a href="https://cleantalk.org/register?platform=wordpress" target="_blank">https://cleantalk.org/register</a>

3. Enter Access key in the settings: WordPress console -> Settings -> Antispam by CleanTalk

4. Do dummy spam comment (registration or contact message) with email **stop_email@example.com**. You should see notice: **Forbidden. Sender blacklisted.**

5. Done! The plugin is ready to use.

[Video guide](https://youtu.be/NbTG5BhFOEM) - Anti-Spam Plugin Installation in WordPress

**Important!** 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.

= How can setup plugin in WPMU version? =
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 WPMS, define constant in your wp-config.php file before defining database constants:

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

**Make it before you activated the plugin. If the plugin already activated, deactivate it and add the code and active it again.**
Now, all subsites will have this access key.

= Manage and control spam protection =

Go to <a href="https://cleantalk.org/my" target="_blank">Dashboard</a> at the cleantalk.org or use <a href="https://play.google.com/store/apps/details?id=org.cleantalk.app">Android</a>, <a href="https://itunes.apple.com/us/app/cleantalk/id825479913?mt=8">iPhone</a> anti-spam app to manage and control spam protection.


== Frequently Asked Questions ==

= 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 **stop_email@example.com** 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 <a href="http://cleantalk.org/my/show_requests">Dashboard</a> or look at the folder "Spam" for banned comments.

= 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.
1. **Email, IP, domain spam activity list entries check.** The plugin uses spam activity database online at cleantalk.org, 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.
1. **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.

= 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 to remove pending spam comments? =
Yes, you can. The plugin has the option to test all pending comments via database of <a href="https://cleantalk.org/blacklists">spam active IP/Email</a>, 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

= 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 *stop_email@example.com* 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.
https://en.wikipedia.org/wiki/Software_as_a_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. Follow this guide <a href="https://cleantalk.org/help/api-check-message">https://cleantalk.org/help/api-check-message</a>

= 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

or

	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: https://cleantalk.org/help/exclusion-from-anti-spam-checking#wordpress

= 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: https://cleantalk.org/help/exclusion-from-anti-spam-checking#WordPress_field_exclusions

= How to test Spam FireWall? =
Use special IP 10.10.10.10 in URL to test Spam FireWall. For example,

    https://cleantalk.org/blog/?sfw_test_ip=10.10.10.10

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: https://www.wikihow.com/Activate-Incognito-Mode

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

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

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

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

2. **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.

3. **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: https://cleantalk.org/my/show_requests?int=week

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:
https://cleantalk.org/help/spam-comment-management

= Is the plugin EU GDPR compatible? =
Yes, it is. Please read this article,
<a href="https://cleantalk.org/publicoffer#cleantalk_gdpr_compliance">https://cleantalk.org/publicoffer#cleantalk_gdpr_compliance</a>

= Is CleanTalk Google reCAPTCHA alternative? =
Yes, CleanTalk can be used as an [alternative to reCAPTCHA](https://cleantalk.org/recaptcha-alternative), but it works differently.
Instead of showing challenges, it blocks spam automatically in the background with no user interaction, improving user experience and conversions.

= Is CleanTalk an Akismet alternative? =
Yes — CleanTalk can be used as an [alternative to Akismet](https://cleantalk.org/akismet-alternative).
They solve the same problem, but CleanTalk protects all site forms (not just comments) and works as a broader, cloud-based anti-spam solution.

= Will the anti-spam plugin protect my theme? =
Yes, it will. The Anti-spam by CleanTalk is compatible with any WordPress theme.

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



== Screenshots ==
1. AntiSpam settings are easy to use to protect any contact forms. For example - Ninja forms, Fluent forms and etc.
2. AntiSpam plugin rejected a spam bot at the CAPTCHA less registration form. The plugin provides explanation to visitor and websites about each rejected comment/registration or contact message.
3. Use AntiSpam analytics tool for each website in service Dashboard to have information about spam/legitimate stats.
4. Special interface to find spam comments.
5. Special interface to find spammers in users.
6. Prevent WooCommerce checkout from spammers.
7. Prevent spam contact occurs in your life.
8. Prevent any other spamers, from any other forms, for example from WPForms.

== Changelog ==

= 6.81 10.06.2026 =
* New. Code. Amelia integration
* Code. Links from backend
* Fix. Code. Improve statement.
* Fix. Code. Editing the array key transfer
* Fix. SFWUpdateLog. Transferring values to placeholders prepare()
* Fix. SFW. Mixing values in cookies SFW
* New. Pingback and trackback rejection implemented.
* Code. Mobile styles fix (#803)
* Mod. Integrations. Opting out of force alt cookies for SmartForms. (#808)

= 6.80 28.05.2026 =
* Fix. catchJqueryAjax. Object as null comparison fixed.
* Fix. CatchXHR. Mailpoet integration added to provide the event_token.
* Upd. Bot Detector Service. Added alternative source URL.
* Upd. Bot Detector Service. Updates.
* Fix. PHP8. Prevent duplicate headers before sending HTTP response code.
* Fix. TRP. Correctly save TRP hashes.
* Mod. Settings. Transferring an option and deleting its description
* Fix. Code. Bug fixes after WP 7.0 update
* Fix. Admin banners. Call-to-action buttons visibility fixed.
* Mod. Settings. Editing the description of the Anti-Crawler option
* Fix. Settings. Edit long description
* Mod. Integration. Opting out of force alt cookies for UserRegistrationPro members
* Fix. BotDetector. Editing the bot detector connection
* Fix. CheckJS. Edit the check_js entry if the global key is not available
* Fix. Code. Added a space between the username and the TRP text

= 6.79.1 25.05.2026 =
* Fix. Admin banners. Call-to-action buttons visibility fixed.

= 6.79 14.05.2026 =
* Mod. Settings. Moving the AC option
* Fix. Search forms. Add a sign of 's' GET param to a native search form signs.
* Fix. Contacts Encoder. Shortcodes. Content sanitization improved.
* Fix. NoCookieData. Correcting an error when encoding a NoCookie array
* Fix. CheckForSpam. Editing the deletion of spam check logs
* Mod. AntiCrawler. Editing the option description

= 6.78 29.04.2026 =
* Removing the link to install "Gravity Forms to doBoard" (#784)
* Mod. BloomForms. Editing the integration with BloomForms
* Update inc/cleantalk-settings.php
* Upd. Integrations. Improve Divi newsletters flow to attach meta data to request.
* Add "Read more" link to cleantalk page (#782)
* New. BaseCall. Default params class.
* Fix. REST API. Updated 'email' argument type from 'email' to 'string' in callbacks.
* Fix. GFA. Replaced email regex with isEmailLike method and added unit tests for validation.
* Upd. Integrations. Improve Divi newsletters flow to attach meta data to request. (#786)
* Ref. AntiCrawler. Module flow refactored. (#788)

= 6.77 16.04.2026 =
* Fix. AltSession. Correcting the issue of array conversion
* New. BookingCalendar. New integration with BookingCalendar
* Upd. Settings. Updated flow to check pingback. (#764) (#773) (#774)
* Fix. CF7. Edit honeypot
* Fix. Integration. EDD integration fixed. (#770)
* Fix. Code. Editing the bot detector settings
* Fix. Exclusion. Skip request from Metorik Helper
* Fix. Common. Add bot detector state to ct_options. (#778)
* Fix. WPMS. Errors output for WPMS mutual-mutual mode fixed. (#772)
* Fix. WPMS. Settings for `mutual/mutual` fixed.
* Fix. WPMS. Settings page error fixed.

= 6.76 02.04.2026 =
* Mod. ForceAltCookies. Removed the use of force alt cookies for integration with piotnet-addons-for-elementor
* Upd. Integrations. Improve FluentBooking flow to attach meta data to request.
* Upd. Settings. Updated flow to check pingback.
* Upd. Settings. Bot Detector setting - bot-detector setting removed.
* Fix. Code. Unit tests fixed: TestFluentForms, TestNinjaForms.
* Fix. JS. Gathering. Passing js_on independent of gathering loaded.
* Fix. Integrations. QuForm. Fixed js_on param gathering.

= 6.75 19.03.2026 =
* Upd. JS. catchJqueryAjax. Refactored to also use ajaxPrefilter. Bloomform now skip using force alt-sessions.
* Upd. ContactEncoder. Improve aria labels protect.
* Upd. Integration. HivePress forms protection improved.
* Upd. Settings. SFW outdated message refactored.
* Upd. Settings. Error. Fixed case when SFW outdated error is not removable.
* Upd. TRP. TRP popup text and styles updated.
* Fix. Integrations. Improve statement to protect memberpress.
* Fix. Integrations. Improved membershippro processing statement.
* Fix. Integration. Gravity forms integration fixed.
* Add. Integrations. Added Elfsight compability.
* Fix. RemoteCalls. Changes to the RC functionality
* Upd. Settings. Improved copability.
* Fix. Contacts Encoder. Shortcode for exclude encoding.
* Upd. BotDetector. Update load strategy.
* Upd. BotDetector. Update load strategy for fluent booking and fluent form.

= 6.74 05.03.2026 =
* Mod. SFW. Atomic approach to updating SFW
* Upd. Exclusions. Ajax. Plugin "cart-recovery".
* Fix. Code. JS loading by defer fixed.
* Mod. OtterForms. Changing integration from a hook to a route
* Mod. OtterForms. Changing the integration, renaming the request interception method
* Upd. Connection reports. Email subject updated.
* Fix. JS. catchFetchRequest. Origin fetch definitions.
* Upd. Exclusions. Ajax. Plugin "invoicing".
* Upd. Gravity Forms. Skipped request extended log.
* Fix. Translate. Fixed msgids.
* Upd. Connection reports. Email title edited.
* Upd. Connection reports. Service id added.
* Fix. SubmitTime. Calculation of the submit time when enabling the gathering script
* Upd. SFW updates sentinel. Updated report.
* Upd. Settings. Updated RC to init settings update.
* Fix. SubmitTime. Editing the creation of a timestamp

= 6.73.1 19.02.2026 =
* Fix. Code. JS loading by `defer` fixed.

= 6.73 19.02.2026 =
* Upd. Code. SFW Update. HTTP multi request refactored.
* New. ShadowrootProtection. Implementation of form protection in Shadowroot elements, integration with Mailchimp shadowroot
* Mod. ShadowrootPrt. Architectural changes in logic, the addition of situational callbacks
* Fix. CurlMulti. Editing implementation comments
* Fix. Integration. Ninja forms. Filter NF common fields before processing.
* Fix. Exclusions. "woocommerce-abandoned-cart"
* Fix. Exclusions. "woo-abandoned-cart-recovery"
* Fix. Exclusions. "abandoned-cart-capture"
* Fix. Code. Returned the lost code during the merge
* Fix. FluentForm. Vendor integration compliance fixed.
* Upd. Integrations. Elementor UltimateAddons Register integration handler to use ajax middleware.
* Fix. IntegMailChimp. Clearing all fields except for the field whose name contains message
* Fix. Code. Edit Remote Calls
* Fix. AdminActions. Checking permissions for Actions
* Upd. Exclusions. Ajax. Plugin "wp-multi-step-checkout".
* Fix. Exclusions. Ajax. Plugin "woo-abandoned-cart-recovery". Fixed condition.
* Code. Unit tests for apbct_is_skip_request() refactored.
* Fix. Code. Escaping woocommerce order data
* Upd. Exclusions. Ajax. Plugin "woocommerce-sendinblue-newsletter-subscription"
* Fix. Remote Calls. Skip check if no sign of RC action provided in Request.
* Fix. Exclusion. Added path invoice4u/v1/callback.
* Fix. Contact Encoder. Every hook that has actions BEFORE modify now have actions AFTER.
* Fix. Enqueue. Script individual-disable-comments.js renamed to cleantalk-individual-disable-comments.js
* Upd. CommentsCheck. Improve statement.
* Upd. JS parameters. Gathering dynamic lod implemented.
* Fix. Connection reports. Email for reports fixed.
* Fix. Integration. SmartQuizBuilder integration fixed.
* Fix. ContentEncoder. Editing the data type in the 3rd str_replace argument

= 6.72 05.02.2026 =
* Upd. WooCommSpamOrders. Added a hint for the disabled option to save spam orders.
* Fix. Integrations. Fluent Forms. Visible fields collection fixed.
* Fix. Integrations. Skip encoding for woo registration button. (#722)
* Upd. Integration. Mailpoet. Visible fields gathering.
* Upd. Visible fields extractor. Static method to get a new extractor.
* Fix. Integration. Exclusions for WC requests fixed.
* Fix. Integrations. GiveWP multi-page form. Exclude requests without email.
* Fix. Integrations. GiveWP. Skip external forms check.
* Fix. Integrations. GiveWP. Bot detector token. Intercept iframe fetch to add field if available.
* Fix. Integrations. Fixed fetch request fields assignment (NoCookie|EventToken)
* Fix. Woocommerce. Stored oreders. Fixed code error.
* Mod. ContentEncoder. The ability to exclude the main page by hook
* Fix. Code. Getting cleantalk addresses fixed.
* Fix. Integrations. Add event token in jQuery catching for forms of "wpr_form_builder_email" action.
* Upd. Footer. Footer promo link added. (#729)
* Fix. Integrations. WooCommerce. Stripe express checkout address normalize excluded.
* Fix. Integrations. Paid Membership Pro. Login form excluded.
* Upd. Updater. Add index update mechanism. (#721)
* Fix. Skip Elementor login widget request for WooCommerce checkout.
* Fix. Integration. Mailpoet integration fixed.

= 6.71.1 26.01.2026 =
* Fix. Promotion. GF2DB promo setting and message reverted.

= 6.71 22.01.2026 =
* Fix. Integration. Woocommerce (checkout by REST) integration fixed.
* Fix. Integration. Fluent forms integration fixed
* Fix. Integration. Klaviyo (external forms) integration fixed.
* Upd. PHPUnit. testIsAllowMessage/User refactored
* Fix. Settings. Description for Send connection reports fixed.
* Fix. Contacts Encoder. Exclusions fixed.
* Fix. Contacts Encoder. Regex pattern for emails fixed.
* Upd. Links. UTM preset for bbPress spam scanner added.
* Fix. Fetch request catching. Fixed case with empty GET requests from pojo-accessebility plugin.
* Fix. SFW pages. Fixed bundle name with resolver.
* Fix. Common. Helper. PHP 8.4. Function str_getcsv() escape argument added
* Fix. Workflow. Make the zip with subfolder instead of zip-root.
* Fix. Exclusions by URL. Fixed validation and URL gain for ajax requests.
* Upd. Requirements Checker. Modified curl_multi_exec to curl_multi array of functions.
* Upd. SFW update. Do not start update if curl multi funcs are not available.
* Fix. Integrations. Excluded recaptcha from cloning and ensured it is reinserted into the origin form during processing.
* Fix. Integrations. Update condition to skip check of account update for logged in users.
* New. Promotions. GF2DB.
* New. Settings. Added RC to init settings update.
* New. Integration. Bit Form integration implemented.
* Upd. Code. PHP compatibility increased to 7.2.
* New. Settings. Added project management menu item.

= Look for early changelogs in <a href="https://github.com/CleanTalk/wordpress-antispam/blob/master/changelog.txt" target="_blank">changelog.txt</a>=
