City: unknown
Region: unknown
Country: Germany
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.14.242.120
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 18307
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;139.14.242.120. IN A
;; AUTHORITY SECTION:
. 444 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022122700 1800 900 604800 86400
;; Query time: 174 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Dec 27 22:31:47 CST 2022
;; MSG SIZE rcvd: 107Host 120.242.14.139.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 120.242.14.139.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 103.84.175.197 | attackbotsspam | CMS (WordPress or Joomla) login attempt. |
2020-10-04 03:56:11 |
| 212.70.149.36 | attack | Oct 3 21:54:37 s1 postfix/submission/smtpd\[22075\]: warning: unknown\[212.70.149.36\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 3 21:54:55 s1 postfix/submission/smtpd\[22183\]: warning: unknown\[212.70.149.36\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 3 21:55:13 s1 postfix/submission/smtpd\[22075\]: warning: unknown\[212.70.149.36\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 3 21:55:34 s1 postfix/submission/smtpd\[22183\]: warning: unknown\[212.70.149.36\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 3 21:56:02 s1 postfix/submission/smtpd\[22075\]: warning: unknown\[212.70.149.36\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 3 21:56:21 s1 postfix/submission/smtpd\[25379\]: warning: unknown\[212.70.149.36\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 3 21:56:44 s1 postfix/submission/smtpd\[22183\]: warning: unknown\[212.70.149.36\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 3 21:57:10 s1 postfix/submission/smtpd\[25379\]: warning: unknown\[ |
2020-10-04 04:02:38 |
| 106.13.189.172 | attackbotsspam | SSH Login Bruteforce |
2020-10-04 04:11:54 |
| 118.70.170.120 | attack | 2020-10-02T11:23:46.967259hostname sshd[27452]: Failed password for invalid user signature from 118.70.170.120 port 49780 ssh2 ... |
2020-10-04 03:45:13 |
| 117.50.107.175 | attack | (sshd) Failed SSH login from 117.50.107.175 (CN/China/-): 5 in the last 3600 secs |
2020-10-04 03:54:41 |
| 122.51.194.254 | attackbotsspam | Oct 3 20:38:44 nextcloud sshd\[11664\]: Invalid user cmsuser from 122.51.194.254 Oct 3 20:38:44 nextcloud sshd\[11664\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.194.254 Oct 3 20:38:46 nextcloud sshd\[11664\]: Failed password for invalid user cmsuser from 122.51.194.254 port 43060 ssh2 |
2020-10-04 03:59:24 |
| 45.142.120.39 | attackspambots | Oct 3 21:53:41 relay postfix/smtpd\[15760\]: warning: unknown\[45.142.120.39\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 3 21:53:56 relay postfix/smtpd\[14135\]: warning: unknown\[45.142.120.39\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 3 21:53:59 relay postfix/smtpd\[14088\]: warning: unknown\[45.142.120.39\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 3 21:54:01 relay postfix/smtpd\[14150\]: warning: unknown\[45.142.120.39\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 3 21:54:18 relay postfix/smtpd\[14150\]: warning: unknown\[45.142.120.39\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 3 21:54:18 relay postfix/smtpd\[16681\]: warning: unknown\[45.142.120.39\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-10-04 04:03:18 |
| 106.75.247.206 | attackspam | Oct 3 08:50:39 php1 sshd\[30929\]: Invalid user user2 from 106.75.247.206 Oct 3 08:50:39 php1 sshd\[30929\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.247.206 Oct 3 08:50:42 php1 sshd\[30929\]: Failed password for invalid user user2 from 106.75.247.206 port 35762 ssh2 Oct 3 08:53:05 php1 sshd\[31085\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.247.206 user=root Oct 3 08:53:07 php1 sshd\[31085\]: Failed password for root from 106.75.247.206 port 44178 ssh2 |
2020-10-04 03:56:42 |
| 116.68.160.114 | attackbotsspam | $f2bV_matches |
2020-10-04 03:46:16 |
| 46.187.38.244 | attackspam |
|
2020-10-04 03:53:04 |
| 185.26.28.232 | attackspam | 2020-10-03T09:13:47.501799abusebot.cloudsearch.cf sshd[24351]: Invalid user rodrigo from 185.26.28.232 port 42166 2020-10-03T09:13:47.509737abusebot.cloudsearch.cf sshd[24351]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.26.28.232 2020-10-03T09:13:47.501799abusebot.cloudsearch.cf sshd[24351]: Invalid user rodrigo from 185.26.28.232 port 42166 2020-10-03T09:13:49.702662abusebot.cloudsearch.cf sshd[24351]: Failed password for invalid user rodrigo from 185.26.28.232 port 42166 ssh2 2020-10-03T09:17:36.205816abusebot.cloudsearch.cf sshd[24430]: Invalid user deploy from 185.26.28.232 port 49822 2020-10-03T09:17:36.212391abusebot.cloudsearch.cf sshd[24430]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.26.28.232 2020-10-03T09:17:36.205816abusebot.cloudsearch.cf sshd[24430]: Invalid user deploy from 185.26.28.232 port 49822 2020-10-03T09:17:38.510372abusebot.cloudsearch.cf sshd[24430]: Failed passwor ... |
2020-10-04 04:13:37 |
| 190.85.163.46 | attack | 2020-10-03T10:07:13.993947shield sshd\[19806\]: Invalid user ansible from 190.85.163.46 port 49765 2020-10-03T10:07:14.005630shield sshd\[19806\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.85.163.46 2020-10-03T10:07:16.468801shield sshd\[19806\]: Failed password for invalid user ansible from 190.85.163.46 port 49765 ssh2 2020-10-03T10:11:28.705758shield sshd\[20209\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.85.163.46 user=root 2020-10-03T10:11:30.366648shield sshd\[20209\]: Failed password for root from 190.85.163.46 port 53818 ssh2 |
2020-10-04 03:40:35 |
| 63.80.187.59 | attackspam | E-Mail Spam (RBL) [REJECTED] |
2020-10-04 03:38:51 |
| 114.4.227.194 | attackbotsspam | Oct 3 18:57:06 scw-focused-cartwright sshd[32121]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.4.227.194 Oct 3 18:57:08 scw-focused-cartwright sshd[32121]: Failed password for invalid user test from 114.4.227.194 port 55182 ssh2 |
2020-10-04 04:01:20 |
| 207.244.252.113 | attackspam | (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:00:38 |