City: unknown
Region: unknown
Country: Germany
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 134.92.45.52
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 82
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;134.92.45.52. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012801 1800 900 604800 86400
;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 29 04:29:50 CST 2025
;; MSG SIZE rcvd: 105
Host 52.45.92.134.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 52.45.92.134.in-addr.arpa: NXDOMAIN
| IP | Type | Details | Datetime |
|---|---|---|---|
| 159.65.96.102 | attackbotsspam | May 13 17:51:38 server sshd\[165004\]: Invalid user randy from 159.65.96.102 May 13 17:51:38 server sshd\[165004\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.96.102 May 13 17:51:40 server sshd\[165004\]: Failed password for invalid user randy from 159.65.96.102 port 40856 ssh2 ... |
2019-10-09 16:59:01 |
| 159.65.164.133 | attack | Jul 2 19:18:35 server sshd\[89343\]: Invalid user constructor from 159.65.164.133 Jul 2 19:18:35 server sshd\[89343\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.164.133 Jul 2 19:18:37 server sshd\[89343\]: Failed password for invalid user constructor from 159.65.164.133 port 59012 ssh2 ... |
2019-10-09 17:22:49 |
| 159.89.116.97 | attackspam | Apr 20 05:43:23 server sshd\[212693\]: Invalid user token from 159.89.116.97 Apr 20 05:43:23 server sshd\[212693\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.116.97 Apr 20 05:43:25 server sshd\[212693\]: Failed password for invalid user token from 159.89.116.97 port 48316 ssh2 ... |
2019-10-09 16:55:34 |
| 159.65.239.104 | attackspam | May 24 08:09:10 server sshd\[164877\]: Invalid user kj from 159.65.239.104 May 24 08:09:10 server sshd\[164877\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.239.104 May 24 08:09:11 server sshd\[164877\]: Failed password for invalid user kj from 159.65.239.104 port 39204 ssh2 ... |
2019-10-09 17:13:08 |
| 116.212.141.50 | attack | SSH invalid-user multiple login attempts |
2019-10-09 17:23:28 |
| 159.89.199.216 | attack | Jul 2 07:49:48 server sshd\[128954\]: Invalid user admin from 159.89.199.216 Jul 2 07:49:48 server sshd\[128954\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.199.216 Jul 2 07:49:50 server sshd\[128954\]: Failed password for invalid user admin from 159.89.199.216 port 58294 ssh2 ... |
2019-10-09 16:41:06 |
| 159.65.159.1 | attackbotsspam | Apr 23 15:42:57 server sshd\[80221\]: Invalid user telnetd from 159.65.159.1 Apr 23 15:42:57 server sshd\[80221\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.159.1 Apr 23 15:42:59 server sshd\[80221\]: Failed password for invalid user telnetd from 159.65.159.1 port 46122 ssh2 ... |
2019-10-09 17:25:06 |
| 177.69.237.49 | attackspambots | SSH Brute-Force reported by Fail2Ban |
2019-10-09 16:40:15 |
| 106.75.21.242 | attackbots | Oct 8 22:42:22 auw2 sshd\[8732\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.21.242 user=root Oct 8 22:42:24 auw2 sshd\[8732\]: Failed password for root from 106.75.21.242 port 54098 ssh2 Oct 8 22:47:06 auw2 sshd\[9127\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.21.242 user=root Oct 8 22:47:08 auw2 sshd\[9127\]: Failed password for root from 106.75.21.242 port 59590 ssh2 Oct 8 22:51:40 auw2 sshd\[9519\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.21.242 user=root |
2019-10-09 17:00:48 |
| 139.59.89.7 | attackspam | Oct 9 11:14:58 MK-Soft-VM6 sshd[16107]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.89.7 Oct 9 11:15:00 MK-Soft-VM6 sshd[16107]: Failed password for invalid user !23e$56y&89o from 139.59.89.7 port 44292 ssh2 ... |
2019-10-09 17:18:03 |
| 46.148.127.209 | attackbotsspam | B: Magento admin pass test (wrong country) |
2019-10-09 16:53:54 |
| 51.68.189.69 | attack | Jul 13 16:20:47 server sshd\[4136\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.68.189.69 user=root Jul 13 16:20:49 server sshd\[4136\]: Failed password for root from 51.68.189.69 port 45528 ssh2 Jul 13 16:25:32 server sshd\[4341\]: Invalid user xm from 51.68.189.69 Jul 13 16:25:32 server sshd\[4341\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.68.189.69 ... |
2019-10-09 17:15:16 |
| 159.65.236.58 | attackspambots | May 3 23:50:40 server sshd\[62521\]: Invalid user jboss from 159.65.236.58 May 3 23:50:40 server sshd\[62521\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.236.58 May 3 23:50:42 server sshd\[62521\]: Failed password for invalid user jboss from 159.65.236.58 port 40620 ssh2 ... |
2019-10-09 17:13:54 |
| 159.89.170.154 | attackbots | Jun 29 11:20:46 server sshd\[224628\]: Invalid user cible from 159.89.170.154 Jun 29 11:20:46 server sshd\[224628\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.170.154 Jun 29 11:20:48 server sshd\[224628\]: Failed password for invalid user cible from 159.89.170.154 port 50094 ssh2 ... |
2019-10-09 16:47:42 |
| 159.65.70.218 | attackbotsspam | Aug 4 17:28:52 server sshd\[91698\]: Invalid user am from 159.65.70.218 Aug 4 17:28:52 server sshd\[91698\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.70.218 Aug 4 17:28:54 server sshd\[91698\]: Failed password for invalid user am from 159.65.70.218 port 38432 ssh2 ... |
2019-10-09 17:05:25 |