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: China

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
110.89.139.21 attackbotsspam
Brute force SMTP login attempted.
...
2020-04-01 08:06:49
110.89.139.183 attack
Port Scan: TCP/2222
2019-09-10 18:15:59
110.89.139.21 attack
$f2bV_matches
2019-09-10 03:56:17
110.89.139.252 attack
Sep  2 05:09:21 v22019058497090703 sshd[15664]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.89.139.252
Sep  2 05:09:22 v22019058497090703 sshd[15664]: Failed password for invalid user admin from 110.89.139.252 port 54844 ssh2
Sep  2 05:09:25 v22019058497090703 sshd[15664]: Failed password for invalid user admin from 110.89.139.252 port 54844 ssh2
Sep  2 05:09:26 v22019058497090703 sshd[15664]: Failed password for invalid user admin from 110.89.139.252 port 54844 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=110.89.139.252
2019-09-02 11:57:20
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 110.89.139.121
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12170
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;110.89.139.121.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 10 16:01:12 CST 2022
;; MSG SIZE  rcvd: 107
Host info
121.139.89.110.in-addr.arpa domain name pointer 121.139.89.110.broad.ly.fj.dynamic.163data.com.cn.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
121.139.89.110.in-addr.arpa	name = 121.139.89.110.broad.ly.fj.dynamic.163data.com.cn.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
218.237.65.93 attack
CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2019-09-05 21:12:09
172.103.172.7 attack
Unauthorized connection attempt from IP address 172.103.172.7 on Port 445(SMB)
2019-09-05 20:21:09
117.93.16.233 attackbotsspam
Sep  5 10:31:01 vps sshd[4255]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.93.16.233 
Sep  5 10:31:03 vps sshd[4255]: Failed password for invalid user admin from 117.93.16.233 port 18280 ssh2
Sep  5 10:31:07 vps sshd[4255]: Failed password for invalid user admin from 117.93.16.233 port 18280 ssh2
Sep  5 10:31:10 vps sshd[4255]: Failed password for invalid user admin from 117.93.16.233 port 18280 ssh2
...
2019-09-05 21:06:08
182.151.23.140 attackbots
RDP Bruteforce
2019-09-05 20:53:10
183.136.236.55 attackspambots
Unauthorized connection attempt from IP address 183.136.236.55 on Port 445(SMB)
2019-09-05 20:25:18
190.116.21.131 attack
Sep  4 22:26:30 hpm sshd\[2271\]: Invalid user gitolite from 190.116.21.131
Sep  4 22:26:30 hpm sshd\[2271\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.116.21.131
Sep  4 22:26:32 hpm sshd\[2271\]: Failed password for invalid user gitolite from 190.116.21.131 port 33162 ssh2
Sep  4 22:31:45 hpm sshd\[2708\]: Invalid user deb from 190.116.21.131
Sep  4 22:31:45 hpm sshd\[2708\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.116.21.131
2019-09-05 20:30:49
206.189.232.29 attack
2019-09-05T15:31:38.233780enmeeting.mahidol.ac.th sshd\[19332\]: Invalid user www-data from 206.189.232.29 port 56858
2019-09-05T15:31:38.248315enmeeting.mahidol.ac.th sshd\[19332\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.232.29
2019-09-05T15:31:39.465349enmeeting.mahidol.ac.th sshd\[19332\]: Failed password for invalid user www-data from 206.189.232.29 port 56858 ssh2
...
2019-09-05 20:33:55
183.82.3.248 attackspam
Automatic report - Banned IP Access
2019-09-05 20:39:01
115.79.196.113 attackbotsspam
Unauthorized connection attempt from IP address 115.79.196.113 on Port 445(SMB)
2019-09-05 20:34:56
202.78.197.198 attackbotsspam
2019-09-05T12:20:45.749679abusebot-7.cloudsearch.cf sshd\[9015\]: Invalid user steamcmd from 202.78.197.198 port 60280
2019-09-05 20:44:04
139.162.120.76 attackbotsspam
" "
2019-09-05 20:28:27
186.207.128.104 attackspam
2019-09-05T14:01:12.142490lon01.zurich-datacenter.net sshd\[9855\]: Invalid user alex from 186.207.128.104 port 13184
2019-09-05T14:01:12.152933lon01.zurich-datacenter.net sshd\[9855\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.207.128.104
2019-09-05T14:01:14.562044lon01.zurich-datacenter.net sshd\[9855\]: Failed password for invalid user alex from 186.207.128.104 port 13184 ssh2
2019-09-05T14:07:33.292505lon01.zurich-datacenter.net sshd\[10016\]: Invalid user jenkins from 186.207.128.104 port 23038
2019-09-05T14:07:33.301213lon01.zurich-datacenter.net sshd\[10016\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.207.128.104
...
2019-09-05 21:17:10
85.105.112.134 attack
Unauthorized connection attempt from IP address 85.105.112.134 on Port 445(SMB)
2019-09-05 20:32:59
116.58.235.17 attackspam
Unauthorized connection attempt from IP address 116.58.235.17 on Port 445(SMB)
2019-09-05 20:45:22
87.103.201.26 attackbots
port scan and connect, tcp 8080 (http-proxy)
2019-09-05 20:58:46

Recently Reported IPs

122.255.210.121 93.141.6.8 120.23.82.50 39.92.0.137
10.103.189.41 31.60.28.89 197.141.190.40 88.65.89.86
111.53.193.184 176.235.254.168 199.17.55.33 46.182.175.7
171.245.42.206 175.176.59.91 12.208.138.217 134.202.70.181
178.209.52.138 103.170.98.64 181.174.192.32 42.209.197.212