城市(city): unknown
省份(region): unknown
国家(country): Republic of China (ROC)
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 119.14.163.223 | attack | Unauthorized connection attempt detected from IP address 119.14.163.223 to port 81 [J] |
2020-01-07 17:02:09 |
| 119.14.163.138 | attackspambots | Dec 19 15:32:33 mc1 kernel: \[924769.416940\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=119.14.163.138 DST=159.69.205.51 LEN=60 TOS=0x00 PREC=0x00 TTL=43 ID=50770 DF PROTO=TCP SPT=49558 DPT=80 WINDOW=14600 RES=0x00 SYN URGP=0 Dec 19 15:32:33 mc1 kernel: \[924769.627497\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=119.14.163.138 DST=159.69.205.51 LEN=60 TOS=0x00 PREC=0x00 TTL=43 ID=50771 DF PROTO=TCP SPT=49558 DPT=80 WINDOW=14600 RES=0x00 SYN URGP=0 Dec 19 15:32:35 mc1 kernel: \[924771.622825\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=119.14.163.138 DST=159.69.205.51 LEN=60 TOS=0x00 PREC=0x00 TTL=43 ID=50772 DF PROTO=TCP SPT=49558 DPT=80 WINDOW=14600 RES=0x00 SYN URGP=0 ... |
2019-12-20 04:47:36 |
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 119.14.16.24
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 31049
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;119.14.16.24. IN A
;; AUTHORITY SECTION:
. 249 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022030800 1800 900 604800 86400
;; Query time: 183 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 08 18:03:59 CST 2022
;; MSG SIZE rcvd: 105
24.16.14.119.in-addr.arpa domain name pointer host-24.16-14-119.dynamic.totalbb.net.tw.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
24.16.14.119.in-addr.arpa name = host-24.16-14-119.dynamic.totalbb.net.tw.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 158.69.112.76 | attack | 2020-04-03T13:14:44.962304shield sshd\[3404\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.69.112.76 user=root 2020-04-03T13:14:47.134081shield sshd\[3404\]: Failed password for root from 158.69.112.76 port 48170 ssh2 2020-04-03T13:17:00.633304shield sshd\[4237\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.69.112.76 user=root 2020-04-03T13:17:02.809841shield sshd\[4237\]: Failed password for root from 158.69.112.76 port 55320 ssh2 2020-04-03T13:19:18.953450shield sshd\[5124\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.69.112.76 user=root |
2020-04-04 00:34:18 |
| 93.170.36.2 | attackbots | Apr 3 16:22:24 hell sshd[7543]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.170.36.2 Apr 3 16:22:25 hell sshd[7543]: Failed password for invalid user first from 93.170.36.2 port 52900 ssh2 ... |
2020-04-03 23:59:38 |
| 80.28.211.131 | attackspam | (sshd) Failed SSH login from 80.28.211.131 (ES/Spain/131.red-80-28-211.staticip.rima-tde.net): 5 in the last 3600 secs |
2020-04-04 00:52:04 |
| 45.168.35.90 | attackbots | Invalid user admin from 45.168.35.90 port 41102 |
2020-04-04 00:12:25 |
| 106.12.182.1 | attack | Invalid user test from 106.12.182.1 port 49530 |
2020-04-03 23:56:18 |
| 106.13.125.241 | attackbotsspam | $f2bV_matches |
2020-04-04 00:46:24 |
| 31.184.254.198 | attack | Invalid user yhk from 31.184.254.198 port 47190 |
2020-04-04 00:15:18 |
| 51.77.145.114 | attackbots | Invalid user feng from 51.77.145.114 port 60518 |
2020-04-04 00:08:41 |
| 213.194.163.229 | attackspam | Apr 3 13:03:30 web8 sshd\[19104\]: Invalid user pi from 213.194.163.229 Apr 3 13:03:30 web8 sshd\[19104\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.194.163.229 Apr 3 13:03:30 web8 sshd\[19106\]: Invalid user pi from 213.194.163.229 Apr 3 13:03:31 web8 sshd\[19106\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.194.163.229 Apr 3 13:03:32 web8 sshd\[19104\]: Failed password for invalid user pi from 213.194.163.229 port 33304 ssh2 |
2020-04-04 00:19:58 |
| 134.209.228.253 | attackspam | Invalid user richard from 134.209.228.253 port 39262 |
2020-04-04 00:38:04 |
| 125.213.150.7 | attack | 2020-04-03T14:12:34.950337abusebot-3.cloudsearch.cf sshd[1167]: Invalid user wangrui from 125.213.150.7 port 58600 2020-04-03T14:12:34.956406abusebot-3.cloudsearch.cf sshd[1167]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.213.150.7 2020-04-03T14:12:34.950337abusebot-3.cloudsearch.cf sshd[1167]: Invalid user wangrui from 125.213.150.7 port 58600 2020-04-03T14:12:36.831744abusebot-3.cloudsearch.cf sshd[1167]: Failed password for invalid user wangrui from 125.213.150.7 port 58600 ssh2 2020-04-03T14:17:03.514768abusebot-3.cloudsearch.cf sshd[1500]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.213.150.7 user=root 2020-04-03T14:17:05.318831abusebot-3.cloudsearch.cf sshd[1500]: Failed password for root from 125.213.150.7 port 40960 ssh2 2020-04-03T14:21:47.386540abusebot-3.cloudsearch.cf sshd[1806]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.213.150 ... |
2020-04-04 00:39:25 |
| 218.253.69.134 | attack | Apr 3 17:12:55 * sshd[23822]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.253.69.134 Apr 3 17:12:58 * sshd[23822]: Failed password for invalid user zhanghongwei from 218.253.69.134 port 33244 ssh2 |
2020-04-04 00:18:51 |
| 107.170.91.121 | attackbotsspam | Apr 3 17:42:30 eventyay sshd[17064]: Failed password for root from 107.170.91.121 port 12759 ssh2 Apr 3 17:48:09 eventyay sshd[17260]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.170.91.121 Apr 3 17:48:11 eventyay sshd[17260]: Failed password for invalid user bkroot from 107.170.91.121 port 26100 ssh2 ... |
2020-04-04 00:45:37 |
| 182.72.207.148 | attack | detected by Fail2Ban |
2020-04-04 00:29:42 |
| 182.156.209.222 | attack | fail2ban |
2020-04-04 00:29:16 |