Retention & purge (data minimization)

Feature Log retention and purge — Automatically purges old log entries to reduce database bloat and minimize stored data. How it works A scheduled cleanup removes events older than your retention window. This keeps performance stable on shared hosting. How to access / enable WP Admin → AegisSpamGuard → Settings Privacy / retention section (if present) Set retention days and save. Recommended setting Recommended: 30–90 days depending on traffic. Most tuning and audits happen in the first few weeks; keeping 1–3 months is usually enough without bloating the DB. Why you need this If you are investigating an incident, temporarily increase retention. Additional information

External disposable list URL

Feature External disposable list URL — Optionally fetch a disposable email domain list from a URL (requires external calls). How it works If enabled, AegisSpamGuard downloads a list periodically and caches it. This improves coverage beyond the built-in local list. How to access / enable WP Admin → AegisSpamGuard → Settings Identity module settings Set external list URL and enable the toggle. Recommended setting Recommended: Leave OFF if “No external calls” is ON; otherwise enable only from trusted sources. External lists can add coverage but introduce network dependency—use only if you trust the source and caching works on your host. Why you need this Use caching intervals to reduce bandwidth and avoid timeouts. Additional information

Trust existing users older than N days

Feature Trust users older than N days — Applies a trust boost to accounts older than a configurable age, reducing false positives for established users. How it works Older accounts are statistically lower risk; this setting lets you encode that into scoring. How to access / enable WP Admin → AegisSpamGuard → Settings Trust settings section Set “Trust existing user if older than N days”. Recommended setting Recommended: 7–14 days for most sites. A week is enough to separate drive-by spam from normal members without granting immediate trust to new signups. Why you need this Admins improve UX for established users while keeping defenses strong for new accounts. Additional information

Trust WooCommerce customers

Feature Trust WooCommerce customers — Applies a trust boost to known customers to avoid blocking legitimate orders and support requests. How it works When enabled, the engine checks user/customer status and reduces risk score or avoids harsh enforcement for trusted customers. How to access / enable WP Admin → AegisSpamGuard → Settings Trust settings section Toggle “Trust WooCommerce customers”. Recommended setting Recommended: ON for stores. Real customers should not see friction at checkout; trust reduces false positives where it matters most. Why you need this Combine with allowlist rules for staff and service providers. Additional information

Trust logged-in users

Feature Trust logged-in users — Reduces score or bypasses certain checks for authenticated users to minimize false positives. How it works If enabled, the engine treats logged-in users as lower risk (configurable), which helps membership and community sites. How to access / enable WP Admin → AegisSpamGuard → Settings Trust settings section Toggle “Trust logged-in users”. Recommended setting Recommended: ON for membership/community sites; OFF for open registrations with frequent compromised accounts. Trusted sessions reduce friction for real users; turn off only if you see abuse from compromised accounts. Why you need this Admins keep UX smooth for known users while still protecting public endpoints. Additional information

AegisForm integration

Feature AegisForm protection — First-class protection for AegisForm submissions with JS proof and scoring. How it works Because AegisForm is part of your ecosystem, AegisSpamGuard can integrate tightly: consistent tokens, clean event shapes, and shared UI/UX expectations. How to access / enable WP Admin → AegisSpamGuard → Settings Enable JS proof + honeypot. Ensure AegisForm is active; integration runs automatically. Recommended setting Recommended: Keep enabled (default). It gives your product suite a cohesive, premium ‘works together’ experience. Why you need this If you rename form fields, AegisSpamGuard still scores generically via normalized payload. Additional information

Gravity Forms integration

Feature Gravity Forms protection — Adds JS proof and scoring to Gravity Forms submissions. How it works Hooks into Gravity Forms validation; injects/validates proof token and scores content + behavior. Enforcement follows the same policy bands as other vectors. How to access / enable WP Admin → AegisSpamGuard → Settings Enable JS proof for forms. Ensure Gravity Forms is active; integration activates automatically. Recommended setting Recommended: JS proof ON; progressive delay ON for Challenge band. This reduces bot throughput while keeping real users unaffected. Why you need this Review the Spam Log for ‘challenge’ decisions to tune thresholds. Additional information

Feature WPForms protection — Injects JS proof and scores WPForms submissions to stop form spam without CAPTCHAs. How it works Uses WPForms hooks to add a proof token and then validates it during submission. Missing/invalid proofs add score; combined with other signals, this stops headless bots. How to access / enable WP Admin → AegisSpamGuard → Settings Enable JS proof for forms. Ensure WPForms is active; AegisSpamGuard auto-integrates. Recommended setting Recommended: JS proof ON + honeypot ON. This combination is low-friction but high-signal on modern bot traffic. Why you need this If a WPForms form breaks, add the action/path to allowlists (if you enabled generic AJAX/admin-post protection). Additional information

REST abuse protection

Feature REST request abuse protection — Scores suspicious REST requests to reduce spam and automated abuse of WordPress endpoints. How it works The engine inspects request context, headers, and patterns. Depending on your configuration, it can apply scoring and rate-limit or block abusive requests. How to access / enable WP Admin → AegisSpamGuard → Settings Enable REST protection (if available). Tune firewall/velocity thresholds for best results. Recommended setting Recommended: Enabled on public sites with heavy bot traffic. REST endpoints are commonly probed; early scoring and rate-limiting reduces load and abuse. Why you need this Admins protect site performance and reduce automated scanning noise. Additional information

WooCommerce protection

Feature WooCommerce checkout notes + orders spam protection — Scores WooCommerce checkout submissions and order notes to stop spam and fraud patterns. How it works On checkout-related hooks, AegisSpamGuard analyzes fields and behavior signals; suspicious submissions can be challenged or held before completing workflows (depending on integration points). How to access / enable WP Admin → AegisSpamGuard → Settings Enable WooCommerce protection (if available). Review Held items after enabling. Recommended setting Recommended: Enabled on stores. Stores are a high-value target; adding this layer reduces bogus orders and spammy notes without CAPTCHAs. Why you need this Admins protect revenue, reduce operational noise, and keep customer experience clean. Additional information

Archives: FAQs | Aegisify - WordPress Tools, Security…

Categories: AegisSpam
Retention & purge (data minimization)
read more
Categories: AegisSpam
External disposable list URL
read more
Categories: AegisSpam
Trust existing users older than N days
read more
Categories: AegisSpam
Trust WooCommerce customers
read more
Categories: AegisSpam
Trust logged-in users
read more
Categories: AegisSpam
AegisForm integration
read more
Categories: AegisSpam
Gravity Forms integration
read more
Categories: AegisSpam
WPForms integration
read more
Categories: AegisSpam
REST abuse protection
read more
Categories: AegisSpam
WooCommerce protection
read more

What’s New At Aegisify