Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: unknown

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
IP Type Details Datetime
139.59.41.222 attack
Fraud connect
2024-05-17 13:22:44
139.59.41.229 attack
Jul 28 17:20:44 saturn sshd[314292]: Invalid user lyj from 139.59.41.229 port 43460
Jul 28 17:20:46 saturn sshd[314292]: Failed password for invalid user lyj from 139.59.41.229 port 43460 ssh2
Jul 28 17:27:28 saturn sshd[314543]: Invalid user wcm from 139.59.41.229 port 50226
...
2020-07-29 00:08:11
139.59.41.154 attackbots
Mar  9 07:23:36 v22018086721571380 sshd[4898]: Failed password for invalid user daniel from 139.59.41.154 port 44426 ssh2
Mar  9 07:32:15 v22018086721571380 sshd[6383]: Failed password for invalid user olivier from 139.59.41.154 port 56290 ssh2
2020-03-09 15:13:02
139.59.41.154 attack
$f2bV_matches
2020-03-08 06:21:15
139.59.41.154 attack
Mar  7 14:23:14 DAAP sshd[30518]: Invalid user shuangbo from 139.59.41.154 port 39176
Mar  7 14:23:14 DAAP sshd[30518]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.41.154
Mar  7 14:23:14 DAAP sshd[30518]: Invalid user shuangbo from 139.59.41.154 port 39176
Mar  7 14:23:17 DAAP sshd[30518]: Failed password for invalid user shuangbo from 139.59.41.154 port 39176 ssh2
Mar  7 14:33:13 DAAP sshd[30645]: Invalid user nagios from 139.59.41.154 port 51530
...
2020-03-07 23:33:46
139.59.41.154 attackspambots
Invalid user tmpu1 from 139.59.41.154 port 46412
2020-03-04 02:17:39
139.59.41.154 attackbots
Mar  2 14:41:13 MK-Soft-Root1 sshd[31471]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.41.154 
Mar  2 14:41:16 MK-Soft-Root1 sshd[31471]: Failed password for invalid user hh from 139.59.41.154 port 51194 ssh2
...
2020-03-02 22:21:32
139.59.41.154 attackbots
suspicious action Mon, 24 Feb 2020 01:57:20 -0300
2020-02-24 14:07:23
139.59.41.170 attackbots
Unauthorized connection attempt detected from IP address 139.59.41.170 to port 2220 [J]
2020-02-23 15:39:49
139.59.41.154 attackbots
Feb 17 17:25:06 haigwepa sshd[31392]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.41.154 
Feb 17 17:25:08 haigwepa sshd[31392]: Failed password for invalid user security from 139.59.41.154 port 42356 ssh2
...
2020-02-18 00:29:33
139.59.41.154 attackbotsspam
Feb 10 20:34:58 sd-53420 sshd\[12346\]: Invalid user wsk from 139.59.41.154
Feb 10 20:34:58 sd-53420 sshd\[12346\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.41.154
Feb 10 20:35:00 sd-53420 sshd\[12346\]: Failed password for invalid user wsk from 139.59.41.154 port 59138 ssh2
Feb 10 20:39:14 sd-53420 sshd\[12779\]: Invalid user uks from 139.59.41.154
Feb 10 20:39:14 sd-53420 sshd\[12779\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.41.154
...
2020-02-11 03:51:01
139.59.41.154 attack
Feb  7 19:08:41 v22018076622670303 sshd\[4119\]: Invalid user fks from 139.59.41.154 port 50316
Feb  7 19:08:41 v22018076622670303 sshd\[4119\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.41.154
Feb  7 19:08:43 v22018076622670303 sshd\[4119\]: Failed password for invalid user fks from 139.59.41.154 port 50316 ssh2
...
2020-02-08 02:50:14
139.59.41.154 attackspambots
Feb  1 07:05:34 haigwepa sshd[32057]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.41.154 
Feb  1 07:05:37 haigwepa sshd[32057]: Failed password for invalid user musikbot from 139.59.41.154 port 57310 ssh2
...
2020-02-01 14:43:29
139.59.41.154 attackbots
Feb  1 02:43:24 legacy sshd[22766]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.41.154
Feb  1 02:43:27 legacy sshd[22766]: Failed password for invalid user tester from 139.59.41.154 port 34730 ssh2
Feb  1 02:47:42 legacy sshd[22932]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.41.154
...
2020-02-01 09:55:19
139.59.41.170 attackspam
Unauthorized connection attempt detected from IP address 139.59.41.170 to port 2220 [J]
2020-01-29 15:53:40
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.59.41.242
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57352
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.59.41.242.			IN	A

;; AUTHORITY SECTION:
.			468	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2022030803 1800 900 604800 86400

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 08:38:13 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 242.41.59.139.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 242.41.59.139.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
158.69.127.133 attackbotsspam
Unauthorized access detected from banned ip
2020-01-08 05:11:36
51.255.109.165 attackbotsspam
Honeypot hit.
2020-01-08 05:41:02
178.90.36.202 attackbotsspam
20/1/7@07:53:09: FAIL: Alarm-Telnet address from=178.90.36.202
...
2020-01-08 05:18:47
45.242.41.4 attackspambots
20/1/7@16:20:53: FAIL: Alarm-Network address from=45.242.41.4
...
2020-01-08 05:29:02
45.119.212.222 attackbots
01/07/2020-19:11:57.481940 45.119.212.222 Protocol: 6 ET POLICY Cleartext WordPress Login
2020-01-08 05:10:56
186.95.66.164 attackbots
Port 1433 Scan
2020-01-08 05:31:55
134.175.168.97 attackbotsspam
Unauthorized connection attempt detected from IP address 134.175.168.97 to port 22 [T]
2020-01-08 05:10:05
118.193.31.180 attack
Unauthorized connection attempt detected from IP address 118.193.31.180 to port 1234 [J]
2020-01-08 05:20:11
192.3.25.92 attackspambots
Jan  7 11:19:55 auw2 sshd\[1737\]: Invalid user jfk from 192.3.25.92
Jan  7 11:19:55 auw2 sshd\[1737\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.25.92
Jan  7 11:19:57 auw2 sshd\[1737\]: Failed password for invalid user jfk from 192.3.25.92 port 39749 ssh2
Jan  7 11:23:02 auw2 sshd\[1961\]: Invalid user rony from 192.3.25.92
Jan  7 11:23:02 auw2 sshd\[1961\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.25.92
2020-01-08 05:23:08
159.65.152.201 attackspambots
Unauthorized connection attempt detected from IP address 159.65.152.201 to port 2220 [J]
2020-01-08 05:15:03
92.118.37.86 attack
Jan  7 22:20:23 debian-2gb-nbg1-2 kernel: \[691340.498503\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=92.118.37.86 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=53939 PROTO=TCP SPT=45789 DPT=3482 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-08 05:47:58
180.166.103.51 attackbotsspam
Port 1433 Scan
2020-01-08 05:34:12
188.213.165.189 attackbotsspam
Unauthorized connection attempt detected from IP address 188.213.165.189 to port 2220 [J]
2020-01-08 05:26:04
218.92.0.173 attackspambots
$f2bV_matches
2020-01-08 05:48:32
113.116.132.160 attackbots
Port 1433 Scan
2020-01-08 05:46:59

Recently Reported IPs

139.59.41.120 118.254.202.35 139.59.41.9 139.59.42.190
139.59.42.35 139.59.42.63 139.59.42.82 139.59.41.86
139.59.43.1 139.59.42.156 139.59.42.170 139.59.41.84
118.254.202.38 139.59.43.188 139.59.43.155 139.59.44.169
139.59.44.144 139.59.44.108 139.59.45.120 139.59.45.210