城市(city): unknown
省份(region): unknown
国家(country): Singapore
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 13.214.252.219
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 22499
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;13.214.252.219. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025022000 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 23:46:40 CST 2025
;; MSG SIZE rcvd: 107219.252.214.13.in-addr.arpa domain name pointer ec2-13-214-252-219.ap-southeast-1.compute.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
219.252.214.13.in-addr.arpa name = ec2-13-214-252-219.ap-southeast-1.compute.amazonaws.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 79.198.61.141 | attackspam | fire |
2019-11-18 07:05:59 |
| 113.219.81.122 | attackbotsspam | Telnet Server BruteForce Attack |
2019-11-18 06:52:37 |
| 222.186.175.161 | attackspam | Nov 17 20:10:44 firewall sshd[4268]: Failed password for root from 222.186.175.161 port 33956 ssh2 Nov 17 20:11:00 firewall sshd[4268]: error: maximum authentication attempts exceeded for root from 222.186.175.161 port 33956 ssh2 [preauth] Nov 17 20:11:00 firewall sshd[4268]: Disconnecting: Too many authentication failures [preauth] ... |
2019-11-18 07:13:22 |
| 106.13.101.129 | attackbots | Nov 17 15:21:49 ns382633 sshd\[24709\]: Invalid user asterisk from 106.13.101.129 port 59008 Nov 17 15:21:49 ns382633 sshd\[24709\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.101.129 Nov 17 15:21:51 ns382633 sshd\[24709\]: Failed password for invalid user asterisk from 106.13.101.129 port 59008 ssh2 Nov 17 15:33:43 ns382633 sshd\[26824\]: Invalid user braunstein from 106.13.101.129 port 35758 Nov 17 15:33:43 ns382633 sshd\[26824\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.101.129 |
2019-11-18 06:38:05 |
| 145.239.83.89 | attack | Nov 18 00:41:07 server sshd\[9406\]: Invalid user schilles from 145.239.83.89 port 53980 Nov 18 00:41:07 server sshd\[9406\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.83.89 Nov 18 00:41:08 server sshd\[9406\]: Failed password for invalid user schilles from 145.239.83.89 port 53980 ssh2 Nov 18 00:44:51 server sshd\[14791\]: Invalid user buono from 145.239.83.89 port 34700 Nov 18 00:44:51 server sshd\[14791\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.83.89 |
2019-11-18 06:59:28 |
| 82.232.89.194 | attackspam | fire |
2019-11-18 07:00:23 |
| 77.6.165.202 | attackspam | fire |
2019-11-18 07:08:14 |
| 111.200.242.26 | attack | Nov 17 10:25:19 ny01 sshd[19722]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.200.242.26 Nov 17 10:25:21 ny01 sshd[19722]: Failed password for invalid user ut from 111.200.242.26 port 32389 ssh2 Nov 17 10:30:09 ny01 sshd[20340]: Failed password for root from 111.200.242.26 port 42154 ssh2 |
2019-11-18 06:36:28 |
| 46.101.171.183 | attack | Attempted to connect 3 times to port 80 TCP |
2019-11-18 06:50:27 |
| 117.66.243.77 | attackbots | CyberHackers.eu > SSH Bruteforce attempt! |
2019-11-18 06:36:00 |
| 62.219.50.252 | attackspambots | Nov 17 08:23:25 : SSH login attempts with invalid user |
2019-11-18 07:07:58 |
| 67.205.180.200 | attackbotsspam | WordPress login Brute force / Web App Attack on client site. |
2019-11-18 06:41:39 |
| 185.234.216.173 | attackbotsspam | Connection by 185.234.216.173 on port: 25 got caught by honeypot at 11/17/2019 9:45:04 PM |
2019-11-18 06:55:02 |
| 78.148.138.214 | attackbotsspam | fire |
2019-11-18 07:06:22 |
| 185.143.223.139 | attackbotsspam | firewall-block, port(s): 36048/tcp, 36049/tcp, 36060/tcp, 36113/tcp, 36421/tcp, 36687/tcp, 36849/tcp, 36855/tcp, 36867/tcp, 36914/tcp |
2019-11-18 06:37:51 |