City: unknown
Region: unknown
Country: Ecuador
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 200.25.140.79
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4337
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;200.25.140.79. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012100 1800 900 604800 86400
;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 21 16:41:23 CST 2025
;; MSG SIZE rcvd: 10679.140.25.200.in-addr.arpa domain name pointer 79.140.uio.satnet.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
79.140.25.200.in-addr.arpa name = 79.140.uio.satnet.net.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 197.211.9.62 | attackspam | Dec 25 13:04:32 localhost sshd\[15486\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=197.211.9.62 user=root Dec 25 13:04:34 localhost sshd\[15486\]: Failed password for root from 197.211.9.62 port 34428 ssh2 Dec 25 13:08:57 localhost sshd\[15523\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=197.211.9.62 user=root Dec 25 13:09:00 localhost sshd\[15523\]: Failed password for root from 197.211.9.62 port 36940 ssh2 Dec 25 13:13:18 localhost sshd\[15674\]: Invalid user kanao from 197.211.9.62 port 39428 Dec 25 13:13:18 localhost sshd\[15674\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=197.211.9.62 ... |
2019-12-25 21:19:34 |
| 171.251.238.117 | attackbotsspam | Attempt to attack host OS, exploiting network vulnerabilities, on 25-12-2019 06:20:09. |
2019-12-25 21:04:06 |
| 107.175.2.121 | attackspambots | (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-25 21:22:18 |
| 192.3.4.106 | attackspam | 40,44-04/04 [bc03/m123] PostRequest-Spammer scoring: nairobi |
2019-12-25 20:54:20 |
| 35.189.210.129 | attackbots | $f2bV_matches |
2019-12-25 21:22:56 |
| 59.145.221.103 | attackbotsspam | Dec 25 12:18:57 thevastnessof sshd[21877]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.145.221.103 ... |
2019-12-25 20:41:27 |
| 125.41.244.100 | attackbots | Scanning |
2019-12-25 20:44:46 |
| 64.71.131.98 | attackbots | Unauthorized connection attempt detected from IP address 64.71.131.98 to port 445 |
2019-12-25 21:07:25 |
| 216.10.249.73 | attack | Dec 25 12:59:05 localhost sshd\[21398\]: Invalid user contactus from 216.10.249.73 port 50512 Dec 25 12:59:05 localhost sshd\[21398\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=216.10.249.73 Dec 25 12:59:07 localhost sshd\[21398\]: Failed password for invalid user contactus from 216.10.249.73 port 50512 ssh2 |
2019-12-25 21:09:34 |
| 14.169.159.225 | attackspam | Attempt to attack host OS, exploiting network vulnerabilities, on 25-12-2019 06:20:09. |
2019-12-25 21:05:13 |
| 171.230.69.242 | attackspambots | Automatic report - Port Scan Attack |
2019-12-25 20:40:38 |
| 103.46.240.254 | attackbots | Unauthorised access (Dec 25) SRC=103.46.240.254 LEN=40 TTL=248 ID=28196 TCP DPT=445 WINDOW=1024 SYN |
2019-12-25 20:49:07 |
| 78.22.89.35 | attack | [ssh] SSH attack |
2019-12-25 20:46:47 |
| 158.69.204.215 | attackspambots | Dec 25 13:38:19 Invalid user test from 158.69.204.215 port 34472 |
2019-12-25 21:06:59 |
| 59.35.94.134 | attackbotsspam | Scanning |
2019-12-25 21:21:44 |