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

城市(city): Wuxi

省份(region): Jiangsu

国家(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-CMCC1-AP
admin-c:        ct74-AP
tech-c:         HL1318-AP
abuse-c:        AC1895-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-CHINAMOBILE2-CN
last-modified:  2020-12-15T02:55:47Z
source:         APNIC

irt:            IRT-CHINAMOBILE2-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-03-23T00:47:51Z
source:         APNIC

organisation:   ORG-CMCC1-AP
org-name:       China Mobile Communications Corporation
org-type:       LIR
country:        CN
address:        29,Jinrong Ave.,
address:        Xicheng District,
phone:          +861052686688
fax-no:         +861052616187
e-mail:         hostmaster@chinamobile.com
mnt-ref:        APNIC-HM
mnt-by:         APNIC-HM
last-modified:  2023-09-05T02:14:58Z
source:         APNIC

role:           ABUSE CHINAMOBILE2CN
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:        AC1895-AP
remarks:        Generated from irt object IRT-CHINAMOBILE2-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:00Z
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.24.0.0/13AS9808'

route:          112.24.0.0/13
descr:          China Mobile communications corporation
origin:         AS9808
mnt-by:         MAINT-CN-CMCC
last-modified:  2009-10-20T06:58:15Z
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.24.142.242
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 60649
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;112.24.142.242.			IN	A

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

;; Query time: 30 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Apr 23 23:02:17 CST 2026
;; MSG SIZE  rcvd: 107
HOST信息:
Host 242.142.24.112.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 242.142.24.112.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
203.143.12.26 attack
May 11 14:08:19 vmd17057 sshd[21176]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.143.12.26 
May 11 14:08:21 vmd17057 sshd[21176]: Failed password for invalid user 558 from 203.143.12.26 port 44196 ssh2
...
2020-05-11 21:29:02
112.3.29.199 attackbots
2020-05-11T15:03:06.468312vps773228.ovh.net sshd[26042]: Failed password for invalid user ut2k4server from 112.3.29.199 port 56648 ssh2
2020-05-11T15:07:27.201052vps773228.ovh.net sshd[26064]: Invalid user www-data from 112.3.29.199 port 40148
2020-05-11T15:07:27.212795vps773228.ovh.net sshd[26064]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.3.29.199
2020-05-11T15:07:27.201052vps773228.ovh.net sshd[26064]: Invalid user www-data from 112.3.29.199 port 40148
2020-05-11T15:07:29.569639vps773228.ovh.net sshd[26064]: Failed password for invalid user www-data from 112.3.29.199 port 40148 ssh2
...
2020-05-11 21:09:53
188.128.28.56 attackbots
May 10 23:57:44 hostnameproxy sshd[4919]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.128.28.56  user=r.r
May 10 23:57:46 hostnameproxy sshd[4919]: Failed password for r.r from 188.128.28.56 port 12013 ssh2
May 10 23:58:59 hostnameproxy sshd[4996]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.128.28.56  user=r.r
May 10 23:59:01 hostnameproxy sshd[4996]: Failed password for r.r from 188.128.28.56 port 10467 ssh2
May 10 23:59:09 hostnameproxy sshd[5005]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.128.28.56  user=r.r
May 10 23:59:11 hostnameproxy sshd[5005]: Failed password for r.r from 188.128.28.56 port 29456 ssh2
May 11 00:00:26 hostnameproxy sshd[5066]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.128.28.56  user=r.r
May 11 00:00:28 hostnameproxy sshd[5066]: Failed password for r.r ........
------------------------------
2020-05-11 21:40:07
49.234.83.240 attackbotsspam
$f2bV_matches | Triggered by Fail2Ban at Vostok web server
2020-05-11 21:06:48
118.69.225.57 attackspambots
'IP reached maximum auth failures for a one day block'
2020-05-11 21:29:34
222.186.30.35 attackspambots
May 11 13:29:01 localhost sshd[16868]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.35  user=root
May 11 13:29:02 localhost sshd[16868]: Failed password for root from 222.186.30.35 port 26328 ssh2
May 11 13:29:05 localhost sshd[16868]: Failed password for root from 222.186.30.35 port 26328 ssh2
May 11 13:29:01 localhost sshd[16868]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.35  user=root
May 11 13:29:02 localhost sshd[16868]: Failed password for root from 222.186.30.35 port 26328 ssh2
May 11 13:29:05 localhost sshd[16868]: Failed password for root from 222.186.30.35 port 26328 ssh2
May 11 13:29:01 localhost sshd[16868]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.35  user=root
May 11 13:29:02 localhost sshd[16868]: Failed password for root from 222.186.30.35 port 26328 ssh2
May 11 13:29:05 localhost sshd[16868]: Failed pas
...
2020-05-11 21:33:22
222.186.175.163 attackbotsspam
web-1 [ssh] SSH Attack
2020-05-11 21:11:27
185.50.149.26 attackbots
May 11 13:40:28 mail postfix/smtpd\[29703\]: warning: unknown\[185.50.149.26\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
May 11 14:10:58 mail postfix/smtpd\[30996\]: warning: unknown\[185.50.149.26\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
May 11 14:11:16 mail postfix/smtpd\[30996\]: warning: unknown\[185.50.149.26\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
May 11 15:18:34 mail postfix/smtpd\[32269\]: warning: unknown\[185.50.149.26\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
2020-05-11 21:21:57
188.128.28.50 attackspambots
May 10 23:58:46 hostnameproxy sshd[4986]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.128.28.50  user=r.r
May 10 23:58:48 hostnameproxy sshd[4986]: Failed password for r.r from 188.128.28.50 port 29791 ssh2
May 11 00:05:56 hostnameproxy sshd[5445]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.128.28.50  user=r.r
May 11 00:05:58 hostnameproxy sshd[5445]: Failed password for r.r from 188.128.28.50 port 12496 ssh2
May 11 00:06:00 hostnameproxy sshd[5454]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.128.28.50  user=r.r
May 11 00:06:02 hostnameproxy sshd[5454]: Failed password for r.r from 188.128.28.50 port 23653 ssh2
May 11 00:07:27 hostnameproxy sshd[5519]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.128.28.50  user=r.r
May 11 00:07:29 hostnameproxy sshd[5519]: Failed password for r.r ........
------------------------------
2020-05-11 21:34:21
149.202.164.82 attack
2020-05-11T12:58:38.985950shield sshd\[3427\]: Invalid user demo from 149.202.164.82 port 58432
2020-05-11T12:58:38.990634shield sshd\[3427\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.202.164.82
2020-05-11T12:58:40.724998shield sshd\[3427\]: Failed password for invalid user demo from 149.202.164.82 port 58432 ssh2
2020-05-11T13:02:56.026898shield sshd\[4269\]: Invalid user edp from 149.202.164.82 port 38796
2020-05-11T13:02:56.034466shield sshd\[4269\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.202.164.82
2020-05-11 21:09:29
222.186.3.249 attackbots
May 11 15:18:56 OPSO sshd\[9362\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.3.249  user=root
May 11 15:18:58 OPSO sshd\[9362\]: Failed password for root from 222.186.3.249 port 14934 ssh2
May 11 15:19:00 OPSO sshd\[9362\]: Failed password for root from 222.186.3.249 port 14934 ssh2
May 11 15:19:03 OPSO sshd\[9362\]: Failed password for root from 222.186.3.249 port 14934 ssh2
May 11 15:20:14 OPSO sshd\[9830\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.3.249  user=root
2020-05-11 21:20:46
190.197.76.51 attackbotsspam
DATE:2020-05-11 14:51:31, IP:190.197.76.51, PORT:telnet Telnet brute force auth on honeypot server (epe-honey1-hq)
2020-05-11 21:25:20
181.47.3.39 attack
prod6
...
2020-05-11 21:25:04
189.7.129.60 attackbotsspam
May 11 12:02:02 localhost sshd[9330]: Invalid user xdn from 189.7.129.60 port 47004
May 11 12:02:02 localhost sshd[9330]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.7.129.60
May 11 12:02:02 localhost sshd[9330]: Invalid user xdn from 189.7.129.60 port 47004
May 11 12:02:03 localhost sshd[9330]: Failed password for invalid user xdn from 189.7.129.60 port 47004 ssh2
May 11 12:08:18 localhost sshd[9845]: Invalid user vps from 189.7.129.60 port 54744
...
2020-05-11 21:33:43
219.139.184.207 attackbotsspam
SASL broute force
2020-05-11 21:26:08

最近上报的IP列表

176.65.148.196 102.170.191.157 2606:4700:10::6814:8227 2606:4700:10::6814:8460
2606:4700:10::6816:4914 2606:4700:10::6814:4410 124.225.22.32 48.215.98.69
168.144.38.34 121.199.163.238 52.23.194.58 121.41.171.45
134.35.157.69 2606:4700:10::6814:9398 2606:4700:10::ac43:1875 2606:4700:10::6816:4505
121.230.89.132 39.100.69.170 159.223.63.125 183.54.234.241