Allow/Deny by IP and CIDR ranges

Feature IP / CIDR rules — Allow or block specific IP addresses or CIDR ranges (e.g., 203.0.113.0/24). How it works CIDR support lets you handle office networks, known providers, or abusive subnets efficiently while keeping the rules list short. How to access / enable WP Admin → AegisSpamGuard → Allow/Deny Add a rule for an IP or CIDR range Choose Allow or Deny and save. Recommended setting Recommended: Allowlist trusted office/VPN IPs; deny only when you have repeated confirmed abuse. Over-blocking IP ranges can affect legitimate users (mobile carriers and shared networks). Why you need this Admins use IP rules to quickly stop persistent offenders and protect internal workflows. Additional information

Allow/Deny lists overview

Feature Allow/Deny lists — Create rules that always allow trusted sources or always block known spam sources. How it works Rules are applied during scoring and (where applicable) during firewall checks. This gives you deterministic control over outcomes regardless of signal noise. How to access / enable WP Admin → AegisSpamGuard → Allow/Deny Recommended setting Recommended: Add allow rules for your team/testing IPs and block repeat offenders. Lists provide immediate control and reduce reliance on heuristic scoring alone. Why you need this Admins need deterministic overrides—especially on business-critical forms and checkout. Additional information

Firewall velocity threshold (10-minute burst control)

Feature Firewall velocity threshold — Limits rapid repeat hits from the same fingerprint within a rolling time window at the firewall layer. How it works If a visitor or bot hits too many pages quickly, AegisSpamGuard can challenge or block before WordPress performs heavier work. How to access / enable WP Admin → AegisSpamGuard → Settings Firewall section Set the “Firewall velocity threshold (10m)” value. Recommended setting Recommended: Start conservative (higher number), then tighten. You don’t want to block legitimate users browsing quickly; tune after watching the Firewall log. Why you need this Admins use this to stop aggressive crawlers, scrapers, and flood behavior. Additional information

Firewall ‘blank page’ response (bot-unfriendly block)

Feature Firewall returns blank page — When blocking at the firewall layer, return a simple blank/fast response instead of a friendly error page. How it works Bots learn from rich error pages; a minimal response is faster and reveals less information while still stopping abusive traffic. How to access / enable WP Admin → AegisSpamGuard → Settings Firewall section Toggle “Firewall returns blank page” ON/OFF. Recommended setting Recommended: ON for public sites. It’s faster and less informative to bots while still being safe for humans (humans rarely see firewall blocks). Why you need this Admins who care about performance and reducing bot feedback loops benefit from this. Additional information

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

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

Categories: AegisSpam
Allow/Deny by IP and CIDR ranges
read more
Categories: AegisSpam
Allow/Deny lists overview
read more
Categories: AegisSpam
Firewall velocity threshold (10-minute burst control)
read more
Categories: AegisSpam
Firewall ‘blank page’ response (bot-unfriendly block)
read more
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

News & Events