WordPress XMLRPC scan :: 23.94.148.207 1.000 BYPASS [22/Jul/2019:23:08:17  1000] www.[censored_1] "POST /xmlrpc.php HTTP/1.1" 200 382 "https://www.[censored_1]/" "PHP/6.2.91"

(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found mcfaddenchiropractic.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well.

So here’s my question – what happens AFTER someone lands on your site?  Anything?

Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever.

That means that all the work and effort you put into getting them to show up, goes down the tubes.

Why would you want all that good work – and the great site you’ve built – go to waste?

Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry.

But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket?
  
You can – thanks to revolutionary new softwar

(From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across maltbychiro.com a few minutes ago.

Looks great… but now what?

By that I mean, when someone like me finds your website – either through Search or just bouncing around – what happens next?  Do you get a lot of leads from your site, or at least enough to make you happy?

Honestly, most business websites fall a bit short when it comes to generating paying customers. Studies show that 70% of a site’s visitors disappear and are gone forever after just a moment.

Here’s an idea…
 
How about making it really EASY for every visitor who shows up to get a personal phone call you as soon as they hit your site…
 
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 signals you the moment they let you know they’re interested – so that you can talk to that lead while they’re literally looking over your site.

CLICK HERE http://www.talkw

Spam

(From eric@talkwithcustomer.com) Hello palmerchiroga.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 palmerchiroga.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 palmerchiroga.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 famous mar

(From eric@talkwithcustomer.com) Hello higleychiropractic.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 higleychiropractic.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 higleychiropractic.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

(From eric@talkwithcustomer.com) Hello zchiro.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 zchiro.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 zchiro.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 famous marketer put it, “you’re

ssh failed login

Sep 29 17:20:30 tux-35-217 sshd\[16562\]: Invalid user raife from 102.165.50.10 port 35884
Sep 29 17:20:30 tux-35-217 sshd\[16562\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=102.165.50.10
Sep 29 17:20:33 tux-35-217 sshd\[16562\]: Failed password for invalid user raife from 102.165.50.10 port 35884 ssh2
Sep 29 17:24:54 tux-35-217 sshd\[16609\]: Invalid user spark from 102.165.50.10 port 48782
Sep 29 17:24:54 tux-35-217 sshd\[16609\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=102.165.50.10
...

2019-09-29T14:02:50.978652lon01.zurich-datacenter.net sshd\[10701\]: Invalid user vweru from 51.75.171.150 port 58214
2019-09-29T14:02:50.985794lon01.zurich-datacenter.net sshd\[10701\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.ip-51-75-171.eu
2019-09-29T14:02:53.014998lon01.zurich-datacenter.net sshd\[10701\]: Failed password for invalid user vweru from 51.75.171.150 port 58214 ssh2
2019-09-29T14:07:04.067313lon01.zurich-datacenter.net sshd\[10802\]: Invalid user kristine from 51.75.171.150 port 42420
2019-09-29T14:07:04.074504lon01.zurich-datacenter.net sshd\[10802\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.ip-51-75-171.eu
...

23/tcp 23/tcp 23/tcp...
[2019-09-08/29]5pkt,1pt.(tcp)

2019-09-29T10:27:00.2012901495-001 sshd\[15253\]: Invalid user steam from 222.190.127.58 port 51422
2019-09-29T10:27:00.2081071495-001 sshd\[15253\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.190.127.58
2019-09-29T10:27:02.3974561495-001 sshd\[15253\]: Failed password for invalid user steam from 222.190.127.58 port 51422 ssh2
2019-09-29T10:36:44.8841451495-001 sshd\[15988\]: Invalid user steam from 222.190.127.58 port 56126
2019-09-29T10:36:44.8872141495-001 sshd\[15988\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.190.127.58
2019-09-29T10:36:46.5798061495-001 sshd\[15988\]: Failed password for invalid user steam from 222.190.127.58 port 56126 ssh2
...

IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/180.3.130.216/ 
 JP - 1H : (261)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : JP 
 NAME ASN : ASN4713 
 
 IP : 180.3.130.216 
 
 CIDR : 180.0.0.0/13 
 
 PREFIX COUNT : 301 
 
 UNIQUE IP COUNT : 28900096 
 
 
 WYKRYTE ATAKI Z ASN4713 :  
  1H - 3 
  3H - 6 
  6H - 8 
 12H - 16 
 24H - 26 
 
 INFO : Port SERVER 80 Scan Detected and Blocked by ADMIN  - data recovery

Sep 29 16:27:32 mail sshd\[3485\]: Invalid user ubnt from 49.235.226.9 port 55398
Sep 29 16:27:32 mail sshd\[3485\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.226.9
Sep 29 16:27:34 mail sshd\[3485\]: Failed password for invalid user ubnt from 49.235.226.9 port 55398 ssh2
Sep 29 16:33:48 mail sshd\[3953\]: Invalid user cesar from 49.235.226.9 port 35056
Sep 29 16:33:48 mail sshd\[3953\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.226.9

Sep 29 14:42:57 game-panel sshd[21608]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.117.163.21
Sep 29 14:42:59 game-panel sshd[21608]: Failed password for invalid user admin from 27.117.163.21 port 54010 ssh2
Sep 29 14:49:05 game-panel sshd[21830]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.117.163.21

Sep 29 10:51:10 ny01 sshd[11267]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.161.19.98
Sep 29 10:51:12 ny01 sshd[11267]: Failed password for invalid user admin from 14.161.19.98 port 37382 ssh2
Sep 29 10:56:20 ny01 sshd[12486]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.161.19.98

Sep 29 16:40:19 lnxded63 sshd[15930]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.52.234

Sep 29 05:18:05 kapalua sshd\[24144\]: Invalid user qs from 94.191.60.199
Sep 29 05:18:05 kapalua sshd\[24144\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.191.60.199
Sep 29 05:18:07 kapalua sshd\[24144\]: Failed password for invalid user qs from 94.191.60.199 port 54244 ssh2
Sep 29 05:22:57 kapalua sshd\[24597\]: Invalid user quegen from 94.191.60.199
Sep 29 05:22:57 kapalua sshd\[24597\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.191.60.199

2019-09-29T10:40:01.1408361495-001 sshd\[16259\]: Failed password for invalid user Public@123 from 128.199.95.60 port 55034 ssh2
2019-09-29T10:50:14.4236911495-001 sshd\[17030\]: Invalid user OCS from 128.199.95.60 port 49982
2019-09-29T10:50:14.4310751495-001 sshd\[17030\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.95.60
2019-09-29T10:50:16.3244471495-001 sshd\[17030\]: Failed password for invalid user OCS from 128.199.95.60 port 49982 ssh2
2019-09-29T10:55:36.2784761495-001 sshd\[17484\]: Invalid user password from 128.199.95.60 port 33340
2019-09-29T10:55:36.2814691495-001 sshd\[17484\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.95.60
...

Sep 29 17:18:17 SilenceServices sshd[9144]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.59.114.113
Sep 29 17:18:19 SilenceServices sshd[9144]: Failed password for invalid user scpuser from 37.59.114.113 port 55756 ssh2
Sep 29 17:21:57 SilenceServices sshd[10137]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.59.114.113

IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/103.94.7.98/ 
 ID - 1H : (172)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : ID 
 NAME ASN : ASN9341 
 
 IP : 103.94.7.98 
 
 CIDR : 103.94.7.0/24 
 
 PREFIX COUNT : 168 
 
 UNIQUE IP COUNT : 43520 
 
 
 WYKRYTE ATAKI Z ASN9341 :  
  1H - 1 
  3H - 2 
  6H - 2 
 12H - 3 
 24H - 4 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery

Sep 29 16:31:55 mail sshd\[3796\]: Invalid user iv from 211.104.171.239 port 41819
Sep 29 16:31:55 mail sshd\[3796\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.104.171.239
Sep 29 16:31:57 mail sshd\[3796\]: Failed password for invalid user iv from 211.104.171.239 port 41819 ssh2
Sep 29 16:36:55 mail sshd\[4269\]: Invalid user PlcmSpIp from 211.104.171.239 port 34075
Sep 29 16:36:55 mail sshd\[4269\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.104.171.239