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

城市(city): unknown

省份(region): unknown

国家(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 '183.192.0.0 - 183.255.255.255'

% Abuse contact for '183.192.0.0 - 183.255.255.255' is 'abuse@chinamobile.com'

inetnum:        183.192.0.0 - 183.255.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 '183.192.0.0/11AS9808'

route:          183.192.0.0/11
descr:          China Mobile communications corporation
origin:         AS9808
mnt-by:         MAINT-CN-CMCC
last-modified:  2010-12-08T08:06:16Z
source:         APNIC

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

;; QUESTION SECTION:
;183.212.12.189.			IN	A

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

;; Query time: 32 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Oct 17 01:00:19 CST 2026
;; MSG SIZE  rcvd: 107
HOST信息:
Host 189.12.212.183.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 189.12.212.183.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
37.143.160.18 attackbotsspam
Jul 31 02:44:58 SilenceServices sshd[1788]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.143.160.18
Jul 31 02:45:00 SilenceServices sshd[1788]: Failed password for invalid user much from 37.143.160.18 port 52668 ssh2
Jul 31 02:49:22 SilenceServices sshd[5188]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.143.160.18
2019-07-31 08:56:20
91.195.99.114 attackbots
firewall-block, port(s): 80/tcp
2019-07-31 08:46:26
173.218.243.137 attack
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.218.243.137  user=root
Failed password for root from 173.218.243.137 port 36218 ssh2
Invalid user hwang from 173.218.243.137 port 32908
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.218.243.137
Failed password for invalid user hwang from 173.218.243.137 port 32908 ssh2
2019-07-31 09:13:36
114.119.4.74 attackspambots
Jul 31 00:53:34 v22018076622670303 sshd\[13626\]: Invalid user kramer from 114.119.4.74 port 33300
Jul 31 00:53:34 v22018076622670303 sshd\[13626\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.119.4.74
Jul 31 00:53:36 v22018076622670303 sshd\[13626\]: Failed password for invalid user kramer from 114.119.4.74 port 33300 ssh2
...
2019-07-31 08:24:57
106.241.16.119 attackbots
Jul 30 23:55:23 ip-172-31-62-245 sshd\[21460\]: Invalid user ben from 106.241.16.119\
Jul 30 23:55:25 ip-172-31-62-245 sshd\[21460\]: Failed password for invalid user ben from 106.241.16.119 port 37350 ssh2\
Jul 31 00:00:14 ip-172-31-62-245 sshd\[21504\]: Invalid user apotre from 106.241.16.119\
Jul 31 00:00:16 ip-172-31-62-245 sshd\[21504\]: Failed password for invalid user apotre from 106.241.16.119 port 60772 ssh2\
Jul 31 00:05:11 ip-172-31-62-245 sshd\[21546\]: Invalid user update from 106.241.16.119\
2019-07-31 08:38:13
142.93.47.125 attackbots
Jul 31 02:22:23 dedicated sshd[13556]: Invalid user chase from 142.93.47.125 port 60406
2019-07-31 08:24:01
114.67.70.94 attack
Jul 31 03:42:13 server sshd\[5060\]: Invalid user nunes from 114.67.70.94 port 47788
Jul 31 03:42:13 server sshd\[5060\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.70.94
Jul 31 03:42:15 server sshd\[5060\]: Failed password for invalid user nunes from 114.67.70.94 port 47788 ssh2
Jul 31 03:47:08 server sshd\[7233\]: Invalid user john from 114.67.70.94 port 41400
Jul 31 03:47:08 server sshd\[7233\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.70.94
2019-07-31 08:53:04
5.196.27.26 attackspam
SSH bruteforce (Triggered fail2ban)
2019-07-31 08:27:06
5.196.88.127 attackbots
Jul 31 01:44:11 SilenceServices sshd[21006]: Failed password for root from 5.196.88.127 port 50728 ssh2
Jul 31 01:53:29 SilenceServices sshd[27710]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.196.88.127
Jul 31 01:53:30 SilenceServices sshd[27710]: Failed password for invalid user administrator from 5.196.88.127 port 41216 ssh2
2019-07-31 08:26:40
27.100.25.114 attackspambots
Jul 30 21:41:21 vtv3 sshd\[14728\]: Invalid user sshtunnel from 27.100.25.114 port 54416
Jul 30 21:41:21 vtv3 sshd\[14728\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.100.25.114
Jul 30 21:41:23 vtv3 sshd\[14728\]: Failed password for invalid user sshtunnel from 27.100.25.114 port 54416 ssh2
Jul 30 21:46:35 vtv3 sshd\[17126\]: Invalid user direction from 27.100.25.114 port 51761
Jul 30 21:46:35 vtv3 sshd\[17126\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.100.25.114
Jul 30 22:01:37 vtv3 sshd\[24548\]: Invalid user mario from 27.100.25.114 port 43575
Jul 30 22:01:37 vtv3 sshd\[24548\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.100.25.114
Jul 30 22:01:38 vtv3 sshd\[24548\]: Failed password for invalid user mario from 27.100.25.114 port 43575 ssh2
Jul 30 22:06:39 vtv3 sshd\[27063\]: Invalid user customer from 27.100.25.114 port 40828
Jul 30 22:06:39 vtv3 sshd\
2019-07-31 08:44:43
190.85.48.102 attack
Jul 31 01:39:55 srv-4 sshd\[11257\]: Invalid user daniel from 190.85.48.102
Jul 31 01:39:55 srv-4 sshd\[11257\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.85.48.102
Jul 31 01:39:57 srv-4 sshd\[11257\]: Failed password for invalid user daniel from 190.85.48.102 port 56188 ssh2
...
2019-07-31 08:52:43
49.234.74.45 attack
Jul 31 00:00:30 ip-172-31-62-245 sshd\[21509\]: Invalid user lliam from 49.234.74.45\
Jul 31 00:00:33 ip-172-31-62-245 sshd\[21509\]: Failed password for invalid user lliam from 49.234.74.45 port 42936 ssh2\
Jul 31 00:05:11 ip-172-31-62-245 sshd\[21544\]: Invalid user mcm from 49.234.74.45\
Jul 31 00:05:13 ip-172-31-62-245 sshd\[21544\]: Failed password for invalid user mcm from 49.234.74.45 port 35872 ssh2\
Jul 31 00:09:53 ip-172-31-62-245 sshd\[21656\]: Invalid user portal_user from 49.234.74.45\
2019-07-31 08:41:41
27.9.209.220 attackbots
Automatic report - Port Scan Attack
2019-07-31 08:45:09
144.217.164.104 attack
Jul 31 00:39:28 bouncer sshd\[13615\]: Invalid user NetLinx from 144.217.164.104 port 54412
Jul 31 00:39:28 bouncer sshd\[13615\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.164.104 
Jul 31 00:39:30 bouncer sshd\[13615\]: Failed password for invalid user NetLinx from 144.217.164.104 port 54412 ssh2
...
2019-07-31 09:04:02
202.75.216.136 attack
Jul 31 00:13:07 **** sshd[6447]: User root from 202.75.216.136 not allowed because not listed in AllowUsers
2019-07-31 08:50:39

最近上报的IP列表

223.66.184.182 223.107.239.129 183.210.108.166 123.90.148.140
120.245.130.242 112.32.240.75 112.0.139.30 5.133.192.99
34.95.243.221 151.245.151.199 44.220.185.216 20.58.188.171
51.159.110.25 147.185.133.229 61.185.73.2 36.42.94.248
209.38.247.95 198.235.24.86 216.36.111.75 87.192.41.180