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 Mobile

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 '120.192.0.0 - 120.255.255.255'

% Abuse contact for '120.192.0.0 - 120.255.255.255' is 'abuse@chinamobile.com'

inetnum:        120.192.0.0 - 120.255.255.255
netname:        CMNET
descr:          China Mobile Communications Corporation
descr:          Mobile Communications Network Operator in China
descr:          Internet Service Provider in China
country:        CN
org:            ORG-CM1-AP
admin-c:        ct74-AP
tech-c:         HL1318-AP
abuse-c:        AC2006-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-CN-CMCC
mnt-routes:     MAINT-CN-CMCC
mnt-irt:        IRT-CHINAMOBILE-CN
last-modified:  2020-07-15T13:10:01Z
source:         APNIC

irt:            IRT-CHINAMOBILE-CN
address:        China Mobile Communications Corporation
address:        29, Jinrong Ave., Xicheng District, Beijing, 100032
e-mail:         abuse@chinamobile.com
abuse-mailbox:  abuse@chinamobile.com
admin-c:        CT74-AP
tech-c:         CT74-AP
auth:           # Filtered
remarks:        abuse@chinamobile.com was validated on 2026-09-30
mnt-by:         MAINT-CN-CMCC
last-modified:  2026-09-30T02:37:06Z
source:         APNIC

organisation:   ORG-CM1-AP
org-name:       China Mobile Communications Group Co., Ltd
org-type:       LIR
country:        CN
address:        29, Jinrong Ave.
phone:          +86-10-5268-6688
fax-no:         +86-10-5261-6187
e-mail:         hostmaster@chinamobile.com
mnt-ref:        APNIC-HM
mnt-by:         APNIC-HM
last-modified:  2026-07-31T13:46:41Z
source:         APNIC

role:           ABUSE CHINAMOBILECN
country:        ZZ
address:        China Mobile Communications Corporation
address:        29, Jinrong Ave., Xicheng District, Beijing, 100032
phone:          +000000000
e-mail:         abuse@chinamobile.com
admin-c:        CT74-AP
tech-c:         CT74-AP
nic-hdl:        AC2006-AP
remarks:        Generated from irt object IRT-CHINAMOBILE-CN
remarks:        abuse@chinamobile.com was validated on 2026-09-30
abuse-mailbox:  abuse@chinamobile.com
mnt-by:         APNIC-ABUSE
last-modified:  2026-09-30T02:37:41Z
source:         APNIC

role:           chinamobile tech
address:        29, Jinrong Ave.,Xicheng district
address:        Beijing
country:        CN
phone:          +86 5268 6688
fax-no:         +86 5261 6187
e-mail:         hostmaster@chinamobile.com
admin-c:        HL1318-AP
tech-c:         HL1318-AP
nic-hdl:        ct74-AP
notify:         hostmaster@chinamobile.com
mnt-by:         MAINT-cn-cmcc
abuse-mailbox:  abuse@chinamobile.com
last-modified:  2016-11-29T09:37:27Z
source:         APNIC

person:         haijun li
nic-hdl:        HL1318-AP
e-mail:         hostmaster@chinamobile.com
address:        29,Jinrong Ave, Xicheng district,beijing,100032
phone:          +86 1052686688
fax-no:         +86 10 52616187
country:        CN
mnt-by:         MAINT-CN-CMCC
abuse-mailbox:  abuse@chinamobile.com
last-modified:  2016-11-29T09:38:38Z
source:         APNIC

% Information related to '120.240.0.0/13AS9808'

route:          120.240.0.0/13
descr:          China Mobile communications corporation
origin:         AS9808
mnt-by:         MAINT-CN-CMCC
last-modified:  2008-11-05T07:45:20Z
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 <<>> 120.245.130.242
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 36991
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;120.245.130.242.		IN	A

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

;; Query time: 4 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Oct 17 01:00:28 CST 2026
;; MSG SIZE  rcvd: 108
Host info
Host 242.130.245.120.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 242.130.245.120.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
113.173.116.132 attackbots
Nov 27 07:47:32 pl3server sshd[12182]: Address 113.173.116.132 maps to static.vnpt.vn, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Nov 27 07:47:32 pl3server sshd[12182]: Invalid user admin from 113.173.116.132
Nov 27 07:47:32 pl3server sshd[12182]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.173.116.132
Nov 27 07:47:33 pl3server sshd[12182]: Failed password for invalid user admin from 113.173.116.132 port 44617 ssh2
Nov 27 07:47:34 pl3server sshd[12182]: Connection closed by 113.173.116.132 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=113.173.116.132
2019-12-01 00:15:25
218.92.0.133 attackspam
Nov 30 15:59:41 game-panel sshd[9763]: Failed password for root from 218.92.0.133 port 25225 ssh2
Nov 30 15:59:57 game-panel sshd[9763]: error: maximum authentication attempts exceeded for root from 218.92.0.133 port 25225 ssh2 [preauth]
Nov 30 16:00:03 game-panel sshd[9765]: Failed password for root from 218.92.0.133 port 65107 ssh2
2019-12-01 00:02:25
200.57.73.170 attackbotsspam
Nov 30 09:36:56 web1 postfix/smtpd[16997]: warning: unknown[200.57.73.170]: SASL LOGIN authentication failed: authentication failure
...
2019-12-01 00:07:41
164.132.102.168 attackspambots
Nov 30 05:50:53 eddieflores sshd\[29236\]: Invalid user hazeldine from 164.132.102.168
Nov 30 05:50:53 eddieflores sshd\[29236\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.ip-164-132-102.eu
Nov 30 05:50:56 eddieflores sshd\[29236\]: Failed password for invalid user hazeldine from 164.132.102.168 port 56566 ssh2
Nov 30 05:53:56 eddieflores sshd\[29441\]: Invalid user ftpuser from 164.132.102.168
Nov 30 05:53:56 eddieflores sshd\[29441\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.ip-164-132-102.eu
2019-12-01 00:25:25
51.38.176.147 attack
Nov 30 16:38:07 MK-Soft-VM4 sshd[15564]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.176.147 
Nov 30 16:38:08 MK-Soft-VM4 sshd[15564]: Failed password for invalid user neptune from 51.38.176.147 port 46457 ssh2
...
2019-12-01 00:00:42
122.51.167.43 attackspambots
Nov 30 15:36:59 v22018076622670303 sshd\[16761\]: Invalid user contador from 122.51.167.43 port 56020
Nov 30 15:36:59 v22018076622670303 sshd\[16761\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.167.43
Nov 30 15:37:01 v22018076622670303 sshd\[16761\]: Failed password for invalid user contador from 122.51.167.43 port 56020 ssh2
...
2019-12-01 00:03:44
188.166.119.234 attack
2019-11-30T16:37:03.032826hz01.yumiweb.com sshd\[24593\]: Invalid user guest from 188.166.119.234 port 35320
2019-11-30T16:39:03.581622hz01.yumiweb.com sshd\[24595\]: Invalid user deploy from 188.166.119.234 port 50874
2019-11-30T16:41:10.256178hz01.yumiweb.com sshd\[24621\]: Invalid user demo from 188.166.119.234 port 38198
...
2019-12-01 00:31:07
78.88.190.170 attackbots
Nov 30 11:04:59 TORMINT sshd\[29306\]: Invalid user francoise from 78.88.190.170
Nov 30 11:04:59 TORMINT sshd\[29306\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=78.88.190.170
Nov 30 11:05:01 TORMINT sshd\[29306\]: Failed password for invalid user francoise from 78.88.190.170 port 38048 ssh2
...
2019-12-01 00:20:55
185.176.27.2 attack
Nov 30 16:45:19 h2177944 kernel: \[8003978.121423\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.176.27.2 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=41238 PROTO=TCP SPT=8080 DPT=20337 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov 30 16:45:59 h2177944 kernel: \[8004018.997020\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.176.27.2 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=14362 PROTO=TCP SPT=8080 DPT=21508 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov 30 16:50:49 h2177944 kernel: \[8004308.168485\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.176.27.2 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=7543 PROTO=TCP SPT=8080 DPT=20680 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov 30 17:00:42 h2177944 kernel: \[8004901.097559\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.176.27.2 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=11268 PROTO=TCP SPT=8080 DPT=20204 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov 30 17:03:57 h2177944 kernel: \[8005096.476055\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.176.27.2 DST=85.214.117.9 LEN=4
2019-12-01 00:25:09
69.4.83.242 attackspambots
[Sat Nov 30 15:27:42 2019] Failed password for r.r from 69.4.83.242 port 47168 ssh2
[Sat Nov 30 15:27:42 2019] Failed password for r.r from 69.4.83.242 port 47178 ssh2
[Sat Nov 30 15:27:42 2019] Failed password for r.r from 69.4.83.242 port 47166 ssh2
[Sat Nov 30 15:27:44 2019] Failed password for r.r from 69.4.83.242 port 47396 ssh2
[Sat Nov 30 15:27:45 2019] Failed password for r.r from 69.4.83.242 port 47168 ssh2
[Sat Nov 30 15:27:45 2019] Failed password for r.r from 69.4.83.242 port 47166 ssh2
[Sat Nov 30 15:27:45 2019] Failed password for r.r from 69.4.83.242 port 47178 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=69.4.83.242
2019-12-01 00:12:29
94.190.50.238 attack
Unauthorised access (Nov 30) SRC=94.190.50.238 LEN=52 TTL=119 ID=31704 DF TCP DPT=445 WINDOW=8192 SYN 
Unauthorised access (Nov 30) SRC=94.190.50.238 LEN=52 TTL=119 ID=24615 DF TCP DPT=445 WINDOW=8192 SYN
2019-12-01 00:39:56
196.34.32.164 attack
2019-11-30T15:41:56.562584abusebot-5.cloudsearch.cf sshd\[9517\]: Invalid user firdmann from 196.34.32.164 port 40956
2019-12-01 00:08:05
49.81.95.190 attackspam
$f2bV_matches
2019-12-01 00:41:17
49.51.163.30 attackbotsspam
49.51.163.30 - - \[30/Nov/2019:15:36:59 +0100\] "POST /wp-login.php HTTP/1.0" 200 5731 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
49.51.163.30 - - \[30/Nov/2019:15:36:59 +0100\] "POST /wp-login.php HTTP/1.0" 200 5598 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
49.51.163.30 - - \[30/Nov/2019:15:37:00 +0100\] "POST /wp-login.php HTTP/1.0" 200 5594 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-12-01 00:04:19
14.98.32.214 attackbots
fail2ban
2019-12-01 00:10:19

Recently Reported IPs

151.245.151.86 39.162.163.14 223.66.184.182 223.107.239.129
183.212.12.189 183.210.108.166 123.90.148.140 112.32.240.75
112.0.139.30 5.133.192.99 34.95.243.221 151.245.151.199
44.220.185.216 20.58.188.171 51.159.110.25 147.185.133.229
61.185.73.2 36.42.94.248 209.38.247.95 198.235.24.86