City: unknown
Region: unknown
Country: None
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 157.19.3.216
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 33961
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;157.19.3.216. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021900 1800 900 604800 86400
;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 01:29:02 CST 2025
;; MSG SIZE rcvd: 105
Host 216.3.19.157.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 216.3.19.157.in-addr.arpa: NXDOMAIN
IP | Type | Details | Datetime |
---|---|---|---|
199.187.211.101 | attackbots | 4,12-01/02 [bc00/m26] PostRequest-Spammer scoring: paris |
2020-10-04 04:31:13 |
131.196.216.39 | attack | Oct 3 22:31:39 vm1 sshd[6280]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=131.196.216.39 Oct 3 22:31:42 vm1 sshd[6280]: Failed password for invalid user tams from 131.196.216.39 port 42392 ssh2 ... |
2020-10-04 04:39:21 |
190.156.238.155 | attackspam | SSH brute-force attack detected from [190.156.238.155] |
2020-10-04 04:29:10 |
170.0.160.165 | attackspam | Oct 2 16:27:05 cumulus sshd[22622]: Did not receive identification string from 170.0.160.165 port 56894 Oct 2 16:27:05 cumulus sshd[22624]: Did not receive identification string from 170.0.160.165 port 56901 Oct 2 16:27:05 cumulus sshd[22623]: Did not receive identification string from 170.0.160.165 port 56900 Oct 2 16:27:06 cumulus sshd[22625]: Did not receive identification string from 170.0.160.165 port 57113 Oct 2 16:27:06 cumulus sshd[22626]: Did not receive identification string from 170.0.160.165 port 57110 Oct 2 16:27:06 cumulus sshd[22627]: Did not receive identification string from 170.0.160.165 port 57122 Oct 2 16:27:06 cumulus sshd[22628]: Did not receive identification string from 170.0.160.165 port 57151 Oct 2 16:27:08 cumulus sshd[22631]: Invalid user guest from 170.0.160.165 port 57170 Oct 2 16:27:08 cumulus sshd[22634]: Invalid user guest from 170.0.160.165 port 57173 Oct 2 16:27:08 cumulus sshd[22632]: Invalid user guest from 170.0.160.165 po........ ------------------------------- |
2020-10-04 04:43:49 |
104.131.110.155 | attack | web-1 [ssh] SSH Attack |
2020-10-04 04:44:08 |
182.126.87.169 | attack | DATE:2020-10-02 22:38:55, IP:182.126.87.169, PORT:telnet Telnet brute force auth on honeypot server (epe-honey1-hq) |
2020-10-04 04:49:19 |
112.238.151.20 | attackbotsspam | REQUESTED PAGE: /GponForm/diag_Form?images/ |
2020-10-04 05:02:34 |
175.137.104.57 | attack | Lines containing failures of 175.137.104.57 (max 1000) Oct 2 22:27:37 srv sshd[98150]: Connection closed by 175.137.104.57 port 61298 Oct 2 22:27:40 srv sshd[98151]: Invalid user 666666 from 175.137.104.57 port 61479 Oct 2 22:27:40 srv sshd[98151]: Connection closed by invalid user 666666 175.137.104.57 port 61479 [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=175.137.104.57 |
2020-10-04 04:47:51 |
200.140.234.142 | attackbotsspam | 2020-10-03T21:40:46.491037hostname sshd[62440]: Failed password for root from 200.140.234.142 port 55452 ssh2 ... |
2020-10-04 05:03:39 |
89.233.112.6 | attack |
|
2020-10-04 04:41:15 |
167.172.36.232 | attackbots | Oct 3 22:02:05 icinga sshd[46373]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.36.232 Oct 3 22:02:07 icinga sshd[46373]: Failed password for invalid user shen from 167.172.36.232 port 50120 ssh2 Oct 3 22:14:30 icinga sshd[1592]: Failed password for root from 167.172.36.232 port 38420 ssh2 ... |
2020-10-04 04:38:11 |
1.255.48.197 | attackspambots | (From annabelle@merchantpay.top) I have a quick question about working with your business. Like most business owners you just want to survive through to 2021. In order for that to happen you need to save every dollar possible right? This is an honest question, would you continue with the high credit card processing fees if there was another way? New laws are on your side. Test this newly released card processing model this October - just send a phone number and we'll call. $24.99/mo Flat Fee Credit Card Processing (Unlimited) 1) As a small business owner accepting credit/debit, recently passed State Laws are on your side. - Were you aware? New state regulations now in effect, the law was successfully passed in 46 states - effective since August 2019. Since that date you shouldn't be paying above 0.75% Credit Card Processing Fees. 2) You're legally able to demand this new option. Bottom Line: Your processor isn't telling you everything. Why are they hiding the lower fee options? We repre |
2020-10-04 04:44:26 |
101.133.174.69 | attack | 101.133.174.69 - - [03/Oct/2020:19:45:11 +0100] "POST /wp-login.php HTTP/1.1" 200 2208 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 101.133.174.69 - - [03/Oct/2020:19:45:14 +0100] "POST /wp-login.php HTTP/1.1" 200 2205 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 101.133.174.69 - - [03/Oct/2020:19:45:15 +0100] "POST /xmlrpc.php HTTP/1.1" 200 247 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" ... |
2020-10-04 04:59:58 |
156.208.229.118 | attackbotsspam | Telnet Server BruteForce Attack |
2020-10-04 04:27:11 |
27.151.115.81 | attackspambots | [MK-VM2] Blocked by UFW |
2020-10-04 04:41:39 |