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 '112.80.0.0 - 112.87.255.255'

% Abuse contact for '112.80.0.0 - 112.87.255.255' is 'hqs-ipabuse@chinaunicom.cn'

inetnum:        112.80.0.0 - 112.87.255.255
netname:        UNICOM-JS
descr:          China Unicom Jiangsu province network
descr:          China Unicom
country:        CN
admin-c:        CH1302-AP
tech-c:         LL58-AP
abuse-c:        AC1718-AP
status:         ALLOCATED PORTABLE
remarks:        service provider
remarks:        --------------------------------------------------------
remarks:        To report network abuse, please contact mnt-irt
remarks:        For troubleshooting, please contact tech-c and admin-c
remarks:        Report invalid contact via www.apnic.net/invalidcontact
remarks:        --------------------------------------------------------
mnt-by:         APNIC-HM
mnt-lower:      MAINT-CNCGROUP-JS
mnt-routes:     MAINT-CNCGROUP-RR
mnt-irt:        IRT-CU-CN
last-modified:  2025-01-22T13:12:40Z
source:         APNIC

irt:            IRT-CU-CN
address:        No.21,Financial Street
address:        Beijing,100033
address:        P.R.China
e-mail:         hqs-ipabuse@chinaunicom.cn
abuse-mailbox:  hqs-ipabuse@chinaunicom.cn
admin-c:        CH1302-AP
tech-c:         CH1302-AP
auth:           # Filtered
remarks:        hqs-ipabuse@chinaunicom.cn was validated on 2026-08-19
mnt-by:         MAINT-CNCGROUP
last-modified:  2026-08-19T00:57:22Z
source:         APNIC

role:           ABUSE CUCN
country:        ZZ
address:        No.21,Financial Street
address:        Beijing,100033
address:        P.R.China
phone:          +000000000
e-mail:         hqs-ipabuse@chinaunicom.cn
admin-c:        CH1302-AP
tech-c:         CH1302-AP
nic-hdl:        AC1718-AP
remarks:        Generated from irt object IRT-CU-CN
remarks:        hqs-ipabuse@chinaunicom.cn was validated on 2026-08-19
abuse-mailbox:  hqs-ipabuse@chinaunicom.cn
mnt-by:         APNIC-ABUSE
last-modified:  2026-08-20T03:22:23Z
source:         APNIC

person:         ChinaUnicom Hostmaster
nic-hdl:        CH1302-AP
e-mail:         hqs-ipabuse@chinaunicom.cn
address:        No.21,Jin-Rong Street
address:        Beijing,100033
address:        P.R.China
phone:          +86-10-66259764
fax-no:         +86-10-66259764
country:        CN
mnt-by:         MAINT-CNCGROUP
last-modified:  2017-08-17T06:13:16Z
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 '112.80.0.0/13AS4837'

route:          112.80.0.0/13
descr:          China Unicom CHINA169 Jiangsu Province Network
country:        CN
origin:         AS4837
mnt-by:         MAINT-CNCGROUP-RR
last-modified:  2008-12-31T01:00:07Z
source:         APNIC

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

;; QUESTION SECTION:
;112.83.235.190.			IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Oct 29 12:02:55 CST 2026
;; MSG SIZE  rcvd: 107
Host info
Host 190.235.83.112.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 190.235.83.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
51.38.178.226 attack
Sep  6 07:01:48 lcprod sshd\[6609\]: Invalid user qwe123 from 51.38.178.226
Sep  6 07:01:48 lcprod sshd\[6609\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=226.ip-51-38-178.eu
Sep  6 07:01:50 lcprod sshd\[6609\]: Failed password for invalid user qwe123 from 51.38.178.226 port 38328 ssh2
Sep  6 07:06:26 lcprod sshd\[7003\]: Invalid user minecraft! from 51.38.178.226
Sep  6 07:06:26 lcprod sshd\[7003\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=226.ip-51-38-178.eu
2019-09-07 01:52:45
218.98.26.173 attackbotsspam
Sep  6 19:12:38 h2177944 sshd\[21505\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.98.26.173  user=root
Sep  6 19:12:41 h2177944 sshd\[21505\]: Failed password for root from 218.98.26.173 port 23013 ssh2
Sep  6 19:12:43 h2177944 sshd\[21505\]: Failed password for root from 218.98.26.173 port 23013 ssh2
Sep  6 19:12:46 h2177944 sshd\[21505\]: Failed password for root from 218.98.26.173 port 23013 ssh2
...
2019-09-07 01:16:10
80.82.70.118 attackbots
19/9/6@12:18:44: FAIL: IoT-Telnet address from=80.82.70.118
...
2019-09-07 00:19:08
192.210.203.101 attackbotsspam
Sep  6 17:12:45 mercury kernel: [UFW ALLOW] IN=eth0 OUT= MAC=f2:3c:91:bc:4d:f8:84:78:ac:0d:8f:41:08:00 SRC=192.210.203.101 DST=109.74.200.221 LEN=57 TOS=0x00 PREC=0x00 TTL=243 ID=54321 PROTO=UDP SPT=53690 DPT=123 LEN=37 
...
2019-09-07 00:14:14
157.230.91.45 attack
Sep  6 17:57:35 SilenceServices sshd[14635]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.91.45
Sep  6 17:57:37 SilenceServices sshd[14635]: Failed password for invalid user guest1 from 157.230.91.45 port 38003 ssh2
Sep  6 18:01:59 SilenceServices sshd[16331]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.91.45
2019-09-07 00:23:41
37.49.227.202 attackbots
firewall-block, port(s): 81/tcp
2019-09-07 00:27:48
217.182.68.146 attack
Sep  6 17:05:24 web8 sshd\[18093\]: Invalid user deploy from 217.182.68.146
Sep  6 17:05:24 web8 sshd\[18093\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.182.68.146
Sep  6 17:05:26 web8 sshd\[18093\]: Failed password for invalid user deploy from 217.182.68.146 port 47475 ssh2
Sep  6 17:09:51 web8 sshd\[20377\]: Invalid user user1 from 217.182.68.146
Sep  6 17:09:51 web8 sshd\[20377\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.182.68.146
2019-09-07 01:19:53
167.114.251.164 attackspambots
Sep  6 07:52:09 hcbb sshd\[15986\]: Invalid user tsbot from 167.114.251.164
Sep  6 07:52:09 hcbb sshd\[15986\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.ip-167-114-251.eu
Sep  6 07:52:11 hcbb sshd\[15986\]: Failed password for invalid user tsbot from 167.114.251.164 port 54977 ssh2
Sep  6 07:56:27 hcbb sshd\[16399\]: Invalid user sammy from 167.114.251.164
Sep  6 07:56:27 hcbb sshd\[16399\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.ip-167-114-251.eu
2019-09-07 01:57:04
45.163.158.169 attack
Honeypot attack, port: 23, PTR: isp-158-169.ozanet.net.br.
2019-09-07 00:58:56
125.139.180.128 attackspam
Sep  6 16:09:36 albuquerque sshd\[7412\]: User root from 125.139.180.128 not allowed because not listed in AllowUsersSep  6 16:09:37 albuquerque sshd\[7415\]: User root from 125.139.180.128 not allowed because not listed in AllowUsersSep  6 16:09:38 albuquerque sshd\[7412\]: Failed password for invalid user root from 125.139.180.128 port 45367 ssh2
...
2019-09-07 01:01:11
162.144.119.35 attackspambots
Sep  6 07:17:27 lcprod sshd\[7986\]: Invalid user webmasterwebmaster from 162.144.119.35
Sep  6 07:17:27 lcprod sshd\[7986\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.144.119.35
Sep  6 07:17:29 lcprod sshd\[7986\]: Failed password for invalid user webmasterwebmaster from 162.144.119.35 port 33098 ssh2
Sep  6 07:22:22 lcprod sshd\[8418\]: Invalid user smbguest from 162.144.119.35
Sep  6 07:22:22 lcprod sshd\[8418\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.144.119.35
2019-09-07 01:36:37
176.218.217.208 attack
Telnet Server BruteForce Attack
2019-09-07 01:15:32
41.78.158.67 attackspambots
Honeypot attack, port: 445, PTR: PTR record not found
2019-09-07 01:12:48
177.47.115.70 attack
Sep  6 12:43:11 xtremcommunity sshd\[21297\]: Invalid user live from 177.47.115.70 port 56167
Sep  6 12:43:11 xtremcommunity sshd\[21297\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.47.115.70
Sep  6 12:43:13 xtremcommunity sshd\[21297\]: Failed password for invalid user live from 177.47.115.70 port 56167 ssh2
Sep  6 12:48:11 xtremcommunity sshd\[21462\]: Invalid user 111111 from 177.47.115.70 port 49836
Sep  6 12:48:11 xtremcommunity sshd\[21462\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.47.115.70
...
2019-09-07 00:55:27
201.116.12.217 attackbots
Sep  6 16:17:43 MK-Soft-VM7 sshd\[21728\]: Invalid user hadoop from 201.116.12.217 port 59461
Sep  6 16:17:43 MK-Soft-VM7 sshd\[21728\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.116.12.217
Sep  6 16:17:45 MK-Soft-VM7 sshd\[21728\]: Failed password for invalid user hadoop from 201.116.12.217 port 59461 ssh2
...
2019-09-07 01:05:07

Recently Reported IPs

61.163.152.238 42.85.63.107 42.232.7.179 39.180.193.161
223.89.237.79 223.88.214.225 222.138.47.70 163.125.162.228
153.36.87.1 1.25.149.171 1.24.26.205 122.97.167.164
198.18.0.227 112.92.67.74 111.208.78.1 101.74.62.247
45.150.243.134 95.179.134.211 217.146.2.63 187.17.228.241