City: unknown
Region: unknown
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.21.234.59
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24356
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.21.234.59. IN A
;; AUTHORITY SECTION:
. 470 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022021700 1800 900 604800 86400
;; Query time: 28 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 02:18:10 CST 2022
;; MSG SIZE rcvd: 106Host 59.234.21.104.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 59.234.21.104.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 180.113.86.177 | attackspam | Apr 1 10:38:13 IngegnereFirenze sshd[11784]: User root from 180.113.86.177 not allowed because not listed in AllowUsers ... |
2020-04-01 18:38:38 |
| 140.246.245.144 | attackspambots | Apr 1 05:21:56 ns392434 sshd[31314]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.246.245.144 user=root Apr 1 05:21:58 ns392434 sshd[31314]: Failed password for root from 140.246.245.144 port 37654 ssh2 Apr 1 05:38:27 ns392434 sshd[789]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.246.245.144 user=root Apr 1 05:38:30 ns392434 sshd[789]: Failed password for root from 140.246.245.144 port 49366 ssh2 Apr 1 05:43:30 ns392434 sshd[1689]: Invalid user dh from 140.246.245.144 port 44000 Apr 1 05:43:30 ns392434 sshd[1689]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.246.245.144 Apr 1 05:43:30 ns392434 sshd[1689]: Invalid user dh from 140.246.245.144 port 44000 Apr 1 05:43:33 ns392434 sshd[1689]: Failed password for invalid user dh from 140.246.245.144 port 44000 ssh2 Apr 1 05:48:28 ns392434 sshd[2310]: Invalid user jyang from 140.246.245.144 port 38632 |
2020-04-01 18:14:09 |
| 110.93.200.118 | attack | Apr 1 08:58:22 icinga sshd[40678]: Failed password for root from 110.93.200.118 port 16740 ssh2 Apr 1 09:06:28 icinga sshd[53281]: Failed password for root from 110.93.200.118 port 31770 ssh2 ... |
2020-04-01 18:29:19 |
| 92.222.78.178 | attackbots | Apr 1 12:22:00 mail sshd[2980]: Invalid user user from 92.222.78.178 Apr 1 12:22:00 mail sshd[2980]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.222.78.178 Apr 1 12:22:00 mail sshd[2980]: Invalid user user from 92.222.78.178 Apr 1 12:22:03 mail sshd[2980]: Failed password for invalid user user from 92.222.78.178 port 46200 ssh2 Apr 1 12:35:49 mail sshd[24414]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.222.78.178 user=root Apr 1 12:35:50 mail sshd[24414]: Failed password for root from 92.222.78.178 port 34826 ssh2 ... |
2020-04-01 18:42:28 |
| 103.250.136.179 | attack | 1585712853 - 04/01/2020 05:47:33 Host: 103.250.136.179/103.250.136.179 Port: 445 TCP Blocked |
2020-04-01 18:52:05 |
| 180.241.249.2 | attackbots | Unauthorized connection attempt detected from IP address 180.241.249.2 to port 445 |
2020-04-01 18:24:28 |
| 168.1.124.238 | attackbots | Mar 30 18:45:25 giraffe sshd[12047]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.1.124.238 user=r.r Mar 30 18:45:26 giraffe sshd[12047]: Failed password for r.r from 168.1.124.238 port 47042 ssh2 Mar 30 18:45:27 giraffe sshd[12047]: Received disconnect from 168.1.124.238 port 47042:11: Bye Bye [preauth] Mar 30 18:45:27 giraffe sshd[12047]: Disconnected from 168.1.124.238 port 47042 [preauth] Mar 30 18:52:26 giraffe sshd[12307]: Invalid user ll from 168.1.124.238 Mar 30 18:52:26 giraffe sshd[12307]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.1.124.238 Mar 30 18:52:28 giraffe sshd[12307]: Failed password for invalid user ll from 168.1.124.238 port 53850 ssh2 Mar 30 18:52:29 giraffe sshd[12307]: Received disconnect from 168.1.124.238 port 53850:11: Bye Bye [preauth] Mar 30 18:52:29 giraffe sshd[12307]: Disconnected from 168.1.124.238 port 53850 [preauth] ........ ----------------------------------------------- htt |
2020-04-01 18:37:39 |
| 129.226.67.136 | attack | (sshd) Failed SSH login from 129.226.67.136 (SG/Singapore/-): 5 in the last 3600 secs |
2020-04-01 18:27:23 |
| 178.32.218.192 | attackspambots | Apr 1 08:51:41 vlre-nyc-1 sshd\[1280\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.32.218.192 user=root Apr 1 08:51:43 vlre-nyc-1 sshd\[1280\]: Failed password for root from 178.32.218.192 port 44151 ssh2 Apr 1 08:55:27 vlre-nyc-1 sshd\[1378\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.32.218.192 user=root Apr 1 08:55:29 vlre-nyc-1 sshd\[1378\]: Failed password for root from 178.32.218.192 port 50601 ssh2 Apr 1 08:59:15 vlre-nyc-1 sshd\[1463\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.32.218.192 user=root ... |
2020-04-01 18:40:28 |
| 64.94.208.221 | attack | (From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across drjenniferbrandon.com a few minutes ago. Looks great… but now what? By that I mean, when someone like me finds your website – either through Search or just bouncing around – what happens next? Do you get a lot of leads from your site, or at least enough to make you happy? Honestly, most business websites fall a bit short when it comes to generating paying customers. Studies show that 70% of a site’s visitors disappear and are gone forever after just a moment. Here’s an idea… How about making it really EASY for every visitor who shows up to get a personal phone call you as soon as they hit your site… You can – Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number. It signals you the moment they let you know they’re interested – so that you can talk to that lead while they’re literally looking over your site. CLICK HERE http://www |
2020-04-01 18:45:30 |
| 142.93.15.179 | attackbotsspam | Apr 1 12:36:18 vmd17057 sshd[20527]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.15.179 Apr 1 12:36:20 vmd17057 sshd[20527]: Failed password for invalid user hhan from 142.93.15.179 port 53474 ssh2 ... |
2020-04-01 18:51:14 |
| 106.13.63.120 | attackspambots | Apr 1 06:22:57 roki sshd[12078]: Invalid user db1 from 106.13.63.120 Apr 1 06:22:58 roki sshd[12078]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.63.120 Apr 1 06:22:59 roki sshd[12078]: Failed password for invalid user db1 from 106.13.63.120 port 57620 ssh2 Apr 1 06:37:32 roki sshd[14811]: Invalid user chenyang from 106.13.63.120 Apr 1 06:37:32 roki sshd[14811]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.63.120 ... |
2020-04-01 18:41:51 |
| 70.65.174.69 | attackspam | Apr 1 11:11:39 vpn01 sshd[23461]: Failed password for root from 70.65.174.69 port 55376 ssh2 ... |
2020-04-01 18:17:01 |
| 115.204.64.34 | attack | Unauthorised access (Apr 1) SRC=115.204.64.34 LEN=40 TTL=52 ID=51816 TCP DPT=8080 WINDOW=22725 SYN Unauthorised access (Mar 31) SRC=115.204.64.34 LEN=40 TTL=52 ID=7562 TCP DPT=8080 WINDOW=7373 SYN Unauthorised access (Mar 31) SRC=115.204.64.34 LEN=40 TTL=52 ID=49646 TCP DPT=8080 WINDOW=7373 SYN |
2020-04-01 18:26:25 |
| 123.206.190.82 | attackbotsspam | Apr 1 12:10:34 silence02 sshd[21632]: Failed password for root from 123.206.190.82 port 55774 ssh2 Apr 1 12:12:44 silence02 sshd[21849]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.206.190.82 Apr 1 12:12:47 silence02 sshd[21849]: Failed password for invalid user hamamoto from 123.206.190.82 port 51636 ssh2 |
2020-04-01 18:16:25 |