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

;; QUESTION SECTION:
;112.8.52.171.			IN	A

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

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Oct 13 08:32:02 CST 2026
;; MSG SIZE  rcvd: 105
HOST信息:
b'Host 171.52.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 171.52.8.112.in-addr.arpa: SERVFAIL
相关IP信息:
最新评论:
IP 类型 评论内容 时间
154.245.52.77 attackbots
Repeated attempts against wp-login
2020-04-14 13:28:27
137.74.44.162 attackbots
Apr 14 04:54:02 cdc sshd[13329]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.44.162  user=root
Apr 14 04:54:04 cdc sshd[13329]: Failed password for invalid user root from 137.74.44.162 port 50988 ssh2
2020-04-14 13:15:58
176.197.19.247 attack
" "
2020-04-14 13:38:07
178.170.58.28 attackbots
(smtpauth) Failed SMTP AUTH login from 178.170.58.28 (NL/Netherlands/frhb40262flex.ikexpress.com): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-04-14 08:23:16 login authenticator failed for frhb40262flex.ikexpress.com (ADMIN) [178.170.58.28]: 535 Incorrect authentication data (set_id=dr.akhavan@rahapharm.com)
2020-04-14 13:47:34
218.78.81.255 attack
Bruteforce detected by fail2ban
2020-04-14 13:16:52
79.80.9.110 attackspambots
Apr 14 05:41:04 scw-6657dc sshd[27151]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.80.9.110
Apr 14 05:41:04 scw-6657dc sshd[27151]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.80.9.110
Apr 14 05:41:07 scw-6657dc sshd[27151]: Failed password for invalid user admin from 79.80.9.110 port 38636 ssh2
...
2020-04-14 13:46:12
212.23.138.78 attack
Apr 14 06:50:15 debian-2gb-nbg1-2 kernel: \[9098806.465078\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=212.23.138.78 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=11419 PROTO=TCP SPT=45450 DPT=25 WINDOW=1024 RES=0x00 SYN URGP=0
2020-04-14 13:08:16
60.173.179.69 attackspambots
port scan and connect, tcp 23 (telnet)
2020-04-14 13:39:54
180.166.184.66 attackbotsspam
2020-04-14T07:09:00.710475  sshd[29543]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.166.184.66  user=root
2020-04-14T07:09:02.287634  sshd[29543]: Failed password for root from 180.166.184.66 port 49416 ssh2
2020-04-14T07:12:47.286329  sshd[29607]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.166.184.66  user=root
2020-04-14T07:12:49.691714  sshd[29607]: Failed password for root from 180.166.184.66 port 56014 ssh2
...
2020-04-14 13:23:36
128.199.79.230 attackspam
Apr 14 03:53:32 sshgateway sshd\[16632\]: Invalid user test from 128.199.79.230
Apr 14 03:53:32 sshgateway sshd\[16632\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.79.230
Apr 14 03:53:34 sshgateway sshd\[16632\]: Failed password for invalid user test from 128.199.79.230 port 46326 ssh2
2020-04-14 13:35:08
111.229.28.34 attackbots
Apr 14 05:31:50 h2646465 sshd[7136]: Invalid user postdrop from 111.229.28.34
Apr 14 05:31:50 h2646465 sshd[7136]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.28.34
Apr 14 05:31:50 h2646465 sshd[7136]: Invalid user postdrop from 111.229.28.34
Apr 14 05:31:52 h2646465 sshd[7136]: Failed password for invalid user postdrop from 111.229.28.34 port 41484 ssh2
Apr 14 05:43:24 h2646465 sshd[8455]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.28.34  user=root
Apr 14 05:43:26 h2646465 sshd[8455]: Failed password for root from 111.229.28.34 port 42970 ssh2
Apr 14 05:48:29 h2646465 sshd[9102]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.28.34  user=root
Apr 14 05:48:31 h2646465 sshd[9102]: Failed password for root from 111.229.28.34 port 41996 ssh2
Apr 14 05:53:43 h2646465 sshd[9716]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rh
2020-04-14 13:28:49
217.170.205.14 attackbotsspam
$f2bV_matches
2020-04-14 13:10:17
117.70.39.95 attackspambots
Apr 14 05:53:48 srv01 postfix/smtpd[11447]: warning: unknown[117.70.39.95]: SASL LOGIN authentication failed: authentication failure
Apr 14 05:53:49 srv01 postfix/smtpd[11447]: warning: unknown[117.70.39.95]: SASL LOGIN authentication failed: authentication failure
Apr 14 05:53:52 srv01 postfix/smtpd[11447]: warning: unknown[117.70.39.95]: SASL LOGIN authentication failed: authentication failure


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=117.70.39.95
2020-04-14 13:22:37
222.186.175.169 attack
Apr 14 07:12:32 legacy sshd[13149]: Failed password for root from 222.186.175.169 port 43096 ssh2
Apr 14 07:12:36 legacy sshd[13149]: Failed password for root from 222.186.175.169 port 43096 ssh2
Apr 14 07:12:39 legacy sshd[13149]: Failed password for root from 222.186.175.169 port 43096 ssh2
Apr 14 07:12:42 legacy sshd[13149]: Failed password for root from 222.186.175.169 port 43096 ssh2
...
2020-04-14 13:21:38
1.11.201.18 attackbots
$f2bV_matches
2020-04-14 13:09:42

最近上报的IP列表

116.77.7.124 112.49.137.91 112.20.104.24 111.25.165.244
111.208.79.219 101.65.14.208 61.134.133.137 42.49.45.125
42.228.119.73 42.228.116.6 4.148.240.239 39.146.10.201
34.204.53.150 223.74.228.233 116.147.144.102 115.57.248.95
112.10.239.182 110.18.14.22 36.36.92.247 40.124.172.22