必须是合法有效的IP地址, 可以是IPv4或者是IPv6, 例如127.0.0.1或者2001:DB8:0:0:8:800:200C:417A
基本信息:

城市(city): Guangzhou

省份(region): Guangdong

国家(country): China

运营商(isp): China Mobile

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
暂无关于此IP所属子网相关IP的讨论.
WHOIS信息:
% [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 2025-09-15
mnt-by:         MAINT-CN-CMCC
last-modified:  2025-11-18T00:26:27Z
source:         APNIC

organisation:   ORG-CM1-AP
org-name:       China Mobile
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:  2023-09-05T02:14:48Z
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 2025-09-15
abuse-mailbox:  abuse@chinamobile.com
mnt-by:         APNIC-ABUSE
last-modified:  2025-09-15T02:20:13Z
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.47 (WHOIS-AU4)
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 120.235.44.94
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51473
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;120.235.44.94.			IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 05 22:55:14 CST 2026
;; MSG SIZE  rcvd: 106
HOST信息:
Host 94.44.235.120.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 94.44.235.120.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
165.227.97.108 attackbotsspam
Aug 22 12:43:04 cp sshd[670]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.97.108
Aug 22 12:43:06 cp sshd[670]: Failed password for invalid user upload from 165.227.97.108 port 35654 ssh2
Aug 22 12:47:53 cp sshd[4132]: Failed password for root from 165.227.97.108 port 50952 ssh2
2019-08-22 19:09:45
51.83.40.213 attack
Aug 21 23:28:48 kapalua sshd\[12837\]: Invalid user 1 from 51.83.40.213
Aug 21 23:28:48 kapalua sshd\[12837\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.ip-51-83-40.eu
Aug 21 23:28:50 kapalua sshd\[12837\]: Failed password for invalid user 1 from 51.83.40.213 port 45760 ssh2
Aug 21 23:32:39 kapalua sshd\[13327\]: Invalid user minecraft from 51.83.40.213
Aug 21 23:32:39 kapalua sshd\[13327\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.ip-51-83-40.eu
2019-08-22 18:37:50
220.176.204.91 attackspam
2019-08-22T09:57:07.810796abusebot-7.cloudsearch.cf sshd\[8427\]: Invalid user ca from 220.176.204.91 port 40197
2019-08-22 18:13:59
186.4.224.171 attackbots
Aug 22 00:52:06 hcbb sshd\[12926\]: Invalid user ftpvm from 186.4.224.171
Aug 22 00:52:06 hcbb sshd\[12926\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=host-186-4-224-171.netlife.ec
Aug 22 00:52:08 hcbb sshd\[12926\]: Failed password for invalid user ftpvm from 186.4.224.171 port 35852 ssh2
Aug 22 00:56:50 hcbb sshd\[13404\]: Invalid user ntadmin from 186.4.224.171
Aug 22 00:56:50 hcbb sshd\[13404\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=host-186-4-224-171.netlife.ec
2019-08-22 19:09:15
92.63.194.47 attackspambots
Automatic report - Banned IP Access
2019-08-22 18:49:15
222.186.15.110 attackspam
Aug 22 06:37:43 TORMINT sshd\[16034\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.15.110  user=root
Aug 22 06:37:46 TORMINT sshd\[16034\]: Failed password for root from 222.186.15.110 port 26060 ssh2
Aug 22 06:37:53 TORMINT sshd\[16036\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.15.110  user=root
...
2019-08-22 18:51:46
195.154.221.30 attackspambots
Automatic report - Port Scan Attack
2019-08-22 18:05:22
139.59.8.66 attackspambots
Aug 22 06:54:18 TORMINT sshd\[16973\]: Invalid user marko from 139.59.8.66
Aug 22 06:54:18 TORMINT sshd\[16973\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.8.66
Aug 22 06:54:20 TORMINT sshd\[16973\]: Failed password for invalid user marko from 139.59.8.66 port 36764 ssh2
...
2019-08-22 19:03:53
36.156.24.78 attackspambots
SSH Brute Force, server-1 sshd[3755]: Failed password for root from 36.156.24.78 port 40772 ssh2
2019-08-22 18:06:01
5.196.204.173 attackbots
Attempted WordPress login: "GET /wp-login.php"
2019-08-22 18:45:23
67.205.177.0 attack
Aug 22 10:35:47 hb sshd\[19139\]: Invalid user deploy from 67.205.177.0
Aug 22 10:35:47 hb sshd\[19139\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.205.177.0
Aug 22 10:35:49 hb sshd\[19139\]: Failed password for invalid user deploy from 67.205.177.0 port 50690 ssh2
Aug 22 10:40:00 hb sshd\[19539\]: Invalid user gaming from 67.205.177.0
Aug 22 10:40:00 hb sshd\[19539\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.205.177.0
2019-08-22 18:52:45
106.12.83.210 attack
Aug 22 06:14:29 xtremcommunity sshd\[9163\]: Invalid user romeo from 106.12.83.210 port 47832
Aug 22 06:14:29 xtremcommunity sshd\[9163\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.83.210
Aug 22 06:14:32 xtremcommunity sshd\[9163\]: Failed password for invalid user romeo from 106.12.83.210 port 47832 ssh2
Aug 22 06:18:43 xtremcommunity sshd\[9404\]: Invalid user ts3 from 106.12.83.210 port 59756
Aug 22 06:18:43 xtremcommunity sshd\[9404\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.83.210
...
2019-08-22 18:32:33
197.45.177.130 attackspambots
19/8/22@05:05:43: FAIL: Alarm-Intrusion address from=197.45.177.130
...
2019-08-22 19:03:36
144.217.234.174 attack
Aug 22 03:41:55 dallas01 sshd[6668]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.234.174
Aug 22 03:41:57 dallas01 sshd[6668]: Failed password for invalid user recovery from 144.217.234.174 port 38297 ssh2
Aug 22 03:45:57 dallas01 sshd[7245]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.234.174
2019-08-22 18:43:15
134.209.7.179 attackspambots
Aug 22 12:51:41 vps691689 sshd[19412]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.7.179
Aug 22 12:51:43 vps691689 sshd[19412]: Failed password for invalid user ovidiu from 134.209.7.179 port 34782 ssh2
...
2019-08-22 19:07:59

最近上报的IP列表

101.236.211.26 47.77.235.0 20.220.62.160 185.93.89.75
38.244.66.157 198.145.121.150 10.40.3.254 10.40.3.71
213.209.159.175 213.176.16.157 39.173.107.62 20.231.128.65
18.203.221.131 161.118.250.115 111.250.107.10 172.237.120.154
27.45.39.56 40.104.20.40 103.122.164.65 5.236.105.164