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.8.136.66
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 34363
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;41.8.136.66. IN A
;; AUTHORITY SECTION:
. 514 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022010500 1800 900 604800 86400
;; Query time: 121 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 05 20:14:20 CST 2022
;; MSG SIZE rcvd: 104
b'66.136.8.41.in-addr.arpa domain name pointer vc-kzn-41-8-136-66.umts.vodacom.co.za.
'
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
66.136.8.41.in-addr.arpa name = vc-kzn-41-8-136-66.umts.vodacom.co.za.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 184.22.201.129 | attack | 2020-09-06 02:40:05.268076-0500 localhost smtpd[16817]: NOQUEUE: reject: RCPT from unknown[184.22.201.129]: 554 5.7.1 Service unavailable; Client host [184.22.201.129] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/184.22.201.129 / https://www.spamhaus.org/sbl/query/SBLCSS; from= |
2020-09-07 00:15:01 |
| 134.202.64.131 | attackspambots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found staytunedchiropractic.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well. So here’s my question – what happens AFTER someone lands on your site? Anything? Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever. That means that all the work and effort you put into getting them to show up, goes down the tubes. Why would you want all that good work – and the great site you’ve built – go to waste? Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry. But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket? You can – thanks to revolutionary new softwa |
2020-09-06 23:49:07 |
| 94.102.51.95 | attack |
|
2020-09-07 00:06:48 |
| 191.240.39.77 | attack | Sep 5 18:47:52 *host* postfix/smtps/smtpd\[6352\]: warning: unknown\[191.240.39.77\]: SASL PLAIN authentication failed: |
2020-09-07 00:25:53 |
| 107.173.193.197 | proxy | Tried to hack vpn... |
2020-09-06 23:56:08 |
| 185.220.101.206 | attack | (sshd) Failed SSH login from 185.220.101.206 (DE/Germany/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep 6 17:50:47 amsweb01 sshd[26838]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.220.101.206 user=root Sep 6 17:50:50 amsweb01 sshd[26838]: Failed password for root from 185.220.101.206 port 16454 ssh2 Sep 6 17:50:51 amsweb01 sshd[26838]: Failed password for root from 185.220.101.206 port 16454 ssh2 Sep 6 17:50:53 amsweb01 sshd[26838]: Failed password for root from 185.220.101.206 port 16454 ssh2 Sep 6 17:50:55 amsweb01 sshd[26838]: Failed password for root from 185.220.101.206 port 16454 ssh2 |
2020-09-06 23:55:14 |
| 209.50.62.28 | attackspam | This IP is associated with RDP abuse. It was found in a paste by https://twitter.com/RdpSnitch - https://pastebin.com/fZES2rHx For more information, or to report interesting/incorrect findings, contact us - bot@tines.io |
2020-09-06 23:49:58 |
| 189.126.95.27 | attackspam | DATE:2020-09-05 18:48:26, IP:189.126.95.27, PORT:telnet - Telnet brute force auth on a honeypot server (epe-dc) |
2020-09-07 00:00:54 |
| 101.99.12.202 | attackbotsspam | 20/9/5@12:47:53: FAIL: Alarm-Network address from=101.99.12.202 ... |
2020-09-07 00:24:48 |
| 178.32.163.202 | attackspambots | 178.32.163.202 (FR/France/-), 7 distributed sshd attacks on account [root] in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_DISTATTACK; Logs: Sep 6 10:21:15 server2 sshd[20192]: Failed password for root from 178.32.163.202 port 39872 ssh2 Sep 6 10:20:30 server2 sshd[19770]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.109.150.77 user=root Sep 6 10:18:23 server2 sshd[18592]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.235.94 user=root Sep 6 10:17:31 server2 sshd[18039]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.52.68.21 user=root Sep 6 10:17:32 server2 sshd[18039]: Failed password for root from 60.52.68.21 port 35728 ssh2 Sep 6 10:20:32 server2 sshd[19770]: Failed password for root from 150.109.150.77 port 33414 ssh2 Sep 6 10:18:25 server2 sshd[18592]: Failed password for root from 167.172.235.94 port 40036 ssh2 IP Addresses Blocked: |
2020-09-07 00:19:44 |
| 51.75.87.58 | attack | 2020-09-05 12:39:32.540258-0500 localhost smtpd[46585]: NOQUEUE: reject: RCPT from unknown[51.75.87.58]: 450 4.7.25 Client host rejected: cannot find your hostname, [51.75.87.58]; from= |
2020-09-07 00:15:31 |
| 120.133.136.75 | attack | Sep 6 02:31:48 melroy-server sshd[1237]: Failed password for root from 120.133.136.75 port 60310 ssh2 ... |
2020-09-06 23:44:23 |
| 14.141.244.114 | attackspam | RDP Bruteforce |
2020-09-07 00:11:12 |
| 150.109.147.145 | attackbots | $f2bV_matches |
2020-09-07 00:23:35 |
| 61.133.232.253 | attack | SSH bruteforce |
2020-09-06 23:51:05 |