City: Odesa
Region: Odesa
Country: Ukraine
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 195.138.184.90
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10558
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;195.138.184.90. IN A
;; AUTHORITY SECTION:
. 402 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2023012200 1800 900 604800 86400
;; Query time: 73 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 22 23:36:41 CST 2023
;; MSG SIZE rcvd: 107Host 90.184.138.195.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 90.184.138.195.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 23.108.48.44 | attack | (From eric@talkwithcustomer.com) Hey, You have a website naturalhealthdcs.com, right? Of course you do. I am looking at your website now. It gets traffic every day – that you’re probably spending $2 / $4 / $10 or more a click to get. Not including all of the work you put into creating social media, videos, blog posts, emails, and so on. So you’re investing seriously in getting people to that site. But how’s it working? Great? Okay? Not so much? If that answer could be better, then it’s likely you’re putting a lot of time, effort, and money into an approach that’s not paying off like it should. Now… imagine doubling your lead conversion in just minutes… In fact, I’ll go even better. You could actually get up to 100X more conversions! I’m not making this up. As Chris Smith, best-selling author of The Conversion Code says: Speed is essential - there is a 100x decrease in Leads when a Lead is contacted within 14 minutes vs being contacted within 5 minutes. He’s backed up by a st |
2019-11-04 21:05:08 |
| 36.99.141.211 | attackbotsspam | $f2bV_matches |
2019-11-04 20:43:53 |
| 216.218.206.125 | attack | firewall-block, port(s): 1434/udp |
2019-11-04 20:50:37 |
| 41.33.178.202 | attackbots | Nov 4 07:35:37 thevastnessof sshd[31343]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.33.178.202 ... |
2019-11-04 20:35:15 |
| 129.28.142.81 | attack | $f2bV_matches |
2019-11-04 20:26:33 |
| 59.92.216.207 | attack | Unauthorised access (Nov 4) SRC=59.92.216.207 LEN=52 PREC=0x20 TTL=110 ID=10611 DF TCP DPT=445 WINDOW=8192 SYN Unauthorised access (Nov 4) SRC=59.92.216.207 LEN=52 PREC=0x20 TTL=110 ID=7081 DF TCP DPT=445 WINDOW=8192 SYN |
2019-11-04 20:57:44 |
| 80.188.112.168 | attackspambots | postfix (unknown user, SPF fail or relay access denied) |
2019-11-04 20:59:28 |
| 195.228.22.54 | attackspam | web-1 [ssh_2] SSH Attack |
2019-11-04 21:08:35 |
| 162.252.57.45 | attackspambots | 2019-11-04T00:27:58.451706mail.arvenenaske.de sshd[2422]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.252.57.45 user=r.r 2019-11-04T00:28:00.422348mail.arvenenaske.de sshd[2422]: Failed password for r.r from 162.252.57.45 port 60376 ssh2 2019-11-04T00:33:11.997272mail.arvenenaske.de sshd[2435]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.252.57.45 user=r.r 2019-11-04T00:33:13.937597mail.arvenenaske.de sshd[2435]: Failed password for r.r from 162.252.57.45 port 43366 ssh2 2019-11-04T00:36:55.529718mail.arvenenaske.de sshd[2450]: Invalid user temp from 162.252.57.45 port 54590 2019-11-04T00:36:55.535378mail.arvenenaske.de sshd[2450]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.252.57.45 user=temp 2019-11-04T00:36:55.538329mail.arvenenaske.de sshd[2450]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh rus........ ------------------------------ |
2019-11-04 20:30:11 |
| 14.187.196.205 | attackbots | Nov 4 00:22:13 mailman postfix/smtpd[25920]: warning: unknown[14.187.196.205]: SASL PLAIN authentication failed: authentication failure |
2019-11-04 20:39:41 |
| 182.61.105.89 | attack | $f2bV_matches |
2019-11-04 20:29:11 |
| 222.186.173.183 | attack | Nov 4 13:38:46 nextcloud sshd\[5668\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.183 user=root Nov 4 13:38:48 nextcloud sshd\[5668\]: Failed password for root from 222.186.173.183 port 56890 ssh2 Nov 4 13:38:52 nextcloud sshd\[5668\]: Failed password for root from 222.186.173.183 port 56890 ssh2 ... |
2019-11-04 20:42:49 |
| 39.75.239.39 | attackbotsspam | Automatic report - Port Scan |
2019-11-04 20:27:32 |
| 45.224.171.27 | attackbotsspam | Automatic report - Port Scan Attack |
2019-11-04 20:28:36 |
| 103.252.250.107 | attack | Nov 4 08:56:15 server sshd\[21177\]: Invalid user user1 from 103.252.250.107 Nov 4 08:56:15 server sshd\[21177\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.252.250.107 Nov 4 08:56:16 server sshd\[21177\]: Failed password for invalid user user1 from 103.252.250.107 port 47550 ssh2 Nov 4 09:22:02 server sshd\[27636\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.252.250.107 user=root Nov 4 09:22:03 server sshd\[27636\]: Failed password for root from 103.252.250.107 port 51436 ssh2 ... |
2019-11-04 20:46:42 |