City: unknown
Region: unknown
Country: Switzerland
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 57.40.45.41
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 23635
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;57.40.45.41. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020302 1800 900 604800 86400
;; Query time: 67 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 04 09:08:58 CST 2025
;; MSG SIZE rcvd: 104Host 41.45.40.57.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 41.45.40.57.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 80.82.77.189 | attackspambots | Feb 14 07:57:07 debian-2gb-nbg1-2 kernel: \[3922653.303305\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=80.82.77.189 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=42195 PROTO=TCP SPT=51749 DPT=1890 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-02-14 15:34:15 |
| 123.207.144.186 | attackbots | Invalid user git from 123.207.144.186 port 51528 |
2020-02-14 16:08:15 |
| 88.102.244.211 | attackspambots | Feb 14 05:55:14 MK-Soft-VM4 sshd[24557]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.102.244.211 Feb 14 05:55:16 MK-Soft-VM4 sshd[24557]: Failed password for invalid user zhu from 88.102.244.211 port 35122 ssh2 ... |
2020-02-14 15:55:38 |
| 222.186.15.10 | attackspam | Feb 14 08:53:54 MK-Soft-VM4 sshd[15206]: Failed password for root from 222.186.15.10 port 36405 ssh2 Feb 14 08:53:58 MK-Soft-VM4 sshd[15206]: Failed password for root from 222.186.15.10 port 36405 ssh2 ... |
2020-02-14 16:01:16 |
| 103.48.192.48 | attackbotsspam | Automatic report - SSH Brute-Force Attack |
2020-02-14 16:06:53 |
| 119.56.222.52 | attack | MultiHost/MultiPort Probe, Scan, Hack - |
2020-02-14 15:53:15 |
| 222.186.52.78 | attackspam | 2020-02-14T07:50:06.336253shield sshd\[15905\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.52.78 user=root 2020-02-14T07:50:08.306557shield sshd\[15905\]: Failed password for root from 222.186.52.78 port 25660 ssh2 2020-02-14T07:50:09.808513shield sshd\[15905\]: Failed password for root from 222.186.52.78 port 25660 ssh2 2020-02-14T07:50:12.251539shield sshd\[15905\]: Failed password for root from 222.186.52.78 port 25660 ssh2 2020-02-14T07:52:21.412217shield sshd\[15999\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.52.78 user=root |
2020-02-14 15:57:35 |
| 123.207.78.83 | attackspambots | Feb 14 07:04:01 silence02 sshd[10302]: Failed password for root from 123.207.78.83 port 41370 ssh2 Feb 14 07:07:26 silence02 sshd[10513]: Failed password for root from 123.207.78.83 port 33216 ssh2 Feb 14 07:10:23 silence02 sshd[10690]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.207.78.83 |
2020-02-14 15:41:13 |
| 49.164.50.252 | attackbotsspam | Feb 14 05:55:52 |
2020-02-14 15:46:50 |
| 165.227.211.13 | attackbots | Invalid user cr from 165.227.211.13 port 57710 |
2020-02-14 15:56:50 |
| 95.9.35.222 | attack | Automatic report - Port Scan Attack |
2020-02-14 15:31:58 |
| 45.188.66.81 | attackspambots | Automatic report - Banned IP Access |
2020-02-14 15:47:25 |
| 212.47.250.50 | attackspambots | Feb 14 07:46:42 silence02 sshd[13281]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.47.250.50 Feb 14 07:46:44 silence02 sshd[13281]: Failed password for invalid user adrock from 212.47.250.50 port 34072 ssh2 Feb 14 07:56:34 silence02 sshd[13824]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.47.250.50 |
2020-02-14 16:10:15 |
| 125.25.90.103 | attackbotsspam | SSH authentication failure x 6 reported by Fail2Ban ... |
2020-02-14 15:46:23 |
| 222.186.175.220 | attack | Fail2Ban Ban Triggered |
2020-02-14 15:48:31 |