Anti-spam MOD for phpBB3 updated, the changes in the new version,
- fixed bug with removing the signature of service;
- improved JavaScript anti-spam test;
- updated CleanTalk PHP API.
Archive module phpbb-antispam-3.75.zip.

Anti-spam MOD for phpBB3 updated, the changes in the new version,
Archive module phpbb-antispam-3.75.zip.
Available updated anti-spam plugin for Joomla, changes in the new version,
We remind all the plugin functions,
The archive with the updating joomla15-antispam-1.73.zip, joomla25-3x-antispam-1.73.zip.
The algorithm for spam filtering has new exceptions for links to photo hostings and tiny-urls web-sites. For example, links to sites such as img.gd, goo.gl bit.ly etc. will be ignored when determining the links to spam active web sites.
The type of the web site – blog, forum, photo hosting, tiny url and etc. is determined automatically by analyzing the structure of HTTP links.
Innovation will reduce the number of messages sent to the moderators of websites.

From 24 February till 24 March 2014 for all packages are disabled daily limits of approved “registrations/comments”.
We are testing the new tariff policy, we hope to use it in the future on a permanent basis for all customers of the service.

Anti-spam MOD for phpBB3 updated, the changes in the new version,
Archive module cleantalk_spam_protect_v_3.74.zip.

Available updated anti-spam plugin for Joomla, changes in the new version,
We remind all the plugin functions,
The archive with the updating UNZIPFIRST.cleantalk.joomla.plugin-v1.70.zip.

Anti-spam MOD for phpBB3 updated, the changes in the new version,
Archive module cleantalk_spam_protect_v_3.73.zip.

Ready to use the updated version of the anti-spam plugin for WordPress, changes,
Archive with the plugin cleantalk-spam-protect.2.33.zip.

Ready to use the updated version of the anti-spam plugin for WordPress, changes,
Archive with the plugin cleantalk-spam-protect.2.31.zip.

Today 16.01.2014, in the first half of the day (until 06:00 GMT time) during the upgrade of the billing system mistakenly sent messages about disabling the service. In the same time the service wasn’t disabled!
We apologize for inconvenience!