Auth log analyzer
Paste SSH or sudo log lines to spot brute-force attempts, successful logins after failures, and suspicious patterns.
Runs in your browser ยท nothing is sentLogs & configNew
Paste auth log lines to see the result.
How to use
- Export or copy the relevant lines, for example with "grep sshd /var/log/auth.log" or "journalctl -u sshd --since today".
- Paste them into the tool.
- Review the findings, grouped by pattern.
- Check the recognized events table for per-line detail.
Common scenarios
Paste recent auth log lines to see whether there was a brute-force attempt and, more importantly, whether it ever succeeded.
Check regularly for root login attempts and unusual scanning patterns, as a complement to automated monitoring.
About this tool
Paste lines from /var/log/auth.log, /var/log/secure, or "journalctl -u sshd"/"journalctl _COMM=sudo", and the tool recognizes the patterns most often looked for in a security review: brute-force attempts (many failed logins from one IP), a successful login from an IP that previously failed, several invalid usernames tried from one IP (typical scanning), and any attempt to log in as root. Every recognized line is also shown individually with its type, user and IP. Nothing is sent anywhere; the log lines stay in your browser.
๐ Your input stays in your browser and is never sent anywhere.
Frequently asked questions
What log format does this understand?
The standard syslog style ("Jan 10 03:14:01 host sshd[1234]: ...") and journalctl's ISO timestamp style ("2024-01-10T03:14:01+0100 host sshd[1234]: ..."), for both sshd and sudo lines.
After how many failures is something flagged as brute-force?
From 5 failed attempts (wrong password, invalid user, or failed key authentication) from the same IP address within the pasted lines.
Does this connect to my server to fetch logs?
No. You paste a copy of the lines yourself; the tool never connects to a server or logging system.
What to do next
Found a problem or have a suggestion? Tell us