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

城市(city): unknown

省份(region): unknown

国家(country): Kazakhstan

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
暂无关于此IP所属子网相关IP的讨论.
WHOIS信息:
b
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 194.146.41.104
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 34754
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;194.146.41.104.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 19 04:16:22 CST 2022
;; MSG SIZE  rcvd: 107
HOST信息:
104.41.146.194.in-addr.arpa domain name pointer apkz3.hoster.kz.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
104.41.146.194.in-addr.arpa	name = apkz3.hoster.kz.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
118.163.97.19 attack
[munged]::443 118.163.97.19 - - [22/Aug/2019:00:29:01 +0200] "POST /[munged]: HTTP/1.1" 200 9359 "http://[munged]:/[munged]:" "Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Firefox/60.0"
[munged]::443 118.163.97.19 - - [22/Aug/2019:00:29:02 +0200] "POST /[munged]: HTTP/1.1" 200 4698 "http://[munged]:/[munged]:" "Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Firefox/60.0"
[munged]::443 118.163.97.19 - - [22/Aug/2019:00:29:04 +0200] "POST /[munged]: HTTP/1.1" 200 4698 "http://[munged]:/[munged]:" "Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Firefox/60.0"
[munged]::443 118.163.97.19 - - [22/Aug/2019:00:29:05 +0200] "POST /[munged]: HTTP/1.1" 200 4698 "http://[munged]:/[munged]:" "Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Firefox/60.0"
[munged]::443 118.163.97.19 - - [22/Aug/2019:00:29:06 +0200] "POST /[munged]: HTTP/1.1" 200 4698 "http://[munged]:/[munged]:" "Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Firefox/60.0"
[munged]::443 118.163.97.19 - - [22/Aug/2019:00:29:07
2019-08-22 06:51:41
93.174.95.106 attackspam
Aug 22 00:29:12 mail postfix/smtpd[25593]: lost connection after STARTTLS from battery.census.shodan.io[93.174.95.106]
Aug 22 00:29:12 mail postfix/smtpd[25593]: lost connection after STARTTLS from battery.census.shodan.io[93.174.95.106]
Aug 22 00:29:13 mail postfix/smtpd[25593]: lost connection after STARTTLS from battery.census.shodan.io[93.174.95.106]
Aug 22 00:29:13 mail postfix/smtpd[25593]: lost connection after STARTTLS from battery.census.shodan.io[93.174.95.106]
Aug 22 00:29:14 mail postfix/smtpd[25593]: lost connection after STARTTLS from battery.census.shodan.io[93.174.95.106]
...
2019-08-22 06:48:57
85.57.40.188 attackspambots
Aug 22 00:41:38 lnxded63 sshd[22331]: Failed password for root from 85.57.40.188 port 57077 ssh2
Aug 22 00:41:38 lnxded63 sshd[22331]: Failed password for root from 85.57.40.188 port 57077 ssh2
Aug 22 00:45:52 lnxded63 sshd[22645]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.57.40.188
2019-08-22 06:57:04
54.245.188.130 attack
Aug 22 01:45:06 www2 sshd\[51619\]: Failed password for root from 54.245.188.130 port 37040 ssh2Aug 22 01:50:19 www2 sshd\[52325\]: Invalid user adm from 54.245.188.130Aug 22 01:50:21 www2 sshd\[52325\]: Failed password for invalid user adm from 54.245.188.130 port 55372 ssh2
...
2019-08-22 07:02:32
164.132.56.243 attack
k+ssh-bruteforce
2019-08-22 07:01:26
50.239.140.1 attackbots
SSH Bruteforce attempt
2019-08-22 07:20:04
119.147.213.222 attack
Aug 21 18:28:58 web1 postfix/smtpd[18891]: warning: unknown[119.147.213.222]: SASL LOGIN authentication failed: authentication failure
...
2019-08-22 07:03:58
82.196.4.46 attackbots
Aug 22 00:29:10 ubuntu-2gb-nbg1-dc3-1 sshd[17116]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.196.4.46
Aug 22 00:29:12 ubuntu-2gb-nbg1-dc3-1 sshd[17116]: Failed password for invalid user ftpd from 82.196.4.46 port 56528 ssh2
...
2019-08-22 06:54:14
210.120.112.18 attack
vps1:sshd-InvalidUser
2019-08-22 07:18:49
159.65.157.194 attackbots
Fail2Ban Ban Triggered
2019-08-22 07:19:25
162.215.255.3 attack
22.08.2019 00:29:00 - Wordpress fail 
Detected by ELinOX-ALM
2019-08-22 07:11:40
182.61.104.242 attackbots
Aug 21 13:00:53 web9 sshd\[7268\]: Invalid user smbuser from 182.61.104.242
Aug 21 13:00:53 web9 sshd\[7268\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.104.242
Aug 21 13:00:54 web9 sshd\[7268\]: Failed password for invalid user smbuser from 182.61.104.242 port 36654 ssh2
Aug 21 13:05:43 web9 sshd\[8255\]: Invalid user krissu from 182.61.104.242
Aug 21 13:05:43 web9 sshd\[8255\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.104.242
2019-08-22 07:23:24
67.203.1.18 attackbotsspam
WordPress wp-login brute force :: 67.203.1.18 0.052 BYPASS [22/Aug/2019:08:28:45  1000] [censored_4] "POST /wp-login.php HTTP/1.1" 200 3989 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-08-22 07:18:26
58.211.168.246 attackspambots
Aug 22 00:43:18 meumeu sshd[23707]: Failed password for invalid user mail1 from 58.211.168.246 port 52736 ssh2
Aug 22 00:47:59 meumeu sshd[24385]: Failed password for invalid user class from 58.211.168.246 port 41474 ssh2
...
2019-08-22 07:07:06
112.85.42.177 attackspam
SSH Brute-Force reported by Fail2Ban
2019-08-22 06:50:04

最近上报的IP列表

194.146.239.129 194.146.239.152 194.146.50.113 194.146.42.74
194.146.59.87 22.134.64.57 194.150.68.51 194.150.70.249
194.147.154.28 194.150.234.163 194.156.140.75 194.163.138.108
194.163.152.104 194.163.175.75 194.163.186.173 194.163.167.167
194.163.162.10 194.163.182.32 194.163.35.82 194.163.36.38