City: unknown
Region: unknown
Country: IANA Special-Purpose Address
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 245.56.109.21
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 43848
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;245.56.109.21. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020300 1800 900 604800 86400
;; Query time: 30 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 03 17:12:54 CST 2025
;; MSG SIZE rcvd: 106Host 21.109.56.245.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 21.109.56.245.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 46.105.75.105 | attack | $f2bV_matches |
2020-10-03 12:24:36 |
| 112.238.151.20 | attackbotsspam | REQUESTED PAGE: /GponForm/diag_Form?images/ |
2020-10-03 12:35:36 |
| 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 |
| 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 |
| 45.67.234.168 | attackspambots | From retorno-leonir.tsi=toptec.net.br@praticoerapido.live Fri Oct 02 13:41:00 2020 Received: from [45.67.234.168] (port=58989 helo=01host234168.praticoerapido.live) |
2020-10-03 12:42:33 |
| 154.209.253.241 | attack | fail2ban |
2020-10-03 12:29:08 |
| 190.36.156.72 | attackspam | Unauthorised access (Oct 2) SRC=190.36.156.72 LEN=52 TTL=116 ID=7606 DF TCP DPT=445 WINDOW=8192 SYN |
2020-10-03 12:28:39 |
| 160.124.103.55 | attack | Oct 3 05:28:26 abendstille sshd\[29296\]: Invalid user service from 160.124.103.55 Oct 3 05:28:26 abendstille sshd\[29296\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=160.124.103.55 Oct 3 05:28:29 abendstille sshd\[29296\]: Failed password for invalid user service from 160.124.103.55 port 36864 ssh2 Oct 3 05:31:38 abendstille sshd\[32475\]: Invalid user josh from 160.124.103.55 Oct 3 05:31:38 abendstille sshd\[32475\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=160.124.103.55 ... |
2020-10-03 12:03:43 |
| 46.101.7.41 | attackbotsspam | 20 attempts against mh-ssh on air |
2020-10-03 12:35:51 |
| 122.51.252.45 | attackbotsspam | SSH Invalid Login |
2020-10-03 12:38:11 |
| 183.166.170.133 | attackspam | Oct 2 22:30:45 srv01 postfix/smtpd\[1755\]: warning: unknown\[183.166.170.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 2 22:34:11 srv01 postfix/smtpd\[6490\]: warning: unknown\[183.166.170.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 2 22:37:37 srv01 postfix/smtpd\[11183\]: warning: unknown\[183.166.170.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 2 22:41:03 srv01 postfix/smtpd\[11183\]: warning: unknown\[183.166.170.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 2 22:41:14 srv01 postfix/smtpd\[11183\]: warning: unknown\[183.166.170.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-10-03 12:28:54 |
| 222.186.42.57 | attack | Oct 3 00:06:59 plusreed sshd[8332]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.57 user=root Oct 3 00:07:00 plusreed sshd[8332]: Failed password for root from 222.186.42.57 port 63305 ssh2 ... |
2020-10-03 12:16:02 |
| 211.220.27.191 | attackbotsspam | Oct 3 08:54:56 web1 sshd[804]: Invalid user kevin from 211.220.27.191 port 32826 Oct 3 08:54:56 web1 sshd[804]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.220.27.191 Oct 3 08:54:56 web1 sshd[804]: Invalid user kevin from 211.220.27.191 port 32826 Oct 3 08:54:58 web1 sshd[804]: Failed password for invalid user kevin from 211.220.27.191 port 32826 ssh2 Oct 3 09:01:15 web1 sshd[3022]: Invalid user postgres from 211.220.27.191 port 59730 Oct 3 09:01:15 web1 sshd[3022]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.220.27.191 Oct 3 09:01:15 web1 sshd[3022]: Invalid user postgres from 211.220.27.191 port 59730 Oct 3 09:01:17 web1 sshd[3022]: Failed password for invalid user postgres from 211.220.27.191 port 59730 ssh2 Oct 3 09:04:03 web1 sshd[3895]: Invalid user arkserver from 211.220.27.191 port 59532 ... |
2020-10-03 12:14:27 |
| 190.167.244.87 | attack | Lines containing failures of 190.167.244.87 Oct 2 22:27:15 shared04 sshd[2191]: Did not receive identification string from 190.167.244.87 port 3192 Oct 2 22:27:17 shared04 sshd[2195]: Invalid user user1 from 190.167.244.87 port 3994 Oct 2 22:27:17 shared04 sshd[2195]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.167.244.87 Oct 2 22:27:19 shared04 sshd[2195]: Failed password for invalid user user1 from 190.167.244.87 port 3994 ssh2 Oct 2 22:27:20 shared04 sshd[2195]: Connection closed by invalid user user1 190.167.244.87 port 3994 [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=190.167.244.87 |
2020-10-03 12:18:59 |
| 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 |