Spam protection, AntiSpam, FireWall by CleanTalk

Descripción

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

Características Anti-Spam

  1. Hace parar spam comentarios.
  2. Hace parar spam registros.
  3. Hace parar spam direcciones del correo electrónico.
  4. Hace parar spam órdenes.
  5. Hace parar spam reservas.
  6. Hace parar spam suscripciones.
  7. Stops spam surveys, polls.
  8. Hace parar spam aplicaciones.
  9. Stops spam in WooCommerce.
  10. Comprueba y elimina los comentarios de spam existentes y los usuarios de spam.
  11. Compatible con usuarios y dispositivos móviles.
  12. Compatible con el Reglamento General de Protección de Datos (RGPD) (UE).
  13. Validación de correo electrónico en tiempo real. ¿El correo electrónico es real o no?
  14. Bloqueo de correos electrónicos desechables y temporales.
  15. Sin spam: sin penalizaciones de Google. Dale impulso a tu SEO.
  16. Compatible con móviles, antispam y cortafuegos.
  17. Detiene el spam en el formulario de búsqueda.
  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 $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 https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/#6-software-as-a-service-is-permitted

Public reviews

CleanTalk: servicio antispam basado en la nube para mantener Tu sitio libre de bots.
   Reseña de NewsWatch.

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

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.
www.techwibe.com

El punto de venta clave de CleanTalk para mí no es simplemente su efectividad. Es el hecho de que CleanTalk funciona en segundo plano. No hace que los usuarios pasen por alto para enviar un comentario o completar un formulario.
   www.kevinmuldoon.com

Protección Anti-Spam para comentarios

Protección anti-spam nativa para WordPress, comentarios de JetPack y cualquier otro plugins de comentarios. El plugin mueve los comentarios de spam a la carpeta SPAM o puede configurar la opción para prohibir los comentarios de spam silenciosamente. También puede activar la opción en la configuración del plugin para eliminar automáticamente los comentarios de la carpeta SPAM.

Filtro de registros de spam bots

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

Filtros para correos no deseados en WooCommerce.

Anti-spam por CleanTalk filtra registros de spam y comentarios de spam para WooCommerce. El plugin es totalmente compatible con WooCommerce 2.1 y superior.

Filtro anti spam en boletines

Filtros de spam para formularios de contacto tema

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.

filtro de spam bbPress

Protección contra spam para todo lo relacionado con bbPress: inicios de sesión, registros, foros, debate y respuestas.

Other spam filters

  • WordPress Landing Pages.
  • Portada del usuario WP, usuario Pro.
  • Any WordPress form (checkbox ‘Custom contact forms’).
  • Cualquier presentación al sitio (casilla ‘Comprobar todos los datos de POST’)

Compatible with WordPress cache plugins

Verifica los comentarios existentes en busca de spam. Eliminación en bloque de comentarios de spam. 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.

Verifica los usuarios existentes en busca de spam. Eliminación en lotes de cuentas de spam. 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.

El bloqueo de usuarios por país

Bloquea automáticamente los comentarios y los registros de los países que ha establecido una prohibición para. Esta opción es útil en casos de protección contra el spam manual y para la mejora de la protección. Si su sitio no está destinado para el público internacional y no esperas comentarios/usuarios de otros países.

El bloqueo de los comentarios de acuerdo a «palabras vacías»

Puede bloquear los comentarios que contengan «palabras de detención» para mejorar la protección contra correo no deseado y los mensajes con obsceno bloqueo de palabras. Puede agregar palabras o frases en particular.

Listas negras privadas para el servicio anti-spam

Bloquea automáticamente los comentarios y los registros de tu lista privada de direcciones IP / correo electrónico black. Esta opción ayuda a reforzar la protección contra el spam de un spam manual o bloquear los comentarios no deseados de los usuarios. Puede agregar no sólo ciertas direcciones IP, sino también una subred separada a su lista negra personal.

Private black list for Spam FireWall

Te permite ñadir direcciones IP y subredes individuales a SpamFireWall.
bloquea los ataques de spam de las direcciones IP que aún no están incluidas en la base SFW. Esta opción puede ayudar a bloquear HTTP / HTTPS DDoS, SQL, ataques de fuerza bruta y cualquier otro que lo hizo a través del HTTP / HTTPS. Puedes añadir no sólo ciertas direcciones IP, sino también una subred separada a tu lista negra personal.

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.

¿Qué tan efectivo es CleanTalk?

Bloquear el spam con precisión no es algo fácil de hacer, pero CleanTalk tiene una tasa de Falso/Positivo probada muy baja. Aquí hay estadísticas reales sobre falsos positivos para todos los clientes.

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

La estadística se calculó el 28 de agosto de 2020 para 2.5 millones de solicitudes.

¿Cómo CleanTalk mejora SEO para su sitio web?

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

CleanTalk funciona más rápido que la mayoría de los otros plugins anti-spam. Es de conocimiento común que contra más rápido se cargue su sitio, mejor será la experiencia del cliente, mejor será su SEO, y mejor se convertirá su sitio. La velocidad es cada vez más importante en SEO, la conversión y la experiencia del usuario. Hoy en día, la velocidad del sitio es uno de los factores de clasificación más importantes de Google. Un sitio que se carga lentamente perderá los visitantes y los ingresos potenciales.

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.

https://s.w.org/plugins/cleantalk-spam-protect/screenshot-5.png?r=1288723

¿Cómo funciona CleanTalk?

  • 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 es totalmente compatible con los servicios VPN más populares.
Además, Spam FireWall es compatible con todos los motores de búsqueda Google, Bing, Yahoo, Baidu, MSN, Yandex, 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.

Toda la actividad Spam Firewall de CleanTalk se está registrando en el proceso de filtrado.

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

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.

Hemos desarrollado el antispam para WordPress que te protege de los robots de spam al máximo nivel, lo que te permite proporcionar a tus visitantes un formulario simple y conveniente de comentarios/registros sin molestos CAPTCHA y rompecabezas. CleanTalk detecta spam en pruebas de varios niveles, lo que nos permite bloquear hasta el 99,998 % de los robots de spam.
El método antispam ofrecido por CleanTalk evita inconvenientes para los métodos de comunicación (CAPTCHA, pregunta-respuesta, etc.) y ofrece a los visitantes del sitio uno más cómodo.

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.
  • Protección contra el spam de los varios sitios web a la vez en diferentes CMS.
  • Facilidad de instalación y uso.
  • Traffic increase and loyalty to the users.
  • 24/7 technical support.
  • Borrar las estadísticas.
  • 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 cleantalk.org.

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.

Características de CleanTalk

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.

El equipo de CleanTalk ha desarrollado algoritmos anti spam únicos para evaluar el comportamiento de los visitantes. CleanTalk analiza el comportamiento del usuario y los parámetros de los formularios fill
. Nuestro módulo anti-spam, que se instala en su sitio web, envía los parámetros de comportamiento de un visitante o un bot de spam. Cuando estos parámetros
se calculan, el servicio anti spam toma una decisión: publicar un mensaje o definirlo como spam y rechazarlo. Sobre la base de estas comprobaciones, el servicio forma su propia lista de direcciones de correo electrónico utilizadas por los robots de spam.

Los registros de visitantes se controlarán de forma similar. El servicio se suma a la lista negra no sólo direcciones de correo electrónico, sino también las direcciones IP y dominios de sitios web que promueven a sí mismos a través de correo de spam. Todo esto sucede de forma automática y no requiere ninguna acción por parte de la administración de la página web. En 2,5 millones de consultas al servicio comete un error en 40-45 casos, es decir CleanTalk detecta el spam con 99.9982% de precisión. Monitoreamos constantemente estos errores y realizamos ajustes a nuestros algoritmos. Incluso con esta precisión excepcional de nuestro equipo tiene el objetivo de mejorar las cifras a través del tiempo.

Todo-en-uno. CleanTalk protege todos los formularios de forma instantánea – comentarios, registros, comentarios, contactos. No es necesario instalar plugins adicionales para cada formulario. Ahorrar recursos y aumentar el rendimiento de su sitio web.

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.

«El equipo de CleanTalk ha estado desarrollando un sistema de protección de spam en la nube por cinco años y ha creado un servicio anti-spam verdaderamente fiable diseñado para usted y garantizar su seguridad».

Modo marca blanca

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.

El plugin hará todo lo demás.

Actualización automática de CleanTalk Anti-Spam

CleanTalk Dashboard te permite establecer la actualización automática del plugin y seleccionar varias web y actualizar el plugin de una sola vez en todos los sitios con un solo clic o puedes configurar la actualización automática para todos las web o webs separadas.

Nota: hay 24 horas de retraso antes de que se realice la actualización automática. Este retraso permite evitar cualquier problema. Todas las actualizaciones realizadas a través del escritorio de CleanTalk de forma manual se realizarán de inmediato.

El sistema de actualización automática funcionará desde CleanTalk Anti-Spam versión 5.88

Validación de correo electrónico en tiempo real. ¿El correo electrónico es real o no?

Es muy importante asegurarse de que el usuario haya usado su dirección de correo electrónico real. Los spambots a menudo usan direcciones de correo electrónico falsas, es decir, direcciones que no existen.

CleanTalk verificará la existencia de direcciones de correo electrónico en tiempo real.

Las direcciones de correo electrónico no existentes también conllevan otros problemas para los propietarios de webs.

  • Nunca puedes contactarlos por correo electrónico,
  • el cliente nunca recibirá avisos tuyos (carta de activación de cuenta, recuperación de contraseña, distribución de correo electrónico, avisos, etc.),
  • Si utilizas el marketing por correo electrónico para tus clientes, una gran cantidad de correos electrónicos inexistentes en la lista de correo pueden hacer que tu dirección IP se añada a varias listas negras de servidores de correo electrónico.

Mejora tu lista de correo electrónico con la validación del correo electrónico sin correos electrónicos falsos.

Bloqueo de correos electrónicos desechables y temporales.

Bloquea usuarios falsos y sospechosos con correos electrónicos desechables y temporales para mejorar la entrega del correo electrónico. Por lo tanto, también evita la actividad malintencionada, los bots de spam y los trolls de internet.

Detiene el spam en el formulario de búsqueda.

Los robots de spam pueden usar tu formulario de búsqueda para hacer una solicitud GET con texto de spam.
CleanTalk Anti-Spam tiene la opción de proteger el formulario de búsqueda de tu web de los robots de spam. Cada vez, la búsqueda genera una nueva página y si hay muchas solicitudes, esto puede crear una carga adicional. Entonces, en algunas condiciones, las búsquedas de spam pueden indexarse, lo que afecta al SEO,

  • Spam FireWall bloquea el acceso a todas las páginas de ña web para los robots de spam más activos. Reduce la carga y el tráfico de tu servidor web simplemente haciendo esto.
  • La protección antispam para los formularios de búsqueda de webs repele los robots de spam.
  • Si tu formulario de búsqueda obtiene datos con demasiada frecuencia, el plugin CleanTalk Anti-Spam agregará una pausa y la aumentará con cada nuevo intento de enviar datos. Le ahorra tiempo al procesador de tu servidor web.
  • La protección contra spam te permite no prohibir la indexación de los robots rastreadores si realmente la necesitas, pero al mismo tiempo obtendrás protección contra los robots de spam.

Siempre sabrás qué buscaban los usuarios en tu sitio.

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.

Traducciones

  • Albanian (sq_AL) – thanks to fjalaime https://wordpress.org/support/users/fjalaime/
  • Francés (fr_FR) – gracias a Gilles Santacreu http://net-ik.net
  • Español (es_ES) – gracias a Andrew Kurtis y WebHostingHub

Requisitos

WordPress 3.0 al menos. PHP 5 con la función CURL o file_get_contents () y ajustes activados ‘allow_url_fopen’. El plugin es totalmente compatible con 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.

Capturas

  • Los ajustes de anti spam son fáciles de usar.
  • 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 o contact message.
  • Use AntiSpam analytics tool for each website in service Dashboard to have information about spam/legitimate stats.
  • Use AntiSpam log to control anti-spam plugin.
  • CleanTalk funciona más rápido que la mayoría de los otros plugins anti-spam.
  • The Dashboard with a map of most spam active countries per your account.
  • El plugin borra/elimina los comentarios de spam existentes y las cuentas de los usuarios.
  • CleanTalk's dashboard update link.
  • Confirmación de actualización automática.
  • Website's options.
  • CleanTalk's dashboard.
  • SpamFireWall log.

Instalación

Instrucciones de instalación

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

  2. Obtener clave de acceso https://cleantalk.org/register

  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. ¡Hecho! El plug-in está listo para usar.

Guía en vídeo – Instalación del plugin Anti-Spam en 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.

¿Cómo se puede configurar el plugin en la versión WPMU?

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');

Hazlo antes de activar el plugin. Si el plugin ya está activado, desactívalo, añade el código y actívalo nuevamente.
Ahora, todos los subsitios tendrán esta clave de acceso.

Manage and control spam protection

Ir al Escritorioen cleantalk.org o usar Android, iPhone anti-spam app para administrar y controlar la protección contra el spam.

FAQ

¿Por qué me envían spam?

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

¿Te protege el plugin de la fuerza bruta, ataques DoS y ataques de spam?

Sí, lo hace. Por favor, activa la opción ‘SpamFirewall’ en la configuración del plugin para proteger tu web de DoS/DDoS, ataques XMLRPC.

How does the plugin stop spam?

Por favor, ten en cuenta – las acciones del administrador no se están comprobando.

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. Correo Electrónico, IP, comprobar la entrada de actividad de spam de dominio. El plugin utiliza la base de datos en línea en la actividad de spam cleantalk.org, que consta de más de 20 millones de registros de actividades spam de los IPs, correo electrónicos, dominios y ASN. Si el IP o el correo electrónico del remitente está en la base de datos, el remitente recibe algunas puntuaciones de spam. Para reducir la tasa de falso/positivo el plugin no sólo utiliza la prueba de lista negra para prohibir los spammers, el remitente será prohibido cuando, y sólo cuando las pruebas múltiples de spam han fracasado.
  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.

¿El plugin antispam protegerá mi tema?

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.

¿Puedo utilizar CleanTalk con 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.

¿Es CleanTalk mejor que Akismet?

Please look at this features comparison here https://cleantalk.org/cleantalk-vs-akismet

¿Puedo utilizar CleanTalk para eliminar la espera de comentarios de spam?

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?

El plugin comprueba todos los comentarios que no son spam en la base de datos de la lista negra y te muestra los remitentes que tienen actividad de spam en otras webs.
Hay algunas diferencias entre la base de datos de lista negra y la API para protegerte de los registros/comentarios de los robots de spam online. Las listas negras muestran todo el historial de la actividad de spam, pero nuestra API (que se usa en las pruebas de spam) también se basa en otros parámetros: último día de actividad, número de ataques de spam durante los últimos días, etc. Estos mecanismos nos ayudan a reducir el número de resultados falsos. Por tanto, no hay nada extraño si algunos correos electrónicos o IPs no se encuentran en las pruebas en lote de los comentarios/cuentas.

Para revisar los comentarios por favor vayan aquí:

WordPress console -> Comments -> Find spam comments

Para revisar los usuarios por favor vayan aquí:

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

¿Puedo utilizar CleanTalk con plugins de caché?

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.

¿Es CleanTalk compatible con 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.

¿ Es CleanTalk compatible con una red de distribución de contenidos (CDN)?

Sí, lo es. CleanTalk funciona con cualquier sistema de CDN, es decir, CloudFlare, MaxCDN, Akamai.

¿Puedo utilizar la funcionalidad de CleanTalk en mis plugins?

Yes, you can. Just use following snippet:

<?php
if(!function_exists('ct_test_message')){
    include_once( ABSPATH . '/wp-content/plugins/cleantalk-spam-protect/cleantalk.php' );
}
//for registration test:
$res=ct_test_registration("nickname", "stop_email@example.com", "127.0.0.1");
//or for some other messages (contact forms, comments etc.)
$res=ct_test_message("nickname", "stop_email@example.com", "127.0.0.1", "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

o

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

¿Puedo añadir exclusiones para algunas páginas de mi sitio?

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

¿Qué No puedo enviar mis datos personales a los servidores CleanTalk?

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

¡Atención! El modo de incógnito debe estar activado en tu navegador cuando realizas una prueba. Para activar el modo de incógnito, presiona Ctrl + May + N para los navegadores Chrome, Opera y Safari; presiona Ctrl + May + P para Firefox, Internet Explorer y Microsoft Edge. Una guía completa para habilitar el modo de incógnito está aquí: 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.

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: https://cleantalk.org/checkout-javascript-support.

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

¿Funciona el plug-in con 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.

¿Cómo cerrar la renovación o el aviso de prueba en el backend de WordPress?

Para cerrar el aviso por favor, guarde la configuración del plugin de nuevo o que se cerrará automáticamente en el plazo de 60 minutos después de la renovación.

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: https://cleantalk.org/my/support.

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.

  • Filtrar los registros de spam por país de donde provienen.

  • Filtrar los registros de spam por dirección IP, dirección de correo electrónico o nombre de usuario.

  • Opciones disponibles para un registro específico:

    • 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: https://cleantalk.org/faq#feedback_spam
    • 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.

Por favor, lee más aquí
https://cleantalk.org/help/sfw-blocks-networks

Gestión de comentarios de spam

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.

Los comentarios bloqueados y prohibidos se pueden ver en el registro anti spam aquí: https://cleantalk.org/my/show_requests?int=week

Para administrar las acciones con comentarios de spam, ve al panel de control, selecciona la web para la que deseas cambiar las acciones y ve a «Ajustes» debajo del nombre de la web.

Por favor, lee más aquí:
https://cleantalk.org/help/spam-comment-management

¿Cómo informo un bot de spam perdido o un filtro incorrecto?

Si crees que el servicio ha perdido un bot de spam o un visitante de la web filtrado incorrectamente, puedes avisarnos a través del panel de control Anti-spam. Para hacer esto,
Accede al panel de control https://cleantalk.org/my.
Haz clic en la línea «Acceder» debajo del nombre de tu web.
Cuando marcas un registro como «SPAM», su correo electrónico y dirección IP se añadirán a tu lista negra personal para tu web.
Cuando marcas un registro como «No es SPAM», su correo electrónico y dirección IP se añadirán a tu lista blanca personal para tu web.

Por favor, lea más aquí
https://cleantalk.org/faq#feedback_spam

¿El plugin es rápido?

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.

¿Es compatible el plugin con la RGPD de la UE?

Yes, it is. Please read this article,
https://cleantalk.org/publicoffer#cleantalk_gdpr_compliance

Verificar formularios externos

Si tu web tiene formularios que envían datos a fuentes externas, puedes activar la opción «proteger formularios externos». En este caso, si el plugin determina que el mensaje actual es spam, su acción de formulario será reemplazada temporalmente por su nombre de host actual para evitar el envío de datos falsos a una fuente externa.

Reseñas

1 de octubre de 2022
I kept passing up on using CleanTalk but decided to give it a try after using several other plugins over the years that promised to help combat spam, etc. One particular site was getting tons of spam a day and nothing seemed to really stop it. I can say that so far, CleanTalk has done a very great job. It has blocked almost 7000 spam bots in 14 days.
26 de septiembre de 2022
The plugin is good and stops almost all spam. However upgrading to the premium version requires care. The upgrade form automatically selects the three website, three year, extra package with auto-renew. So your £11 plugin could become £55 if you assume clicking the single website option will just work honestly. It's not much cost but I wouldn't continue with this plugin but the client liked it so it stays.
24 de septiembre de 2022
I've tried several anti-spam plugins over the years but this one is by and far the best. It requires very little on my part, is quite reasonably priced, and it does an awesome job of stopping nearly all spam. I've been using it for quite a few years now and it also just keeps getting better as they build their spam database. It is also great for my site visitors as I can let them leave comments without being logged in and they do NOT have to deal with those annoying and time consuming captcha puzzles. If there were 10 stars I give this a 10 star rating!
22 de septiembre de 2022
Been troubled by spammers creating dodgy WooCommerce accounts for a long time. Akismet didn't touch them, ReCaptcha slowed everything down and I could never quite understand how WordFence wanted to me to tweak settings - then I came across a review for CleanTalk. The joy here is that they give you a 7-day free trial, which immediately allows you to see it how good it is. And it is good - for once you don't have to dive deep into techy tweaks - just press the on button and you're good. I saw an immediate cessation in spam account creation - and then they offered to cleanse existing records of clutter! Tiny fee in comparison to the trouble its resolved - I rarely write reviews but this totally deserves one. Top drawer plugin that is a must if you have a user base.
Leer todas las 2.499 reseñas

Colaboradores y desarrolladores

«Spam protection, AntiSpam, FireWall by CleanTalk» es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

«Spam protection, AntiSpam, FireWall by CleanTalk» ha sido traducido a 20 idiomas locales. Gracias a los traductores por sus contribuciones.

Traduce «Spam protection, AntiSpam, FireWall by CleanTalk» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios

5.186 Oct 06 2022

Several integrations added 🔥, custom logo for SFW blocking pages added 🎯, external forms into iframe protected 🎉 and some minor issues fixed 💪🏼

  • New. MemberPress direct integration.
  • New. SFW. Added custom logo on sfw die page.
  • New. Integrations. Handle EasyDigitalDownloads plugin registration hook.
  • New. External forms. External forms into an iframe has been protected.
  • Fix. ct_ajax_hook. Latepoint serice AJAX requests ignored.
  • Fix. apbct_settings__prepare_errors() Mismatching types fix.
  • Fix. Integrations. Ignore service requests in GiveWP integration.
  • Fix: Removed duplication of the hidden field in the search form
  • Fix. EmailEncoding. Styles fix.
  • Mod. EmailEncoding. Add a tooltip while decoding mailto: links.
  • Fix. External forms. Mautic external forms integration.
  • Fix. Internal forms. Modify regexp for exclusion urls of wordpress native internal forms.
  • Fix. Intergrations. Correct registration flag translation to basecall due EasyDigitalDownloads handling.
  • Fix. Common. Rotating m-servers fixed.
  • Fix. JS. Custom ajax forms blocking answer fixed.
  • Fix. JS. Headless parameter cast to boolean type.
  • Fix. NoCookie.php. Remove namespace redundant declaration to keep compat with <php5.6
  • Fix. Internal forms. Internal forms protection fixed.

5.185.1 Sep 28 2022

Fixed a security issues.

  • Fix. Fixed a security issues.

5.185 Sep 22 2022

NoCookie data collection, new admin notices style, external forms logic improved and many minor issues fixed.

  • New. NoCookie data collection.
  • New style admin notices
  • Upd. Settings. Email encoder setting duplicated on the top level place.
  • Fix: Fixed SFW looping with alternative cookies
  • Fix: Changed hook for EventsManager
  • Fix: Changed option description
  • Fix. External forms. JS logic fixed.
  • Fix. Cookies. Skip cookies setup on favicon loading.
  • Fix. HttpRequest. Error string offset fix due request error handling.
  • Fix: Fixed AdminNotices->is_cleantalk_page
  • Fix. Common. Rotating moderate-server via cron job fixed.
  • Fix. Common. Moderate servers details updated.
  • Fix. Email encoder. An ability to decode again implemented if an error was occurred.
  • Fix. GDPR. Contact form 7 integration fixed and upgraded.
  • Fix. ct_ajax_hook(). ProfileGrid AJAX actions skipped.
  • Fix. Connection report. Option implemented.
  • Fix. Integrations. Formidable forms item_meta handling.
  • Mod: Added clearing AC table from AC logs once a day
  • Fix. Debugging logic. Now drops debug data correct.
  • Mod. AltSessions. Now sends and parse cookies data as JSON.
  • Fix. AltCookies. Getting some parameters fixed.
  • New. MemberPress integration.
  • Fix. Cookie. Mouse/scrolling cookie storing fixed.
  • Fix. AltCookies. Correct handle types before save to DB when value is false.
  • Mod. Ajax/Rest selection. Now check if REST route provide a JSON string.
  • Fix. AltCookies. AltSession JSON handling fix.
  • Fix. Common. ‘no_cookie_data_taken’ notice fixed.

5.184 Sep 08 2022

Settings interface fixed, Email Encoder improved, jQuery dependency removed and some minor issues fixed.

  • New. cleantalk-admin-settings-page.js. Higlight access key field on key typos and do warn user.
  • New. Class for inline notices.
  • New. cleantalk-admin-settings-page.js. Notice user if key is bad to force retry synchronization.
  • New. cleantalk-admin.php. Localize key_is_ok to js script.
  • New. cleantalk-settings.php. Remove ‘save settings’ button disabling.
  • New. SFW. Adding custom logo to the block page ability implemented.
  • New: Email Decode. ‘check_bot’ method sending implemented
  • Fix. Email encoder. Handle mailto: links.
  • Fix: Added exception checking when adding a hidden field to WC Checkout
  • Fix: Fixed sending the email when the order was received
  • Imp. cleantalk-admin-settings-page.css. Notices CSS changed.
  • Imp. cleantalk-admin-settings-page.js. New notice view.
  • Fix: Fixed JS emailencoder
  • Fix: Fixed Upay integration
  • Fix. HTML5. Remove «text/javascript» in tag script.
  • Fix: Excluded email encoding on UltimateMember validation request
  • Fix. Code. JS refactored to be free of jquery
  • Fix. Internal forms. Some logic fixed.
  • Fix. External forms. Some logic fixed.
  • Fix. Admin. FeedBack sending timeout increased up to 15 sec.

5.183 Aug 18 2022

Checking for bot while email encoder decode, negative reports improved, some integrations fixed and some minor issues fixed.

  • New: Email Encoder. Check bot before decode.
  • New. Storing big connection reports.
  • Fix. Kses tag fixed.
  • Fix: Skipped login form for Wishlist Member
  • Mod: Added headers_sent in Cookie::set
  • Mod: Added aweber external form integration
  • Fix. Server variables. Getting Request variable fixed.
  • Fix. Connection reports. Getting data from options fixed.
  • Fix. Connection reports. Saving data fixed.
  • Fix. Connection reports. Displaying data fixed.
  • Fix. Cookies. Getting cookies from alternative way fixed.
  • Fix. Cookies. ApbctWP\Variables\Cookie getting fixed.
  • Fix. Cookies. Cookie check parameter fixed.
  • Fix: Fixed error with response from custom ajax requests

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. Sendfox.com 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 tp.media 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 tp.media 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: webto.salesforce.com extended form
  • Fix. SFW. Statistics fixed.
  • Fix: secure2.convio.net external
  • Fix: hookb.in 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