This IP address has been reported a total of
30
times from
22 distinct
sources.
34.20.140.122 was first reported on
, and the most recent report was
.
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-08-31.
show less
2026-09-01T05:42:03Z GET /test/.env
2026-09-01T05:42:03Z GET /qa/.env
2026-09-01T05:42:03Z GET /prev ...
show more2026-09-01T05:42:03Z GET /test/.env
2026-09-01T05:42:03Z GET /qa/.env
2026-09-01T05:42:03Z GET /preview/.env
2026-09-01T05:42:03Z GET /beta/.env
2026-09-01T05:42:04Z GET /uat/.env
2026-09-01T05:42:04Z GET /stage/.env
2026-09-01T05:42:04Z GET /development/.env
2026-09-01T05:42:04Z GET /production/.env
2026-09-01T05:42:05Z GET /config/app/.env
2026-09-01T05:42:17Z GET /wp-admin/phpinfo.php
show less
XORP (haproxy): 73x HTTP 404/403/500 or handshake failure in 24h. Automated report from log_check_ip ...
show moreXORP (haproxy): 73x HTTP 404/403/500 or handshake failure in 24h. Automated report from log_check_iptables_generator.sh (xorp.hu)
show less