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

城市(city): unknown

省份(region): Jilin

国家(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 '111.0.0.0 - 111.63.255.255'

% Abuse contact for '111.0.0.0 - 111.63.255.255' is 'abuse@chinamobile.com'

inetnum:        111.0.0.0 - 111.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
abuse-c:        AC2006-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-CHINAMOBILE-CN
last-modified:  2020-07-15T13:10:04Z
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-03-23T00:47:53Z
source:         APNIC

organisation:   ORG-CM1-AP
org-name:       China Mobile
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:  2023-09-05T02:14:48Z
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 '111.0.0.0/10AS9808'

route:          111.0.0.0/10
descr:          China Mobile communications corporation
origin:         AS9808
mnt-by:         MAINT-CN-CMCC
last-modified:  2012-02-15T08:47:26Z
source:         APNIC

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

;; QUESTION SECTION:
;111.25.134.126.			IN	A

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

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jun 17 12:37:37 CST 2026
;; MSG SIZE  rcvd: 107
HOST信息:
Host 126.134.25.111.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 126.134.25.111.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
68.183.233.74 attack
WordPress login Brute force / Web App Attack on client site.
2019-07-19 08:45:03
162.243.142.193 attack
Jul 19 02:11:35 s64-1 sshd[16958]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.243.142.193
Jul 19 02:11:37 s64-1 sshd[16958]: Failed password for invalid user amir from 162.243.142.193 port 39074 ssh2
Jul 19 02:18:11 s64-1 sshd[17060]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.243.142.193
...
2019-07-19 08:23:39
96.69.10.237 attackspambots
Mar 21 01:33:18 vpn sshd[751]: Failed password for root from 96.69.10.237 port 45478 ssh2
Mar 21 01:37:39 vpn sshd[763]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=96.69.10.237
Mar 21 01:37:40 vpn sshd[763]: Failed password for invalid user support from 96.69.10.237 port 49014 ssh2
2019-07-19 08:09:38
168.253.72.209 attackbots
Dec 26 22:52:48 vpn sshd[10358]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.253.72.209
Dec 26 22:52:50 vpn sshd[10358]: Failed password for invalid user andor from 168.253.72.209 port 37187 ssh2
Dec 26 22:59:18 vpn sshd[10386]: Failed password for root from 168.253.72.209 port 39872 ssh2
2019-07-19 08:25:43
168.195.229.198 attack
Apr 22 10:52:33 vpn sshd[11767]: Invalid user support from 168.195.229.198
Apr 22 10:52:33 vpn sshd[11767]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.195.229.198
Apr 22 10:52:35 vpn sshd[11767]: Failed password for invalid user support from 168.195.229.198 port 3950 ssh2
Apr 22 10:52:38 vpn sshd[11767]: Failed password for invalid user support from 168.195.229.198 port 3950 ssh2
Apr 22 10:52:40 vpn sshd[11767]: Failed password for invalid user support from 168.195.229.198 port 3950 ssh2
2019-07-19 08:31:15
169.57.2.72 attackspam
Nov 30 14:03:09 vpn sshd[4212]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=169.57.2.72
Nov 30 14:03:11 vpn sshd[4212]: Failed password for invalid user alka from 169.57.2.72 port 40604 ssh2
Nov 30 14:06:42 vpn sshd[4252]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=169.57.2.72
2019-07-19 08:03:09
190.2.103.134 attackspambots
Jul 18 19:25:36 microserver sshd[41416]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.2.103.134  user=root
Jul 18 19:25:38 microserver sshd[41416]: Failed password for root from 190.2.103.134 port 44877 ssh2
Jul 18 19:32:01 microserver sshd[42203]: Invalid user temp from 190.2.103.134 port 24557
Jul 18 19:32:01 microserver sshd[42203]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.2.103.134
Jul 18 19:32:02 microserver sshd[42203]: Failed password for invalid user temp from 190.2.103.134 port 24557 ssh2
Jul 18 19:44:44 microserver sshd[43799]: Invalid user tomy from 190.2.103.134 port 55779
Jul 18 19:44:44 microserver sshd[43799]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.2.103.134
Jul 18 19:44:47 microserver sshd[43799]: Failed password for invalid user tomy from 190.2.103.134 port 55779 ssh2
Jul 18 19:51:07 microserver sshd[44954]: Invalid user dev from 190.2.103.134
2019-07-19 08:15:54
169.44.161.155 attack
Dec 30 01:03:04 vpn sshd[1047]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=169.44.161.155
Dec 30 01:03:05 vpn sshd[1047]: Failed password for invalid user abraham from 169.44.161.155 port 45362 ssh2
Dec 30 01:06:14 vpn sshd[1054]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=169.44.161.155
2019-07-19 08:13:55
168.62.181.144 attack
Jul 25 23:48:36 vpn sshd[24511]: Invalid user butter from 168.62.181.144
Jul 25 23:48:36 vpn sshd[24511]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.62.181.144
Jul 25 23:48:38 vpn sshd[24511]: Failed password for invalid user butter from 168.62.181.144 port 34196 ssh2
Jul 25 23:50:04 vpn sshd[24514]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.62.181.144  user=root
Jul 25 23:50:07 vpn sshd[24514]: Failed password for root from 168.62.181.144 port 59844 ssh2
2019-07-19 08:23:04
168.255.251.126 attack
Jan 13 00:37:10 vpn sshd[29894]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.255.251.126
Jan 13 00:37:12 vpn sshd[29894]: Failed password for invalid user test from 168.255.251.126 port 35114 ssh2
Jan 13 00:39:54 vpn sshd[29909]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.255.251.126
2019-07-19 08:25:00
169.56.80.221 attackbots
Mar 11 11:37:51 vpn sshd[1825]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=169.56.80.221
Mar 11 11:37:52 vpn sshd[1825]: Failed password for invalid user postgres from 169.56.80.221 port 59182 ssh2
Mar 11 11:45:39 vpn sshd[1919]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=169.56.80.221
2019-07-19 08:04:30
159.65.13.203 attackspam
Jul 18 19:05:10 aat-srv002 sshd[23997]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.13.203
Jul 18 19:05:12 aat-srv002 sshd[23997]: Failed password for invalid user deployer from 159.65.13.203 port 41222 ssh2
Jul 18 19:10:26 aat-srv002 sshd[24084]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.13.203
Jul 18 19:10:29 aat-srv002 sshd[24084]: Failed password for invalid user ftpuser from 159.65.13.203 port 39549 ssh2
...
2019-07-19 08:17:05
169.255.104.20 attack
Jun 27 03:10:44 vpn sshd[24891]: Invalid user administrator from 169.255.104.20
Jun 27 03:10:44 vpn sshd[24891]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=169.255.104.20
Jun 27 03:10:46 vpn sshd[24891]: Failed password for invalid user administrator from 169.255.104.20 port 35002 ssh2
Jun 27 03:10:47 vpn sshd[24891]: Failed password for invalid user administrator from 169.255.104.20 port 35002 ssh2
Jun 27 03:10:50 vpn sshd[24891]: Failed password for invalid user administrator from 169.255.104.20 port 35002 ssh2
2019-07-19 08:19:13
123.207.11.182 attack
Jul 18 20:17:25 plusreed sshd[22646]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.207.11.182  user=root
Jul 18 20:17:27 plusreed sshd[22646]: Failed password for root from 123.207.11.182 port 53726 ssh2
...
2019-07-19 08:30:18
169.255.196.156 attackspam
Feb 25 10:05:31 vpn sshd[6705]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=169.255.196.156
Feb 25 10:05:34 vpn sshd[6705]: Failed password for invalid user admin from 169.255.196.156 port 43185 ssh2
Feb 25 10:14:56 vpn sshd[6736]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=169.255.196.156
2019-07-19 08:17:34

最近上报的IP列表

223.73.18.225 120.230.22.178 119.44.61.192 2606:4700:10::ac43:2843
2606:4700:10::ac43:1706 2606:4700:10::6816:1768 172.202.113.251 129.121.75.86
50.16.232.215 48.44.175.49 2606:4700:10::6814:4552 2606:4700:10::6814:8785
110.78.153.103 2606:4700:10::6814:8741 112.86.225.96 180.163.116.178
47.254.215.87 110.78.158.236 23.237.109.122 112.81.59.107