Clearer answers from WordPress logs.
LogScope helps site owners, developers, and hosting support teams turn raw access and error logs into a useful first investigation.
What the tool does
Add logs from cPanel, a VPS, or a hosting provider, or paste a small excerpt. The analyzer reads common Apache and NGINX access formats, WordPress and PHP errors, and common server error logs. It summarizes traffic, HTTP failures, suspicious request patterns, and fatal errors, then links findings to their source lines.
You can inspect top IPs, requested paths, user agents when recorded, and exact HTTP status codes. Filters help trace one source across retained requests. A PDF gives you a portable summary, and CSV exports the lines you selected.
Privacy by design
Analysis runs in your browser. The selected log files and pasted text are not uploaded to an analysis server or saved in a LogScope account. Read the privacy policy for the details that apply to ordinary website visits and downloads.
What findings mean
Logs are evidence, but they are incomplete. A probe is not proof of intrusion; a 200 response is not proof that a login or upload succeeded. A PHP error path is a clue to inspect, not an automatic verdict about a plugin. LogScope states these limits in its report and points to the next checks.
For very large files, summary counts scan all recognized records while detailed findings retain the first 100,000 and last 20,000 parsed records. This can miss an incident in the middle. Collect a narrower log export around the incident and compare it with other evidence.