City: unknown
Region: unknown
Country: Switzerland
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 82.130.79.141
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38330
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;82.130.79.141. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021400 1800 900 604800 86400
;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 14 20:30:04 CST 2025
;; MSG SIZE rcvd: 106141.79.130.82.in-addr.arpa domain name pointer 82-130-79-141.net4.ethz.ch.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
141.79.130.82.in-addr.arpa name = 82-130-79-141.net4.ethz.ch.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 177.68.74.97 | attackspambots | Automatic report - Port Scan Attack |
2019-10-13 12:38:05 |
| 158.69.210.117 | attackspambots | 2019-10-13T03:57:16.174686abusebot-7.cloudsearch.cf sshd\[15493\]: Invalid user Qaz_123 from 158.69.210.117 port 41248 |
2019-10-13 12:35:04 |
| 80.132.221.10 | attack | IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/80.132.221.10/ DE - 1H : (55) Protection Against DDoS WordPress plugin : "odzyskiwanie danych help-dysk" IP Address Ranges by Country : DE NAME ASN : ASN3320 IP : 80.132.221.10 CIDR : 80.128.0.0/12 PREFIX COUNT : 481 UNIQUE IP COUNT : 29022208 WYKRYTE ATAKI Z ASN3320 : 1H - 1 3H - 3 6H - 4 12H - 13 24H - 18 DateTime : 2019-10-13 05:56:56 INFO : Port SERVER 80 Scan Detected and Blocked by ADMIN - data recovery |
2019-10-13 12:46:55 |
| 59.25.197.154 | attackspambots | 2019-10-13T03:57:05.877849abusebot-5.cloudsearch.cf sshd\[809\]: Invalid user robert from 59.25.197.154 port 55590 |
2019-10-13 12:44:16 |
| 89.245.80.189 | attackbotsspam | 2019-10-13T04:33:38.468839abusebot-8.cloudsearch.cf sshd\[14509\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=i59f550bd.versanet.de user=root |
2019-10-13 12:37:08 |
| 218.76.171.129 | attack | Oct 13 00:34:29 mail sshd[13382]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.76.171.129 user=root Oct 13 00:34:31 mail sshd[13382]: Failed password for root from 218.76.171.129 port 24928 ssh2 Oct 13 05:57:08 mail sshd[25991]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.76.171.129 user=root Oct 13 05:57:10 mail sshd[25991]: Failed password for root from 218.76.171.129 port 45666 ssh2 ... |
2019-10-13 12:39:18 |
| 121.134.159.21 | attackspambots | Oct 12 18:34:24 php1 sshd\[3758\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.134.159.21 user=root Oct 12 18:34:26 php1 sshd\[3758\]: Failed password for root from 121.134.159.21 port 43110 ssh2 Oct 12 18:39:09 php1 sshd\[4226\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.134.159.21 user=root Oct 12 18:39:11 php1 sshd\[4226\]: Failed password for root from 121.134.159.21 port 54456 ssh2 Oct 12 18:43:59 php1 sshd\[4582\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.134.159.21 user=root |
2019-10-13 12:59:23 |
| 182.252.0.188 | attackspam | Oct 13 03:48:13 ip-172-31-62-245 sshd\[8496\]: Invalid user P4SSW0RD from 182.252.0.188\ Oct 13 03:48:15 ip-172-31-62-245 sshd\[8496\]: Failed password for invalid user P4SSW0RD from 182.252.0.188 port 33119 ssh2\ Oct 13 03:52:18 ip-172-31-62-245 sshd\[8518\]: Invalid user Dirty@2017 from 182.252.0.188\ Oct 13 03:52:20 ip-172-31-62-245 sshd\[8518\]: Failed password for invalid user Dirty@2017 from 182.252.0.188 port 52636 ssh2\ Oct 13 03:56:29 ip-172-31-62-245 sshd\[8555\]: Invalid user Virus2017 from 182.252.0.188\ |
2019-10-13 13:05:03 |
| 222.186.15.160 | attack | Oct 13 07:06:46 v22018076622670303 sshd\[31739\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.15.160 user=root Oct 13 07:06:48 v22018076622670303 sshd\[31739\]: Failed password for root from 222.186.15.160 port 53464 ssh2 Oct 13 07:06:51 v22018076622670303 sshd\[31739\]: Failed password for root from 222.186.15.160 port 53464 ssh2 ... |
2019-10-13 13:07:41 |
| 106.51.80.198 | attackbots | 2019-10-13T04:51:43.248577abusebot-3.cloudsearch.cf sshd\[11212\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.51.80.198 user=root |
2019-10-13 12:53:47 |
| 154.117.154.34 | attackbots | firewall-block, port(s): 23/tcp |
2019-10-13 12:56:34 |
| 37.49.231.121 | attackspam | *Port Scan* detected from 37.49.231.121 (NL/Netherlands/-). 4 hits in the last 165 seconds |
2019-10-13 12:33:29 |
| 185.30.160.190 | attackspam | [ 🧯 ] From bounce6@informativo-planosdesaude.com.br Sun Oct 13 00:56:48 2019 Received: from mail6.informativo-planosdesaude.com.br ([185.30.160.190]:35021) |
2019-10-13 12:51:55 |
| 23.94.177.187 | attackbots | (From eric@talkwithcustomer.com) Hey, You have a website roscoechiro.com, right? Of course you do. I am looking at your website now. It gets traffic every day – that you’re probably spending $2 / $4 / $10 or more a click to get. Not including all of the work you put into creating social media, videos, blog posts, emails, and so on. So you’re investing seriously in getting people to that site. But how’s it working? Great? Okay? Not so much? If that answer could be better, then it’s likely you’re putting a lot of time, effort, and money into an approach that’s not paying off like it should. Now… imagine doubling your lead conversion in just minutes… In fact, I’ll go even better. You could actually get up to 100X more conversions! I’m not making this up. As Chris Smith, best-selling author of The Conversion Code says: Speed is essential - there is a 100x decrease in Leads when a Lead is contacted within 14 minutes vs being contacted within 5 minutes. He’s backed up by a study a |
2019-10-13 12:35:42 |
| 134.175.62.14 | attackspam | Automatic report - Banned IP Access |
2019-10-13 13:03:44 |