No external calls mode (privacy-first master toggle)

Feature No external calls (master toggle) — Disables outbound HTTP calls so the plugin runs fully local-first. How it works When enabled, AegisSpamGuard skips external disposable list fetches, external reputation, and optional geo providers that require downloads/calls (depending on your configuration). How to access / enable WP Admin → AegisSpamGuard → Settings Privacy defaults Enable “No external calls”. Recommended setting Recommended: ON for strict privacy / offline environments. This ensures no data leaves the site and removes network dependency. Why you need this Admins with privacy constraints or locked-down hosting can still run strong anti-spam without SaaS. Additional information

IP handling mode (store / anonymize / hash / off)

Feature IP handling mode — Controls how IP addresses are stored and used in logs and rules: full store, anonymize, hash, or disable IP storage entirely. How it works AegisSpamGuard can still function with reduced IP storage by relying more on fingerprinting and content/behavior signals. Hash/anonymize modes preserve privacy while supporting rate limiting and reputation. How to access / enable WP Admin → AegisSpamGuard → Settings Privacy defaults Set “IP handling mode”. Recommended setting Recommended: Hash or Anonymize for most sites; Store only if you need strict IP auditing. Hash/anonymize reduces personal data footprint while keeping anti-abuse effectiveness. Why you need this Admins need flexibility to match privacy policy requirements and regional compliance. Additional information

Per-site salt for email hashing

Feature Per-site salted email hashing — Hashes email identities with a unique per-site salt so stored identifiers can’t be reused across sites. How it works The salt is generated on activation and used when computing email_hash. This improves privacy while still allowing allow/deny and reputation features. How to access / enable WP Admin → AegisSpamGuard → Settings Privacy defaults Ensure per-site hashing is enabled (default). Recommended setting Recommended: Keep enabled (default). It protects user privacy and still allows consistent per-site identity reputation. Why you need this Admins can stay privacy-forward (and GDPR-friendly) without sacrificing control. Additional information

Local ML (Naive Bayes) and training workflow

Feature Local ML (Naive Bayes) — A lightweight local classifier that learns from your site’s own spam vs not-spam decisions. How it works Tokens are normalized (URLs/emails/numbers become special tokens). Training updates a local DB table so ML becomes one signal in your score, not the entire decision. How to access / enable WP Admin → AegisSpamGuard → Settings Enable “Local ML” (if present) and set ML weight. Go to Spam Log → select events → Train Spam / Train Not Spam. Recommended setting Recommended: ON with a modest weight (e.g., 8–15 points). Keeping ML as a small signal prevents model drift from overpowering strong deterministic signals like honeypot or deny rules. Why you need this Admins get site-specific learning without sending data to a cloud service. Additional information

Similarity to known spam (site-local reputation)

Feature Similarity to known spam — Scores new submissions by comparing them to spam previously blocked on your site. How it works AegisSpamGuard stores fingerprints and patterns from blocked events and checks similarity within a lookback window. Similar messages get points even if they change slightly. How to access / enable WP Admin → AegisSpamGuard → Settings Content module settings Enable similarity and set lookback + threshold. Recommended setting Recommended: ON with 30-day lookback and ~0.72 threshold to start. This catches evolving spam campaigns while reducing false positives by requiring high similarity. Why you need this Admins benefit because spam waves usually reuse templates—similarity detection breaks that advantage. Additional information

Optional MX checks (email existence signal)

Feature Domain MX checks — Optionally checks if the email domain has valid MX records (cached) to detect obviously fake addresses. How it works If enabled, AegisSpamGuard performs a DNS lookup and caches results so the check is fast after the first run. Failed MX can add points or trigger Challenge/Hold depending on policy. How to access / enable WP Admin → AegisSpamGuard → Settings Identity module settings Toggle “Enable MX checks” ON/OFF. Recommended setting Recommended: OFF on shared hosting unless you verify DNS performance; enable after testing. DNS lookups can be slow or blocked in some environments—test first to avoid latency. Why you need this Admins who rely on email deliverability and quality can use this to reduce fake signups. Additional information

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

Archives: FAQs | Aegisify - WordPress Tools, Security…

Categories: AegisSpam
No external calls mode (privacy-first master toggle)
read more
Categories: AegisSpam
IP handling mode (store / anonymize / hash / off)
read more
Categories: AegisSpam
Per-site salt for email hashing
read more
Categories: AegisSpam
Local ML (Naive Bayes) and training workflow
read more
Categories: AegisSpam
Similarity to known spam (site-local reputation)
read more
Categories: AegisSpam
Optional MX checks (email existence signal)
read more
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

What’s New At Aegisify