City: unknown
Region: unknown
Country: Brazil
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 189.95.67.12
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 53115
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;189.95.67.12. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025022001 1800 900 604800 86400
;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 21 06:21:26 CST 2025
;; MSG SIZE rcvd: 10512.67.95.189.in-addr.arpa domain name pointer 189-95-67-12.3g.claro.net.br.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
12.67.95.189.in-addr.arpa name = 189-95-67-12.3g.claro.net.br.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 113.170.130.188 | attackspam | IP reached maximum auth failures |
2020-08-30 06:53:00 |
| 117.50.5.94 | attack | Unauthorized access to SSH at 29/Aug/2020:20:24:04 +0000. |
2020-08-30 06:55:44 |
| 141.98.10.209 | attack | SSH Brute-Force attacks |
2020-08-30 07:09:05 |
| 92.222.92.237 | attackspambots | 92.222.92.237 - - \[29/Aug/2020:22:23:48 +0200\] "POST /wp-login.php HTTP/1.0" 200 5983 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" 92.222.92.237 - - \[29/Aug/2020:22:23:49 +0200\] "POST /wp-login.php HTTP/1.0" 200 5815 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" 92.222.92.237 - - \[29/Aug/2020:22:23:50 +0200\] "POST /xmlrpc.php HTTP/1.0" 200 736 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" |
2020-08-30 07:01:44 |
| 134.202.64.173 | attackspambots | (From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across guarinochiropractic.com a few minutes ago. Looks great… but now what? By that I mean, when someone like me finds your website – either through Search or just bouncing around – what happens next? Do you get a lot of leads from your site, or at least enough to make you happy? Honestly, most business websites fall a bit short when it comes to generating paying customers. Studies show that 70% of a site’s visitors disappear and are gone forever after just a moment. Here’s an idea… How about making it really EASY for every visitor who shows up to get a personal phone call you as soon as they hit your site… You can – Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number. It signals you the moment they let you know they’re interested – so that you can talk to that lead while they’re literally looking over your site. CLICK HERE http://w |
2020-08-30 06:51:12 |
| 178.128.217.135 | attackbotsspam | $f2bV_matches |
2020-08-30 06:28:07 |
| 222.186.180.223 | attack | Aug 30 00:50:58 melroy-server sshd[24047]: Failed password for root from 222.186.180.223 port 61104 ssh2 Aug 30 00:51:03 melroy-server sshd[24047]: Failed password for root from 222.186.180.223 port 61104 ssh2 ... |
2020-08-30 06:58:49 |
| 52.231.92.23 | attackspambots | Aug 30 00:27:59 home sshd[2748569]: Failed password for invalid user testftp from 52.231.92.23 port 38482 ssh2 Aug 30 00:32:41 home sshd[2750193]: Invalid user sinusbot from 52.231.92.23 port 48516 Aug 30 00:32:41 home sshd[2750193]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.231.92.23 Aug 30 00:32:41 home sshd[2750193]: Invalid user sinusbot from 52.231.92.23 port 48516 Aug 30 00:32:43 home sshd[2750193]: Failed password for invalid user sinusbot from 52.231.92.23 port 48516 ssh2 ... |
2020-08-30 06:56:58 |
| 180.164.176.50 | attackbotsspam | Invalid user cma from 180.164.176.50 port 59996 |
2020-08-30 06:35:20 |
| 185.38.3.138 | attackspam | Aug 30 00:28:23 minden010 sshd[8664]: Failed password for root from 185.38.3.138 port 49644 ssh2 Aug 30 00:30:12 minden010 sshd[9330]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.38.3.138 Aug 30 00:30:14 minden010 sshd[9330]: Failed password for invalid user sibyl from 185.38.3.138 port 53812 ssh2 ... |
2020-08-30 07:00:13 |
| 139.59.59.187 | attackbots | Invalid user tester from 139.59.59.187 port 52896 |
2020-08-30 07:00:41 |
| 106.12.171.188 | attack | Banned for a week because repeated abuses, for example SSH, but not only |
2020-08-30 06:57:46 |
| 93.150.110.52 | attack | Port probing on unauthorized port 23 |
2020-08-30 06:26:55 |
| 182.235.230.167 | attackbotsspam | Port probing on unauthorized port 23 |
2020-08-30 06:58:29 |
| 112.85.42.180 | attackbotsspam | Aug 30 00:31:04 marvibiene sshd[31031]: Failed password for root from 112.85.42.180 port 8295 ssh2 Aug 30 00:31:09 marvibiene sshd[31031]: Failed password for root from 112.85.42.180 port 8295 ssh2 |
2020-08-30 06:36:13 |