frequently asked questions
(No Gimmicks, No CC,No Commitment, Free Features, Stay Free If You Prefer!)
Feature
Geo/ASN provider framework (hook/provider selection support)
Description
Provider abstraction for geo/asn.
How it works
AegisWAF applies this capability inside the Bot Control module. The engine evaluates configuration, applies matching (path/method/tokens/counters/providers), then records evidence into the event log and executes the configured enforcement action when conditions are met.
How to access / Enable or disable
- Access: AegisWAF → Bot Control
- Enable/Disable: Use the module toggle/switch on this screen (or the relevant category toggle) to enable/disable.
Recommended setting
Only block geos/ASNs you are confident are abusive for your site; log first if uncertain.
Feature
Comments cleanup — Re-scores existing comments and lets you apply actions: Report-only, Move to Spam, or Delete.
How it works
The tool processes comments in batches to avoid shared-host issues. It can optionally skip logging (so cleanup doesn’t pollute live spam logs).
How to access / enable
- WP Admin → AegisSpamGuard → Cleanup
- Choose “Comments cleanup”
- Run Report-only first, then choose Move to Spam or Delete.
Recommended setting
Recommended: Move to Spam (safe default).
You can recover mistakes from Spam; deletion is permanent and should be used only after validation.
Why you need this
Admins need to remove existing spam to improve SEO, trust, and site usability.
Additional information
Description
Tools to diagnose sitemap access issues.
How it works
Checks permalinks/rewrite and outputs correct headers.
How to access / enable
Tools → Diagnostics.
Recommended setting
Use Post Name permalinks.
Description
Sets your site identity so schema outputs correct “publisher” and “about” signals.
How it works
Stores site_type and uses it as base schema entity (Organization/Person).
How to access / enable
AegisSEO → Setup Wizard → Site Type → Save.
Recommended setting
Organization for businesses/brands; Person for personal blogs/portfolios.
Description: Enforces password complexity requirements by role (Pro).
How it works: When enabled, AegisShield validates new passwords against configured rules (length and character requirements) and rejects weak passwords.
How to access / configure:
- WP Admin → AegisShield → Hardening → Password Policy.
- Enable strong password enforcement.
- Configure requirements and Save Changes.
Recommended setting: Enforce for administrators and editors at minimum; require 12+ characters with mixed classes.
Feature
Managed Rules: Path Traversal category toggle
Description
Enable/disable traversal managed rules.
How it works
AegisWAF applies this capability inside the WAF Rules module. The engine evaluates configuration, applies matching (path/method/tokens/counters/providers), then records evidence into the event log and executes the configured enforcement action when conditions are met.
How to access / Enable or disable
- Access: AegisWAF → WAF Settings (Rules section)
- Enable/Disable: Use the toggle on this screen to turn it ON or OFF, then click Save.
Recommended setting
Start conservative (LOG or Challenge) for new deployments; tighten to Block once you confirm low false positives.
Description: Edit allows you to update a short link’s target, slug options, tracking, groups/tags, and UTMs.
How it works: AegisLink loads the existing short link post and updates metadata on save.
How to access / enable: WP Admin → AegisLink → ShortURL Links → Manage → Edit.
Recommended setting: Edit rather than delete when campaigns move; preserve history and analytics continuity where possible.
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
Feature
Logs retention cleanup job
Description
Auto-deletes events older than retention days (PRO).
How it works
AegisWAF applies this capability inside the Logs / Attack Story module. The engine evaluates configuration, applies matching (path/method/tokens/counters/providers), then records evidence into the event log and executes the configured enforcement action when conditions are met.
How to access / Enable or disable
- Access: AegisWAF → Logs / Attack Story
- Enable/Disable: Use the module toggle/switch on this screen (or the relevant category toggle) to enable/disable.
Recommended setting
Set 30 days retention for most sites; shorten to 7–14 days on small databases.
FREE: Not available.
PRO: Available.
What it does: Updates prefix-dependent keys.
How to use it properly: Mandatory for prefix changes.
Feature
Attack Story Narrative analysis generation (incident-style explanation)
Description
Narrative incident summaries.
How it works
AegisWAF applies this capability inside the Logging & Evidence module. The engine evaluates configuration, applies matching (path/method/tokens/counters/providers), then records evidence into the event log and executes the configured enforcement action when conditions are met.
How to access / Enable or disable
- Access: AegisWAF → Logs / Attack Story
- Enable/Disable: Use the module toggle/switch on this screen (or the relevant category toggle) to enable/disable.
Recommended setting
Start conservative (LOG or Challenge) for new deployments; tighten to Block once you confirm low false positives.
Description
Suggests internal links to related content.
How it works
Matches keywords/title/taxonomy terms against other posts.
How to access / enable
Linking Assistant tab.
Recommended setting
Link to cornerstone pages first.
Description: Add custom directives to CSP when you need advanced control (Pro).
How it works: builder_extra_directives and builder_extra_mode append additional CSP rules beyond the guided fields.
How to access / configure:
- WP Admin → AegisShield → Security Headers → CSP Builder.
- Enter extra directives.
- Save and test.
Recommended setting: Only use if you understand CSP; validate directives to avoid breaking the site.
Feature
Inspection scope: Body
Description
Enable body inspection during rule evaluation.
How it works
AegisWAF applies this capability inside the WAF Rules module. The engine evaluates configuration, applies matching (path/method/tokens/counters/providers), then records evidence into the event log and executes the configured enforcement action when conditions are met.
How to access / Enable or disable
- Access: AegisWAF → WAF Settings (Rules section)
- Enable/Disable: Use the module toggle/switch on this screen (or the relevant category toggle) to enable/disable.
Recommended setting
Start conservative (LOG or Challenge) for new deployments; tighten to Block once you confirm low false positives.
Feature
TOR / Proxy Signals
Description
Detect/block TOR/proxy signals.
How it works
AegisWAF applies this capability inside the Geo & ASN Protection module. The engine evaluates configuration, applies matching (path/method/tokens/counters/providers), then records evidence into the event log and executes the configured enforcement action when conditions are met.
How to access / Enable or disable
- Access: AegisWAF → Bot Control (Geo/ASN) / API Shield (if exposed)
- Enable/Disable: Use the module toggle/switch on this screen (or the relevant category toggle) to enable/disable.
Recommended setting
Start conservative (LOG or Challenge) for new deployments; tighten to Block once you confirm low false positives.
Description: Visualizes relative risk across modules so you can see where attention is needed.
How it works: Each module contributes a risk score based on its findings (e.g., lockouts, file changes, malware suspects, header posture).
How to access / configure:
- WP Admin → AegisShield → Dashboard.
- View “Module Risk Index (7d)”.
- Open the highest-risk module and address findings.
Recommended setting: Prioritize high-risk modules first; aim to keep all modules at low/medium risk.
Description: Controls how often incremental quick scans run when enabled.
How it works: quick_schedule_frequency determines the cadence (e.g., hourly/daily) for quick scan execution.
How to access / configure:
- WP Admin → AegisShield → Malware Scan → Incremental / Quick Scan.
- Set quick scan frequency.
- Save changes.
Recommended setting: Daily is usually enough; use more frequent scans only if your hosting can handle it.
Description: Forces browsers to use HTTPS for your site, reducing downgrade and cookie hijacking risks.
How it works: When enable_hsts is on, AegisShield sends the Strict-Transport-Security header so browsers remember to use HTTPS.
How to access / configure:
- WP Admin → AegisShield → Security Headers.
- Enable HSTS.
- Confirm your site is fully HTTPS first, then Save Changes.
Recommended setting: Enable only after confirming HTTPS is permanent and working across all subpages.
Feature
Managed Rule categories (always available): SQLi / XSS / Path Traversal
Description
Core OWASP categories.
How it works
AegisWAF applies this capability inside the WAF Rules module. The engine evaluates configuration, applies matching (path/method/tokens/counters/providers), then records evidence into the event log and executes the configured enforcement action when conditions are met.
How to access / Enable or disable
- Access: AegisWAF → WAF Settings (Rules section)
- Enable/Disable: Use the module toggle/switch on this screen (or the relevant category toggle) to enable/disable.
Recommended setting
Start conservative (LOG or Challenge) for new deployments; tighten to Block once you confirm low false positives.
Feature
Enable WordPress protection layer (master switch)
Description
Master switch for WP protection layer.
How it works
AegisWAF applies this capability inside the API Shield module. The engine evaluates configuration, applies matching (path/method/tokens/counters/providers), then records evidence into the event log and executes the configured enforcement action when conditions are met.
How to access / Enable or disable
- Access: AegisWAF → API Shield
- Enable/Disable: Use the toggle on this screen to turn it ON or OFF, then click Save.
Recommended setting
Start conservative (LOG or Challenge) for new deployments; tighten to Block once you confirm low false positives.
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
Description
Default archive meta description template.
How it works
Uses desc_archive; term description may be used.
How to access / enable
Global SEO → Titles & Meta → Archive Meta Description Template.
Recommended setting
Write category descriptions for top categories.
Feature
Endpoint Policies framework (per-path policy match + applied logging)
Description
Per-endpoint policy matching framework.
How it works
AegisWAF applies this capability inside the WAF Rules module. The engine evaluates configuration, applies matching (path/method/tokens/counters/providers), then records evidence into the event log and executes the configured enforcement action when conditions are met.
How to access / Enable or disable
- Access: AegisWAF → WAF Settings (Rules section)
- Enable/Disable: Use the module toggle/switch on this screen (or the relevant category toggle) to enable/disable.
Recommended setting
Start conservative (LOG or Challenge) for new deployments; tighten to Block once you confirm low false positives.
FREE: Not available.
PRO: Available.
What it does: Allows fine-tuned lockout thresholds.
How to use it properly: Use stricter rules for admins.
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