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

城市(city): Wenzhou

省份(region): Zhejiang

国家(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.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.12.100.86
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24524
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;112.12.100.86.			IN	A

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

;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri May 08 18:01:59 CST 2026
;; MSG SIZE  rcvd: 106
HOST信息:
Host 86.100.12.112.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 86.100.12.112.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
106.12.121.189 attackspambots
2020-05-07T21:48:44.760825shield sshd\[20748\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.121.189  user=root
2020-05-07T21:48:46.378045shield sshd\[20748\]: Failed password for root from 106.12.121.189 port 49096 ssh2
2020-05-07T21:50:15.339486shield sshd\[20950\]: Invalid user steam from 106.12.121.189 port 41076
2020-05-07T21:50:15.343254shield sshd\[20950\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.121.189
2020-05-07T21:50:17.452402shield sshd\[20950\]: Failed password for invalid user steam from 106.12.121.189 port 41076 ssh2
2020-05-08 05:52:51
40.117.228.216 attack
0,52-02/02 [bc01/m16] PostRequest-Spammer scoring: Durban01
2020-05-08 05:46:59
193.153.186.159 attackspam
May  7 19:18:08 Ubuntu-1404-trusty-64-minimal sshd\[1864\]: Invalid user pi from 193.153.186.159
May  7 19:18:08 Ubuntu-1404-trusty-64-minimal sshd\[1864\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.153.186.159
May  7 19:18:08 Ubuntu-1404-trusty-64-minimal sshd\[1866\]: Invalid user pi from 193.153.186.159
May  7 19:18:08 Ubuntu-1404-trusty-64-minimal sshd\[1866\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.153.186.159
May  7 19:18:10 Ubuntu-1404-trusty-64-minimal sshd\[1864\]: Failed password for invalid user pi from 193.153.186.159 port 36460 ssh2
2020-05-08 05:39:53
180.76.152.157 attackspambots
May  7 19:19:25 xeon sshd[28935]: Failed password for root from 180.76.152.157 port 39566 ssh2
2020-05-08 05:40:04
106.13.29.29 attackspambots
May  7 19:42:53 legacy sshd[28882]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.29.29
May  7 19:42:55 legacy sshd[28882]: Failed password for invalid user postgres from 106.13.29.29 port 36770 ssh2
May  7 19:46:57 legacy sshd[29120]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.29.29
...
2020-05-08 05:32:10
159.89.194.103 attackspam
SSH Invalid Login
2020-05-08 05:53:58
112.85.42.174 attack
May  7 21:39:34 vlre-nyc-1 sshd\[23149\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.174  user=root
May  7 21:39:36 vlre-nyc-1 sshd\[23149\]: Failed password for root from 112.85.42.174 port 36105 ssh2
May  7 21:39:39 vlre-nyc-1 sshd\[23149\]: Failed password for root from 112.85.42.174 port 36105 ssh2
May  7 21:39:43 vlre-nyc-1 sshd\[23149\]: Failed password for root from 112.85.42.174 port 36105 ssh2
May  7 21:39:47 vlre-nyc-1 sshd\[23149\]: Failed password for root from 112.85.42.174 port 36105 ssh2
...
2020-05-08 05:43:01
190.85.171.126 attack
May  7 22:52:17 nextcloud sshd\[18234\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.85.171.126  user=root
May  7 22:52:19 nextcloud sshd\[18234\]: Failed password for root from 190.85.171.126 port 57804 ssh2
May  7 22:56:18 nextcloud sshd\[22588\]: Invalid user upgrade from 190.85.171.126
2020-05-08 05:23:18
49.176.146.35 attackspam
May  7 13:13:33 pixelmemory sshd[1307212]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.176.146.35 
May  7 13:13:33 pixelmemory sshd[1307212]: Invalid user danb from 49.176.146.35 port 38660
May  7 13:13:35 pixelmemory sshd[1307212]: Failed password for invalid user danb from 49.176.146.35 port 38660 ssh2
May  7 13:22:00 pixelmemory sshd[1309046]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.176.146.35  user=root
May  7 13:22:02 pixelmemory sshd[1309046]: Failed password for root from 49.176.146.35 port 52184 ssh2
...
2020-05-08 05:22:04
146.0.143.253 attackbotsspam
Ddosing server
2020-05-08 05:31:53
51.91.111.73 attackbots
Automatic report BANNED IP
2020-05-08 05:30:40
51.158.162.242 attackbots
2020-05-07T20:20:40.653517vps773228.ovh.net sshd[6014]: Invalid user comfort from 51.158.162.242 port 50482
2020-05-07T20:20:40.667758vps773228.ovh.net sshd[6014]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.158.162.242
2020-05-07T20:20:40.653517vps773228.ovh.net sshd[6014]: Invalid user comfort from 51.158.162.242 port 50482
2020-05-07T20:20:42.783700vps773228.ovh.net sshd[6014]: Failed password for invalid user comfort from 51.158.162.242 port 50482 ssh2
2020-05-07T20:25:37.175221vps773228.ovh.net sshd[6072]: Invalid user tullo from 51.158.162.242 port 59686
...
2020-05-08 05:46:30
61.133.232.251 attackspam
SSH brute-force attempt
2020-05-08 05:29:47
213.217.0.131 attack
May  7 23:18:16 debian-2gb-nbg1-2 kernel: \[11145179.964600\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=213.217.0.131 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=1894 PROTO=TCP SPT=56680 DPT=51258 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-08 05:25:45
51.38.230.10 attackbotsspam
k+ssh-bruteforce
2020-05-08 05:47:50

最近上报的IP列表

133.23.116.152 38.84.91.253 110.78.138.184 2606:4700:10::6814:8147
183.129.201.150 183.129.201.149 102.129.152.27 38.125.62.183
204.10.160.147 41.182.41.124 34.163.198.178 2606:4700:10::ac43:2778
46.17.41.25 92.113.142.96 85.217.140.25 39.154.8.117
183.222.201.229 120.230.23.81 2606:4700:10::6814:9911 2606:4700:10::ac43:2578