城市(city): unknown
省份(region): unknown
国家(country): None
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 54.90.134.95
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 37728
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;54.90.134.95. IN A
;; AUTHORITY SECTION:
. 215 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022021301 1800 900 604800 86400
;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 14 11:34:11 CST 2022
;; MSG SIZE rcvd: 105
95.134.90.54.in-addr.arpa domain name pointer ec2-54-90-134-95.compute-1.amazonaws.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
95.134.90.54.in-addr.arpa name = ec2-54-90-134-95.compute-1.amazonaws.com.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 88.147.125.131 | attackbots | Honeypot attack, port: 23, PTR: 88-147-125-131.v4.ngi.it. |
2019-12-24 16:12:39 |
| 5.178.87.219 | attackspam | Automatic report - SSH Brute-Force Attack |
2019-12-24 15:50:11 |
| 222.186.180.147 | attackspam | --- report --- Dec 24 04:36:37 sshd: Connection from 222.186.180.147 port 13760 Dec 24 04:36:41 sshd: Failed password for root from 222.186.180.147 port 13760 ssh2 Dec 24 04:36:42 sshd: Received disconnect from 222.186.180.147: 11: [preauth] |
2019-12-24 15:48:15 |
| 74.82.47.8 | attackbots | firewall-block, port(s): 50075/tcp |
2019-12-24 16:09:03 |
| 202.126.208.122 | attack | Dec 24 08:20:07 host sshd[33249]: Invalid user bohr from 202.126.208.122 port 56341 ... |
2019-12-24 16:11:55 |
| 201.48.65.147 | attackbotsspam | Invalid user dyrnes from 201.48.65.147 port 52714 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.48.65.147 Failed password for invalid user dyrnes from 201.48.65.147 port 52714 ssh2 Invalid user grimesa from 201.48.65.147 port 45174 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.48.65.147 |
2019-12-24 15:58:42 |
| 218.92.0.164 | attack | Dec 14 04:00:55 microserver sshd[37709]: Failed none for root from 218.92.0.164 port 53343 ssh2 Dec 14 04:00:56 microserver sshd[37709]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.164 user=root Dec 14 04:00:57 microserver sshd[37709]: Failed password for root from 218.92.0.164 port 53343 ssh2 Dec 14 04:01:01 microserver sshd[37709]: Failed password for root from 218.92.0.164 port 53343 ssh2 Dec 14 04:01:04 microserver sshd[37709]: Failed password for root from 218.92.0.164 port 53343 ssh2 Dec 15 13:53:06 microserver sshd[43960]: Failed none for root from 218.92.0.164 port 39399 ssh2 Dec 15 13:53:07 microserver sshd[43960]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.164 user=root Dec 15 13:53:09 microserver sshd[43960]: Failed password for root from 218.92.0.164 port 39399 ssh2 Dec 15 13:53:12 microserver sshd[43960]: Failed password for root from 218.92.0.164 port 39399 ssh2 Dec 15 13:53:15 microserve |
2019-12-24 16:17:51 |
| 120.132.124.237 | attackbots | Invalid user user7 from 120.132.124.237 port 50748 |
2019-12-24 16:15:57 |
| 190.221.48.250 | attackspambots | Attempt to attack host OS, exploiting network vulnerabilities, on 24-12-2019 07:20:11. |
2019-12-24 16:02:57 |
| 150.242.74.187 | attackbots | Dec 24 00:54:43 h1946882 sshd[22283]: Address 150.242.74.187 maps to dh= cp.tripleplay.in, but this does not map back to the address - POSSIBLE = BREAK-IN ATTEMPT! Dec 24 00:54:43 h1946882 sshd[22283]: pam_unix(sshd:auth): authenticati= on failure; logname=3D uid=3D0 euid=3D0 tty=3Dssh ruser=3D rhost=3D150.= 242.74.187=20 Dec 24 00:54:45 h1946882 sshd[22283]: Failed password for invalid user = dbus from 150.242.74.187 port 59930 ssh2 Dec 24 00:54:45 h1946882 sshd[22283]: Received disconnect from 150.242.= 74.187: 11: Bye Bye [preauth] Dec 24 01:05:50 h1946882 sshd[22403]: Address 150.242.74.187 maps to dh= cp.tripleplay.in, but this does not map back to the address - POSSIBLE = BREAK-IN ATTEMPT! Dec 24 01:05:50 h1946882 sshd[22403]: pam_unix(sshd:auth): authenticati= on failure; logname=3D uid=3D0 euid=3D0 tty=3Dssh ruser=3D rhost=3D150.= 242.74.187 user=3Dr.r Dec 24 01:05:52 h1946882 sshd[22403]: Failed password for r.r from 150= .242.74.187 port 38102 ssh2 ........ --------------------------------------- |
2019-12-24 15:52:43 |
| 176.31.253.55 | attackspambots | Dec 24 08:18:07 vps691689 sshd[14886]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.31.253.55 Dec 24 08:18:08 vps691689 sshd[14886]: Failed password for invalid user prueba123 from 176.31.253.55 port 45060 ssh2 Dec 24 08:20:25 vps691689 sshd[14956]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.31.253.55 ... |
2019-12-24 15:51:48 |
| 222.186.175.215 | attackbots | SSH Bruteforce attempt |
2019-12-24 16:00:07 |
| 194.135.97.42 | attackbotsspam | Unauthorized connection attempt detected from IP address 194.135.97.42 to port 445 |
2019-12-24 15:37:53 |
| 132.232.81.207 | attack | Dec 24 10:17:33 server sshd\[31711\]: Invalid user fab from 132.232.81.207 Dec 24 10:17:33 server sshd\[31711\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.81.207 Dec 24 10:17:36 server sshd\[31711\]: Failed password for invalid user fab from 132.232.81.207 port 48734 ssh2 Dec 24 10:20:08 server sshd\[32160\]: Invalid user webmaster from 132.232.81.207 Dec 24 10:20:08 server sshd\[32160\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.81.207 ... |
2019-12-24 16:07:35 |
| 103.129.47.51 | attackbots | TCP Port: 25 invalid blocked dnsbl-sorbs also barracuda and zen-spamhaus (217) |
2019-12-24 16:16:19 |