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

城市(city): Suzhou

省份(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-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-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 '112.0.0.0/13AS9808'

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

;; QUESTION SECTION:
;112.3.193.195.			IN	A

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

;; Query time: 32 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jul 03 10:58:21 CST 2026
;; MSG SIZE  rcvd: 106
HOST信息:
Host 195.193.3.112.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 195.193.3.112.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
162.219.248.247 attackbots
suspicious action Tue, 03 Mar 2020 10:21:43 -0300
2020-03-04 04:05:31
221.7.213.133 attackbotsspam
SSH Brute Force
2020-03-04 04:23:49
45.235.86.21 attackbots
Mar  3 20:42:35 localhost sshd\[8074\]: Invalid user green from 45.235.86.21 port 44356
Mar  3 20:42:35 localhost sshd\[8074\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.235.86.21
Mar  3 20:42:37 localhost sshd\[8074\]: Failed password for invalid user green from 45.235.86.21 port 44356 ssh2
2020-03-04 04:13:00
37.30.24.66 attackspam
Mar  3 14:05:00 mxgate1 postfix/postscreen[11946]: CONNECT from [37.30.24.66]:6101 to [176.31.12.44]:25
Mar  3 14:05:00 mxgate1 postfix/dnsblog[11948]: addr 37.30.24.66 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Mar  3 14:05:00 mxgate1 postfix/dnsblog[11951]: addr 37.30.24.66 listed by domain cbl.abuseat.org as 127.0.0.2
Mar  3 14:05:00 mxgate1 postfix/dnsblog[11947]: addr 37.30.24.66 listed by domain zen.spamhaus.org as 127.0.0.10
Mar  3 14:05:00 mxgate1 postfix/dnsblog[11947]: addr 37.30.24.66 listed by domain zen.spamhaus.org as 127.0.0.4
Mar  3 14:05:00 mxgate1 postfix/dnsblog[11949]: addr 37.30.24.66 listed by domain bl.spamcop.net as 127.0.0.2
Mar  3 14:05:00 mxgate1 postfix/dnsblog[11950]: addr 37.30.24.66 listed by domain b.barracudacentral.org as 127.0.0.2
Mar  3 14:05:06 mxgate1 postfix/postscreen[11946]: DNSBL rank 6 for [37.30.24.66]:6101
Mar x@x
Mar  3 14:05:07 mxgate1 postfix/postscreen[11946]: HANGUP after 1.1 from [37.30.24.66]:6101 in tests after........
-------------------------------
2020-03-04 04:14:22
69.94.144.19 attackbots
Mar  3 14:03:30 mxgate1 postfix/postscreen[10656]: CONNECT from [69.94.144.19]:46629 to [176.31.12.44]:25
Mar  3 14:03:30 mxgate1 postfix/dnsblog[11418]: addr 69.94.144.19 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Mar  3 14:03:30 mxgate1 postfix/dnsblog[10795]: addr 69.94.144.19 listed by domain zen.spamhaus.org as 127.0.0.3
Mar  3 14:03:30 mxgate1 postfix/dnsblog[10795]: addr 69.94.144.19 listed by domain zen.spamhaus.org as 127.0.0.2
Mar  3 14:03:36 mxgate1 postfix/postscreen[10656]: DNSBL rank 3 for [69.94.144.19]:46629
Mar x@x
Mar  3 14:03:37 mxgate1 postfix/postscreen[10656]: DISCONNECT [69.94.144.19]:46629


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=69.94.144.19
2020-03-04 04:01:48
47.103.18.71 attackspam
REQUESTED PAGE: /wp-admin/admin.php?page=miwoftp&option=com_miwoftp&action=download&dir=/&item=wp-config.php&order=name&srt=yes
2020-03-04 04:38:02
222.186.30.76 attackbots
2020-03-03T19:33:55.105113vps773228.ovh.net sshd[1354]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76  user=root
2020-03-03T19:33:57.036327vps773228.ovh.net sshd[1354]: Failed password for root from 222.186.30.76 port 35071 ssh2
2020-03-03T19:33:59.810884vps773228.ovh.net sshd[1354]: Failed password for root from 222.186.30.76 port 35071 ssh2
2020-03-03T19:33:55.105113vps773228.ovh.net sshd[1354]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76  user=root
2020-03-03T19:33:57.036327vps773228.ovh.net sshd[1354]: Failed password for root from 222.186.30.76 port 35071 ssh2
2020-03-03T19:33:59.810884vps773228.ovh.net sshd[1354]: Failed password for root from 222.186.30.76 port 35071 ssh2
2020-03-03T19:33:55.105113vps773228.ovh.net sshd[1354]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76  user=root
2020-03-03T19:33:57.036327vps
...
2020-03-04 04:35:18
218.253.69.134 attackspam
Mar  3 20:31:07 vpn01 sshd[7144]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.253.69.134
Mar  3 20:31:09 vpn01 sshd[7144]: Failed password for invalid user kabe from 218.253.69.134 port 38550 ssh2
...
2020-03-04 04:24:35
124.40.246.36 attackspambots
2020-03-03 14:06:40 H=(dapifaq.com) [124.40.246.36]:55356 I=[10.100.18.25]:25 sender verify fail for : Unrouteable address
2020-03-03 x@x
2020-03-03 14:06:41 unexpected disconnection while reading SMTP command from (dapifaq.com) [124.40.246.36]:55356 I=[10.100.18.25]:25

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=124.40.246.36
2020-03-04 04:39:07
178.149.114.79 attack
Mar  3 20:48:05 MK-Soft-VM5 sshd[5504]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.149.114.79 
Mar  3 20:48:07 MK-Soft-VM5 sshd[5504]: Failed password for invalid user gerrit from 178.149.114.79 port 41000 ssh2
...
2020-03-04 04:17:31
169.197.108.6 attack
port scan and connect, tcp 143 (imap)
2020-03-04 04:31:57
178.62.251.130 attackspambots
Fail2Ban Ban Triggered
2020-03-04 04:37:28
213.169.39.218 attackspambots
DATE:2020-03-03 20:23:26, IP:213.169.39.218, PORT:ssh SSH brute force auth (docker-dc)
2020-03-04 04:16:07
78.166.27.45 attackspam
firewall-block, port(s): 23/tcp
2020-03-04 04:45:50
104.248.187.231 attackspambots
SSH Brute-Forcing (server1)
2020-03-04 04:09:35

最近上报的IP列表

111.25.13.119 223.107.2.53 27.129.197.156 39.182.11.11
120.228.46.0 47.128.123.164 20.46.235.137 2606:4700:10::6814:9781
2606:4700:20::681a:230 2606:4700:10::6816:1777 117.189.195.194 111.179.17.113
111.55.205.17 171.39.185.53 39.162.169.13 183.211.73.75
36.148.52.54 61.179.178.236 119.0.47.2 27.215.144.13