Log in to view charts and search reports for this IP.
Log In
No reports in the last 60 days
80.169.125.12 has been reported 356
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.
This IP address has been reported a total of
356
times from
167 distinct
sources.
80.169.125.12 was first reported on
, and the most recent report was
.
Fail2Ban sshd: repeated SSH login failures (possible brute-force) detected by automated security too ...
show moreFail2Ban sshd: repeated SSH login failures (possible brute-force) detected by automated security tooling. Technical log details and local server identifiers intentionally omitted for privacy.
show less
Fail2Ban sshd: repeated SSH login failures (possible brute-force) detected by automated security too ...
show moreFail2Ban sshd: repeated SSH login failures (possible brute-force) detected by automated security tooling. Technical log details and local server identifiers intentionally omitted for privacy.
show less
Fail2Ban sshd: repeated SSH login failures (possible brute-force) detected by automated security too ...
show moreFail2Ban sshd: repeated SSH login failures (possible brute-force) detected by automated security tooling. Technical log details and local server identifiers intentionally omitted for privacy.
show less
Fail2Ban sshd: repeated SSH login failures (possible brute-force) detected by automated security too ...
show moreFail2Ban sshd: repeated SSH login failures (possible brute-force) detected by automated security tooling. Technical log details and local server identifiers intentionally omitted for privacy.
show less
This IP address carried out 113 port scanning attempts on 26-05-2026. For more information or to rep ...
show moreThis IP address carried out 113 port scanning attempts on 26-05-2026. For more information or to report interesting / incorrect findings, give me a shoutout @parthmaniar on Twitter.
show less
2026-05-27T13:49:41.147008+02:00 vpn sshd[102533]: Invalid user jbernal from 80.169.125.12 port 7214 ...
show more2026-05-27T13:49:41.147008+02:00 vpn sshd[102533]: Invalid user jbernal from 80.169.125.12 port 7214
2026-05-27T13:51:42.627536+02:00 vpn sshd[102555]: Invalid user email from 80.169.125.12 port 18082
2026-05-27T13:54:28.482319+02:00 vpn sshd[102561]: Invalid user systemd from 80.169.125.12 port 6115
...
show less
(sshd) Failed SSH login from 80.169.125.12 (GB/United Kingdom/-): 5 in the last 3600 secs; Ports: *; ...
show more(sshd) Failed SSH login from 80.169.125.12 (GB/United Kingdom/-): 5 in the last 3600 secs; Ports: *; Direction: 1; Trigger: LF_SSHD; Logs: May 27 06:46:24 15634 sshd[27578]: Invalid user jbernal from 80.169.125.12 port 8354
May 27 06:46:26 15634 sshd[27578]: Failed password for invalid user jbernal from 80.169.125.12 port 8354 ssh2
May 27 06:51:17 15634 sshd[28121]: Invalid user email from 80.169.125.12 port 8525
May 27 06:51:18 15634 sshd[28121]: Failed password for invalid user email from 80.169.125.12 port 8525 ssh2
May 27 06:52:39 15634 sshd[28228]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.169.125.12 user=root
show less
2026-05-27T13:17:25.536830+02:00 axisverse sshd-session[897223]: Invalid user opc from 80.169.125.12 ...
show more2026-05-27T13:17:25.536830+02:00 axisverse sshd-session[897223]: Invalid user opc from 80.169.125.12 port 27054
2026-05-27T13:19:32.323424+02:00 axisverse sshd-session[901462]: Invalid user lekaren from 80.169.125.12 port 10942
2026-05-27T13:23:45.520526+02:00 axisverse sshd-session[910726]: Invalid user ubuntu from 80.169.125.12 port 13668
...
show less