必须是合法有效的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-AU5)
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 112.8.81.107
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25848
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;112.8.81.107.			IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 11 04:02:36 CST 2026
;; MSG SIZE  rcvd: 105
HOST信息:
Host 107.81.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 107.81.8.112.in-addr.arpa: SERVFAIL
相关IP信息:
最新评论:
IP 类型 评论内容 时间
134.209.83.191 attackbotsspam
Automatic report - SSH Brute-Force Attack
2019-10-16 14:31:14
189.254.33.157 attackbots
Oct 16 08:47:46 MK-Soft-VM5 sshd[19992]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.254.33.157 
Oct 16 08:47:48 MK-Soft-VM5 sshd[19992]: Failed password for invalid user ubuntu from 189.254.33.157 port 44964 ssh2
...
2019-10-16 14:57:21
222.186.180.147 attackspambots
Oct 16 08:58:15 dedicated sshd[4717]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.147  user=root
Oct 16 08:58:17 dedicated sshd[4717]: Failed password for root from 222.186.180.147 port 26538 ssh2
2019-10-16 15:04:30
182.72.139.6 attackbots
Oct 16 07:00:54 microserver sshd[789]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.72.139.6  user=root
Oct 16 07:00:56 microserver sshd[789]: Failed password for root from 182.72.139.6 port 45066 ssh2
Oct 16 07:05:20 microserver sshd[1467]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.72.139.6  user=root
Oct 16 07:05:22 microserver sshd[1467]: Failed password for root from 182.72.139.6 port 55794 ssh2
Oct 16 07:09:50 microserver sshd[1769]: Invalid user sekar from 182.72.139.6 port 38296
Oct 16 07:23:12 microserver sshd[3761]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.72.139.6  user=root
Oct 16 07:23:14 microserver sshd[3761]: Failed password for root from 182.72.139.6 port 42290 ssh2
Oct 16 07:27:44 microserver sshd[4416]: Invalid user benny from 182.72.139.6 port 53028
Oct 16 07:27:44 microserver sshd[4416]: pam_unix(sshd:auth): authentication failure; logname= uid
2019-10-16 14:52:00
113.208.95.69 attack
Oct 15 23:37:44 afssrv01 sshd[11907]: Address 113.208.95.69 maps to host-113-208-95-069.absatellhostnamee.net, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Oct 15 23:37:44 afssrv01 sshd[11907]: User r.r from 113.208.95.69 not allowed because not listed in AllowUsers
Oct 15 23:37:44 afssrv01 sshd[11907]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.208.95.69  user=r.r
Oct 15 23:37:45 afssrv01 sshd[11907]: Failed password for invalid user r.r from 113.208.95.69 port 45554 ssh2
Oct 15 23:37:46 afssrv01 sshd[11907]: Received disconnect from 113.208.95.69: 11: Bye Bye [preauth]
Oct 15 23:47:15 afssrv01 sshd[13592]: Address 113.208.95.69 maps to host-113-208-95-069.absatellhostnamee.net, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Oct 15 23:47:15 afssrv01 sshd[13592]: User r.r from 113.208.95.69 not allowed because not listed in AllowUsers
Oct 15 23:47:15 afssrv01 sshd[13592]: ........
-------------------------------
2019-10-16 14:44:59
42.247.22.65 attackspambots
Oct 16 06:36:20 SilenceServices sshd[32711]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.247.22.65
Oct 16 06:36:22 SilenceServices sshd[32711]: Failed password for invalid user ok123456 from 42.247.22.65 port 53223 ssh2
Oct 16 06:41:10 SilenceServices sshd[1638]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.247.22.65
2019-10-16 14:54:10
139.59.135.84 attackbots
2019-10-16T06:47:34.814577abusebot-5.cloudsearch.cf sshd\[17698\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.135.84  user=root
2019-10-16 14:59:51
49.207.183.45 attack
2019-10-16T08:32:43.678632scmdmz1 sshd\[18578\]: Invalid user ism from 49.207.183.45 port 54146
2019-10-16T08:32:43.683020scmdmz1 sshd\[18578\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.207.183.45
2019-10-16T08:32:44.877293scmdmz1 sshd\[18578\]: Failed password for invalid user ism from 49.207.183.45 port 54146 ssh2
...
2019-10-16 14:38:13
220.76.107.50 attack
Oct 16 08:52:28 server sshd\[3764\]: Failed password for invalid user paxos from 220.76.107.50 port 35496 ssh2
Oct 16 09:09:07 server sshd\[9293\]: Invalid user shreeram from 220.76.107.50
Oct 16 09:09:07 server sshd\[9293\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.76.107.50 
Oct 16 09:09:09 server sshd\[9293\]: Failed password for invalid user shreeram from 220.76.107.50 port 45052 ssh2
Oct 16 09:13:21 server sshd\[10802\]: Invalid user Password222 from 220.76.107.50
...
2019-10-16 15:02:30
31.128.19.116 attackspam
Automatic report - Port Scan Attack
2019-10-16 14:35:31
188.254.0.214 attack
Oct 15 18:12:04 auw2 sshd\[24697\]: Invalid user apt1306 from 188.254.0.214
Oct 15 18:12:04 auw2 sshd\[24697\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.214
Oct 15 18:12:07 auw2 sshd\[24697\]: Failed password for invalid user apt1306 from 188.254.0.214 port 39814 ssh2
Oct 15 18:16:13 auw2 sshd\[25089\]: Invalid user 111111 from 188.254.0.214
Oct 15 18:16:13 auw2 sshd\[25089\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.214
2019-10-16 15:07:49
104.238.120.6 attackspam
Automatic report - XMLRPC Attack
2019-10-16 14:32:52
165.22.130.8 attackbotsspam
Oct 16 08:50:14 server sshd\[3230\]: Failed password for invalid user user from 165.22.130.8 port 45064 ssh2
Oct 16 08:57:27 server sshd\[5370\]: Invalid user disklessadmin from 165.22.130.8
Oct 16 08:57:27 server sshd\[5370\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.130.8 
Oct 16 08:57:30 server sshd\[5370\]: Failed password for invalid user disklessadmin from 165.22.130.8 port 41230 ssh2
Oct 16 09:11:50 server sshd\[10408\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.130.8  user=root
...
2019-10-16 14:40:47
139.155.1.252 attackbots
2019-10-16T08:18:48.669850scmdmz1 sshd\[17175\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.1.252  user=root
2019-10-16T08:18:50.903024scmdmz1 sshd\[17175\]: Failed password for root from 139.155.1.252 port 54680 ssh2
2019-10-16T08:23:29.589944scmdmz1 sshd\[17542\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.1.252  user=root
...
2019-10-16 14:49:49
185.156.1.99 attackspam
Oct 16 08:26:16 MK-Soft-VM4 sshd[10445]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.156.1.99 
Oct 16 08:26:19 MK-Soft-VM4 sshd[10445]: Failed password for invalid user changeme from 185.156.1.99 port 51943 ssh2
...
2019-10-16 15:01:56

最近上报的IP列表

115.60.177.129 112.51.80.47 112.51.225.115 112.50.61.177
112.49.247.82 112.47.133.64 112.32.126.201 112.22.224.2
112.0.126.207 111.208.78.101 111.19.19.242 111.18.202.130
111.15.64.171 110.248.114.52 45.79.192.82 72.14.187.207
61.52.122.253 45.79.192.205 39.162.92.89 39.162.181.191