Documentation / Site Health Check

Site Health Check

Overview

Teydea Login Security registers a check in the WordPress Site Health tool that validates the plugin’s settings configuration. If the stored settings contain validation errors, the check alerts you so you can resolve them.

Viewing the Check

1. Navigate to Tools → Site Health in the WordPress admin.
2. Look for the Login Security check in the results.

Check Results

Settings Are Valid

When the plugin settings are valid, the check displays:

• Label: “Login Security plugin settings are valid”
• Status: Good (blue Security badge)
• Description: Confirms that settings are valid and password compliance checks are working properly.

Settings Are Invalid

If the settings contain validation errors, the check displays:

• Label: “Login Security plugin settings are invalid”
• Status: Critical
• Description: Includes the first validation error message to help you identify and fix the issue.

Resolving Issues

If the Site Health check reports invalid settings:

1. Navigate to Settings → Login Security.
2. Review your policy configuration for any invalid values (for example, a minimum length exceeding the allowed range).
3. Click Save all settings to re-validate and save the corrected configuration.

The Site Health check updates automatically once the settings are corrected.

Additional PRO Checks

The PRO version registers three more Site Health tests:

• Pwned Passwords API reachable — reports whether your server can reach the HaveIBeenPwned API used by breached password screening. When it cannot, the test explains your configured fail-open or fail-closed behavior so you can catch connectivity problems early.
• Weaklist readable — reports whether the plugin can read the bundled list of common weak passwords used by the weak password list rule. A list counts as unreadable whenever the plugin cannot read it through to the end, whether it is missing, refuses to open, holds nothing, or stops giving up bytes partway through. The test reports critical while an active password policy enables the rule, and recommended when no active policy does, since nothing on the site reads the list in that case. On critical it also names the fail-open or fail-closed behavior you configured.
• Vendor-default account scan health — reports whether the vendor-default account scan is running normally. If the scan has stalled (usually because scheduled tasks are not running), the test recommends opening the Vendor defaults tab to run the scan manually.