Log in to view charts and search reports for this IP.
Log In
No reports in the last 60 days
139.59.3.244 has been reported 52
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.
2026-03-19T02:22:14.967384+01:00 server2.gitlab.splendid-hosting.de sshd[329958]: Failed password for invalid user postgres from 139.59.3.244 port 40416 ssh2
2026-03-19T02:22:55.979276+01:00 server2.gitlab.splendid-hosting.de sshd[330076]: Invalid us ...
show more2026-03-19T02:22:14.967384+01:00 server2.gitlab.splendid-hosting.de sshd[329958]: Failed password for invalid user postgres from 139.59.3.244 port 40416 ssh2
2026-03-19T02:22:55.979276+01:00 server2.gitlab.splendid-hosting.de sshd[330076]: Invalid user postgres from 139.59.3.244 port 56306
2026-03-19T02:22:56.150578+01:00 server2.gitlab.splendid-hosting.de sshd[330076]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.3.244
2026-03-19T02:22:58.865943+01:00 server2.gitlab.splendid-hosting.de sshd[330076]: Failed password for invalid user postgres from 139.59.3.244 port 56306 ssh2
2026-03-19T02:23:38.299629+01:00 server2.gitlab.splendid-hosting.de sshd[330188]: Invalid user postgres from 139.59.3.244 port 46424
...
show less
2026-03-19T01:22:08.918090+00:00 de2.cbz.pw sshd[1304366]: Failed password for invalid user postgres from 139.59.3.244 port 33482 ssh2
2026-03-19T01:22:49.916563+00:00 de2.cbz.pw sshd[1304369]: Invalid user postgres from 139.59.3.244 port 59926
2026- ...
show more2026-03-19T01:22:08.918090+00:00 de2.cbz.pw sshd[1304366]: Failed password for invalid user postgres from 139.59.3.244 port 33482 ssh2
2026-03-19T01:22:49.916563+00:00 de2.cbz.pw sshd[1304369]: Invalid user postgres from 139.59.3.244 port 59926
2026-03-19T01:22:50.066872+00:00 de2.cbz.pw sshd[1304369]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.3.244
2026-03-19T01:22:52.290796+00:00 de2.cbz.pw sshd[1304369]: Failed password for invalid user postgres from 139.59.3.244 port 59926 ssh2
2026-03-19T01:23:32.015193+00:00 de2.cbz.pw sshd[1304388]: Invalid user postgres from 139.59.3.244 port 58782
...
show less
Mar 19 01:59:10 Debian-1010-buster-64-minimal sshd[722551]: Invalid user test1 from 139.59.3.244 port 57124
Mar 19 02:00:03 Debian-1010-buster-64-minimal sshd[740641]: Invalid user test2 from 139.59.3.244 port 44276
Mar 19 02:01:00 Debian-1010-buster ...
show moreMar 19 01:59:10 Debian-1010-buster-64-minimal sshd[722551]: Invalid user test1 from 139.59.3.244 port 57124
Mar 19 02:00:03 Debian-1010-buster-64-minimal sshd[740641]: Invalid user test2 from 139.59.3.244 port 44276
Mar 19 02:01:00 Debian-1010-buster-64-minimal sshd[771867]: Invalid user test3 from 139.59.3.244 port 54520
Mar 19 02:07:43 Debian-1010-buster-64-minimal sshd[925849]: Invalid user postgres from 139.59.3.244 port 54522
Mar 19 02:08:23 Debian-1010-buster-64-minimal sshd[941264]: Invalid user oracle from 139.59.3.244 port 58562
...
show less
2026-03-19T01:59:08.250048+01:00 Pi sshd[24208]: Invalid user test1 from 139.59.3.244 port 42874
2026-03-19T02:00:01.140870+01:00 Pi sshd[24226]: Invalid user test2 from 139.59.3.244 port 60590
2026-03-19T02:00:58.196889+01:00 Pi sshd[24241]: Invalid ...
show more2026-03-19T01:59:08.250048+01:00 Pi sshd[24208]: Invalid user test1 from 139.59.3.244 port 42874
2026-03-19T02:00:01.140870+01:00 Pi sshd[24226]: Invalid user test2 from 139.59.3.244 port 60590
2026-03-19T02:00:58.196889+01:00 Pi sshd[24241]: Invalid user test3 from 139.59.3.244 port 41964
2026-03-19T02:07:40.971057+01:00 Pi sshd[24366]: Invalid user postgres from 139.59.3.244 port 37458
2026-03-19T02:08:21.611790+01:00 Pi sshd[24374]: Invalid user oracle from 139.59.3.244 port 49934
show less
Mar 19 01:59:52 box sshd[2544975]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.3.244
Mar 19 01:59:54 box sshd[2544975]: Failed password for invalid user test2 from 139.59.3.244 port 40144 ssh2
Mar 1 ...
show moreMar 19 01:59:52 box sshd[2544975]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.3.244
Mar 19 01:59:54 box sshd[2544975]: Failed password for invalid user test2 from 139.59.3.244 port 40144 ssh2
Mar 19 02:00:48 box sshd[2545960]: Invalid user test3 from 139.59.3.244 port 39154
Mar 19 02:00:48 box sshd[2545960]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.3.244
Mar 19 02:00:49 box sshd[2545960]: Failed password for invalid user test3 from 139.59.3.244 port 39154 ssh2
Mar 19 02:01:51 box sshd[2546491]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.3.244 user=root
Mar 19 02:01:53 box sshd[2546491]: Failed password for root from 139.59.3.244 port 40568 ssh2
...
show less
DNS Compromise
DNS Poisoning
DDoS Attack
Ping of Death
Web Spam
Email Spam
Blog Spam
Port Scan
Hacking
Brute-Force
Bad Web Bot
SSH
Web App Attack
2026-03-19T01:59:33.319248+01:00 admin sshd[683375]: Failed password for invalid user test1 from 139.59.3.244 port 45148 ssh2
2026-03-19T02:00:24.468063+01:00 admin sshd[684041]: Invalid user test2 from 139.59.3.244 port 49128
2026-03-19T02:00:24.728 ...
show more2026-03-19T01:59:33.319248+01:00 admin sshd[683375]: Failed password for invalid user test1 from 139.59.3.244 port 45148 ssh2
2026-03-19T02:00:24.468063+01:00 admin sshd[684041]: Invalid user test2 from 139.59.3.244 port 49128
2026-03-19T02:00:24.728001+01:00 admin sshd[684041]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.3.244
2026-03-19T02:00:26.500894+01:00 admin sshd[684041]: Failed password for invalid user test2 from 139.59.3.244 port 49128 ssh2
2026-03-19T02:01:27.061194+01:00 admin sshd[684081]: Invalid user test3 from 139.59.3.244 port 36860
...
show less
Brute-Force
SSH
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown