城市(city): unknown
省份(region): unknown
国家(country): United States of America (the)
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 18.119.20.129
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 49346
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;18.119.20.129. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2024120900 1800 900 604800 86400
;; Query time: 73 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Dec 09 14:54:23 CST 2024
;; MSG SIZE rcvd: 106129.20.119.18.in-addr.arpa domain name pointer ec2-18-119-20-129.us-east-2.compute.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
129.20.119.18.in-addr.arpa name = ec2-18-119-20-129.us-east-2.compute.amazonaws.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 49.234.30.46 | attack | Feb 5 20:47:57 srv-ubuntu-dev3 sshd[78206]: Invalid user insurgency from 49.234.30.46 Feb 5 20:47:57 srv-ubuntu-dev3 sshd[78206]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.30.46 Feb 5 20:47:57 srv-ubuntu-dev3 sshd[78206]: Invalid user insurgency from 49.234.30.46 Feb 5 20:47:59 srv-ubuntu-dev3 sshd[78206]: Failed password for invalid user insurgency from 49.234.30.46 port 34098 ssh2 Feb 5 20:51:18 srv-ubuntu-dev3 sshd[78600]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.30.46 user=root Feb 5 20:51:19 srv-ubuntu-dev3 sshd[78600]: Failed password for root from 49.234.30.46 port 59296 ssh2 Feb 5 20:54:05 srv-ubuntu-dev3 sshd[78861]: Invalid user az from 49.234.30.46 Feb 5 20:54:05 srv-ubuntu-dev3 sshd[78861]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.30.46 Feb 5 20:54:05 srv-ubuntu-dev3 sshd[78861]: Invalid user az from 49.23 ... |
2020-02-06 05:17:53 |
| 119.28.152.247 | attackbotsspam | Unauthorized connection attempt detected from IP address 119.28.152.247 to port 2160 [J] |
2020-02-06 05:12:50 |
| 201.220.188.27 | attack | Unauthorized connection attempt detected from IP address 201.220.188.27 to port 23 [J] |
2020-02-06 05:23:48 |
| 124.115.197.21 | attack | Unauthorized connection attempt detected from IP address 124.115.197.21 to port 5555 [J] |
2020-02-06 05:34:22 |
| 186.232.2.12 | attackspambots | Unauthorized connection attempt detected from IP address 186.232.2.12 to port 80 [J] |
2020-02-06 05:07:03 |
| 116.250.198.242 | attackspambots | Unauthorized connection attempt detected from IP address 116.250.198.242 to port 80 [J] |
2020-02-06 05:13:36 |
| 2.180.29.166 | attackbots | Unauthorized connection attempt detected from IP address 2.180.29.166 to port 8080 [J] |
2020-02-06 05:21:24 |
| 192.162.70.66 | attackspambots | Unauthorized connection attempt detected from IP address 192.162.70.66 to port 2220 [J] |
2020-02-06 05:26:20 |
| 122.138.123.183 | attackbotsspam | Unauthorized connection attempt detected from IP address 122.138.123.183 to port 23 [J] |
2020-02-06 05:35:09 |
| 178.62.108.111 | attackbotsspam | Unauthorized connection attempt detected from IP address 178.62.108.111 to port 2220 [J] |
2020-02-06 05:09:57 |
| 190.122.112.53 | attackspam | Unauthorized connection attempt detected from IP address 190.122.112.53 to port 23 [J] |
2020-02-06 05:05:26 |
| 116.104.92.123 | attackspambots | Unauthorized connection attempt detected from IP address 116.104.92.123 to port 23 [J] |
2020-02-06 05:35:42 |
| 187.162.241.234 | attack | Unauthorized connection attempt detected from IP address 187.162.241.234 to port 23 [J] |
2020-02-06 05:06:20 |
| 92.118.161.29 | attackbots | Unauthorized connection attempt detected from IP address 92.118.161.29 to port 118 [J] |
2020-02-06 05:15:10 |
| 122.51.238.42 | attackbots | Unauthorized connection attempt detected from IP address 122.51.238.42 to port 2220 [J] |
2020-02-06 05:12:08 |