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.92.135 attack
Sep 19 00:11:36 theomazars sshd[24713]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.92.135  user=root
Sep 19 00:11:38 theomazars sshd[24713]: Failed password for root from 139.59.92.135 port 37564 ssh2
2020-09-20 00:43:30
139.59.92.135 attackbotsspam
Sep 19 00:11:36 theomazars sshd[24713]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.92.135  user=root
Sep 19 00:11:38 theomazars sshd[24713]: Failed password for root from 139.59.92.135 port 37564 ssh2
2020-09-19 16:32:13
139.59.92.19 attackspam
Sep  9 19:07:16 rocket sshd[25879]: Failed password for root from 139.59.92.19 port 34424 ssh2
Sep  9 19:11:22 rocket sshd[26662]: Failed password for root from 139.59.92.19 port 40638 ssh2
...
2020-09-10 02:11:28
139.59.92.19 attackspambots
 TCP (SYN) 139.59.92.19:54389 -> port 17475, len 44
2020-09-08 02:43:17
139.59.92.19 attack
Port scan denied
2020-09-07 18:10:53
139.59.92.19 attackbots
Invalid user riana from 139.59.92.19 port 60256
2020-09-04 21:39:40
139.59.92.19 attack
$f2bV_matches
2020-09-04 13:17:18
139.59.92.19 attackbots
" "
2020-09-04 05:46:08
139.59.92.19 attack
Sep  1 02:28:19 mout sshd[8720]: Invalid user theo from 139.59.92.19 port 45262
2020-09-01 08:56:06
139.59.92.19 attackbots
Aug 19 22:28:51 santamaria sshd\[8879\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.92.19  user=root
Aug 19 22:28:53 santamaria sshd\[8879\]: Failed password for root from 139.59.92.19 port 36556 ssh2
Aug 19 22:33:02 santamaria sshd\[8939\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.92.19  user=mysql
...
2020-08-20 04:48:36
139.59.92.19 attackspam
Failed password for postgres from 139.59.92.19 port 52552 ssh2
Invalid user ganyi from 139.59.92.19 port 34042
pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.92.19
Invalid user ganyi from 139.59.92.19 port 34042
Failed password for invalid user ganyi from 139.59.92.19 port 34042 ssh2
2020-08-18 20:05:12
139.59.92.2 attackbotsspam
WordPress brute force
2020-06-17 08:39:00
139.59.92.190 attackbotsspam
SSH Brute-Force Attack
2020-05-04 07:29:05
139.59.92.117 attackbotsspam
Unauthorized connection attempt detected from IP address 139.59.92.117 to port 2220 [J]
2020-02-02 01:15:16
139.59.92.117 attackspam
Jan 11 15:34:37 zulu412 sshd\[2811\]: Invalid user ubuntu from 139.59.92.117 port 45208
Jan 11 15:34:37 zulu412 sshd\[2811\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.92.117
Jan 11 15:34:39 zulu412 sshd\[2811\]: Failed password for invalid user ubuntu from 139.59.92.117 port 45208 ssh2
...
2020-01-11 23:48:14
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.59.92.202
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 18624
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.59.92.202.			IN	A

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

;; Query time: 67 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 08:40:13 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 202.92.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 202.92.59.139.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
123.140.114.252 attackspam
k+ssh-bruteforce
2020-09-03 13:00:55
122.51.166.84 attackbots
fail2ban/Sep  2 22:56:40 h1962932 sshd[4890]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.166.84  user=root
Sep  2 22:56:43 h1962932 sshd[4890]: Failed password for root from 122.51.166.84 port 40614 ssh2
Sep  2 22:59:45 h1962932 sshd[4947]: Invalid user tom from 122.51.166.84 port 48086
Sep  2 22:59:45 h1962932 sshd[4947]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.166.84
Sep  2 22:59:45 h1962932 sshd[4947]: Invalid user tom from 122.51.166.84 port 48086
Sep  2 22:59:47 h1962932 sshd[4947]: Failed password for invalid user tom from 122.51.166.84 port 48086 ssh2
2020-09-03 12:58:36
112.85.42.173 attackspam
DATE:2020-09-03 06:45:12,IP:112.85.42.173,MATCHES:10,PORT:ssh
2020-09-03 12:46:08
103.120.207.3 attackbots
Automatic report - Port Scan Attack
2020-09-03 12:55:26
62.82.75.58 attack
(sshd) Failed SSH login from 62.82.75.58 (ES/Spain/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep  3 00:20:22 server5 sshd[1242]: Invalid user hf from 62.82.75.58
Sep  3 00:20:25 server5 sshd[1242]: Failed password for invalid user hf from 62.82.75.58 port 19081 ssh2
Sep  3 00:23:40 server5 sshd[3214]: Invalid user lucas from 62.82.75.58
Sep  3 00:23:42 server5 sshd[3214]: Failed password for invalid user lucas from 62.82.75.58 port 12842 ssh2
Sep  3 00:26:54 server5 sshd[5530]: Invalid user ubuntu from 62.82.75.58
2020-09-03 13:01:47
180.76.142.19 attackbots
Invalid user bruna from 180.76.142.19 port 57700
2020-09-03 13:15:10
177.205.164.41 attack
Automatic report - Port Scan Attack
2020-09-03 12:59:59
157.230.39.120 attackbotsspam
SSH brute force attempt
2020-09-03 13:03:26
111.21.176.80 attack
Hit honeypot r.
2020-09-03 12:47:17
222.186.180.17 attack
Sep  3 04:43:59 instance-2 sshd[3833]: Failed password for root from 222.186.180.17 port 32420 ssh2
Sep  3 04:44:03 instance-2 sshd[3833]: Failed password for root from 222.186.180.17 port 32420 ssh2
Sep  3 04:44:07 instance-2 sshd[3833]: Failed password for root from 222.186.180.17 port 32420 ssh2
Sep  3 04:44:12 instance-2 sshd[3833]: Failed password for root from 222.186.180.17 port 32420 ssh2
2020-09-03 12:49:25
45.55.182.232 attackbots
Invalid user hj from 45.55.182.232 port 58762
2020-09-03 13:15:47
157.42.179.60 attackbots
1599065335 - 09/02/2020 18:48:55 Host: 157.42.179.60/157.42.179.60 Port: 445 TCP Blocked
...
2020-09-03 12:55:04
68.183.233.228 attack
SSH Brute Force
2020-09-03 13:20:58
165.22.103.3 attackbotsspam
165.22.103.3 - - [02/Sep/2020:21:09:18 +0100] "POST /wp-login.php HTTP/1.1" 200 2415 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
165.22.103.3 - - [02/Sep/2020:21:09:20 +0100] "POST /wp-login.php HTTP/1.1" 200 2342 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
165.22.103.3 - - [02/Sep/2020:21:09:21 +0100] "POST /xmlrpc.php HTTP/1.1" 403 219 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-09-03 12:56:20
180.166.192.66 attackbots
Invalid user wangqiang from 180.166.192.66 port 25727
2020-09-03 13:23:07

Recently Reported IPs

139.59.92.148 118.254.203.143 139.59.92.181 139.59.93.12
139.59.92.63 139.59.94.164 139.59.92.56 139.59.93.61
139.59.93.146 139.59.94.127 139.59.93.21 139.59.94.136
139.59.93.158 118.254.203.15 139.59.94.228 139.59.94.45
139.59.94.230 139.59.95.131 139.59.94.68 139.59.95.123