Feature
JS proof token — Uses a lightweight JavaScript-generated proof token so non-browser bots are penalized, and replay is reduced.
How it works
A one-time nonce/token is created per form/session; missing or invalid proofs add score. This helps stop headless/bot POSTs that skip executing JS.
How to access / enable
- WP Admin → AegisSpamGuard → Settings
- Challenges/Forms section (varies by build)
- Toggle “JS proof token” ON/OFF.
Recommended setting
Recommended: ON for forms.
It improves detection without forcing CAPTCHAs; bots that don’t run JS get flagged.
Why you need this
Admins get better protection with minimal UX cost.
Additional information