City: unknown
Region: unknown
Country: None
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 53.68.157.21
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39721
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;53.68.157.21. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021901 1800 900 604800 86400
;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 02:10:53 CST 2025
;; MSG SIZE rcvd: 105Host 21.157.68.53.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 21.157.68.53.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 5.157.15.158 | attack | Unauthorized access detected from black listed ip! |
2020-03-31 12:21:34 |
| 177.131.146.254 | attack | Mar 31 04:53:28 yesfletchmain sshd\[24606\]: User root from 177.131.146.254 not allowed because not listed in AllowUsers Mar 31 04:53:28 yesfletchmain sshd\[24606\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.131.146.254 user=root Mar 31 04:53:30 yesfletchmain sshd\[24606\]: Failed password for invalid user root from 177.131.146.254 port 57100 ssh2 Mar 31 04:56:05 yesfletchmain sshd\[24711\]: User root from 177.131.146.254 not allowed because not listed in AllowUsers Mar 31 04:56:05 yesfletchmain sshd\[24711\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.131.146.254 user=root ... |
2020-03-31 12:07:21 |
| 51.91.122.150 | attackspam | $f2bV_matches |
2020-03-31 12:18:13 |
| 109.238.187.90 | attackbots | Unauthorized connection attempt from IP address 109.238.187.90 on Port 445(SMB) |
2020-03-31 09:41:25 |
| 185.176.27.90 | attackspam | Mar 31 03:33:13 debian-2gb-nbg1-2 kernel: \[7877448.498922\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.90 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=22226 PROTO=TCP SPT=44329 DPT=8320 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-03-31 09:45:31 |
| 41.93.32.113 | attackspam | (sshd) Failed SSH login from 41.93.32.113 (TZ/Tanzania/-/-/portal.ternet.or.tz/[AS37182 TERNET]): 1 in the last 3600 secs |
2020-03-31 12:29:34 |
| 42.3.51.30 | attackbots | $f2bV_matches |
2020-03-31 12:10:52 |
| 35.241.122.141 | attackspambots | Mar 31 05:56:09 haigwepa sshd[28318]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.241.122.141 Mar 31 05:56:11 haigwepa sshd[28318]: Failed password for invalid user ses-user from 35.241.122.141 port 59176 ssh2 ... |
2020-03-31 12:04:24 |
| 138.128.9.91 | attack | (From webmasterdesigners4u@gmail.com) Greetings! I'm emailing to let you know that I have completed several important SEO tests on your website. The information and data I have retrieved shows how Google and other search engines like Bing are indexing and ranking your website. From what I see here, things can definitely be better. I'm pretty sure you will agree, too. Would you like to know how you can get more unique visits in your website from major search engines like Google? Having your website optimized for search engines like Google is crucial for you to be ahead of your competitors. As of now, you're most likely missing out on a lot of business opportunities since potential clients are having a difficult time finding you. I'm an expert online marketing specialist who focuses in making sure my client's website appears on the first page of search engine results. With my long years of experience in this industry, I can tell you that being on the first page will surely increase your profits. If y |
2020-03-31 12:02:01 |
| 41.234.66.22 | attack | Mar 31 06:55:30 server2 sshd\[3338\]: User root from 41.234.66.22 not allowed because not listed in AllowUsers Mar 31 06:55:43 server2 sshd\[3342\]: User root from 41.234.66.22 not allowed because not listed in AllowUsers Mar 31 06:55:56 server2 sshd\[3345\]: Invalid user user from 41.234.66.22 Mar 31 06:56:10 server2 sshd\[3373\]: Invalid user testuser from 41.234.66.22 Mar 31 06:56:24 server2 sshd\[3380\]: Invalid user ftpadmin from 41.234.66.22 Mar 31 06:56:40 server2 sshd\[3385\]: Invalid user jira from 41.234.66.22 |
2020-03-31 12:09:11 |
| 92.118.37.53 | attackbotsspam | Mar 31 06:15:16 debian-2gb-nbg1-2 kernel: \[7887171.299182\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=92.118.37.53 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=25209 PROTO=TCP SPT=49570 DPT=23389 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-03-31 12:33:01 |
| 218.88.232.201 | attackspambots | IP reached maximum auth failures |
2020-03-31 12:11:22 |
| 152.136.142.30 | attack | Mar 31 04:49:56 sigma sshd\[3502\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.142.30 user=rootMar 31 04:55:44 sigma sshd\[3603\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.142.30 user=root ... |
2020-03-31 12:20:24 |
| 175.236.13.20 | attackspambots | port |
2020-03-31 12:13:10 |
| 222.186.42.137 | attackbotsspam | Mar 31 03:27:56 vmd26974 sshd[4699]: Failed password for root from 222.186.42.137 port 29960 ssh2 Mar 31 03:27:58 vmd26974 sshd[4699]: Failed password for root from 222.186.42.137 port 29960 ssh2 ... |
2020-03-31 09:44:38 |