City: unknown
Region: unknown
Country: China
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 182.42.148.214
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 58129
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;182.42.148.214. IN A
;; AUTHORITY SECTION:
. 596 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2024022802 1800 900 604800 86400
;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 29 08:35:06 CST 2024
;; MSG SIZE rcvd: 107Host 214.148.42.182.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 214.148.42.182.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 154.209.253.241 | attack | fail2ban |
2020-10-03 12:29:08 |
| 191.23.113.164 | attackbotsspam | Oct 2 22:34:06 mx01 sshd[15750]: reveeclipse mapping checking getaddrinfo for 191-23-113-164.user.vivozap.com.br [191.23.113.164] failed - POSSIBLE BREAK-IN ATTEMPT! Oct 2 22:34:06 mx01 sshd[15750]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.23.113.164 user=r.r Oct 2 22:34:08 mx01 sshd[15750]: Failed password for r.r from 191.23.113.164 port 53720 ssh2 Oct 2 22:34:08 mx01 sshd[15750]: Received disconnect from 191.23.113.164: 11: Bye Bye [preauth] Oct 2 22:34:10 mx01 sshd[15754]: reveeclipse mapping checking getaddrinfo for 191-23-113-164.user.vivozap.com.br [191.23.113.164] failed - POSSIBLE BREAK-IN ATTEMPT! Oct 2 22:34:11 mx01 sshd[15754]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.23.113.164 user=r.r Oct 2 22:34:12 mx01 sshd[15754]: Failed password for r.r from 191.23.113.164 port 53804 ssh2 Oct 2 22:34:12 mx01 sshd[15754]: Received disconnect from 191.23.113.1........ ------------------------------- |
2020-10-03 07:17:37 |
| 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-03 12:21:30 |
| 112.238.151.20 | attackbots | REQUESTED PAGE: /GponForm/diag_Form?images/ |
2020-10-03 07:18:38 |
| 129.211.73.2 | attackspambots | 3x Failed Password |
2020-10-03 12:27:48 |
| 199.187.211.101 | attackbotsspam | 4,12-01/02 [bc00/m26] PostRequest-Spammer scoring: paris |
2020-10-03 12:03:31 |
| 1.255.48.197 | attack | (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-03 12:17:46 |
| 159.65.1.41 | attackbotsspam | Oct 3 03:19:54 abendstille sshd\[756\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.1.41 user=root Oct 3 03:19:56 abendstille sshd\[756\]: Failed password for root from 159.65.1.41 port 36392 ssh2 Oct 3 03:24:44 abendstille sshd\[5242\]: Invalid user postgres from 159.65.1.41 Oct 3 03:24:44 abendstille sshd\[5242\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.1.41 Oct 3 03:24:46 abendstille sshd\[5242\]: Failed password for invalid user postgres from 159.65.1.41 port 44072 ssh2 ... |
2020-10-03 12:25:27 |
| 27.151.115.81 | attackbots | port scan and connect, tcp 1433 (ms-sql-s) |
2020-10-03 12:13:57 |
| 152.136.97.217 | attackspam | Oct 2 20:24:59 Server1 sshd[17048]: Invalid user wellington from 152.136.97.217 port 52798 Oct 2 20:24:59 Server1 sshd[17048]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.97.217 Oct 2 20:25:01 Server1 sshd[17048]: Failed password for invalid user wellington from 152.136.97.217 port 52798 ssh2 Oct 2 20:25:01 Server1 sshd[17048]: Connection closed by invalid user wellington 152.136.97.217 port 52798 [preauth] Oct 2 20:25:02 Server1 sshd[17050]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.97.217 user=r.r ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=152.136.97.217 |
2020-10-03 12:10:48 |
| 46.101.5.144 | attack | 20 attempts against mh-ssh on soil |
2020-10-03 07:21:27 |
| 60.174.248.244 | attackspambots | Fail2Ban Ban Triggered |
2020-10-03 12:26:41 |
| 195.133.56.185 | attack | (mod_security) mod_security (id:210730) triggered by 195.133.56.185 (CZ/Czechia/-): 5 in the last 300 secs |
2020-10-03 12:22:32 |
| 81.69.177.253 | attackbots | Oct 3 05:08:56 eventyay sshd[24944]: Failed password for root from 81.69.177.253 port 40404 ssh2 Oct 3 05:12:11 eventyay sshd[25010]: Failed password for root from 81.69.177.253 port 52592 ssh2 Oct 3 05:15:26 eventyay sshd[25091]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.69.177.253 ... |
2020-10-03 12:07:39 |
| 40.77.167.237 | attackbotsspam | caw-Joomla User : try to access forms... |
2020-10-03 12:02:46 |