This IP address has been reported a total of
52
times from
42 distinct
sources.
34.170.122.231 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 12
reports;
United States of America
with 12
reports;
Netherlands
with 8
reports.
The most common categories in these recent reports were:
Web App Attack
43
times;
Bad Web Bot
21
times;
Brute-Force
16
times;
Hacking
9
times;
SSH
2
times;
Other
1
time.
Recent Reports
We have received reports of abusive activity from this IP address within the last week. It is
potentially still actively engaged in abusive activities.
Auto-ban: single probe for restricted files (.env / backups / admin endpoints). Likely mass-scan on ...
show moreAuto-ban: single probe for restricted files (.env / backups / admin endpoints). Likely mass-scan on 2026-10-06.
show less
XORP (haproxy): 2x HTTP 404/403/500 or handshake failure in 24h. Automated report from log_check_ipt ...
show moreXORP (haproxy): 2x HTTP 404/403/500 or handshake failure in 24h. Automated report from log_check_iptables_generator.sh (xorp.hu)
show less
Web scanner probing for sensitive files (.env, .git, backups) or path traversal. Reported by fail2ba ...
show moreWeb scanner probing for sensitive files (.env, .git, backups) or path traversal. Reported by fail2ban.
show less
CrowdSec detected Web application reconnaissance. Scenario: local/framework-recon. Automatic ban tri ...
show moreCrowdSec detected Web application reconnaissance. Scenario: local/framework-recon. Automatic ban triggered. Detection time (UTC): 2026-10-06T19:29:39.780359806Z. Context: http_status=302
show less
Web App Attack
Anonymous
Bot / scanning and/or hacking attempts: GET /.git/config HTTP/1.1
