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

城市(city): unknown

省份(region): unknown

国家(country): China

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
IP 类型 评论内容 时间
106.54.102.140 attack
Mar 26 04:29:45 xxxxxxx0 sshd[24892]: Invalid user informix from 106.54.102.140 port 51750
Mar 26 04:29:45 xxxxxxx0 sshd[24892]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.102.140
Mar 26 04:29:47 xxxxxxx0 sshd[24892]: Failed password for invalid user informix from 106.54.102.140 port 51750 ssh2
Mar 26 04:42:16 xxxxxxx0 sshd[3450]: Invalid user informix from 106.54.102.140 port 34848
Mar 26 04:42:16 xxxxxxx0 sshd[3450]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.102.140

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=106.54.102.140
2020-03-26 14:25:06
106.54.102.127 attack
2020-01-15T13:06:50.981283shield sshd\[26929\]: Invalid user service from 106.54.102.127 port 57908
2020-01-15T13:06:50.989565shield sshd\[26929\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.102.127
2020-01-15T13:06:53.089054shield sshd\[26929\]: Failed password for invalid user service from 106.54.102.127 port 57908 ssh2
2020-01-15T13:09:20.651712shield sshd\[27557\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.102.127  user=root
2020-01-15T13:09:22.686486shield sshd\[27557\]: Failed password for root from 106.54.102.127 port 46482 ssh2
2020-01-15 21:19:18
106.54.102.127 attack
Jan 15 07:55:42 vps58358 sshd\[6280\]: Invalid user qt from 106.54.102.127Jan 15 07:55:44 vps58358 sshd\[6280\]: Failed password for invalid user qt from 106.54.102.127 port 40670 ssh2Jan 15 07:59:18 vps58358 sshd\[6315\]: Invalid user webmaster from 106.54.102.127Jan 15 07:59:19 vps58358 sshd\[6315\]: Failed password for invalid user webmaster from 106.54.102.127 port 40286 ssh2Jan 15 08:03:24 vps58358 sshd\[6350\]: Invalid user king from 106.54.102.127Jan 15 08:03:26 vps58358 sshd\[6350\]: Failed password for invalid user king from 106.54.102.127 port 39900 ssh2
...
2020-01-15 15:40:01
106.54.102.127 attack
2020-01-12T21:37:18.435399shield sshd\[3927\]: Invalid user transfer from 106.54.102.127 port 38600
2020-01-12T21:37:18.440966shield sshd\[3927\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.102.127
2020-01-12T21:37:20.919990shield sshd\[3927\]: Failed password for invalid user transfer from 106.54.102.127 port 38600 ssh2
2020-01-12T21:41:13.185984shield sshd\[5187\]: Invalid user user from 106.54.102.127 port 35558
2020-01-12T21:41:13.190067shield sshd\[5187\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.102.127
2020-01-13 05:49:39
106.54.102.127 attackbotsspam
$f2bV_matches
2020-01-12 08:37:49
106.54.102.127 attackbots
$f2bV_matches
2020-01-11 05:10:52
106.54.102.127 attackbotsspam
Dec 30 23:09:48 server sshd\[25715\]: Invalid user deploy from 106.54.102.127
Dec 30 23:09:48 server sshd\[25715\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.102.127 
Dec 30 23:09:49 server sshd\[25715\]: Failed password for invalid user deploy from 106.54.102.127 port 43966 ssh2
Dec 30 23:13:49 server sshd\[26691\]: Invalid user dragonx from 106.54.102.127
Dec 30 23:13:49 server sshd\[26691\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.102.127 
...
2019-12-31 04:57:16
106.54.102.127 attackbotsspam
Dec 25 17:40:50 sd-53420 sshd\[31649\]: User mysql from 106.54.102.127 not allowed because none of user's groups are listed in AllowGroups
Dec 25 17:40:50 sd-53420 sshd\[31649\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.102.127  user=mysql
Dec 25 17:40:52 sd-53420 sshd\[31649\]: Failed password for invalid user mysql from 106.54.102.127 port 54494 ssh2
Dec 25 17:46:51 sd-53420 sshd\[1509\]: Invalid user nfs from 106.54.102.127
Dec 25 17:46:51 sd-53420 sshd\[1509\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.102.127
...
2019-12-26 00:59:12
106.54.102.94 attackspam
Unauthorized connection attempt detected from IP address 106.54.102.94 to port 22
2019-12-24 06:51:35
106.54.102.94 attackbots
SSH brutforce
2019-11-23 07:38:48
106.54.102.94 attack
Nov 20 19:00:53 lnxded64 sshd[11377]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.102.94
Nov 20 19:00:55 lnxded64 sshd[11377]: Failed password for invalid user heinrik from 106.54.102.94 port 47176 ssh2
Nov 20 19:06:24 lnxded64 sshd[12728]: Failed password for mysql from 106.54.102.94 port 43728 ssh2
2019-11-21 02:06:33
106.54.102.94 attack
Lines containing failures of 106.54.102.94
Nov 18 15:55:30 www sshd[29223]: Invalid user allaman from 106.54.102.94 port 47096
Nov 18 15:55:30 www sshd[29223]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.102.94
Nov 18 15:55:32 www sshd[29223]: Failed password for invalid user allaman from 106.54.102.94 port 47096 ssh2
Nov 18 15:55:33 www sshd[29223]: Received disconnect from 106.54.102.94 port 47096:11: Bye Bye [preauth]
Nov 18 15:55:33 www sshd[29223]: Disconnected from invalid user allaman 106.54.102.94 port 47096 [preauth]
Nov 18 16:15:41 www sshd[31757]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.102.94  user=r.r
Nov 18 16:15:43 www sshd[31757]: Failed password for r.r from 106.54.102.94 port 36950 ssh2
Nov 18 16:15:43 www sshd[31757]: Received disconnect from 106.54.102.94 port 36950:11: Bye Bye [preauth]
Nov 18 16:15:43 www sshd[31757]: Disconnected from authentic........
------------------------------
2019-11-19 18:47:06
106.54.102.94 attack
106.54.102.94 was recorded 5 times by 2 hosts attempting to connect to the following ports: 22. Incident counter (4h, 24h, all-time): 5, 5, 9
2019-11-17 01:39:38
106.54.102.94 attackspam
SSH bruteforce
2019-11-11 15:03:22
WHOIS信息:
b
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 106.54.102.214
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13866
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;106.54.102.214.			IN	A

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

;; Query time: 111 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 01 03:25:37 CST 2022
;; MSG SIZE  rcvd: 107
HOST信息:
Host 214.102.54.106.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 214.102.54.106.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
202.137.120.37 attack
37215/tcp
[2019-07-11]1pkt
2019-07-11 18:34:32
120.35.189.180 attackspam
Jul  9 12:52:27 rigel postfix/smtpd[18475]: warning: hostname 180.189.35.120.broad.zz.fj.dynamic.163data.com.cn does not resolve to address 120.35.189.180: Name or service not known
Jul  9 12:52:27 rigel postfix/smtpd[18475]: connect from unknown[120.35.189.180]
Jul  9 12:52:28 rigel postfix/smtpd[18154]: warning: hostname 180.189.35.120.broad.zz.fj.dynamic.163data.com.cn does not resolve to address 120.35.189.180: Name or service not known
Jul  9 12:52:28 rigel postfix/smtpd[18154]: connect from unknown[120.35.189.180]
Jul  9 12:52:28 rigel postfix/smtpd[18475]: lost connection after CONNECT from unknown[120.35.189.180]
Jul  9 12:52:28 rigel postfix/smtpd[18475]: disconnect from unknown[120.35.189.180]
Jul  9 12:52:32 rigel postfix/smtpd[18154]: warning: unknown[120.35.189.180]: SASL LOGIN authentication failed: authentication failure
Jul  9 12:52:33 rigel postfix/smtpd[18154]: lost connection after AUTH from unknown[120.35.189.180]
Jul  9 12:52:33 rigel postfix/smtpd[........
-------------------------------
2019-07-11 18:38:55
185.176.26.104 attackspambots
9281/tcp 7036/tcp 7766/tcp...
[2019-06-14/07-09]1241pkt,497pt.(tcp)
2019-07-11 18:23:45
54.36.150.63 attackspam
Automatic report - Web App Attack
2019-07-11 18:00:11
142.11.240.29 attackbots
DATE:2019-07-11_05:47:10, IP:142.11.240.29, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc)
2019-07-11 18:23:28
110.159.155.237 attackbots
Jul  8 09:31:07 mail01 postfix/postscreen[9860]: CONNECT from [110.159.155.237]:41108 to [94.130.181.95]:25
Jul  8 09:31:07 mail01 postfix/dnsblog[9863]: addr 110.159.155.237 listed by domain zen.spamhaus.org as 127.0.0.3
Jul  8 09:31:07 mail01 postfix/dnsblog[9863]: addr 110.159.155.237 listed by domain zen.spamhaus.org as 127.0.0.11
Jul  8 09:31:07 mail01 postfix/dnsblog[9863]: addr 110.159.155.237 listed by domain zen.spamhaus.org as 127.0.0.4
Jul  8 09:31:07 mail01 postfix/dnsblog[9862]: addr 110.159.155.237 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Jul  8 09:31:07 mail01 postfix/dnsblog[9861]: addr 110.159.155.237 listed by domain bl.blocklist.de as 127.0.0.9
Jul  8 09:31:07 mail01 postfix/postscreen[9860]: PREGREET 40 after 0.63 from [110.159.155.237]:41108: EHLO 241.155.159.110.tm-hsbb.tm.net.my

Jul  8 09:31:07 mail01 postfix/postscreen[9860]: DNSBL rank 5 for [110.159.155.237]:41108
Jul x@x
Jul  8 09:31:09 mail01 postfix/postscreen[9860]: HANGUP after 1........
-------------------------------
2019-07-11 17:56:41
198.108.67.34 attack
8825/tcp 2077/tcp 830/tcp...
[2019-05-11/07-10]106pkt,103pt.(tcp)
2019-07-11 18:01:55
185.222.211.242 attackbots
2019-07-11 H=\(\[185.222.211.2\]\) \[185.222.211.242\] F=\ rejected RCPT \: relay not permitted
2019-07-11 H=\(\[185.222.211.2\]\) \[185.222.211.242\] F=\ rejected RCPT \: relay not permitted
2019-07-11 H=\(\[185.222.211.2\]\) \[185.222.211.242\] F=\ rejected RCPT \: relay not permitted
2019-07-11 18:38:25
175.161.59.56 attackbotsspam
Caught in portsentry honeypot
2019-07-11 18:28:19
185.176.27.26 attack
11.07.2019 08:52:33 Connection to port 18988 blocked by firewall
2019-07-11 18:21:51
181.143.17.66 attackspam
Attempts against Pop3/IMAP
2019-07-11 18:02:28
42.116.248.148 attackbots
60001/tcp
[2019-07-11]1pkt
2019-07-11 18:55:55
196.52.43.88 attackbotsspam
5060/tcp 23/tcp 5632/udp...
[2019-05-10/07-10]70pkt,40pt.(tcp),8pt.(udp)
2019-07-11 17:50:28
82.221.105.7 attack
2019-07-11T09:33:10.162613Z 816324244e40 New connection: 82.221.105.7:48941 (172.17.0.4:2222) [session: 816324244e40]
2019-07-11T09:33:10.556234Z 24e0d237b932 New connection: 82.221.105.7:48973 (172.17.0.4:2222) [session: 24e0d237b932]
2019-07-11 18:05:23
80.211.102.169 attackspam
Jul x@x
Jul x@x
Jul x@x
Jul x@x
Jul x@x


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=80.211.102.169
2019-07-11 18:40:36

最近上报的IP列表

106.54.100.76 106.54.116.180 106.54.108.100 106.54.12.168
106.54.120.151 106.54.123.78 106.54.131.15 106.54.13.199
106.54.131.242 106.54.135.165 106.54.131.90 106.59.117.155
106.59.126.188 106.59.243.200 106.59.199.7 106.59.252.26
106.59.2.228 106.59.123.75 106.58.63.65 106.59.125.24