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

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-03-23
mnt-by:         MAINT-CN-CMCC
last-modified:  2026-08-13T06:25:29Z
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-03-23
abuse-mailbox:  abuse@chinamobile.com
mnt-by:         APNIC-ABUSE
last-modified:  2026-03-23T00:48:02Z
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.224.0.0/12AS9808'

route:          120.224.0.0/12
descr:          China Mobile communications corporation
origin:         AS9808
mnt-by:         MAINT-CN-CMCC
last-modified:  2008-11-05T07:40:19Z
source:         APNIC

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

;; QUESTION SECTION:
;120.230.22.125.			IN	A

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

;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Sep 03 11:32:12 CST 2026
;; MSG SIZE  rcvd: 107
Host info
Host 125.22.230.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 125.22.230.120.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
116.241.184.206 attackspam
2020-02-08T01:06:56.235441vostok sshd\[20055\]: Invalid user jzm from 116.241.184.206 port 47550
2020-02-08T01:06:56.239162vostok sshd\[20055\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.241.184.206 | Triggered by Fail2Ban at Vostok web server
2020-02-08 14:14:22
125.18.79.123 attackbots
23/tcp
[2020-02-08]1pkt
2020-02-08 14:09:15
152.101.194.18 attackspam
Feb  8 06:49:00 sd-53420 sshd\[22455\]: Invalid user cqz from 152.101.194.18
Feb  8 06:49:00 sd-53420 sshd\[22455\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.101.194.18
Feb  8 06:49:01 sd-53420 sshd\[22455\]: Failed password for invalid user cqz from 152.101.194.18 port 54298 ssh2
Feb  8 06:50:55 sd-53420 sshd\[22715\]: Invalid user zyp from 152.101.194.18
Feb  8 06:50:55 sd-53420 sshd\[22715\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.101.194.18
...
2020-02-08 14:06:52
59.44.152.108 attackspam
2020-2-8 6:28:20 AM: failed ssh attempt
2020-02-08 14:10:48
106.75.74.225 attackspambots
02/07/2020-23:58:41.647752 106.75.74.225 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-02-08 13:59:47
157.245.252.2 attackspam
2020-02-07T23:32:47.9396831495-001 sshd[43205]: Invalid user rga from 157.245.252.2 port 49906
2020-02-07T23:32:47.9479771495-001 sshd[43205]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.245.252.2
2020-02-07T23:32:47.9396831495-001 sshd[43205]: Invalid user rga from 157.245.252.2 port 49906
2020-02-07T23:32:50.0083251495-001 sshd[43205]: Failed password for invalid user rga from 157.245.252.2 port 49906 ssh2
2020-02-07T23:43:21.9194431495-001 sshd[43804]: Invalid user xgr from 157.245.252.2 port 57464
2020-02-07T23:43:21.9243131495-001 sshd[43804]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.245.252.2
2020-02-07T23:43:21.9194431495-001 sshd[43804]: Invalid user xgr from 157.245.252.2 port 57464
2020-02-07T23:43:24.0198281495-001 sshd[43804]: Failed password for invalid user xgr from 157.245.252.2 port 57464 ssh2
2020-02-07T23:45:35.5550561495-001 sshd[43932]: Invalid user hxa from 157.245.25
...
2020-02-08 13:50:07
58.215.57.157 attackbots
20/2/7@23:59:14: FAIL: Alarm-Intrusion address from=58.215.57.157
...
2020-02-08 13:40:56
184.82.9.210 attack
20/2/7@23:59:17: FAIL: Alarm-Telnet address from=184.82.9.210
...
2020-02-08 13:39:42
157.55.39.175 attackbots
Automatic report - Banned IP Access
2020-02-08 13:50:32
158.69.223.91 attackbotsspam
Feb  8 05:34:40 work-partkepr sshd\[12894\]: Invalid user jif from 158.69.223.91 port 54029
Feb  8 05:34:40 work-partkepr sshd\[12894\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.69.223.91
...
2020-02-08 14:00:13
217.182.129.39 attackbotsspam
Feb  8 06:10:36 localhost sshd\[21439\]: Invalid user joe from 217.182.129.39 port 41520
Feb  8 06:10:36 localhost sshd\[21439\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.182.129.39
Feb  8 06:10:38 localhost sshd\[21439\]: Failed password for invalid user joe from 217.182.129.39 port 41520 ssh2
2020-02-08 13:33:13
193.188.22.196 attackspambots
RDP Bruteforce
2020-02-08 14:01:28
93.174.93.195 attackbots
93.174.93.195 was recorded 27 times by 11 hosts attempting to connect to the following ports: 40822,40815,40820. Incident counter (4h, 24h, all-time): 27, 157, 3786
2020-02-08 13:42:51
222.186.30.218 attackspam
Feb  8 07:11:51 silence02 sshd[9493]: Failed password for root from 222.186.30.218 port 22377 ssh2
Feb  8 07:11:53 silence02 sshd[9493]: Failed password for root from 222.186.30.218 port 22377 ssh2
Feb  8 07:11:55 silence02 sshd[9493]: Failed password for root from 222.186.30.218 port 22377 ssh2
2020-02-08 14:13:04
222.186.175.140 attackbotsspam
Feb  7 19:26:38 kapalua sshd\[4839\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.140  user=root
Feb  7 19:26:39 kapalua sshd\[4839\]: Failed password for root from 222.186.175.140 port 1152 ssh2
Feb  7 19:26:43 kapalua sshd\[4839\]: Failed password for root from 222.186.175.140 port 1152 ssh2
Feb  7 19:26:56 kapalua sshd\[4872\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.140  user=root
Feb  7 19:26:58 kapalua sshd\[4872\]: Failed password for root from 222.186.175.140 port 8824 ssh2
2020-02-08 13:29:57

Recently Reported IPs

120.235.42.126 112.50.61.189 112.0.139.92 47.95.202.140
42.236.216.126 42.234.20.249 223.106.31.100 222.132.122.124
14.205.90.20 1.28.108.28 124.133.59.46 121.24.3.115
2606:4700:10::6814:8535 14.207.194.182 119.250.130.152 115.54.175.216
112.111.128.170 111.35.241.67 111.166.154.138 110.241.45.14