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

城市(city): Hefei

省份(region): Anhui

国家(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.32.0.0/13AS9808'

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

;; QUESTION SECTION:
;112.32.152.43.			IN	A

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

;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 11 10:30:46 CST 2026
;; MSG SIZE  rcvd: 106
HOST信息:
Host 43.152.32.112.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 43.152.32.112.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
60.190.114.82 attack
Jan  9 10:10:39 ws24vmsma01 sshd[177417]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.190.114.82
Jan  9 10:10:41 ws24vmsma01 sshd[177417]: Failed password for invalid user dyl from 60.190.114.82 port 54633 ssh2
...
2020-01-09 21:45:35
114.98.225.210 attackspam
Jan  9 14:05:50 ns382633 sshd\[28842\]: Invalid user ph from 114.98.225.210 port 52468
Jan  9 14:05:50 ns382633 sshd\[28842\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.98.225.210
Jan  9 14:05:52 ns382633 sshd\[28842\]: Failed password for invalid user ph from 114.98.225.210 port 52468 ssh2
Jan  9 14:11:54 ns382633 sshd\[29872\]: Invalid user fl from 114.98.225.210 port 38829
Jan  9 14:11:54 ns382633 sshd\[29872\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.98.225.210
2020-01-09 21:29:45
41.157.29.156 attackbotsspam
Fail2Ban Ban Triggered
2020-01-09 22:01:27
157.7.52.201 attackbotsspam
Jan  9 16:06:22 server sshd\[29750\]: Invalid user mj from 157.7.52.201
Jan  9 16:06:22 server sshd\[29750\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=m720x.dwzumq.tokyo 
Jan  9 16:06:25 server sshd\[29750\]: Failed password for invalid user mj from 157.7.52.201 port 55078 ssh2
Jan  9 16:10:30 server sshd\[31077\]: Invalid user bxp from 157.7.52.201
Jan  9 16:10:30 server sshd\[31077\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=m720x.dwzumq.tokyo 
...
2020-01-09 21:57:29
14.236.45.248 attackspam
1578575442 - 01/09/2020 14:10:42 Host: 14.236.45.248/14.236.45.248 Port: 445 TCP Blocked
2020-01-09 21:42:34
14.169.154.179 attackbots
Unauthorized IMAP connection attempt
2020-01-09 21:58:59
193.188.22.229 attack
Fail2Ban Ban Triggered
2020-01-09 22:09:51
222.186.180.6 attackbots
Jan  9 14:58:50 eventyay sshd[5885]: Failed password for root from 222.186.180.6 port 48950 ssh2
Jan  9 14:59:04 eventyay sshd[5885]: error: maximum authentication attempts exceeded for root from 222.186.180.6 port 48950 ssh2 [preauth]
Jan  9 14:59:11 eventyay sshd[5887]: Failed password for root from 222.186.180.6 port 16270 ssh2
...
2020-01-09 22:04:46
218.92.0.138 attack
2020-01-09T13:45:36.662289abusebot-4.cloudsearch.cf sshd[19054]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.138  user=root
2020-01-09T13:45:39.457807abusebot-4.cloudsearch.cf sshd[19054]: Failed password for root from 218.92.0.138 port 2233 ssh2
2020-01-09T13:45:42.734323abusebot-4.cloudsearch.cf sshd[19054]: Failed password for root from 218.92.0.138 port 2233 ssh2
2020-01-09T13:45:36.662289abusebot-4.cloudsearch.cf sshd[19054]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.138  user=root
2020-01-09T13:45:39.457807abusebot-4.cloudsearch.cf sshd[19054]: Failed password for root from 218.92.0.138 port 2233 ssh2
2020-01-09T13:45:42.734323abusebot-4.cloudsearch.cf sshd[19054]: Failed password for root from 218.92.0.138 port 2233 ssh2
2020-01-09T13:45:36.662289abusebot-4.cloudsearch.cf sshd[19054]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=2
...
2020-01-09 21:48:29
104.236.226.93 attackbots
$f2bV_matches
2020-01-09 21:51:42
84.29.154.56 attack
Jan  9 15:29:51 www sshd\[230033\]: Invalid user provider from 84.29.154.56
Jan  9 15:29:51 www sshd\[230033\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.29.154.56
Jan  9 15:29:53 www sshd\[230033\]: Failed password for invalid user provider from 84.29.154.56 port 55852 ssh2
...
2020-01-09 21:38:06
222.186.175.161 attackspambots
SSH Brute Force, server-1 sshd[22017]: Failed password for root from 222.186.175.161 port 19020 ssh2
2020-01-09 21:35:46
61.174.50.50 attackspam
Jan  9 14:10:18 debian-2gb-nbg1-2 kernel: \[834730.828904\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=61.174.50.50 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=238 ID=1352 PROTO=TCP SPT=42733 DPT=1433 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-09 22:06:49
124.128.73.58 attackspambots
(mod_security) mod_security (id:230011) triggered by 124.128.73.58 (CN/China/-): 5 in the last 3600 secs
2020-01-09 21:28:12
134.48.5.250 attack
Jan  9 14:11:33 lakhesis sshd[31144]: Invalid user mlsmhostnameh from 134.48.5.250 port 52842
Jan  9 14:11:33 lakhesis sshd[31144]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.48.5.250
Jan  9 14:11:35 lakhesis sshd[31144]: Failed password for invalid user mlsmhostnameh from 134.48.5.250 port 52842 ssh2
Jan  9 14:14:35 lakhesis sshd[32198]: Invalid user hta from 134.48.5.250 port 57002
Jan  9 14:14:35 lakhesis sshd[32198]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.48.5.250

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=134.48.5.250
2020-01-09 21:44:17

最近上报的IP列表

223.73.27.148 39.162.168.237 39.154.15.143 183.199.82.83
171.118.48.36 112.47.200.166 101.73.166.41 188.166.54.43
188.166.20.218 47.95.199.109 66.132.186.198 34.75.179.116
60.5.185.65 58.19.73.136 58.16.53.3 42.229.253.83
39.182.229.116 39.154.23.31 223.66.157.116 222.137.99.250