City: unknown
Region: unknown
Country: United States of America (the)
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 95.41.3.140
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 64556
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;95.41.3.140. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025022500 1800 900 604800 86400
;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 25 18:15:23 CST 2025
;; MSG SIZE rcvd: 104Host 140.3.41.95.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 140.3.41.95.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 119.149.136.46 | attack | SSH brute-force attempt |
2020-09-30 00:24:40 |
| 49.232.79.23 | attackbotsspam | Invalid user testuser from 49.232.79.23 port 38722 |
2020-09-30 00:12:05 |
| 171.8.135.136 | attackbotsspam | Sep 29 18:20:32 serwer sshd\[4503\]: Invalid user list1 from 171.8.135.136 port 9797 Sep 29 18:20:32 serwer sshd\[4503\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.8.135.136 Sep 29 18:20:34 serwer sshd\[4503\]: Failed password for invalid user list1 from 171.8.135.136 port 9797 ssh2 ... |
2020-09-30 00:20:44 |
| 192.99.168.9 | attackspambots | Invalid user vagrant from 192.99.168.9 port 38706 |
2020-09-30 00:10:41 |
| 87.251.70.79 | attackbotsspam | port scan |
2020-09-30 00:37:59 |
| 23.108.4.58 | attackbots | (From eric@talkwithwebvisitor.com) Good day, My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations What for? Part of my job is to check out websites and the work you’ve done with kckchiropractic.com definitely stands out. It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality. There is, however, a catch… more accurately, a question… So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? More importantly, how do you make a connection with that person? Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind. Here’s a way to create INSTANT engagement that you may not have known about… Talk With Web Visitor is a software widget that’s works on your site, ready to capture any |
2020-09-30 00:26:04 |
| 203.148.20.162 | attack | Sep 29 15:06:47 ip-172-31-16-56 sshd\[32750\]: Invalid user ian1 from 203.148.20.162\ Sep 29 15:06:49 ip-172-31-16-56 sshd\[32750\]: Failed password for invalid user ian1 from 203.148.20.162 port 47090 ssh2\ Sep 29 15:09:36 ip-172-31-16-56 sshd\[364\]: Invalid user manager from 203.148.20.162\ Sep 29 15:09:38 ip-172-31-16-56 sshd\[364\]: Failed password for invalid user manager from 203.148.20.162 port 46670 ssh2\ Sep 29 15:12:27 ip-172-31-16-56 sshd\[389\]: Invalid user internet1 from 203.148.20.162\ |
2020-09-30 00:31:29 |
| 192.144.187.153 | attackbotsspam | Invalid user laravel from 192.144.187.153 port 51286 |
2020-09-30 00:42:09 |
| 85.106.182.144 | attackspambots | 20/9/28@16:35:30: FAIL: Alarm-Network address from=85.106.182.144 20/9/28@16:35:30: FAIL: Alarm-Network address from=85.106.182.144 ... |
2020-09-30 00:53:03 |
| 92.184.97.161 | attack | Automatic report - Banned IP Access |
2020-09-30 00:50:37 |
| 45.55.237.182 | attackbotsspam | Sep 29 16:38:19 localhost sshd[7046]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.237.182 user=ftp Sep 29 16:38:22 localhost sshd[7046]: Failed password for ftp from 45.55.237.182 port 43386 ssh2 Sep 29 16:43:08 localhost sshd[7385]: Invalid user tester from 45.55.237.182 port 35260 Sep 29 16:43:08 localhost sshd[7385]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.237.182 Sep 29 16:43:08 localhost sshd[7385]: Invalid user tester from 45.55.237.182 port 35260 Sep 29 16:43:11 localhost sshd[7385]: Failed password for invalid user tester from 45.55.237.182 port 35260 ssh2 ... |
2020-09-30 00:46:11 |
| 210.178.36.207 | attack | " " |
2020-09-30 00:51:27 |
| 111.229.40.252 | attackspam | (sshd) Failed SSH login from 111.229.40.252 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep 29 11:55:14 server5 sshd[7148]: Invalid user system from 111.229.40.252 Sep 29 11:55:14 server5 sshd[7148]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.40.252 Sep 29 11:55:15 server5 sshd[7148]: Failed password for invalid user system from 111.229.40.252 port 51490 ssh2 Sep 29 12:02:11 server5 sshd[10218]: Invalid user library from 111.229.40.252 Sep 29 12:02:11 server5 sshd[10218]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.40.252 |
2020-09-30 00:34:06 |
| 124.128.158.37 | attackspambots | Sep 29 10:31:05 george sshd[6874]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.128.158.37 user=root Sep 29 10:31:08 george sshd[6874]: Failed password for root from 124.128.158.37 port 28456 ssh2 Sep 29 10:35:11 george sshd[6916]: Invalid user cute from 124.128.158.37 port 28457 Sep 29 10:35:11 george sshd[6916]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.128.158.37 Sep 29 10:35:14 george sshd[6916]: Failed password for invalid user cute from 124.128.158.37 port 28457 ssh2 ... |
2020-09-30 00:48:56 |
| 23.108.4.81 | attackbotsspam | (From eric@talkwithwebvisitor.com) My name’s Eric and I just came across your website - nassauchiropracticphysicaltherapy.com - in the search results. Here’s what that means to me… Your SEO’s working. You’re getting eyeballs – mine at least. Your content’s pretty good, wouldn’t change a thing. BUT… Eyeballs don’t pay the bills. CUSTOMERS do. And studies show that 7 out of 10 visitors to a site like nassauchiropracticphysicaltherapy.com will drop by, take a gander, and then head for the hills without doing anything else. It’s like they never were even there. You can fix this. You can make it super-simple for them to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket… thanks to Talk With Web Visitor. Talk With Web Visitor is a software widget that sits on your site, ready and waiting to capture any visitor’s Name, Email address and Phone Number. It lets you know immediately – so you can talk to that lead immediate |
2020-09-30 00:32:16 |