This IP address has been reported a total of
7
times from
5 distinct
sources.
172.56.161.30 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.
[Mon Oct 12 10:57:58.458690 2026] [security2:error] [pid 1783166:tid 140629778626240] [client 172.56 ...
show more[Mon Oct 12 10:57:58.458690 2026] [security2:error] [pid 1783166:tid 140629778626240] [client 172.56.161.30:0] ModSecurity: Access denied with code 403 (phase 1). Match of "pm matomo.staklim-malang.info " against "SERVER_NAME" required. [file "/etc/modsecurity/coreruleset-4.29.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "224"] [id "440235"] [msg "BAD REQUEST Bro"] [data " Matched Data ARGS charset: - Matched Data TX.1: found within Content-Type multipart form Matched Data: ?id= found within SERVER_NAME: staklim-jatim.bmkg.go.id request_line = GET /index.php/prakiraan-iklim/prakiraan-dasarian/prakiraan-dasarian-daerah-potensi-banjir?id=477&start=75 HTTP/1.1 Request URI RAW = /index.php/prakiraan-iklim/prakiraan-dasarian/prakiraan-dasarian-daerah-potensi-banjir?id=477&start=75 Request Basename = prakiraan-dasarian-daerah-potensi-banjir"] [hostname "staklim-jatim.bmkg.go.id"] [uri "/index.php/prakiraan-iklim/prakiraan-dasarian/prakiraan-dasarian-daerah-potensi-banjir"] [unique
...
show less
Fail2Ban: 172.56.161.30 was banned for Aggressive Bad Bot detected by Nginx/Fail2Ban. UA: Mozilla/5. ...
show moreFail2Ban: 172.56.161.30 was banned for Aggressive Bad Bot detected by Nginx/Fail2Ban. UA: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/150.0.0.0 Safari/537.36
show less