City: unknown
Region: unknown
Country: Argentina
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.94.166.65
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 11364
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.94.166.65. IN A
;; AUTHORITY SECTION:
. 335 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2023112203 1800 900 604800 86400
;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Nov 23 10:36:26 CST 2023
;; MSG SIZE rcvd: 106
65.166.94.104.in-addr.arpa domain name pointer a104-94-166-65.deploy.static.akamaitechnologies.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
65.166.94.104.in-addr.arpa name = a104-94-166-65.deploy.static.akamaitechnologies.com.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 45.125.65.35 | attackspam | Apr 16 15:34:10 srv01 postfix/smtpd\[6919\]: warning: unknown\[45.125.65.35\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 16 15:34:30 srv01 postfix/smtpd\[6919\]: warning: unknown\[45.125.65.35\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 16 15:34:37 srv01 postfix/smtpd\[6919\]: warning: unknown\[45.125.65.35\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 16 15:44:26 srv01 postfix/smtpd\[6919\]: warning: unknown\[45.125.65.35\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 16 15:44:37 srv01 postfix/smtpd\[2877\]: warning: unknown\[45.125.65.35\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-04-16 21:47:00 |
| 193.112.18.55 | attack | Unauthorized SSH login attempts |
2020-04-16 21:30:56 |
| 192.144.187.153 | attack | Brute-force attempt banned |
2020-04-16 21:54:06 |
| 103.254.120.222 | attackspam | Apr 16 14:51:53 h2779839 sshd[31648]: Invalid user git from 103.254.120.222 port 38548 Apr 16 14:51:53 h2779839 sshd[31648]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.254.120.222 Apr 16 14:51:53 h2779839 sshd[31648]: Invalid user git from 103.254.120.222 port 38548 Apr 16 14:51:55 h2779839 sshd[31648]: Failed password for invalid user git from 103.254.120.222 port 38548 ssh2 Apr 16 14:56:39 h2779839 sshd[31860]: Invalid user userftp from 103.254.120.222 port 48664 Apr 16 14:56:39 h2779839 sshd[31860]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.254.120.222 Apr 16 14:56:39 h2779839 sshd[31860]: Invalid user userftp from 103.254.120.222 port 48664 Apr 16 14:56:41 h2779839 sshd[31860]: Failed password for invalid user userftp from 103.254.120.222 port 48664 ssh2 Apr 16 15:01:29 h2779839 sshd[31917]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.25 ... |
2020-04-16 22:05:37 |
| 45.14.148.88 | attackspambots | (sshd) Failed SSH login from 45.14.148.88 (RO/Romania/-): 5 in the last 3600 secs |
2020-04-16 21:34:25 |
| 85.103.104.236 | attackspambots | TR_as9121-mnt_<177>1587039272 [1:2010935:3] ET SCAN Suspicious inbound to MSSQL port 1433 [Classification: Potentially Bad Traffic] [Priority: 2]: |
2020-04-16 22:04:08 |
| 180.94.154.3 | attack | 1587039283 - 04/16/2020 14:14:43 Host: 180.94.154.3/180.94.154.3 Port: 445 TCP Blocked |
2020-04-16 21:51:40 |
| 185.238.160.166 | attack | Banned by Fail2Ban. |
2020-04-16 22:02:44 |
| 87.204.149.202 | attack | Apr 16 12:14:48 sshgateway sshd\[9472\]: Invalid user oracle from 87.204.149.202 Apr 16 12:14:48 sshgateway sshd\[9472\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.204.149.202 Apr 16 12:14:50 sshgateway sshd\[9472\]: Failed password for invalid user oracle from 87.204.149.202 port 49230 ssh2 |
2020-04-16 21:42:28 |
| 37.187.54.45 | attackspam | Apr 16 15:17:44 vpn01 sshd[30828]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.187.54.45 Apr 16 15:17:46 vpn01 sshd[30828]: Failed password for invalid user admin from 37.187.54.45 port 55820 ssh2 ... |
2020-04-16 21:52:28 |
| 103.11.117.116 | attackbotsspam | Bruteforce detected by fail2ban |
2020-04-16 21:23:28 |
| 118.96.45.212 | attackspam | Port scan on 1 port(s): 25565 |
2020-04-16 21:35:26 |
| 169.57.189.76 | attackbotsspam | $f2bV_matches |
2020-04-16 21:45:35 |
| 107.174.231.173 | attack | (From eric@talkwithwebvisitor.com) Good day, My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations What for? Part of my job is to check out websites and the work you’ve done with plinkechiropractic.com definitely stands out. It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality. There is, however, a catch… more accurately, a question… So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? More importantly, how do you make a connection with that person? Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind. Here’s a way to create INSTANT engagement that you may not have known about… Talk With Web Visitor is a software widget that’s works on your site, ready to capture |
2020-04-16 21:48:15 |
| 45.55.222.162 | attackbots | Apr 16 07:24:02 server1 sshd\[15060\]: Invalid user virus from 45.55.222.162 Apr 16 07:24:02 server1 sshd\[15060\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.222.162 Apr 16 07:24:04 server1 sshd\[15060\]: Failed password for invalid user virus from 45.55.222.162 port 43212 ssh2 Apr 16 07:25:32 server1 sshd\[15489\]: Invalid user cj from 45.55.222.162 Apr 16 07:25:32 server1 sshd\[15489\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.222.162 ... |
2020-04-16 21:39:13 |