城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.21.20.69
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54548
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.21.20.69. IN A
;; AUTHORITY SECTION:
. 146 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022021700 1800 900 604800 86400
;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 02:15:30 CST 2022
;; MSG SIZE rcvd: 105
Host 69.20.21.104.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 69.20.21.104.in-addr.arpa: NXDOMAIN
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 218.92.0.184 | attack | Nov 23 15:59:01 ns382633 sshd\[26077\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.184 user=root Nov 23 15:59:03 ns382633 sshd\[26077\]: Failed password for root from 218.92.0.184 port 7528 ssh2 Nov 23 15:59:10 ns382633 sshd\[26077\]: Failed password for root from 218.92.0.184 port 7528 ssh2 Nov 23 15:59:13 ns382633 sshd\[26077\]: Failed password for root from 218.92.0.184 port 7528 ssh2 Nov 23 15:59:16 ns382633 sshd\[26077\]: Failed password for root from 218.92.0.184 port 7528 ssh2 |
2019-11-24 00:32:12 |
| 222.186.173.180 | attackbots | Nov 21 11:23:07 microserver sshd[612]: Failed none for root from 222.186.173.180 port 10820 ssh2 Nov 21 11:23:08 microserver sshd[612]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.180 user=root Nov 21 11:23:10 microserver sshd[612]: Failed password for root from 222.186.173.180 port 10820 ssh2 Nov 21 11:23:13 microserver sshd[612]: Failed password for root from 222.186.173.180 port 10820 ssh2 Nov 21 11:23:16 microserver sshd[612]: Failed password for root from 222.186.173.180 port 10820 ssh2 Nov 21 14:16:37 microserver sshd[26209]: Failed none for root from 222.186.173.180 port 22212 ssh2 Nov 21 14:16:37 microserver sshd[26209]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.180 user=root Nov 21 14:16:39 microserver sshd[26209]: Failed password for root from 222.186.173.180 port 22212 ssh2 Nov 21 14:16:42 microserver sshd[26209]: Failed password for root from 222.186.173.180 port 22212 ssh2 Nov 21 14 |
2019-11-24 00:21:07 |
| 179.109.89.168 | attackspam | Unauthorised access (Nov 23) SRC=179.109.89.168 LEN=44 TOS=0x10 PREC=0x40 TTL=50 ID=42823 TCP DPT=23 WINDOW=13922 SYN |
2019-11-24 00:11:49 |
| 110.45.155.101 | attack | Nov 23 17:24:12 OPSO sshd\[7775\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.45.155.101 user=root Nov 23 17:24:14 OPSO sshd\[7775\]: Failed password for root from 110.45.155.101 port 40482 ssh2 Nov 23 17:28:40 OPSO sshd\[8417\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.45.155.101 user=root Nov 23 17:28:41 OPSO sshd\[8417\]: Failed password for root from 110.45.155.101 port 48264 ssh2 Nov 23 17:33:06 OPSO sshd\[9098\]: Invalid user www-data from 110.45.155.101 port 56052 Nov 23 17:33:06 OPSO sshd\[9098\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.45.155.101 |
2019-11-24 00:36:59 |
| 115.231.220.133 | attack | ET SCAN Suspicious inbound to mySQL port 3306 - port: 3306 proto: TCP cat: Potentially Bad Traffic |
2019-11-24 00:35:54 |
| 139.59.16.245 | attackbots | 2019-11-24T01:43:30.127367luisaranguren sshd[3686290]: Connection from 139.59.16.245 port 58592 on 10.10.10.6 port 22 rdomain "" 2019-11-24T01:43:31.292103luisaranguren sshd[3686290]: Invalid user haff from 139.59.16.245 port 58592 2019-11-24T01:43:31.904121luisaranguren sshd[3686290]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.16.245 2019-11-24T01:43:30.127367luisaranguren sshd[3686290]: Connection from 139.59.16.245 port 58592 on 10.10.10.6 port 22 rdomain "" 2019-11-24T01:43:31.292103luisaranguren sshd[3686290]: Invalid user haff from 139.59.16.245 port 58592 2019-11-24T01:43:34.308743luisaranguren sshd[3686290]: Failed password for invalid user haff from 139.59.16.245 port 58592 ssh2 ... |
2019-11-24 00:12:57 |
| 121.157.82.218 | attackspambots | 2019-11-23T14:26:33.707696abusebot-5.cloudsearch.cf sshd\[8664\]: Invalid user bjorn from 121.157.82.218 port 44654 |
2019-11-24 00:02:55 |
| 45.55.67.128 | attackspambots | 2019-11-23T15:45:38.797321shield sshd\[29770\]: Invalid user rueda from 45.55.67.128 port 56977 2019-11-23T15:45:38.801672shield sshd\[29770\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.67.128 2019-11-23T15:45:41.190753shield sshd\[29770\]: Failed password for invalid user rueda from 45.55.67.128 port 56977 ssh2 2019-11-23T15:49:43.573886shield sshd\[30759\]: Invalid user Amazon@123 from 45.55.67.128 port 46340 2019-11-23T15:49:43.578062shield sshd\[30759\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.67.128 |
2019-11-23 23:58:27 |
| 63.88.23.195 | attackbotsspam | 63.88.23.195 was recorded 5 times by 2 hosts attempting to connect to the following ports: 80. Incident counter (4h, 24h, all-time): 5, 5, 469 |
2019-11-24 00:18:37 |
| 210.92.105.120 | attackspam | Nov 23 21:28:10 vibhu-HP-Z238-Microtower-Workstation sshd\[7809\]: Invalid user blaa from 210.92.105.120 Nov 23 21:28:10 vibhu-HP-Z238-Microtower-Workstation sshd\[7809\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.92.105.120 Nov 23 21:28:12 vibhu-HP-Z238-Microtower-Workstation sshd\[7809\]: Failed password for invalid user blaa from 210.92.105.120 port 36366 ssh2 Nov 23 21:32:12 vibhu-HP-Z238-Microtower-Workstation sshd\[7987\]: Invalid user eckhart from 210.92.105.120 Nov 23 21:32:12 vibhu-HP-Z238-Microtower-Workstation sshd\[7987\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.92.105.120 ... |
2019-11-24 00:03:31 |
| 1.186.63.133 | attackspam | postfix (unknown user, SPF fail or relay access denied) |
2019-11-23 23:55:59 |
| 66.108.165.215 | attackspambots | SSH Brute-Force reported by Fail2Ban |
2019-11-24 00:37:58 |
| 220.120.106.254 | attackspambots | Nov 23 16:55:59 vps58358 sshd\[17797\]: Invalid user wittorff from 220.120.106.254Nov 23 16:56:01 vps58358 sshd\[17797\]: Failed password for invalid user wittorff from 220.120.106.254 port 41754 ssh2Nov 23 16:59:47 vps58358 sshd\[17805\]: Invalid user hue from 220.120.106.254Nov 23 16:59:49 vps58358 sshd\[17805\]: Failed password for invalid user hue from 220.120.106.254 port 51558 ssh2Nov 23 17:03:37 vps58358 sshd\[17820\]: Invalid user guest from 220.120.106.254Nov 23 17:03:39 vps58358 sshd\[17820\]: Failed password for invalid user guest from 220.120.106.254 port 60632 ssh2 ... |
2019-11-24 00:25:27 |
| 62.4.14.198 | attackspambots | Automatic report - Banned IP Access |
2019-11-24 00:26:49 |
| 14.186.189.225 | attackspambots | 19/11/23@09:26:02: FAIL: IoT-SSH address from=14.186.189.225 ... |
2019-11-24 00:24:10 |