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

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '122.193.247.0 - 122.193.247.255'

% Abuse contact for '122.193.247.0 - 122.193.247.255' is 'zhaoyz3@chinaunicom.cn'

inetnum:        122.193.247.0 - 122.193.247.255
netname:        liantong_IP-address
country:        CN
descr:          nantong_NET,NANTONG,JIANGSU Province
admin-c:        LL58-AP
tech-c:         LL58-AP
status:         ASSIGNED NON-PORTABLE
mnt-by:         MAINT-CNCGROUP-JS
last-modified:  2009-02-04T01:36:00Z
source:         APNIC

person:         Lan Li
nic-hdl:        LL58-AP
e-mail:         js-cu-ipmanage@chinaunicom.cn
address:        No. 65 Beijing West Road,Nanjing,China
phone:          +86257900060
fax-no:         +86252900280
country:        CN
mnt-by:         MAINT-NEW
last-modified:  2013-08-15T02:13:11Z
source:         APNIC

% Information related to '122.192.0.0/14AS4837'

route:          122.192.0.0/14
descr:          CNC Group CHINA169 Jiangsu Province Network
country:        CN
origin:         AS4837
mnt-by:         MAINT-CNCGROUP-RR
last-modified:  2008-09-04T07:54:52Z
source:         APNIC

% This query was served by the APNIC Whois Service version 1.88.36-SNAPSHOT (WHOIS-AU5)
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 122.193.247.116
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 64100
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;122.193.247.116.		IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 27 08:04:21 CST 2026
;; MSG SIZE  rcvd: 108
Host info
Host 116.247.193.122.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 116.247.193.122.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
52.164.205.238 attack
2019-10-03T07:16:03.477137abusebot-5.cloudsearch.cf sshd\[19877\]: Invalid user fa from 52.164.205.238 port 53070
2019-10-03 15:34:13
51.77.146.136 attack
2019-08-18 18:21:56,800 fail2ban.actions        [878]: NOTICE  [sshd] Ban 51.77.146.136
2019-08-18 21:27:25,516 fail2ban.actions        [878]: NOTICE  [sshd] Ban 51.77.146.136
2019-08-19 00:33:38,151 fail2ban.actions        [878]: NOTICE  [sshd] Ban 51.77.146.136
...
2019-10-03 14:50:28
139.99.78.208 attack
2019-09-19 12:17:18,295 fail2ban.actions        [800]: NOTICE  [sshd] Ban 139.99.78.208
2019-09-19 15:27:10,901 fail2ban.actions        [800]: NOTICE  [sshd] Ban 139.99.78.208
2019-09-19 18:33:09,367 fail2ban.actions        [800]: NOTICE  [sshd] Ban 139.99.78.208
...
2019-10-03 15:00:31
180.166.187.146 attackbots
2019-10-03T03:57:25Z - RDP login failed multiple times. (180.166.187.146)
2019-10-03 14:55:55
202.28.64.1 attack
2019-09-27 00:25:04,903 fail2ban.actions        [818]: NOTICE  [sshd] Ban 202.28.64.1
2019-09-27 03:33:57,556 fail2ban.actions        [818]: NOTICE  [sshd] Ban 202.28.64.1
2019-09-27 06:43:37,608 fail2ban.actions        [818]: NOTICE  [sshd] Ban 202.28.64.1
...
2019-10-03 14:56:45
203.162.13.68 attack
Oct  3 03:47:16 ip-172-31-62-245 sshd\[30742\]: Invalid user vl from 203.162.13.68\
Oct  3 03:47:18 ip-172-31-62-245 sshd\[30742\]: Failed password for invalid user vl from 203.162.13.68 port 35462 ssh2\
Oct  3 03:52:05 ip-172-31-62-245 sshd\[30788\]: Invalid user ftpuser from 203.162.13.68\
Oct  3 03:52:07 ip-172-31-62-245 sshd\[30788\]: Failed password for invalid user ftpuser from 203.162.13.68 port 47100 ssh2\
Oct  3 03:56:47 ip-172-31-62-245 sshd\[30821\]: Invalid user amavis from 203.162.13.68\
2019-10-03 15:28:32
192.99.32.86 attackbots
Oct  2 20:40:26 hanapaa sshd\[11873\]: Invalid user pul from 192.99.32.86
Oct  2 20:40:26 hanapaa sshd\[11873\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns517943.ip-192-99-32.net
Oct  2 20:40:28 hanapaa sshd\[11873\]: Failed password for invalid user pul from 192.99.32.86 port 34902 ssh2
Oct  2 20:44:00 hanapaa sshd\[12148\]: Invalid user oracle from 192.99.32.86
Oct  2 20:44:00 hanapaa sshd\[12148\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns517943.ip-192-99-32.net
2019-10-03 15:02:33
177.87.40.187 attack
Telnet Server BruteForce Attack
2019-10-03 15:00:06
106.13.52.234 attack
Oct  1 00:45:49 eola sshd[25568]: Invalid user rf from 106.13.52.234 port 43924
Oct  1 00:45:49 eola sshd[25568]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.52.234 
Oct  1 00:45:52 eola sshd[25568]: Failed password for invalid user rf from 106.13.52.234 port 43924 ssh2
Oct  1 00:45:52 eola sshd[25568]: Received disconnect from 106.13.52.234 port 43924:11: Bye Bye [preauth]
Oct  1 00:45:52 eola sshd[25568]: Disconnected from 106.13.52.234 port 43924 [preauth]
Oct  1 01:02:12 eola sshd[25883]: Invalid user mapruser from 106.13.52.234 port 34046
Oct  1 01:02:12 eola sshd[25883]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.52.234 
Oct  1 01:02:14 eola sshd[25883]: Failed password for invalid user mapruser from 106.13.52.234 port 34046 ssh2
Oct  1 01:02:15 eola sshd[25883]: Received disconnect from 106.13.52.234 port 34046:11: Bye Bye [preauth]
Oct  1 01:02:15 eola sshd[258........
-------------------------------
2019-10-03 15:05:31
139.99.98.248 attackspambots
2019-09-09 18:23:41,590 fail2ban.actions        [814]: NOTICE  [sshd] Ban 139.99.98.248
2019-09-09 21:35:02,128 fail2ban.actions        [814]: NOTICE  [sshd] Ban 139.99.98.248
2019-09-10 00:45:00,757 fail2ban.actions        [814]: NOTICE  [sshd] Ban 139.99.98.248
...
2019-10-03 14:57:41
111.231.71.157 attackspam
Oct  3 08:22:12 MK-Soft-VM5 sshd[12295]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.71.157 
Oct  3 08:22:15 MK-Soft-VM5 sshd[12295]: Failed password for invalid user thman from 111.231.71.157 port 58748 ssh2
...
2019-10-03 14:58:49
142.4.203.130 attack
2019-10-03T07:09:47.457457abusebot-3.cloudsearch.cf sshd\[10876\]: Invalid user applmgr from 142.4.203.130 port 46500
2019-10-03 15:33:26
117.50.92.160 attackspambots
Oct  3 06:15:02 [snip] sshd[22286]: Invalid user ceng from 117.50.92.160 port 47512
Oct  3 06:15:02 [snip] sshd[22286]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.50.92.160
Oct  3 06:15:04 [snip] sshd[22286]: Failed password for invalid user ceng from 117.50.92.160 port 47512 ssh2[...]
2019-10-03 15:10:46
35.198.236.110 attack
fail2ban honeypot
2019-10-03 15:28:02
124.204.68.210 attackbots
2019-10-03T08:05:40.576923  sshd[9008]: Invalid user right from 124.204.68.210 port 53971
2019-10-03T08:05:40.591250  sshd[9008]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.204.68.210
2019-10-03T08:05:40.576923  sshd[9008]: Invalid user right from 124.204.68.210 port 53971
2019-10-03T08:05:42.847421  sshd[9008]: Failed password for invalid user right from 124.204.68.210 port 53971 ssh2
2019-10-03T08:17:38.379858  sshd[9232]: Invalid user ftpuser from 124.204.68.210 port 62954
...
2019-10-03 14:52:58

Recently Reported IPs

120.211.2.142 2606:4700:10::6816:2304 2606:4700:10::6816:3431 2606:4700:10::ac43:1937
2606:4700:10::6816:452d 2606:4700:10::6814:8157 2606:4700:10::6816:4205 2606:4700:10::6814:8487
2606:4700:10::6814:8507 2606:4700:10::6816:4867 223.104.122.169 103.203.46.137
122.192.203.170 2606:4700:10::ac43:2149 2606:4700:10::ac43:1926 2606:4700:10::6814:4403
2606:4700:10::6814:6771 2606:4700:10::6814:6674 2606:4700:10::6816:2573 2606:4700:10::6814:9840