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.20.149.94
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2180
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;41.20.149.94. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020901 1800 900 604800 86400
;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 11:18:25 CST 2025
;; MSG SIZE rcvd: 105
94.149.20.41.in-addr.arpa domain name pointer vc-41-20-149-94.adsl.vodacom.co.za.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
94.149.20.41.in-addr.arpa name = vc-41-20-149-94.adsl.vodacom.co.za.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 218.92.0.148 | attackspambots | Jan 2 10:34:00 MK-Soft-VM7 sshd[6070]: Failed password for root from 218.92.0.148 port 6186 ssh2 Jan 2 10:34:05 MK-Soft-VM7 sshd[6070]: Failed password for root from 218.92.0.148 port 6186 ssh2 ... |
2020-01-02 17:42:14 |
| 87.67.191.52 | attackspambots | Jan 2 06:17:59 shadeyouvpn sshd[6650]: Invalid user kusch from 87.67.191.52 port 56702 Jan 2 06:17:59 shadeyouvpn sshd[6650]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.67.191.52 Jan 2 06:18:01 shadeyouvpn sshd[6650]: Failed password for invalid user kusch from 87.67.191.52 port 56702 ssh2 Jan 2 06:18:01 shadeyouvpn sshd[6650]: Received disconnect from 87.67.191.52 port 56702:11: Bye Bye [preauth] Jan 2 06:18:01 shadeyouvpn sshd[6650]: Disconnected from 87.67.191.52 port 56702 [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=87.67.191.52 |
2020-01-02 17:22:49 |
| 103.245.10.6 | attackspambots | Jan 2 08:51:18 v22018076622670303 sshd\[24458\]: Invalid user guest from 103.245.10.6 port 43554 Jan 2 08:51:18 v22018076622670303 sshd\[24458\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.245.10.6 Jan 2 08:51:19 v22018076622670303 sshd\[24458\]: Failed password for invalid user guest from 103.245.10.6 port 43554 ssh2 ... |
2020-01-02 17:15:06 |
| 222.186.169.47 | attackbots | Lines containing failures of 222.186.169.47 Jan 1 10:15:05 MAKserver06 sshd[12396]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.169.47 user=r.r Jan 1 10:15:07 MAKserver06 sshd[12396]: Failed password for r.r from 222.186.169.47 port 53856 ssh2 Jan 1 10:15:09 MAKserver06 sshd[12396]: Failed password for r.r from 222.186.169.47 port 53856 ssh2 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=222.186.169.47 |
2020-01-02 17:27:07 |
| 113.255.109.124 | attackspambots | Honeypot attack, port: 5555, PTR: 124-109-255-113-on-nets.com. |
2020-01-02 17:52:45 |
| 128.234.1.80 | attackspambots | Host Scan |
2020-01-02 17:41:48 |
| 103.28.219.152 | attackspam | ssh brute force |
2020-01-02 17:47:49 |
| 81.32.185.207 | attackspam | SSH authentication failure x 6 reported by Fail2Ban ... |
2020-01-02 17:15:24 |
| 186.206.131.158 | attackbots | Jan 2 06:22:01 ws12vmsma01 sshd[7978]: Failed password for invalid user infomatikk from 186.206.131.158 port 53414 ssh2 Jan 2 06:24:00 ws12vmsma01 sshd[8251]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.206.131.158 user=backup Jan 2 06:24:02 ws12vmsma01 sshd[8251]: Failed password for backup from 186.206.131.158 port 41416 ssh2 ... |
2020-01-02 17:17:36 |
| 210.16.189.19 | attackbots | C2,WP GET /wp-login.php |
2020-01-02 17:47:30 |
| 69.94.158.71 | attack | $f2bV_matches |
2020-01-02 17:19:06 |
| 37.209.101.251 | attackbots | Dec 30 07:57:00 sanyalnet-awsem3-1 sshd[30009]: Connection from 37.209.101.251 port 50880 on 172.30.0.184 port 22 Dec 30 07:57:01 sanyalnet-awsem3-1 sshd[30009]: reveeclipse mapping checking getaddrinfo for hsi-kbw-37-209-101-251.hsi15.kabel-badenwuerttemberg.de [37.209.101.251] failed - POSSIBLE BREAK-IN ATTEMPT! Dec 30 07:57:01 sanyalnet-awsem3-1 sshd[30009]: User r.r from 37.209.101.251 not allowed because not listed in AllowUsers Dec 30 07:57:01 sanyalnet-awsem3-1 sshd[30009]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.209.101.251 user=r.r Dec 30 07:57:03 sanyalnet-awsem3-1 sshd[30009]: Failed password for invalid user r.r from 37.209.101.251 port 50880 ssh2 Dec 30 07:57:03 sanyalnet-awsem3-1 sshd[30009]: Received disconnect from 37.209.101.251: 11: Bye Bye [preauth] Dec 30 08:13:04 sanyalnet-awsem3-1 sshd[349]: Connection from 37.209.101.251 port 59416 on 172.30.0.184 port 22 Dec 30 08:13:05 sanyalnet-awsem3-1 sshd[3........ ------------------------------- |
2020-01-02 17:31:17 |
| 82.117.244.85 | attack | Jan 2 07:26:35 |
2020-01-02 17:37:07 |
| 5.135.181.11 | attackspam | 2020-01-02T08:54:01.707426abusebot-7.cloudsearch.cf sshd[28054]: Invalid user shultz from 5.135.181.11 port 41714 2020-01-02T08:54:01.712012abusebot-7.cloudsearch.cf sshd[28054]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns3010967.ip-5-135-181.eu 2020-01-02T08:54:01.707426abusebot-7.cloudsearch.cf sshd[28054]: Invalid user shultz from 5.135.181.11 port 41714 2020-01-02T08:54:04.070764abusebot-7.cloudsearch.cf sshd[28054]: Failed password for invalid user shultz from 5.135.181.11 port 41714 ssh2 2020-01-02T08:56:43.806197abusebot-7.cloudsearch.cf sshd[28237]: Invalid user riiber from 5.135.181.11 port 37070 2020-01-02T08:56:43.810237abusebot-7.cloudsearch.cf sshd[28237]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns3010967.ip-5-135-181.eu 2020-01-02T08:56:43.806197abusebot-7.cloudsearch.cf sshd[28237]: Invalid user riiber from 5.135.181.11 port 37070 2020-01-02T08:56:45.579744abusebot-7.cloudsearc ... |
2020-01-02 17:26:09 |
| 117.102.64.66 | attackspam | Honeypot attack, port: 445, PTR: PTR record not found |
2020-01-02 17:25:12 |