Disposable email detection (local-first)

Feature Disposable email domains — Detects and scores disposable/temporary email domains to reduce fake leads and spam registrations. How it works The engine checks the email domain against a local list (and optionally a fetched list if you enable it) and adds score if it matches. How to access / enable WP Admin → AegisSpamGuard → Settings Identity module settings Enable disposable detection options if present. Recommended setting Recommended: ON (local list), external list OFF unless you enable external calls. Local lists are privacy-first and stable; external lists can improve coverage but require outbound HTTP. Why you need this Admins improve lead quality and reduce fraudulent signups. Additional information

Content intelligence: link volume + shorteners + spam patterns

Feature Content intelligence — Scores content based on link volume, suspicious TLDs, URL shorteners, and common spam patterns/markup. How it works The engine extracts URLs and normalizes text. More links, known shorteners, and spam keywords increase points—especially when combined with other signals. How to access / enable WP Admin → AegisSpamGuard → Settings Modules & signal groups Ensure “Content intelligence” is enabled. Recommended setting Recommended: ON for most sites. Form spam is heavily content-driven; this catches campaigns that bypass behavioral signals. Why you need this Admins need content checks to stop SEO spam, affiliate spam, and copy/paste spam templates. Additional information

Progressive delay (Challenge band forms only)

Feature Progressive delay challenge — Applies a small, increasing delay only when an event falls into the Challenge band—primarily for forms—to discourage bots while keeping UX reasonable. How it works Instead of blocking, AegisSpamGuard can slow suspicious submissions. Higher Challenge scores receive higher delay within your configured min/max range. How to access / enable WP Admin → AegisSpamGuard → Settings Modules & signal groups Enable “Progressive delay” and set min/max milliseconds. Recommended setting Recommended: ON with 150ms min / 1800ms max. This is usually invisible to humans but costly for bots attempting high-volume submissions. Why you need this Admins reduce spam throughput without hard rejects, which helps conversions. Additional information

JS proof token (anti-replay + bot proof)

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

Honeypot field (invisible bot trap)

Feature Honeypot field — Adds a hidden field to supported forms; bots that fill it get a heavy score increase. How it works Real users don’t see the field, but many bots autofill all inputs. A filled honeypot is a high-confidence signal and should heavily influence scoring. How to access / enable WP Admin → AegisSpamGuard → Settings Challenges/Forms section (varies by build) Toggle honeypot ON/OFF. Recommended setting Recommended: ON for all forms. It’s low friction, high signal, and rarely impacts real users. Why you need this Admins want strong spam reduction without user-visible challenges—honeypots deliver that. Additional information

Velocity window + limit (burst submissions control)

Feature Velocity controls — Detects burst submissions from the same fingerprint (IP/session/user agent + payload patterns). How it works AegisSpamGuard tracks how many submissions happen within a rolling window. If the limit is exceeded, it adds points and may trigger Challenge/Hold/Block depending on your thresholds. How to access / enable WP Admin → AegisSpamGuard → Settings Set “Velocity window (seconds)” and “Velocity limit (submissions per window)”. Save changes. Recommended setting Recommended: Window 600 seconds and limit 5 to start. This catches spam floods without punishing normal users; tune down only if you see heavy bot bursts. Why you need this Admins need burst controls to stop rapid spam waves and protect performance. Additional information

Min seconds to submit (fast-submit bot signal)

Feature Min seconds to submit — Adds score if a form submits too quickly after page load, which is a common bot pattern. How it works AegisSpamGuard tracks a timestamp/token on supported forms and compares it to submission time. Faster-than-human submits get a score bump. How to access / enable WP Admin → AegisSpamGuard → Settings Site-wide protection / Behavior section (varies by build) Set “Min seconds to submit”. Recommended setting Recommended: 3 seconds default; use 5+ for longer forms. Longer forms take time; raising this reduces false positives on multi-field forms. Why you need this Admins use this to catch automated submissions that bypass simple honeypots. Additional information

Policy thresholds (Allow / Challenge / Hold / Block bands)

Feature Policy thresholds — Defines how a score (0–100) maps to actions: Allow, Challenge, Hold, or Block. How it works AegisSpamGuard produces a risk score from signals and applies your thresholds to decide enforcement. This keeps decisions consistent and easy to tune. How to access / enable WP Admin → AegisSpamGuard → Settings Open “Policy thresholds” Set Allow/Challenge/Hold max scores and save. Recommended setting Recommended defaults: Allow 29, Challenge 59, Hold 79. These are balanced defaults that reduce false positives while still giving strong protection via Hold/Challenge bands. Why you need this Admins need predictable policy bands to match business risk tolerance. Additional information

Allow/Deny by phrases and URLs

Feature Phrase/URL rules — Allow or block content that matches specific phrases or URL patterns commonly used in spam. How it works Phrase rules are checked against normalized message content. URL rules help you block known spam destinations or suspicious shorteners. How to access / enable WP Admin → AegisSpamGuard → Allow/Deny Add a phrase or URL rule Choose Allow or Deny and save. Recommended setting Recommended: Start with Deny rules for repeated spam campaigns you see in the log. Targeted phrase/URL rules stop waves immediately with low false positive risk. Why you need this Admins often see repeating spam templates—phrase/URL rules shut them down fast. Additional information

Allow/Deny by email hash / domain

Feature Email/domain rules — Allow or block submissions by email domain or hashed email identity. How it works AegisSpamGuard can hash email values (privacy-safe). Domain rules are useful for blocking disposable domains or allowing trusted corporate domains. How to access / enable WP Admin → AegisSpamGuard → Allow/Deny Add a rule for an email domain (e.g., example.com) or email identity Choose Allow or Deny and save. Recommended setting Recommended: Block known disposable domains; allow your own business/customer domains. Domain rules are high-signal and low maintenance. Why you need this Admins reduce spam registrations and fake leads by controlling email quality. Additional information

FAQs – Page 17 – Aegisify, Inc. – Free WordPress Security Audit and Scans with Agentic AI

Categories: AegisSpam
Disposable email detection (local-first)
read more
Categories: AegisSpam
Content intelligence: link volume + shorteners + spam patterns
read more
Categories: AegisSpam
Progressive delay (Challenge band forms only)
read more
Categories: AegisSpam
JS proof token (anti-replay + bot proof)
read more
Categories: AegisSpam
Honeypot field (invisible bot trap)
read more
Categories: AegisSpam
Velocity window + limit (burst submissions control)
read more
Categories: AegisSpam
Min seconds to submit (fast-submit bot signal)
read more
Categories: AegisSpam
Policy thresholds (Allow / Challenge / Hold / Block bands)
read more
Categories: AegisSpam
Allow/Deny by phrases and URLs
read more
Categories: AegisSpam
Allow/Deny by email hash / domain
read more

News & Events