Home / Documentation / Testing Tools and Site Health
TMB Bot Guard

Testing Tools and Site Health

Validate protection, analytics, assets, and runtime status without waiting for uncontrolled traffic.

Quick Actions

ActionWhat it checks
Add Test StrikeCreates controlled strike activity so you can verify Strike Management, Activity Logs, the configured threshold, and clearing behavior.
Reset Test DataRemoves data created by the plugin’s testing workflow. It is not a substitute for Clear All Strikes when unrelated live records exist.
Test GA4 EventQueues a controlled security event through the selected analytics connection. Verify it at the GA4/GTM destination.

Plugin Status cards

  • Suspicious IPs: addresses with active strike records.
  • Strike Threshold and Cooldown: current enforcement values.
  • GA4 Events and Configuration: whether tracking is enabled and how it is connected.
  • Block Mode: access-denied or redirect experience.
  • Diagnostic Mode: whether additional troubleshooting detail is active.
  • Detection Mode: Standard or Cache Compatibility and its WordPress entry point.
  • Development Entitlement: visible only for an authorized signed development setup.

System Health on Settings

The System Health summary reports cache-script availability, trusted proxy configuration, cleanup scheduling and last run, license connectivity, and schema version. A “Not run yet” cleanup result can be normal immediately after installation.

WordPress Site Health

Open Tools → Site Health to review runtime conditions and plugin checks. Use it when an asset is missing, scheduled cleanup is unavailable, or a hosting restriction prevents a module from operating.

Controlled live-request testing

  1. Use a separate browser session and a normal front-end HTML page.
  2. Do not test while logged in or from a whitelisted address.
  3. Use a clearly suspicious test browser identifier.
  4. Confirm one page visit produces one strike; icons, images, scripts, and styles should not add strikes.
  5. Clear the controlled record immediately after testing.
Diagnostic Mode is temporary. It adds troubleshooting detail and more frequent status checks. Disable it when the investigation is complete to avoid unnecessary debug-log growth.