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

Region: Beijing

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 '111.192.0.0 - 111.207.255.255'

% Abuse contact for '111.192.0.0 - 111.207.255.255' is 'hqs-ipabuse@chinaunicom.cn'

inetnum:        111.192.0.0 - 111.207.255.255
netname:        UNICOM-BJ
descr:          China Unicom Beijing province network
descr:          China Unicom
country:        CN
admin-c:        CH1302-AP
tech-c:         SY21-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
mnt-lower:      MAINT-CNCGROUP-BJ
mnt-routes:     MAINT-CNCGROUP-RR
mnt-irt:        IRT-CU-CN
last-modified:  2023-10-21T03:42:11Z
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:         sun ying
address:        fu xing men nei da jie 97, Xicheng District
address:        Beijing 100800
country:        CN
phone:          +86-10-66030657
fax-no:         +86-10-66078815
e-mail:         hostmast@publicf.bta.net.cn
nic-hdl:        SY21-AP
mnt-by:         MAINT-CNCGROUP-BJ
last-modified:  2009-06-30T08:42:48Z
source:         APNIC

% Information related to '111.192.0.0/12AS4808'

route:          111.192.0.0/12
descr:          China Unicom Beijing Province Network
country:        CN
origin:         AS4808
mnt-by:         MAINT-CNCGROUP-RR
last-modified:  2016-05-20T01:24:03Z
source:         APNIC

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

;; QUESTION SECTION:
;111.201.149.101.		IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Oct 13 15:03:48 CST 2026
;; MSG SIZE  rcvd: 108
Host info
Host 101.149.201.111.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 101.149.201.111.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
184.105.139.70 attackbotsspam
Unauthorized SSH login attempts
2020-07-25 12:12:36
65.49.210.231 attackspambots
Jul 25 00:44:50 ws12vmsma01 sshd[21564]: Invalid user steam from 65.49.210.231
Jul 25 00:44:52 ws12vmsma01 sshd[21564]: Failed password for invalid user steam from 65.49.210.231 port 38650 ssh2
Jul 25 00:54:02 ws12vmsma01 sshd[22872]: Invalid user lynn from 65.49.210.231
...
2020-07-25 12:44:11
51.91.110.170 attackspambots
Jul 25 05:14:19 rocket sshd[29046]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.91.110.170
Jul 25 05:14:21 rocket sshd[29046]: Failed password for invalid user wlw from 51.91.110.170 port 36614 ssh2
...
2020-07-25 12:28:11
123.25.121.84 attackbotsspam
20/7/24@23:55:46: FAIL: Alarm-Network address from=123.25.121.84
...
2020-07-25 12:30:55
187.162.25.111 attackbots
Automatic report - Port Scan Attack
2020-07-25 12:26:12
49.88.112.115 attackspambots
Jul 24 18:41:03 hanapaa sshd\[12813\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.115  user=root
Jul 24 18:41:05 hanapaa sshd\[12813\]: Failed password for root from 49.88.112.115 port 43184 ssh2
Jul 24 18:41:07 hanapaa sshd\[12813\]: Failed password for root from 49.88.112.115 port 43184 ssh2
Jul 24 18:41:10 hanapaa sshd\[12813\]: Failed password for root from 49.88.112.115 port 43184 ssh2
Jul 24 18:42:15 hanapaa sshd\[12900\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.115  user=root
2020-07-25 12:44:30
58.250.164.246 attackspambots
Jul 25 06:10:48 roki-contabo sshd\[20559\]: Invalid user uos from 58.250.164.246
Jul 25 06:10:48 roki-contabo sshd\[20559\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.250.164.246
Jul 25 06:10:51 roki-contabo sshd\[20559\]: Failed password for invalid user uos from 58.250.164.246 port 41788 ssh2
Jul 25 06:18:15 roki-contabo sshd\[20691\]: Invalid user lass from 58.250.164.246
Jul 25 06:18:15 roki-contabo sshd\[20691\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.250.164.246
...
2020-07-25 12:25:15
106.53.74.246 attackspam
2020-07-25T04:04:05.669682abusebot-8.cloudsearch.cf sshd[11938]: Invalid user intro from 106.53.74.246 port 58578
2020-07-25T04:04:05.675549abusebot-8.cloudsearch.cf sshd[11938]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.53.74.246
2020-07-25T04:04:05.669682abusebot-8.cloudsearch.cf sshd[11938]: Invalid user intro from 106.53.74.246 port 58578
2020-07-25T04:04:08.154929abusebot-8.cloudsearch.cf sshd[11938]: Failed password for invalid user intro from 106.53.74.246 port 58578 ssh2
2020-07-25T04:11:01.388132abusebot-8.cloudsearch.cf sshd[12042]: Invalid user it from 106.53.74.246 port 39656
2020-07-25T04:11:01.395352abusebot-8.cloudsearch.cf sshd[12042]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.53.74.246
2020-07-25T04:11:01.388132abusebot-8.cloudsearch.cf sshd[12042]: Invalid user it from 106.53.74.246 port 39656
2020-07-25T04:11:03.649131abusebot-8.cloudsearch.cf sshd[12042]: Failed passw
...
2020-07-25 12:13:03
181.30.28.198 attack
Invalid user ying from 181.30.28.198 port 45788
2020-07-25 12:17:31
14.243.201.17 attackspam
Unauthorised access (Jul 25) SRC=14.243.201.17 LEN=52 TTL=113 ID=1151 DF TCP DPT=445 WINDOW=8192 SYN
2020-07-25 12:35:03
175.172.166.34 attackbots
Jul 25 06:29:34 ns381471 sshd[23559]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.172.166.34
Jul 25 06:29:36 ns381471 sshd[23559]: Failed password for invalid user lina from 175.172.166.34 port 39908 ssh2
2020-07-25 12:32:09
192.42.116.26 attack
Jul 25 05:55:18 mout sshd[15504]: Failed password for sshd from 192.42.116.26 port 37890 ssh2
Jul 25 05:55:19 mout sshd[15504]: Failed password for sshd from 192.42.116.26 port 37890 ssh2
Jul 25 05:55:21 mout sshd[15504]: Failed password for sshd from 192.42.116.26 port 37890 ssh2
2020-07-25 12:51:29
94.102.53.112 attackbots
Jul 25 06:13:54 debian-2gb-nbg1-2 kernel: \[17908951.208723\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=94.102.53.112 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=29331 PROTO=TCP SPT=43043 DPT=602 WINDOW=1024 RES=0x00 SYN URGP=0
2020-07-25 12:23:09
121.121.177.112 attackspambots
Jul 25 04:34:02 localhost sshd[65710]: Invalid user llq from 121.121.177.112 port 65457
Jul 25 04:34:02 localhost sshd[65710]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.121.177.112
Jul 25 04:34:02 localhost sshd[65710]: Invalid user llq from 121.121.177.112 port 65457
Jul 25 04:34:04 localhost sshd[65710]: Failed password for invalid user llq from 121.121.177.112 port 65457 ssh2
Jul 25 04:38:48 localhost sshd[66277]: Invalid user influxdb from 121.121.177.112 port 3287
...
2020-07-25 12:39:34
185.220.101.215 attackbots
Jul 25 05:55:37 mout sshd[15540]: Failed password for sshd from 185.220.101.215 port 23412 ssh2
Jul 25 05:55:40 mout sshd[15540]: Failed password for sshd from 185.220.101.215 port 23412 ssh2
Jul 25 05:55:43 mout sshd[15540]: Failed password for sshd from 185.220.101.215 port 23412 ssh2
2020-07-25 12:31:41

Recently Reported IPs

120.231.107.227 110.52.23.17 103.78.127.43 61.244.38.5
101.36.166.17 101.36.166.18 18.201.168.187 124.134.135.229
112.20.22.251 198.18.0.253 39.183.159.250 39.182.25.158
39.154.172.224 39.154.15.220 39.154.14.30 39.146.239.16
27.209.34.236 223.88.30.136 223.87.52.191 223.74.233.17