This IP address has been reported a total of
73
times from
57 distinct
sources.
34.22.126.70 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
United States of America
with 16
reports;
Germany
with 14
reports;
Netherlands
with 11
reports.
The most common categories in these recent reports were:
Web App Attack
54
times;
Brute-Force
27
times;
Bad Web Bot
26
times;
Hacking
16
times;
Port Scan
5
times;
Other
10
times.
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-08.
show less
[Laravel HoneypotPlus] Automated report - Honeypot access detected on path: /.env.js via rule: regex ...
show more[Laravel HoneypotPlus] Automated report - Honeypot access detected on path: /.env.js via rule: regex:/^\/\.env/i
show less
(badbots) Bad bot user-agent [redacted] from 34.22.126.70 (BE/Belgium/70.126.22.34.bc.googleusercont ...
show more(badbots) Bad bot user-agent [redacted] from 34.22.126.70 (BE/Belgium/70.126.22.34.bc.googleusercontent.com)
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-09T04:09:19.990852298Z. Context: http_status=200
show less
Web App Attack
Anonymous
(mod_security) mod_security triggered on hostname [redacted] 34.22.126.70 (BE/Belgium/70.126.22.34.b ...
show more(mod_security) mod_security triggered on hostname [redacted] 34.22.126.70 (BE/Belgium/70.126.22.34.bc.googleusercontent.com): (CF_ENABLE)
show less
