City: unknown
Region: unknown
Country: None
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 54.133.53.145
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 43971
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;54.133.53.145. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021901 1800 900 604800 86400
;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 04:32:17 CST 2025
;; MSG SIZE rcvd: 106Host 145.53.133.54.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 145.53.133.54.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 190.64.141.18 | attack | Oct 13 20:09:09 venus sshd\[19951\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.64.141.18 user=root Oct 13 20:09:11 venus sshd\[19951\]: Failed password for root from 190.64.141.18 port 48268 ssh2 Oct 13 20:14:24 venus sshd\[20057\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.64.141.18 user=root ... |
2019-10-14 06:17:49 |
| 185.90.116.76 | attackbots | 10/13/2019-17:12:49.788184 185.90.116.76 Protocol: 6 ET SCAN Potential SSH Scan |
2019-10-14 06:50:12 |
| 176.31.253.102 | attackbots | miraniessen.de 176.31.253.102 \[13/Oct/2019:22:13:41 +0200\] "POST /wp-login.php HTTP/1.1" 200 5971 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" miraniessen.de 176.31.253.102 \[13/Oct/2019:22:13:42 +0200\] "POST /wp-login.php HTTP/1.1" 200 5975 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" |
2019-10-14 06:48:17 |
| 62.234.67.109 | attack | Oct 13 20:13:54 work-partkepr sshd\[6945\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.67.109 user=root Oct 13 20:13:56 work-partkepr sshd\[6945\]: Failed password for root from 62.234.67.109 port 55170 ssh2 ... |
2019-10-14 06:24:24 |
| 27.124.39.24 | attack | 2019-10-13T21:56:35.777239abusebot-8.cloudsearch.cf sshd\[18614\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.124.39.24 user=root |
2019-10-14 06:34:38 |
| 101.231.146.36 | attack | 2019-10-13T21:49:25.554915abusebot-5.cloudsearch.cf sshd\[12303\]: Invalid user deepak from 101.231.146.36 port 45930 2019-10-13T21:49:25.559960abusebot-5.cloudsearch.cf sshd\[12303\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.231.146.36 |
2019-10-14 06:09:38 |
| 157.230.27.47 | attack | Oct 13 12:03:32 sachi sshd\[18618\]: Invalid user qwerty12345 from 157.230.27.47 Oct 13 12:03:32 sachi sshd\[18618\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.27.47 Oct 13 12:03:34 sachi sshd\[18618\]: Failed password for invalid user qwerty12345 from 157.230.27.47 port 37614 ssh2 Oct 13 12:07:46 sachi sshd\[18966\]: Invalid user Bizz@2017 from 157.230.27.47 Oct 13 12:07:46 sachi sshd\[18966\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.27.47 |
2019-10-14 06:13:03 |
| 197.59.29.192 | attack | "Fail2Ban detected SSH brute force attempt" |
2019-10-14 06:47:58 |
| 2.137.252.21 | attack | IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/2.137.252.21/ ES - 1H : (25) Protection Against DDoS WordPress plugin : "odzyskiwanie danych help-dysk" IP Address Ranges by Country : ES NAME ASN : ASN3352 IP : 2.137.252.21 CIDR : 2.137.0.0/16 PREFIX COUNT : 662 UNIQUE IP COUNT : 10540800 WYKRYTE ATAKI Z ASN3352 : 1H - 1 3H - 2 6H - 3 12H - 6 24H - 9 DateTime : 2019-10-13 22:13:44 INFO : Port Scan TELNET Detected and Blocked by ADMIN - data recovery |
2019-10-14 06:45:06 |
| 167.99.173.0 | attack | Feb 13 03:35:32 dillonfme sshd\[21578\]: Invalid user nagios from 167.99.173.0 port 50428 Feb 13 03:35:32 dillonfme sshd\[21578\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.173.0 Feb 13 03:35:34 dillonfme sshd\[21578\]: Failed password for invalid user nagios from 167.99.173.0 port 50428 ssh2 Feb 13 03:40:28 dillonfme sshd\[21999\]: Invalid user sammy from 167.99.173.0 port 41506 Feb 13 03:40:28 dillonfme sshd\[21999\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.173.0 ... |
2019-10-14 06:28:10 |
| 167.99.159.2 | attack | Feb 10 03:59:03 dillonfme sshd\[16596\]: Invalid user lost from 167.99.159.2 port 45808 Feb 10 03:59:03 dillonfme sshd\[16596\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.159.2 Feb 10 03:59:06 dillonfme sshd\[16596\]: Failed password for invalid user lost from 167.99.159.2 port 45808 ssh2 Feb 10 04:05:50 dillonfme sshd\[16822\]: Invalid user smile from 167.99.159.2 port 41361 Feb 10 04:05:50 dillonfme sshd\[16822\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.159.2 ... |
2019-10-14 06:33:22 |
| 79.181.32.1 | attackspam | ENG,WP GET /wp-login.php |
2019-10-14 06:35:02 |
| 109.194.54.130 | attackbotsspam | SSH authentication failure x 6 reported by Fail2Ban ... |
2019-10-14 06:54:03 |
| 98.207.32.236 | attack | SSH-bruteforce attempts |
2019-10-14 06:19:34 |
| 51.255.197.164 | attackbotsspam | Oct 14 00:17:34 SilenceServices sshd[18325]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.255.197.164 Oct 14 00:17:36 SilenceServices sshd[18325]: Failed password for invalid user P@$$w0rt12345 from 51.255.197.164 port 34748 ssh2 Oct 14 00:21:49 SilenceServices sshd[19459]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.255.197.164 |
2019-10-14 06:34:08 |