| 45.72.61.23 |
attackbotsspam |
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…
My name’s Eric, I found norburgchiro.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 software that c |
2020-08-15 17:50:04 |
| 197.185.101.46 |
attackspambots |
Email rejected due to spam filtering |
2020-08-15 18:09:37 |
| 185.56.92.137 |
attackspam |
20/8/15@00:10:55: FAIL: Alarm-Network address from=185.56.92.137
20/8/15@00:10:55: FAIL: Alarm-Network address from=185.56.92.137
... |
2020-08-15 18:14:15 |
| 157.230.53.57 |
attackbots |
TCP ports : 9167 / 28640 |
2020-08-15 18:29:26 |
| 42.236.10.121 |
attackbotsspam |
Automatic report - Banned IP Access |
2020-08-15 17:57:40 |
| 220.86.227.220 |
attackbotsspam |
Lines containing failures of 220.86.227.220
Jul 31 05:34:06 server-name sshd[6764]: User r.r from 220.86.227.220 not allowed because not listed in AllowUsers
Jul 31 05:34:06 server-name sshd[6764]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.86.227.220 user=r.r
Jul 31 05:34:08 server-name sshd[6764]: Failed password for invalid user r.r from 220.86.227.220 port 34864 ssh2
Jul 31 06:37:40 server-name sshd[5019]: User r.r from 220.86.227.220 not allowed because not listed in AllowUsers
Jul 31 06:37:40 server-name sshd[5019]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.86.227.220 user=r.r
Jul 31 06:37:42 server-name sshd[5019]: Failed password for invalid user r.r from 220.86.227.220 port 60160 ssh2
Jul 31 07:41:13 server-name sshd[24722]: User r.r from 220.86.227.220 not allowed because not listed in AllowUsers
Jul 31 07:41:13 server-name sshd[24722]: pam_unix(sshd:auth): auth........
------------------------------ |
2020-08-15 18:15:34 |
| 222.186.61.191 |
attackbotsspam |
Aug 15 10:30:43 inter-technics postfix/smtpd[22491]: warning: unknown[222.186.61.191]: SASL LOGIN authentication failed: authentication failure
Aug 15 10:30:45 inter-technics postfix/smtpd[22491]: warning: unknown[222.186.61.191]: SASL LOGIN authentication failed: authentication failure
Aug 15 10:30:46 inter-technics postfix/smtpd[22491]: warning: unknown[222.186.61.191]: SASL LOGIN authentication failed: authentication failure
... |
2020-08-15 18:21:42 |
| 103.219.112.47 |
attackspambots |
2020-08-15T15:19:30.077827hostname sshd[87400]: Failed password for root from 103.219.112.47 port 56496 ssh2
2020-08-15T15:23:59.333795hostname sshd[87852]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.219.112.47 user=root
2020-08-15T15:24:01.448277hostname sshd[87852]: Failed password for root from 103.219.112.47 port 37592 ssh2
... |
2020-08-15 17:50:35 |
| 23.95.204.167 |
attack |
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…
My name’s Eric, I found scvfamilychiropractic.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 softwa |
2020-08-15 17:51:01 |
| 201.236.182.92 |
attackspam |
$f2bV_matches |
2020-08-15 17:53:52 |
| 139.155.127.59 |
attackspam |
Aug 15 10:05:52 pornomens sshd\[20440\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.127.59 user=root
Aug 15 10:05:54 pornomens sshd\[20440\]: Failed password for root from 139.155.127.59 port 49502 ssh2
Aug 15 10:24:59 pornomens sshd\[20655\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.127.59 user=root
... |
2020-08-15 18:22:21 |
| 85.209.0.131 |
attackspambots |
TCP (SYN) 85.209.0.131:24444 -> port 22, len 60 |
2020-08-15 18:21:12 |
| 222.186.180.147 |
attackspambots |
Aug 15 05:42:05 plusreed sshd[13573]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.147 user=root
Aug 15 05:42:07 plusreed sshd[13573]: Failed password for root from 222.186.180.147 port 15088 ssh2
... |
2020-08-15 17:49:27 |
| 222.153.54.40 |
attackspam |
REQUESTED PAGE: /wp-json/contact-form-7/v1/contact-forms/4/feedback |
2020-08-15 18:19:56 |
| 200.11.139.233 |
attackspam |
<6 unauthorized SSH connections |
2020-08-15 17:55:06 |