City: unknown
Region: unknown
Country: South Africa
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 41.11.195.21
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17965
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;41.11.195.21. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012600 1800 900 604800 86400
;; Query time: 45 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 26 21:59:30 CST 2025
;; MSG SIZE rcvd: 10521.195.11.41.in-addr.arpa domain name pointer vc-kzn-41-11-195-21.umts.vodacom.co.za.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
21.195.11.41.in-addr.arpa name = vc-kzn-41-11-195-21.umts.vodacom.co.za.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 193.70.43.220 | attack | Nov 16 17:32:05 venus sshd\[31003\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.70.43.220 user=root Nov 16 17:32:07 venus sshd\[31003\]: Failed password for root from 193.70.43.220 port 37796 ssh2 Nov 16 17:35:36 venus sshd\[31028\]: Invalid user alex from 193.70.43.220 port 57084 Nov 16 17:35:36 venus sshd\[31028\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.70.43.220 ... |
2019-11-17 01:38:57 |
| 186.195.119.28 | attackspambots | Automatic report - Port Scan Attack |
2019-11-17 01:01:23 |
| 179.209.65.221 | attackbotsspam | 23/tcp [2019-11-16]1pkt |
2019-11-17 01:38:36 |
| 103.86.111.158 | attackbots | 1024/tcp [2019-11-16]1pkt |
2019-11-17 01:06:39 |
| 62.219.138.14 | attackspam | 2323/tcp [2019-11-16]1pkt |
2019-11-17 01:34:37 |
| 106.13.78.218 | attackspambots | 2019-11-16T15:52:33.660650hub.schaetter.us sshd\[26646\]: Invalid user elleke from 106.13.78.218 port 55052 2019-11-16T15:52:33.672472hub.schaetter.us sshd\[26646\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.78.218 2019-11-16T15:52:35.859838hub.schaetter.us sshd\[26646\]: Failed password for invalid user elleke from 106.13.78.218 port 55052 ssh2 2019-11-16T15:58:28.092140hub.schaetter.us sshd\[26687\]: Invalid user claireen from 106.13.78.218 port 33844 2019-11-16T15:58:28.101520hub.schaetter.us sshd\[26687\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.78.218 2019-11-16T15:58:30.023190hub.schaetter.us sshd\[26687\]: Failed password for invalid user claireen from 106.13.78.218 port 33844 ssh2 ... |
2019-11-17 01:10:03 |
| 123.206.88.24 | attackbotsspam | Fail2Ban - SSH Bruteforce Attempt |
2019-11-17 01:43:28 |
| 176.109.18.65 | attackbots | " " |
2019-11-17 01:23:21 |
| 218.92.0.180 | attackspambots | Nov 16 15:51:07 dedicated sshd[18344]: Failed password for root from 218.92.0.180 port 53220 ssh2 Nov 16 15:51:11 dedicated sshd[18344]: Failed password for root from 218.92.0.180 port 53220 ssh2 Nov 16 15:51:16 dedicated sshd[18344]: Failed password for root from 218.92.0.180 port 53220 ssh2 Nov 16 15:51:18 dedicated sshd[18344]: Failed password for root from 218.92.0.180 port 53220 ssh2 Nov 16 15:51:22 dedicated sshd[18344]: Failed password for root from 218.92.0.180 port 53220 ssh2 |
2019-11-17 01:33:11 |
| 46.105.227.206 | attack | Automatic report - Banned IP Access |
2019-11-17 00:59:23 |
| 182.61.106.79 | attack | Nov 16 16:57:19 legacy sshd[13660]: Failed password for root from 182.61.106.79 port 55480 ssh2 Nov 16 17:01:37 legacy sshd[13787]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.106.79 Nov 16 17:01:39 legacy sshd[13787]: Failed password for invalid user duljit from 182.61.106.79 port 36200 ssh2 ... |
2019-11-17 01:07:07 |
| 5.135.229.186 | attack | 445/tcp [2019-11-16]1pkt |
2019-11-17 01:40:36 |
| 210.56.20.181 | attackspam | Nov 16 16:36:51 XXX sshd[17999]: Invalid user earl from 210.56.20.181 port 34304 |
2019-11-17 01:26:35 |
| 106.54.102.94 | attack | 106.54.102.94 was recorded 5 times by 2 hosts attempting to connect to the following ports: 22. Incident counter (4h, 24h, all-time): 5, 5, 9 |
2019-11-17 01:39:38 |
| 118.201.195.131 | attack | 23/tcp [2019-11-16]1pkt |
2019-11-17 01:19:35 |