Log in to view charts and search reports for this IP.
Log In
No reports in the last 60 days
203.130.212.59 has been reported 120
times. The most recent report is from
.
The full history is preserved below and remains searchable. A
0% score reflects the absence of recent activity, but
this is not a guarantee that earlier reports were invalid. Abuse confidence score decays,
naturally, over time, when the abusive activity stops.
IP Abuse Reports for 203.130.212.59:
This IP address has been reported a total of
120
times from
64 distinct
sources.
203.130.212.59 was first reported on
, and the most recent report was
.
User login to application from malicious IP 203.130.212.59.. Threat Score: 0/10 (INFORMATIONAL). Rep ...
show moreUser login to application from malicious IP 203.130.212.59.. Threat Score: 0/10 (INFORMATIONAL). Reported by TangerangKota-CSIRT
show less
User login to application from malicious IP 203.130.212.59.. Threat Score: 0/10 (INFORMATIONAL). Rep ...
show moreUser login to application from malicious IP 203.130.212.59.. Threat Score: 0/10 (INFORMATIONAL). Reported by TangerangKota-CSIRT
show less
User login to application from malicious IP 203.130.212.59.. Threat Score: 0/10 (INFORMATIONAL). Rep ...
show moreUser login to application from malicious IP 203.130.212.59.. Threat Score: 0/10 (INFORMATIONAL). Reported by TangerangKota-CSIRT
show less
Yesterday, this IP was the source of 26 failed authentications targeting 26 unique usernames on our ...
show moreYesterday, this IP was the source of 26 failed authentications targeting 26 unique usernames on our Mail Server at 216.21.193.119.
show less
(smtpauth) Failed SMTP AUTH login from 203.130.212.59 (ID/Indonesia/-): 1 in the last 3600 secs; Por ...
show more(smtpauth) Failed SMTP AUTH login from 203.130.212.59 (ID/Indonesia/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2025-12-31T07:49:20.070014+11:00 mail postfix/submission/smtpd[4166311]: warning: unknown[203.130.212.59]: SASL LOGIN authentication failed: (reason unavailable), [email protected]show less