City: unknown
Region: unknown
Country: None
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 214.33.75.66
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62737
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;214.33.75.66. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021901 1800 900 604800 86400
;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 04:03:49 CST 2025
;; MSG SIZE rcvd: 105Host 66.75.33.214.in-addr.arpa not found: 2(SERVFAIL)
server can't find 214.33.75.66.in-addr.arpa: SERVFAIL| IP | Type | Details | Datetime |
|---|---|---|---|
| 51.79.86.177 | attack | Sep 1 23:28:46 cp sshd[4119]: Failed password for root from 51.79.86.177 port 60240 ssh2 Sep 1 23:28:46 cp sshd[4119]: Failed password for root from 51.79.86.177 port 60240 ssh2 Sep 1 23:28:48 cp sshd[4119]: Failed password for root from 51.79.86.177 port 60240 ssh2 |
2020-09-02 06:21:09 |
| 159.89.145.59 | attackspam | [N10.H2.VM2] Port Scanner Detected Blocked by UFW |
2020-09-02 06:39:13 |
| 50.63.161.42 | attackspam | 50.63.161.42 - - [01/Sep/2020:21:48:35 +0100] "POST /wp-login.php HTTP/1.1" 200 2254 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 50.63.161.42 - - [01/Sep/2020:21:48:37 +0100] "POST /wp-login.php HTTP/1.1" 200 2181 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 50.63.161.42 - - [01/Sep/2020:21:48:40 +0100] "POST /wp-login.php HTTP/1.1" 200 2187 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" ... |
2020-09-02 06:19:26 |
| 222.186.180.147 | attackbots | Sep 2 00:29:15 abendstille sshd\[16503\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.147 user=root Sep 2 00:29:16 abendstille sshd\[16506\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.147 user=root Sep 2 00:29:17 abendstille sshd\[16503\]: Failed password for root from 222.186.180.147 port 2704 ssh2 Sep 2 00:29:18 abendstille sshd\[16506\]: Failed password for root from 222.186.180.147 port 14742 ssh2 Sep 2 00:29:20 abendstille sshd\[16503\]: Failed password for root from 222.186.180.147 port 2704 ssh2 ... |
2020-09-02 06:37:58 |
| 46.101.189.37 | attack | Invalid user git from 46.101.189.37 port 55470 |
2020-09-02 06:29:22 |
| 128.14.134.134 | attackbotsspam |
|
2020-09-02 06:52:11 |
| 222.186.180.130 | attackbotsspam | Sep 1 15:29:54 dignus sshd[7483]: Failed password for root from 222.186.180.130 port 31808 ssh2 Sep 1 15:29:56 dignus sshd[7483]: Failed password for root from 222.186.180.130 port 31808 ssh2 Sep 1 15:29:59 dignus sshd[7512]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.130 user=root Sep 1 15:30:01 dignus sshd[7512]: Failed password for root from 222.186.180.130 port 41550 ssh2 Sep 1 15:30:03 dignus sshd[7512]: Failed password for root from 222.186.180.130 port 41550 ssh2 ... |
2020-09-02 06:31:27 |
| 106.75.25.114 | attackspambots | $f2bV_matches |
2020-09-02 06:42:43 |
| 49.235.217.169 | attack | Invalid user test from 49.235.217.169 port 48980 |
2020-09-02 06:49:31 |
| 59.110.138.221 | attackbotsspam | [01/Sep/2020:18:47:36 +0200] Web-Request: "GET /wp-login.php", User-Agent: "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" |
2020-09-02 06:24:19 |
| 172.64.88.28 | attackspambots | RUSSIAN SCAMMERS ! |
2020-09-02 06:27:01 |
| 51.255.28.53 | attackbotsspam | Invalid user flo from 51.255.28.53 port 38238 |
2020-09-02 06:20:16 |
| 107.175.33.19 | attack | SSH Invalid Login |
2020-09-02 06:17:32 |
| 224.0.0.252 | botsattackproxy | there are unmediated big problems with this ip range still, in someway utilising bt tv stream packets unbeknowing to bt home hub wifi customers. devices become host servers and use of US at&t proxy ip's on some home hub locations routing other traffic. BT do not use proxy's on home hub connections |
2020-09-02 06:23:55 |
| 129.211.22.160 | attackbotsspam | reported through recidive - multiple failed attempts(SSH) |
2020-09-02 06:42:02 |