WordPress - Login Page Reachability
94-wordpress-login-page.yaml
HTTP(S)
What this example does
WordPress operations: WordPress - Login Page Reachability. Use it for routine availability checks, post-update verification and incident triage.
Checks and behavior
- Sends an GET request to https://www.example.com/wp-login.php.
- Checks allowed/denied HTTP status codes.
- Validates required, forbidden or matching HTTP headers.
- Looks for expected response content and/or rejects known error markers.
- TLS settings cover certificate trust, certificate expiry.
- Formats results for nagios output.
Adapt example domains, addresses, credentials and thresholds to your environment before use.
YAML configuration
# Copyright (c) 2026 mati peterson. Maintainer: mati peterson <ipsonic@mailbox.org>. Project: https://ipsonic.com/probe/. Disclaimer: Provided AS IS, without warranty of any kind. Use at your own risk; validate checks and configurations before production use.
# Optional WordPress login page reachability check; no credentials or login attempt.
# Some sites intentionally block or rename wp-login.php; adapt to local policy.
name: "WordPress - Login Page Reachability"
url: "https://www.example.com/wp-login.php"
request:
method: GET
user_agent: "ipsonic-probe-wordpress/1.0"
follow_redirects: false
timeouts:
connect: 3
response: 10
tls:
verify: true
min_valid_days: 30
tests:
status:
allow: [200]
headers:
contains:
Content-Type: [text/html]
body:
contains: ["loginform"]
monitoring:
service_name: "WordPress Login Page"
output: nagios
on_failure: critical