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.224.0.0 - 112.255.255.255'

% Abuse contact for '112.224.0.0 - 112.255.255.255' is 'zhaoyz3@chinaunicom.cn'

inetnum:        112.224.0.0 - 112.255.255.255
netname:        UNICOM-SD
descr:          China Unicom Shandong province network
descr:          China Unicom
country:        CN
admin-c:        CH1302-AP
tech-c:         XZ14-AP
abuse-c:        AC1718-AP
status:         ALLOCATED PORTABLE
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
mnt-lower:      MAINT-CNCGROUP-SD
mnt-routes:     MAINT-CNCGROUP-RR
mnt-irt:        IRT-CU-CN
last-modified:  2025-01-22T13:07:36Z
source:         APNIC

irt:            IRT-CU-CN
address:        No.21,Financial Street
address:        Beijing,100033
address:        P.R.China
e-mail:         zhaoyz3@chinaunicom.cn
abuse-mailbox:  zhaoyz3@chinaunicom.cn
admin-c:        CH1302-AP
tech-c:         CH1302-AP
auth:           # Filtered
remarks:        zhaoyz3@chinaunicom.cn was validated on 2025-10-17
mnt-by:         MAINT-CNCGROUP
last-modified:  2025-11-18T00:26:20Z
source:         APNIC

role:           ABUSE CUCN
country:        ZZ
address:        No.21,Financial Street
address:        Beijing,100033
address:        P.R.China
phone:          +000000000
e-mail:         zhaoyz3@chinaunicom.cn
admin-c:        CH1302-AP
tech-c:         CH1302-AP
nic-hdl:        AC1718-AP
remarks:        Generated from irt object IRT-CU-CN
remarks:        zhaoyz3@chinaunicom.cn was validated on 2025-10-17
abuse-mailbox:  zhaoyz3@chinaunicom.cn
mnt-by:         APNIC-ABUSE
last-modified:  2025-10-17T02:26:56Z
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:         XIAOFENG ZHANG
nic-hdl:        XZ14-AP
e-mail:         ip@pub.sd.cninfo.net
address:        Jinan,Shandong P.R China
phone:          +86-531-6666666
fax-no:         +86-531-6666666
country:        CN
mnt-by:         MAINT-ZXF
last-modified:  2008-09-04T07:29:35Z
source:         APNIC

% Information related to '112.224.0.0/11AS4837'

route:          112.224.0.0/11
descr:          China Unicom CHINA169 Shandong Province Network
country:        CN
origin:         AS4837
mnt-by:         MAINT-CNCGROUP-RR
last-modified:  2009-02-11T01:12:50Z
source:         APNIC

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

;; QUESTION SECTION:
;112.242.48.196.			IN	A

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

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Apr 08 10:01:49 CST 2026
;; MSG SIZE  rcvd: 107
Host info
Host 196.48.242.112.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
server can't find 112.242.48.196.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
115.238.236.74 attack
Oct 19 14:46:28 vps01 sshd[27583]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.238.236.74
Oct 19 14:46:30 vps01 sshd[27583]: Failed password for invalid user admin99 from 115.238.236.74 port 55234 ssh2
2019-10-19 20:51:30
106.75.31.215 attackbotsspam
2019-10-19T12:30:32.635938abusebot-5.cloudsearch.cf sshd\[4751\]: Invalid user alm from 106.75.31.215 port 50652
2019-10-19 20:58:25
180.245.171.249 attack
Oct 19 09:04:42 ws22vmsma01 sshd[93882]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.245.171.249
Oct 19 09:04:44 ws22vmsma01 sshd[93882]: Failed password for invalid user 666666 from 180.245.171.249 port 57332 ssh2
...
2019-10-19 20:54:58
157.55.39.186 attackspam
Automatic report - Banned IP Access
2019-10-19 20:54:40
112.85.42.195 attackspam
Oct 19 12:37:22 game-panel sshd[24556]: Failed password for root from 112.85.42.195 port 18601 ssh2
Oct 19 12:40:33 game-panel sshd[24753]: Failed password for root from 112.85.42.195 port 11142 ssh2
2019-10-19 20:47:31
185.86.164.100 attackbots
Website administration hacking try
2019-10-19 20:59:59
182.72.124.6 attack
2019-10-19T12:53:45.050673shield sshd\[4295\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.72.124.6  user=root
2019-10-19T12:53:47.445482shield sshd\[4295\]: Failed password for root from 182.72.124.6 port 38808 ssh2
2019-10-19T12:58:47.073523shield sshd\[5074\]: Invalid user leonidas from 182.72.124.6 port 49548
2019-10-19T12:58:47.079041shield sshd\[5074\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.72.124.6
2019-10-19T12:58:48.931939shield sshd\[5074\]: Failed password for invalid user leonidas from 182.72.124.6 port 49548 ssh2
2019-10-19 21:05:31
74.71.245.78 attackspam
DATE:2019-10-19 14:04:15, IP:74.71.245.78, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc)
2019-10-19 21:10:11
222.186.175.150 attack
2019-10-19T13:00:35.106441shield sshd\[5458\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.150  user=root
2019-10-19T13:00:37.455663shield sshd\[5458\]: Failed password for root from 222.186.175.150 port 44892 ssh2
2019-10-19T13:00:41.631601shield sshd\[5458\]: Failed password for root from 222.186.175.150 port 44892 ssh2
2019-10-19T13:00:45.691458shield sshd\[5458\]: Failed password for root from 222.186.175.150 port 44892 ssh2
2019-10-19T13:00:50.298764shield sshd\[5458\]: Failed password for root from 222.186.175.150 port 44892 ssh2
2019-10-19 21:14:30
54.37.232.108 attackspam
Oct 19 14:04:07 DAAP sshd[19675]: Invalid user p455w0rd1 from 54.37.232.108 port 53404
...
2019-10-19 21:15:23
222.186.173.183 attack
v+ssh-bruteforce
2019-10-19 21:08:18
115.94.204.156 attackbots
Triggered by Fail2Ban at Vostok web server
2019-10-19 20:45:13
80.52.199.93 attack
Oct  8 06:29:52 microserver sshd[27917]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.52.199.93  user=root
Oct  8 06:29:54 microserver sshd[27917]: Failed password for root from 80.52.199.93 port 44984 ssh2
Oct  8 06:34:02 microserver sshd[28531]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.52.199.93  user=root
Oct  8 06:34:04 microserver sshd[28531]: Failed password for root from 80.52.199.93 port 57054 ssh2
Oct  8 06:38:06 microserver sshd[29112]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.52.199.93  user=root
Oct 19 14:22:10 microserver sshd[10528]: Invalid user phill from 80.52.199.93 port 36306
Oct 19 14:22:10 microserver sshd[10528]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.52.199.93
Oct 19 14:22:12 microserver sshd[10528]: Failed password for invalid user phill from 80.52.199.93 port 36306 ssh2
Oct 19 14:28:05 micr
2019-10-19 20:48:42
116.31.105.198 attackbotsspam
Oct 19 11:54:05 localhost sshd\[33198\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.31.105.198  user=root
Oct 19 11:54:06 localhost sshd\[33198\]: Failed password for root from 116.31.105.198 port 42152 ssh2
Oct 19 11:59:30 localhost sshd\[33656\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.31.105.198  user=root
Oct 19 11:59:32 localhost sshd\[33656\]: Failed password for root from 116.31.105.198 port 51228 ssh2
Oct 19 12:04:49 localhost sshd\[33806\]: Invalid user com@123 from 116.31.105.198 port 60312
Oct 19 12:04:49 localhost sshd\[33806\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.31.105.198
...
2019-10-19 20:52:52
218.147.227.197 attackbots
2019-10-19T14:41:29.233533vfs-server-01 sshd\[23279\]: Invalid user 116.203.31.11 from 218.147.227.197 port 53756
2019-10-19T14:41:49.918886vfs-server-01 sshd\[23292\]: Invalid user 116.203.31.11 from 218.147.227.197 port 51206
2019-10-19T14:41:57.085864vfs-server-01 sshd\[23298\]: Invalid user 116.203.31.11 from 218.147.227.197 port 49824
2019-10-19 21:21:02

Recently Reported IPs

115.50.192.57 101.26.28.203 171.242.137.185 2606:4700:10::6814:9460
2606:4700:10::6816:4311 2606:4700:10::6816:1963 2606:4700:10::6816:748 2606:4700:10::6816:1633
39.146.31.106 39.146.27.74 223.88.64.180 223.79.60.147
20.219.69.68 183.253.120.92 120.229.85.74 120.229.227.12
117.188.115.240 112.10.184.62 103.141.234.67 36.142.172.194