Brute-Force and Scan Detector for Access Logs (401, 404 Bursts, Probe Paths)

Finds failed login bursts, 404 bursts and probe path requests per IP.

Use the tool

Why this tool exists

Public servers are probed all day. The useful question is which IPs look automated and what they asked for. This tool applies three simple rules.

A burst of 401 or 403 on a login-like path, a burst of 404 responses, and a short list of well-known probe patterns such as wp-login.php or .env. A match is worth a look, not proof of an attack. Shared NAT addresses and monitoring tools can trigger the rules.

How to use it

  1. Paste the access log.
  2. Set the window and thresholds.
  3. Read the IP list and the reasons.
  4. Block or rate-limit only after checking.

Frequently asked questions

Does it block anything?

No. It only reads text.

Why is a probe on a 404 still listed?

The request itself is the signal. A 404 means the server had nothing there.

Which probe patterns?

WordPress login, dot files, database admin tools, shell and PHPUnit paths, path traversal, JNDI strings, SQL injection patterns and some admin paths.

Is my log uploaded?

No. Everything is processed in your browser and nothing is sent. Logs can hold IP addresses and tokens, so the page does not write them into the address bar.