Spam firewall pre-check (early bot filtering)

Feature Spam firewall pre-check — Evaluates unauthenticated traffic early and can challenge or block suspicious requests before templates load. How it works The firewall applies lightweight checks such as allow/deny rules, velocity by fingerprint, and bot-like header patterns. It can return a blank block page to reduce CPU usage and discourage crawlers. How to access / enable WP Admin → AegisSpamGuard → Settings Open the Firewall section Toggle “Spam firewall pre-check” ON/OFF. Recommended setting Recommended: ON for high-traffic sites; start with conservative thresholds. Early filtering reduces server load, but conservative thresholds avoid impacting real visitors. Why you need this Admins use firewall mode to stop noisy bot traffic and keep the site responsive. Additional information

Firewall log stream (dedicated pre-check log)

Feature Firewall log stream — A dedicated log stream for firewall pre-checks so you can report “blocked X bots before WordPress loaded.” How it works Firewall logging is separate from submission events. It records early actions like CHALLENGE/BLOCK/ALLOW with minimal data (privacy-safe) so you can measure edge protection. How to access / enable WP Admin → AegisSpamGuard → Firewall Recommended setting Recommended: Enable firewall logging when Firewall pre-check is ON. It gives you proof-of-value metrics and helps debug if a legitimate client gets challenged. Why you need this Admins benefit from a clear separation between ‘traffic blocked at the edge’ and ‘spam submission attempts’. Additional information

“What happened?” sidebar (score breakdown per signal)

Feature What happened? (score breakdown) — Explains exactly how the score was calculated and which signals contributed points. How it works The sidebar lists signal groups, their configured weights, and awarded points (e.g., honeypot hit, too-fast submit, velocity exceeded, disposable email). This is the transparency advantage over black-box spam tools. How to access / enable WP Admin → AegisSpamGuard → Spam Log Open an event card Open the “What happened?” panel (score breakdown). Recommended setting Recommended: Use this panel before changing weights. It shows you whether you should adjust thresholds, enable/disable a module, or add an allow/deny rule instead. Why you need this Admins need explainability to safely tune protection without guesswork. Additional information

One-click actions on an event (Allow / Block / Train Spam / Train Not Spam)

Feature One-click actions — Each event includes fast actions so you can immediately correct mistakes and improve future detection. How it works Allow adds positive reputation and can add to allowlist; Block adds negative reputation and can add to denylist; Train updates the local ML tables if enabled. How to access / enable WP Admin → AegisSpamGuard → Spam Log Open an event card Click the action you want: Allow, Block, Train Spam, or Train Not Spam. Recommended setting Recommended: Use Allow for false positives and Block for confirmed spam; train only when you’re confident. Training improves the model—but only if the labels are accurate. Why you need this Admins need rapid controls to keep legitimate users flowing while tightening defenses. Additional information

Bulk action bar (Allow / Block / Train)

Feature Bulk actions — Select multiple log events and apply one action (Allow, Block, Train as spam, Train as not spam) in one click. How it works AegisSpamGuard updates local reputation (allow/deny), optionally updates ML training data, and records the admin action so future scoring improves. How to access / enable WP Admin → AegisSpamGuard → Spam Log Select multiple event checkboxes Choose an action in the bulk bar and apply. Recommended setting Recommended: Bulk-Allow known good campaigns; Bulk-Block obvious spam waves. Bulk actions save time during spikes and help your local model and rules converge faster. Why you need this Admins often face bursts—bulk tools make cleanup and learning practical on busy sites. Additional information

Card rows + expandable event details

Feature Card rows (compact summary + expandable body) — Each log entry shows a compact summary row and expands to reveal full details, reasons, and next actions. How it works The summary focuses on what you need at a glance (score, action, type, timestamp). Expanding reveals signal breakdown, actor info (privacy-safe), payload excerpt, and evidence. How to access / enable WP Admin → AegisSpamGuard → Spam Log Click an event card to expand/collapse details. Recommended setting Recommended: Expand Held/Challenged events before deciding. Reviewing details prevents accidental denies and helps you build accurate allow/deny rules. Why you need this Admins need fast scanning and deep diagnostics in one place—cards make the log readable like a real app, not a raw table. Additional information

Quick filter pills (All / Blocked / Held / Challenged / Allowed)

Feature Quick filter pills — Lets you instantly filter the Spam Log by action band so you can focus on what matters. How it works AegisSpamGuard assigns a policy action from the final score (Allow/Challenge/Hold/Block). The pills filter the log view without changing stored data. How to access / enable WP Admin → AegisSpamGuard → Spam Log Click a pill: All, Blocked, Held, Challenged, or Allowed. Recommended setting Recommended: Check Held daily; check Blocked weekly. Held is where legitimate users may be waiting; Blocked is useful for trend review and firewall brag stats. Why you need this This helps admins triage quickly and keeps review time short. Additional information

Spam Log overview (cards, filters, and reasons)

Feature Spam Log — The Spam Log is the heart of AegisSpamGuard: it lists every scored event with the action taken and the reasons behind the score. How it works Each event stores a normalized event type (comment/form/registration/checkout/review/rest/search/post), a fingerprint, and a breakdown of signal points so you can audit and tune. How to access / enable WP Admin → AegisSpamGuard → Spam Log Recommended setting Recommended: Start by filtering to Held and Challenged. That’s where you’ll find borderline events that teach you what to allowlist or denylist. Why you need this Admins need visibility and control—transparent reasons turn anti-spam from a black box into an operator dashboard. Additional information

Why AegisSpamGuard avoids CAPTCHA

Feature Why we don’t use CAPTCHA — Explains the UX and security rationale for score-based protection instead of CAPTCHA challenges. How it works AegisSpamGuard focuses on behavior + content + identity scoring to stop spam while keeping forms accessible and conversion-friendly. How to access / enable WP Admin → AegisSpamGuard → Dashboard Scroll to “Why we don’t use CAPTCHA” panel. Recommended setting Recommended: Use score-based Challenge/Hold instead of CAPTCHA for most sites. CAPTCHA increases friction and can reduce conversions; score-based challenges are softer and easier on real users. Why you need this Admins need a clear explanation they can share with clients and stakeholders about why protection is strong without CAPTCHA. Additional information

Cleanup impact (legacy spam scanning results)

Feature Cleanup impact — Summarizes the results of your last Cleanup run (e.g., suspicious comments flagged) and links you to the Cleanup tool. How it works Cleanup scans existing database items in safe batches, re-scores them, and lets you choose actions like Report-only, Move to Spam, or Delete. How to access / enable WP Admin → AegisSpamGuard → Dashboard In “Cleanup impact”, click “Open Cleanup”. Recommended setting Recommended: Run Report-only first, then Move to Spam. Report-only validates the scan before making changes; Move to Spam is safer than delete until you confirm accuracy. Why you need this Admins often inherit sites with years of spam—Cleanup makes it fast and safe to get the database back under control. Additional information

Archives: FAQs | Aegisify - WordPress Tools, Security…

Categories: AegisSpam
Spam firewall pre-check (early bot filtering)
read more
Categories: AegisSpam
Firewall log stream (dedicated pre-check log)
read more
Categories: AegisSpam
“What happened?” sidebar (score breakdown per signal)
read more
Categories: AegisSpam
One-click actions on an event (Allow / Block / Train Spam / Train Not Spam)
read more
Categories: AegisSpam
Bulk action bar (Allow / Block / Train)
read more
Categories: AegisSpam
Card rows + expandable event details
read more
Categories: AegisSpam
Quick filter pills (All / Blocked / Held / Challenged / Allowed)
read more
Categories: AegisSpam
Spam Log overview (cards, filters, and reasons)
read more
Categories: AegisSpam
Why AegisSpamGuard avoids CAPTCHA
read more
Categories: AegisSpam
Cleanup impact (legacy spam scanning results)
read more

What’s New At Aegisify