城市(city): unknown
省份(region): unknown
国家(country): United States of America
运营商(isp): ColoCrossing
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): Data Center/Web Hosting/Transit
| 类型 | 评论内容 | 时间 |
|---|---|---|
| attack | (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 advancedchirosolutions.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 capt |
2020-06-04 03:16:32 |
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 192.3.215.164 | attackspambots | (From eric@talkwithwebvisitor.com) Hello, my name’s Eric and I just ran across your website at mcleodchiropractic.com... I found it after a quick search, so your SEO’s working out… Content looks pretty good… One thing’s missing though… A QUICK, EASY way to connect with you NOW. Because studies show that a web lead like me will only hang out a few seconds – 7 out of 10 disappear almost instantly, Surf Surf Surf… then gone forever. I have the solution: 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. You’ll know immediately they’re interested and you can call them directly to TALK with them - literally while they’re still on the web looking at your site. CLICK HERE http://www.talkwithwebvisitor.com to try out a Live Demo with Talk With Web Visitor now to see exactly how it works and even give it a try… it could be huge for your business. Plus, now that you’ve got that phone number, with our new |
2020-06-03 02:07:29 |
| 192.3.215.213 | attackspambots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found drjenniferbrandon.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 t |
2020-03-04 23:47:47 |
| 192.3.215.216 | attack | (From eric@talkwithwebvisitor.com) Cool website! My name’s Eric, and I just found your site - fpchiro.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 fpchiro.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 |
2020-02-22 02:56:58 |
| 192.3.215.213 | attack | Several IPs in the 192.3.0.0 range are up to no-good |
2020-02-21 02:40:43 |
| 192.3.215.244 | attackbots | (From eric@talkwithcustomer.com) Hello wardchiropractic.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 wardchiropractic.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 wardchiropractic.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 f |
2020-01-11 06:47:16 |
| 192.3.215.42 | attackbots | (From eric@talkwithcustomer.com) Hello wardchiropractic.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 wardchiropractic.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 wardchiropractic.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 f |
2020-01-11 06:44:45 |
| 192.3.215.244 | attackspam | (From eric@talkwithcustomer.com) Hey, You have a website livewithvitality.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 |
2019-12-29 22:47:37 |
| 192.3.215.42 | attack | 4,33-04/04 [bc03/m123] PostRequest-Spammer scoring: zurich |
2019-12-28 19:55:41 |
| 192.3.215.83 | attackspam | (From eric@talkwithcustomer.com) Hello nwchiro.net, 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 nwchiro.net. - 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 nwchiro.net, 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 |
2019-12-22 05:19:35 |
| 192.3.215.202 | attack | 1,63-14/07 [bc02/m44] PostRequest-Spammer scoring: rome |
2019-10-28 14:57:44 |
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 192.3.215.132
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51412
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;192.3.215.132. IN A
;; AUTHORITY SECTION:
. 591 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2020060301 1800 900 604800 86400
;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jun 04 03:16:29 CST 2020
;; MSG SIZE rcvd: 117132.215.3.192.in-addr.arpa domain name pointer 192-3-215-132-host.colocrossing.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
132.215.3.192.in-addr.arpa name = 192-3-215-132-host.colocrossing.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 182.133.225.54 | attackbotsspam | 04/04/2020-23:57:09.919829 182.133.225.54 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433 |
2020-04-05 13:16:33 |
| 154.113.1.142 | attack | ssh brute force |
2020-04-05 13:37:36 |
| 67.205.153.16 | attackbots | $f2bV_matches |
2020-04-05 13:12:21 |
| 222.186.173.154 | attack | Apr 5 01:21:30 server sshd\[9559\]: Failed password for root from 222.186.173.154 port 34990 ssh2 Apr 5 08:21:49 server sshd\[25022\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.154 user=root Apr 5 08:21:51 server sshd\[25022\]: Failed password for root from 222.186.173.154 port 7652 ssh2 Apr 5 08:21:55 server sshd\[25022\]: Failed password for root from 222.186.173.154 port 7652 ssh2 Apr 5 08:21:58 server sshd\[25022\]: Failed password for root from 222.186.173.154 port 7652 ssh2 ... |
2020-04-05 13:26:43 |
| 106.12.153.107 | attack | Unauthorized SSH login attempts |
2020-04-05 13:22:09 |
| 195.12.137.16 | attack | SSH Brute-Force reported by Fail2Ban |
2020-04-05 13:24:55 |
| 194.67.91.105 | attack | Apr 3 23:47:36 uapps sshd[18506]: User r.r from 194-67-91-105.cloudvps.regruhosting.ru not allowed because not listed in AllowUsers Apr 3 23:47:36 uapps sshd[18506]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=194-67-91-105.cloudvps.regruhosting.ru user=r.r Apr 3 23:47:37 uapps sshd[18506]: Failed password for invalid user r.r from 194.67.91.105 port 41734 ssh2 Apr 3 23:47:37 uapps sshd[18506]: Received disconnect from 194.67.91.105: 11: Bye Bye [preauth] Apr 4 00:00:18 uapps sshd[18826]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=194-67-91-105.cloudvps.regruhosting.ru Apr 4 00:00:20 uapps sshd[18826]: Failed password for invalid user ro from 194.67.91.105 port 46056 ssh2 Apr 4 00:00:20 uapps sshd[18826]: Received disconnect from 194.67.91.105: 11: Bye Bye [preauth] Apr 4 00:04:09 uapps sshd[18854]: User r.r from 194-67-91-105.cloudvps.regruhosting.ru not allowed because no........ ------------------------------- |
2020-04-05 13:36:47 |
| 222.186.30.57 | attack | Apr 5 07:09:31 minden010 sshd[29877]: Failed password for root from 222.186.30.57 port 40327 ssh2 Apr 5 07:09:34 minden010 sshd[29877]: Failed password for root from 222.186.30.57 port 40327 ssh2 Apr 5 07:09:36 minden010 sshd[29877]: Failed password for root from 222.186.30.57 port 40327 ssh2 ... |
2020-04-05 13:15:30 |
| 51.75.201.28 | attack | (sshd) Failed SSH login from 51.75.201.28 (FR/France/28.ip-51-75-201.eu): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 5 05:56:42 ubnt-55d23 sshd[22861]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.201.28 user=root Apr 5 05:56:44 ubnt-55d23 sshd[22861]: Failed password for root from 51.75.201.28 port 57796 ssh2 |
2020-04-05 13:37:59 |
| 186.122.149.144 | attackbotsspam | Apr 4 23:56:25 mail sshd\[30878\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.122.149.144 user=root ... |
2020-04-05 13:49:35 |
| 45.14.150.140 | attackspambots | Apr 4 20:48:07 mockhub sshd[15157]: Failed password for root from 45.14.150.140 port 48404 ssh2 ... |
2020-04-05 13:38:29 |
| 51.161.104.179 | spamattack | try to hack my email |
2020-04-05 13:14:38 |
| 145.239.72.63 | attackspam | $f2bV_matches |
2020-04-05 13:50:34 |
| 97.64.80.12 | attack | Apr 5 07:06:57 site3 sshd\[200161\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=97.64.80.12 user=root Apr 5 07:06:59 site3 sshd\[200161\]: Failed password for root from 97.64.80.12 port 36322 ssh2 Apr 5 07:10:22 site3 sshd\[200221\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=97.64.80.12 user=root Apr 5 07:10:24 site3 sshd\[200221\]: Failed password for root from 97.64.80.12 port 41344 ssh2 Apr 5 07:13:49 site3 sshd\[200242\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=97.64.80.12 user=root ... |
2020-04-05 13:35:09 |
| 164.132.57.16 | attackspam | Apr 5 06:21:39 MainVPS sshd[21917]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.57.16 user=root Apr 5 06:21:41 MainVPS sshd[21917]: Failed password for root from 164.132.57.16 port 55980 ssh2 Apr 5 06:25:38 MainVPS sshd[29998]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.57.16 user=root Apr 5 06:25:40 MainVPS sshd[29998]: Failed password for root from 164.132.57.16 port 33096 ssh2 Apr 5 06:29:24 MainVPS sshd[5264]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.57.16 user=root Apr 5 06:29:26 MainVPS sshd[5264]: Failed password for root from 164.132.57.16 port 38445 ssh2 ... |
2020-04-05 13:29:59 |