City: Boardman
Region: Oregon
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 96.127.93.94
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 19325
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;96.127.93.94. IN A
;; AUTHORITY SECTION:
. 324 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2020080701 1800 900 604800 86400
;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Aug 08 07:30:16 CST 2020
;; MSG SIZE rcvd: 11694.93.127.96.in-addr.arpa domain name pointer ec2-96-127-93-94.us-gov-west-1.compute.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
94.93.127.96.in-addr.arpa name = ec2-96-127-93-94.us-gov-west-1.compute.amazonaws.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 188.166.237.191 | attack | Invalid user openvpn from 188.166.237.191 port 32994 |
2019-10-05 16:00:41 |
| 112.112.102.79 | attackspam | Oct 5 05:35:45 ovpn sshd\[29583\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.112.102.79 user=root Oct 5 05:35:46 ovpn sshd\[29583\]: Failed password for root from 112.112.102.79 port 5259 ssh2 Oct 5 05:46:37 ovpn sshd\[32250\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.112.102.79 user=root Oct 5 05:46:39 ovpn sshd\[32250\]: Failed password for root from 112.112.102.79 port 5261 ssh2 Oct 5 05:51:00 ovpn sshd\[783\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.112.102.79 user=root |
2019-10-05 15:52:48 |
| 217.35.75.193 | attack | 2019-10-05T05:00:37.165458abusebot-7.cloudsearch.cf sshd\[23436\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=host217-35-75-193.in-addr.btopenworld.com user=root |
2019-10-05 15:50:04 |
| 95.154.198.211 | attack | Automatic report - Banned IP Access |
2019-10-05 15:51:51 |
| 27.254.136.29 | attack | Oct 4 22:04:38 php1 sshd\[17370\]: Invalid user p0o9i8u7y6 from 27.254.136.29 Oct 4 22:04:38 php1 sshd\[17370\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.254.136.29 Oct 4 22:04:40 php1 sshd\[17370\]: Failed password for invalid user p0o9i8u7y6 from 27.254.136.29 port 45566 ssh2 Oct 4 22:09:26 php1 sshd\[18077\]: Invalid user Profond2017 from 27.254.136.29 Oct 4 22:09:26 php1 sshd\[18077\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.254.136.29 |
2019-10-05 16:11:56 |
| 146.88.240.4 | attackbotsspam | Scanning random ports - tries to find possible vulnerable services |
2019-10-05 15:40:51 |
| 175.45.1.34 | attackspam | Unauthorised access (Oct 5) SRC=175.45.1.34 LEN=40 TTL=240 ID=58398 TCP DPT=445 WINDOW=1024 SYN |
2019-10-05 15:59:38 |
| 222.186.180.41 | attackspam | frenzy |
2019-10-05 15:49:12 |
| 138.68.82.220 | attack | Invalid user michi from 138.68.82.220 port 58014 |
2019-10-05 15:39:09 |
| 158.69.241.198 | attack | VoIP Brute Force - 158.69.241.198 - Auto Report ... |
2019-10-05 16:14:20 |
| 104.144.21.254 | attackspam | (From gretchen.nichols779@gmail.com) Hello, I'm quite certain you're aware that most successful businesses always have their website come up on the first page of Google search results since they're more relevant, popular, and more credible compared to the other companies found on page 2 or so on. Have you ever wondered how these websites dominated the first page? It's not at all difficult to achieve! We can put your site on the first page using search engine optimization. I ran a few tests on your website and found out that there are many keywords you can potentially rank for. These are crucial for you to be easily found while people searching on Google input words relevant to your products or services. To give you an idea of my work, I will send you case studies of websites I've worked with before and how they gained more profit after the optimization. I'll also give you a free consultation over the phone, and the information about your website can benefit you whether or not you choose to avail of m |
2019-10-05 15:35:47 |
| 27.148.205.75 | attackbots | Oct 5 02:50:12 Tower sshd[38371]: Connection from 27.148.205.75 port 51428 on 192.168.10.220 port 22 Oct 5 02:50:14 Tower sshd[38371]: Failed password for root from 27.148.205.75 port 51428 ssh2 Oct 5 02:50:14 Tower sshd[38371]: Received disconnect from 27.148.205.75 port 51428:11: Bye Bye [preauth] Oct 5 02:50:14 Tower sshd[38371]: Disconnected from authenticating user root 27.148.205.75 port 51428 [preauth] |
2019-10-05 15:43:30 |
| 128.199.133.249 | attackspambots | 2019-10-05T07:15:50.682095homeassistant sshd[16054]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.133.249 user=root 2019-10-05T07:15:52.661512homeassistant sshd[16054]: Failed password for root from 128.199.133.249 port 37880 ssh2 ... |
2019-10-05 16:04:47 |
| 222.186.173.154 | attackspambots | Oct 5 09:52:35 meumeu sshd[9440]: Failed password for root from 222.186.173.154 port 49938 ssh2 Oct 5 09:52:40 meumeu sshd[9440]: Failed password for root from 222.186.173.154 port 49938 ssh2 Oct 5 09:52:55 meumeu sshd[9440]: error: maximum authentication attempts exceeded for root from 222.186.173.154 port 49938 ssh2 [preauth] ... |
2019-10-05 16:03:01 |
| 222.186.180.8 | attack | SSH Brute Force, server-1 sshd[26099]: Failed password for root from 222.186.180.8 port 2352 ssh2 |
2019-10-05 15:58:40 |