Who is requesting my site?
See top source IPs, paths, user agents when recorded, and exact HTTP status codes. Open a count to inspect matching lines.
PRIVATE, BROWSER-BASED TOOL
WordPress log analyzer for access and error logs.
Paste logs or add files from cPanel, a VPS, or your host. Find suspicious requests, PHP fatal errors, traffic patterns, and the lines behind each finding.
1
Add your logs
Choose files from cPanel or your server, or paste log lines below.
Drop log files hereor Access logs, error_log, debug.log, and gzip · up to 512 MB per file
or paste log text
Server timezone (optional)
Your files are processed in this browser. They are not uploaded to a server.
What will I see? A summary, likely issues, practical next steps, and the log lines behind each finding.
From raw logs to a useful first answer
1. Add your logs
Paste a few lines or choose files from cPanel, your VPS, or your host. Add access and error logs together when available.
2. Review findings
See request patterns, top sources, HTTP failures, PHP fatal errors, and the original lines behind each finding.
3. Investigate further
Trace an IP, filter requests by time or status, and export a PDF summary or matching lines as CSV.
Access, security, and error logs in one place
Are there attack signals?
Find login and XML-RPC bursts, sensitive-file probes, PHP requests in uploads, and broad 404 scans. These are leads to investigate, not a malware verdict.
What caused the error?
Group PHP fatals and compare their timing with 5xx requests. Error messages and stack traces can reveal which component needs inspection.
Before you analyze
Which WordPress logs can I analyze?
Use common or combined Apache and NGINX access logs, PHP and WordPress debug logs, and common web server error logs. Files can be named access.log, debug.log, or extensionless error_log; gzip files are detected from their contents. Custom host formats may need a parser we do not yet support.
Can an access log prove that my WordPress site was hacked?
No. It can show suspicious requests, source IPs, paths, HTTP responses, and timing. A 200 response does not prove that code ran or a login succeeded. Compare the clues with WordPress activity, WAF events, and changed files before drawing a conclusion.
Why did WordPress show a fatal error?
An error log can identify the fatal message, affected plugin or theme path when recorded, and repeated occurrences. LogScope groups these entries and suggests checks. The log may point to a likely cause, but an access log alone cannot explain a PHP fatal error.
Do my log files leave my device?
The analyzer reads files and pasted text in your browser. The app does not upload them to an analysis server or save them in an account. Exported PDF and CSV files are created only when you download them.
What happens with a very large log?
The browser accepts individual files up to 512 MB and gzip data up to 1 GB after expansion. Summary counts scan every recognized record. Detailed findings and searchable lines keep the first 100,000 and last 20,000 parsed records, so incidents in the omitted middle can be missed.