Title: Veilo — Invisible Spam Shield
Author: adinax0926
Published: <strong>15 août 2026</strong>
Last modified: 15 août 2026

---

Recherche d’extensions

![](https://ps.w.org/veilo/assets/banner-772x250.png?rev=3648308)

![](https://ps.w.org/veilo/assets/icon-256x256.png?rev=3648308)

# Veilo — Invisible Spam Shield

 Par [adinax0926](https://profiles.wordpress.org/adinax0926/)

[Télécharger](https://downloads.wordpress.org/plugin/veilo.1.1.0.zip)

 * [Détails](https://fr.wordpress.org/plugins/veilo/#description)
 * [Avis](https://fr.wordpress.org/plugins/veilo/#reviews)
 *  [Installation](https://fr.wordpress.org/plugins/veilo/#installation)
 * [Développement](https://fr.wordpress.org/plugins/veilo/#developers)

 [Support](https://wordpress.org/support/plugin/veilo/)

## Description

A working plugin scaffold, not a demo. It scores every submission using three signals—
a honeypot field, submission speed, and pointer/touch movement — with no CAPTCHA
ever shown to the visitor. Spam is blocked (or held for review) automatically.

**Free plan protects:**

 * Native WordPress comments
 * Contact Form 7
 * WPForms

**Pro plan additionally protects:**

 * Elementor Pro Forms
 * Gravity Forms

…and unlocks Veilo  Pro Tools: full Activity Log history (configurable row limit,
free is capped at the 10 most recent) and one-click CSV export.

#### Protecting a custom or hand-coded form

The signal script (`public/js/veilo-signals.js`) tags every `<form>` on the page
automatically, so the three hidden fields are already present in `$_POST` for ANY
form, built-in or custom. To act on them from your own form handler, call the public
helper:

    ```
    $result = veilo_check( $_POST, 'my-booking-form', $_POST['name'] ?? '' );

    if ( 'allowed' !== $result['decision'] ) {
        // stop processing however fits this form — wp_die(), return an
        // error, redirect back with a message, etc.
        wp_die( 'Your submission looks automated and was not sent.' );
    }

    // otherwise continue processing the form as normal
    ```

The second and third arguments are optional and only affect what shows up in Veilo
Activity Log (a source label and a short preview text). This same function is what
every built-in integration calls internally, so custom forms get identical scoring
to comments, CF7, WPForms, Elementor, and Gravity Forms.

## Installation

 1. Zip the `veilo` folder (the folder itself must be inside the zip, e.g. `veilo/veilo.
    php`).
 2. In wp-admin: Plugins  Add New  Upload Plugin  choose the zip  Install  Activate.
 3. Go to the new « Veilo » menu in the sidebar to choose which forms to protect and
    set the sensitivity threshold.
 4. Submit a test comment or form entry, then check Veilo  Activity Log to see the 
    score and reasons it was allowed or blocked.

## FAQ

### How does the score work?

 * Honeypot filled in  strong spam signal (bots fill every field)
 * Submitted in under ~2 seconds  strong spam signal (too fast for a human)
 * No mouse/touch/scroll at all  moderate spam signal
 * Hidden fields missing entirely  the request likely skipped the browser/JS

Everything above 100% is capped; the threshold in Settings (default 50) decides 
where « probably spam » starts.

### Does this require Contact Form 7 or WPForms to be installed?

Contact Form 7 support requires CF7 to be installed and active. WPForms support 
requires WPForms (free or Pro) to be installed and active. Elementor Forms support(
Pro plan) requires Elementor Pro. Gravity Forms support (Pro plan) requires Gravity
Forms. All integrations degrade gracefully — if the target plugin isn’t installed,
Veilo simply does nothing for that form type.

## Avis

Il n’y a aucun avis pour cette extension.

## Contributeurs/contributrices & développeurs/développeuses

« Veilo — Invisible Spam Shield » est un logiciel libre. Les personnes suivantes
ont contribué à cette extension.

Contributeurs

 *   [ adinax0926 ](https://profiles.wordpress.org/adinax0926/)

[Traduisez « Veilo — Invisible Spam Shield » dans votre langue.](https://translate.wordpress.org/projects/wp-plugins/veilo)

### Le développement vous intéresse ?

[Parcourir le code](https://plugins.trac.wordpress.org/browser/veilo/), consulter
le [SVN dépôt](https://plugins.svn.wordpress.org/veilo/), ou s’inscrire au [journal de développement](https://plugins.trac.wordpress.org/log/veilo/)
par [RSS](https://plugins.trac.wordpress.org/log/veilo/?limit=100&mode=stop_on_copy&format=rss).

## Journal des modifications

#### 1.1.0

 * Current release.

## Méta

 *  Version **1.1.0**
 *  Dernière mise à jour **il y a 2 semaines**
 *  Installations actives **Moins de 10**
 *  Version de WordPress ** 5.8 ou plus **
 *  Testé jusqu’à **7.0.4**
 *  Version de PHP ** 7.4 ou plus **
 *  Langue
 * [English (US)](https://wordpress.org/plugins/veilo/)
 * Étiquettes
 * [anti-spam](https://fr.wordpress.org/plugins/tags/anti-spam/)[comments](https://fr.wordpress.org/plugins/tags/comments/)
   [forms](https://fr.wordpress.org/plugins/tags/forms/)[security](https://fr.wordpress.org/plugins/tags/security/)
   [spam](https://fr.wordpress.org/plugins/tags/spam/)
 *  [Vue avancée](https://fr.wordpress.org/plugins/veilo/advanced/)

## Évaluations

Aucun avis n’a encore été envoyé.

[Votre avis](https://wordpress.org/support/plugin/veilo/reviews/#new-post)

[Tout voir](https://wordpress.org/support/plugin/veilo/reviews/)

## Contributeurs

 *   [ adinax0926 ](https://profiles.wordpress.org/adinax0926/)

## Support

Quelque chose à dire ? Besoin d’aide ?

 [Voir le forum de support](https://wordpress.org/support/plugin/veilo/)