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

城市(city): unknown

省份(region): Shandong

国家(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 '112.0.0.0 - 112.63.255.255'

% Abuse contact for '112.0.0.0 - 112.63.255.255' is 'abuse@chinamobile.com'

inetnum:        112.0.0.0 - 112.63.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
status:         ALLOCATED PORTABLE
abuse-c:        AC2006-AP
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:  2026-05-22T03:50:58Z
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 '112.8.0.0/13AS9808'

route:          112.8.0.0/13
descr:          China Mobile communications corporation
origin:         AS9808
mnt-by:         MAINT-CN-CMCC
last-modified:  2009-10-20T06:48:13Z
source:         APNIC

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

;; QUESTION SECTION:
;112.8.135.220.			IN	A

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

;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Sep 27 07:00:45 CST 2026
;; MSG SIZE  rcvd: 106
HOST信息:
Host 220.135.8.112.in-addr.arpa not found: 2(SERVFAIL)
NSLOOKUP信息:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 220.135.8.112.in-addr.arpa: SERVFAIL
相关IP信息:
最新评论:
IP 类型 评论内容 时间
94.177.215.195 attackbots
(sshd) Failed SSH login from 94.177.215.195 (IT/Italy/host195-215-177-94.serverdedicati.aruba.it): 3 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr  8 21:38:24 andromeda sshd[17773]: Invalid user chris from 94.177.215.195 port 47020
Apr  8 21:38:27 andromeda sshd[17773]: Failed password for invalid user chris from 94.177.215.195 port 47020 ssh2
Apr  8 21:47:42 andromeda sshd[18547]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.177.215.195  user=admin
2020-04-09 09:25:04
211.21.157.226 attack
Apr  9 03:03:24 markkoudstaal sshd[16350]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.21.157.226
Apr  9 03:03:27 markkoudstaal sshd[16350]: Failed password for invalid user postgres from 211.21.157.226 port 42644 ssh2
Apr  9 03:05:48 markkoudstaal sshd[16730]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.21.157.226
2020-04-09 09:27:31
111.93.4.174 attackspambots
2020-04-09T03:08:49.138507struts4.enskede.local sshd\[14557\]: Invalid user deploy from 111.93.4.174 port 56292
2020-04-09T03:08:49.144482struts4.enskede.local sshd\[14557\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.93.4.174
2020-04-09T03:08:52.329124struts4.enskede.local sshd\[14557\]: Failed password for invalid user deploy from 111.93.4.174 port 56292 ssh2
2020-04-09T03:16:50.680801struts4.enskede.local sshd\[14738\]: Invalid user developer from 111.93.4.174 port 53330
2020-04-09T03:16:50.687111struts4.enskede.local sshd\[14738\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.93.4.174
...
2020-04-09 09:31:20
90.107.254.153 attackbotsspam
Apr  8 23:47:41 * sshd[10189]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=90.107.254.153
Apr  8 23:47:41 * sshd[10190]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=90.107.254.153
2020-04-09 09:31:41
68.183.22.85 attackbotsspam
Apr  8 21:35:47 firewall sshd[9906]: Invalid user plegrand from 68.183.22.85
Apr  8 21:35:49 firewall sshd[9906]: Failed password for invalid user plegrand from 68.183.22.85 port 59842 ssh2
Apr  8 21:42:52 firewall sshd[10248]: Invalid user admin from 68.183.22.85
...
2020-04-09 09:07:33
178.201.164.76 attack
2020-04-08T23:47:50.763748librenms sshd[10187]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip-178-201-164-76.hsi08.unitymediagroup.de
2020-04-08T23:47:50.760660librenms sshd[10187]: Invalid user jpg from 178.201.164.76 port 55998
2020-04-08T23:47:52.872534librenms sshd[10187]: Failed password for invalid user jpg from 178.201.164.76 port 55998 ssh2
...
2020-04-09 09:19:24
129.204.82.4 attackspam
Tried sshing with brute force.
2020-04-09 09:28:45
175.124.43.162 attack
Apr  8 16:32:05 server1 sshd\[11763\]: Failed password for invalid user atv from 175.124.43.162 port 41674 ssh2
Apr  8 16:34:11 server1 sshd\[12757\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.124.43.162  user=root
Apr  8 16:34:14 server1 sshd\[12757\]: Failed password for root from 175.124.43.162 port 48550 ssh2
Apr  8 16:36:26 server1 sshd\[14399\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.124.43.162  user=root
Apr  8 16:36:28 server1 sshd\[14399\]: Failed password for root from 175.124.43.162 port 55420 ssh2
...
2020-04-09 09:39:09
222.186.42.75 attackspambots
Apr  9 02:47:12 dcd-gentoo sshd[27417]: User root from 222.186.42.75 not allowed because none of user's groups are listed in AllowGroups
Apr  9 02:47:14 dcd-gentoo sshd[27417]: error: PAM: Authentication failure for illegal user root from 222.186.42.75
Apr  9 02:47:12 dcd-gentoo sshd[27417]: User root from 222.186.42.75 not allowed because none of user's groups are listed in AllowGroups
Apr  9 02:47:14 dcd-gentoo sshd[27417]: error: PAM: Authentication failure for illegal user root from 222.186.42.75
Apr  9 02:47:12 dcd-gentoo sshd[27417]: User root from 222.186.42.75 not allowed because none of user's groups are listed in AllowGroups
Apr  9 02:47:14 dcd-gentoo sshd[27417]: error: PAM: Authentication failure for illegal user root from 222.186.42.75
Apr  9 02:47:14 dcd-gentoo sshd[27417]: Failed keyboard-interactive/pam for invalid user root from 222.186.42.75 port 32398 ssh2
...
2020-04-09 09:03:46
106.13.168.150 attack
Apr  9 06:15:11 webhost01 sshd[7786]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.168.150
Apr  9 06:15:13 webhost01 sshd[7786]: Failed password for invalid user rstudio from 106.13.168.150 port 50796 ssh2
...
2020-04-09 09:17:53
94.191.10.105 attackbots
k+ssh-bruteforce
2020-04-09 09:35:11
201.190.152.230 attackbots
Apr  8 18:47:37 ws24vmsma01 sshd[245723]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.190.152.230
Apr  8 18:47:39 ws24vmsma01 sshd[245723]: Failed password for invalid user osm from 201.190.152.230 port 38084 ssh2
...
2020-04-09 09:30:18
129.226.50.78 attackspambots
$f2bV_matches
2020-04-09 09:33:24
136.232.243.134 attack
Apr  8 23:47:53 nextcloud sshd\[15238\]: Invalid user share from 136.232.243.134
Apr  8 23:47:53 nextcloud sshd\[15238\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=136.232.243.134
Apr  8 23:47:54 nextcloud sshd\[15238\]: Failed password for invalid user share from 136.232.243.134 port 49186 ssh2
2020-04-09 09:15:46
222.186.30.76 attackbotsspam
Apr  9 01:06:22 localhost sshd[30369]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76  user=root
Apr  9 01:06:24 localhost sshd[30369]: Failed password for root from 222.186.30.76 port 47344 ssh2
Apr  9 01:06:27 localhost sshd[30369]: Failed password for root from 222.186.30.76 port 47344 ssh2
Apr  9 01:06:22 localhost sshd[30369]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76  user=root
Apr  9 01:06:24 localhost sshd[30369]: Failed password for root from 222.186.30.76 port 47344 ssh2
Apr  9 01:06:27 localhost sshd[30369]: Failed password for root from 222.186.30.76 port 47344 ssh2
Apr  9 01:14:32 localhost sshd[31447]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76  user=root
Apr  9 01:14:35 localhost sshd[31447]: Failed password for root from 222.186.30.76 port 40425 ssh2
...
2020-04-09 09:18:32

最近上报的IP列表

254.60.51.57 40.124.178.103 24.242.66.11 225.31.74.112
230.10.225.149 224.77.172.3 40.80.203.186 224.206.149.210
139.189.115.109 45.74.28.65 112.251.144.236 104.155.207.153
40.76.224.207 217.11.249.149 216.180.135.149 214.238.211.7
40.143.26.106 2.193.66.85 2.193.66.226 213.241.50.222