City: Zurich
Region: Zurich
Country: Switzerland
Internet Service Provider: Swisscom
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 85.2.133.74
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9744
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;85.2.133.74. IN A
;; AUTHORITY SECTION:
. 386 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2020083101 1800 900 604800 86400
;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Sep 01 08:23:45 CST 2020
;; MSG SIZE rcvd: 11574.133.2.85.in-addr.arpa domain name pointer 74.133.2.85.dynamic.wline.res.cust.swisscom.ch.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
74.133.2.85.in-addr.arpa name = 74.133.2.85.dynamic.wline.res.cust.swisscom.ch.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 129.211.63.79 | attackbots | Dec 12 10:55:26 meumeu sshd[10563]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.63.79 Dec 12 10:55:28 meumeu sshd[10563]: Failed password for invalid user ignatz from 129.211.63.79 port 44114 ssh2 Dec 12 11:03:47 meumeu sshd[12130]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.63.79 ... |
2019-12-12 18:13:17 |
| 123.30.181.204 | attackbots | Dec 12 11:04:36 eventyay sshd[25168]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.30.181.204 Dec 12 11:04:38 eventyay sshd[25168]: Failed password for invalid user sjouke from 123.30.181.204 port 60220 ssh2 Dec 12 11:12:22 eventyay sshd[25481]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.30.181.204 ... |
2019-12-12 18:28:15 |
| 104.129.4.229 | attackspam | (From eric@talkwithcustomer.com) Hello knutsonchiropractic.com, People ask, “why does TalkWithCustomer work so well?” It’s simple. TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time. - NOT one week, two weeks, three weeks after they’ve checked out your website knutsonchiropractic.com. - NOT with a form letter style email that looks like it was written by a bot. - NOT with a robocall that could come at any time out of the blue. TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU. They kick off the conversation. They take that first step. They ask to hear from you regarding what you have to offer and how it can make their life better. And it happens almost immediately. In real time. While they’re still looking over your website knutsonchiropractic.com, trying to make up their mind whether you are right for them. When you connect with them at that very moment it’s the ultimate in Perfect Timing – |
2019-12-12 18:03:23 |
| 61.154.96.32 | attackspambots | MultiHost/MultiPort Probe, Scan, Hack - |
2019-12-12 18:26:20 |
| 220.76.107.50 | attackbots | Dec 12 10:41:31 MK-Soft-VM3 sshd[6805]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.76.107.50 Dec 12 10:41:34 MK-Soft-VM3 sshd[6805]: Failed password for invalid user admin from 220.76.107.50 port 37440 ssh2 ... |
2019-12-12 17:50:11 |
| 112.133.229.64 | attackspambots | Unauthorized connection attempt detected from IP address 112.133.229.64 to port 445 |
2019-12-12 18:22:44 |
| 113.161.160.93 | attackspam | Helo |
2019-12-12 18:21:44 |
| 118.42.125.170 | attackbotsspam | Automatic report: SSH brute force attempt |
2019-12-12 18:04:55 |
| 106.12.211.247 | attackspam | [ssh] SSH attack |
2019-12-12 18:24:47 |
| 113.184.105.129 | attackbots | Unauthorized connection attempt from IP address 113.184.105.129 on Port 445(SMB) |
2019-12-12 18:15:24 |
| 68.34.15.8 | attackbotsspam | SSH bruteforce |
2019-12-12 18:01:58 |
| 180.244.208.174 | attackspam | Unauthorized connection attempt detected from IP address 180.244.208.174 to port 445 |
2019-12-12 17:58:27 |
| 115.78.4.96 | attackbots | 1576131998 - 12/12/2019 07:26:38 Host: 115.78.4.96/115.78.4.96 Port: 445 TCP Blocked |
2019-12-12 18:18:01 |
| 197.155.234.157 | attackbotsspam | Dec 12 10:39:00 eventyay sshd[24267]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=197.155.234.157 Dec 12 10:39:02 eventyay sshd[24267]: Failed password for invalid user humboldt from 197.155.234.157 port 54582 ssh2 Dec 12 10:46:12 eventyay sshd[24488]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=197.155.234.157 ... |
2019-12-12 17:55:49 |
| 51.68.97.191 | attack | 2019-12-12T07:51:59.335888shield sshd\[12442\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip191.ip-51-68-97.eu user=root 2019-12-12T07:52:01.388646shield sshd\[12442\]: Failed password for root from 51.68.97.191 port 46824 ssh2 2019-12-12T07:59:40.926479shield sshd\[14992\]: Invalid user nasruddin from 51.68.97.191 port 55552 2019-12-12T07:59:40.930951shield sshd\[14992\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip191.ip-51-68-97.eu 2019-12-12T07:59:42.938179shield sshd\[14992\]: Failed password for invalid user nasruddin from 51.68.97.191 port 55552 ssh2 |
2019-12-12 17:50:38 |