Explain the recorded brute-force bans of one IP or network in a window of at most 31 days.
POST/api/v1/support/bruteforce-bans/search
Requires nauthilus:history_read; a subject is accepted only with nauthilus:history_detail. Candidate networks are computed from rule prefixes, never scanned; the latest activation before the window start is included. The activating request is never a culprit and crossed is a heuristic.
Request
Responses
- 200
- 400
- 401
- 403
- 422
- 429
- 500
- 503
Processed ban search; evidence may be partial or aggregate-only.
Response Headers
Support history answers are never cached.
Malformed request, window above 31 days, foreign cursor, malformed attempt id, or query parameters.
Authentication is missing or invalid.
The verified caller lacks the required history permission.
The read exceeded the server-side budget; narrow the window or add filters.
The shared history concurrency gate is full; retry later.
Unexpected service failure.
No history source configured, the primary source could not be read completely, the reader account is not read-only or does not enforce budgets, or the time budget expired. Never an empty history.