City: unknown
Region: unknown
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
| IP | Type | Details | Datetime |
|---|---|---|---|
| 104.129.3.254 | attackspambots | (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:23:51 |
| 104.129.31.27 | attackspambots | POODLE attack imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=104.129.31.27, lip=[snip], TLS handshaking: SSL_accept() failed: error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate: SSL alert number 42, session=<[snip]> |
2020-06-12 13:09:54 |
| 104.129.3.3 | attackspam | 3,39-06/06 [bc04/m132] PostRequest-Spammer scoring: zurich |
2020-06-07 01:25:41 |
| 104.129.3.144 | attackspam | (From eric@talkwithcustomer.com) Hello pomeroychiropractic.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 pomeroychiropractic.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 pomeroychiropractic.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 – |
2019-07-24 01:40:47 |
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.129.3.58
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46889
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.129.3.58. IN A
;; AUTHORITY SECTION:
. 597 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022022800 1800 900 604800 86400
;; Query time: 78 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 15:59:54 CST 2022
;; MSG SIZE rcvd: 10558.3.129.104.in-addr.arpa domain name pointer 104.129.3.58.static.quadranet.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
58.3.129.104.in-addr.arpa name = 104.129.3.58.static.quadranet.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 66.249.64.46 | attackspam | Web App Attack |
2019-12-31 17:43:09 |
| 222.186.175.182 | attack | Dec 31 10:30:13 localhost sshd\[15854\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.182 user=root Dec 31 10:30:15 localhost sshd\[15854\]: Failed password for root from 222.186.175.182 port 38354 ssh2 Dec 31 10:30:18 localhost sshd\[15854\]: Failed password for root from 222.186.175.182 port 38354 ssh2 |
2019-12-31 17:40:03 |
| 222.186.175.215 | attackbots | SSH login attempts |
2019-12-31 17:36:17 |
| 192.34.62.227 | attack | --- report --- Dec 31 06:18:29 -0300 sshd: Connection from 192.34.62.227 port 40806 |
2019-12-31 17:36:48 |
| 123.27.197.152 | attack | Dec 31 07:15:24 server sshd\[11927\]: Invalid user miklos from 123.27.197.152 Dec 31 07:15:24 server sshd\[11927\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.27.197.152 Dec 31 07:15:26 server sshd\[11927\]: Failed password for invalid user miklos from 123.27.197.152 port 53968 ssh2 Dec 31 09:25:13 server sshd\[9747\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.27.197.152 user=root Dec 31 09:25:15 server sshd\[9747\]: Failed password for root from 123.27.197.152 port 40834 ssh2 ... |
2019-12-31 17:41:27 |
| 213.233.177.118 | attack | Dec 31 06:56:23 sso sshd[13191]: Failed password for root from 213.233.177.118 port 37010 ssh2 ... |
2019-12-31 17:53:14 |
| 192.95.95.95 | attack | *Port Scan* detected from 192.95.95.95 (US/United States/phid.ae). 4 hits in the last 126 seconds |
2019-12-31 17:49:27 |
| 122.51.86.120 | attackspam | Dec 31 08:30:33 ArkNodeAT sshd\[19406\]: Invalid user admin from 122.51.86.120 Dec 31 08:30:33 ArkNodeAT sshd\[19406\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.86.120 Dec 31 08:30:35 ArkNodeAT sshd\[19406\]: Failed password for invalid user admin from 122.51.86.120 port 33600 ssh2 |
2019-12-31 17:28:58 |
| 218.92.0.148 | attack | 19/12/31@04:28:31: FAIL: IoT-SSH address from=218.92.0.148 ... |
2019-12-31 17:32:13 |
| 89.248.168.87 | attackbots | *Port Scan* detected from 89.248.168.87 (NL/Netherlands/-). 4 hits in the last 285 seconds |
2019-12-31 17:45:15 |
| 218.92.0.172 | attackbotsspam | Dec 31 09:43:35 plex sshd[31029]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.172 user=root Dec 31 09:43:37 plex sshd[31029]: Failed password for root from 218.92.0.172 port 24273 ssh2 |
2019-12-31 17:27:16 |
| 196.205.15.34 | attackbotsspam | 19/12/31@01:13:16: FAIL: Alarm-Network address from=196.205.15.34 19/12/31@01:13:16: FAIL: Alarm-Network address from=196.205.15.34 19/12/31@01:13:17: FAIL: Alarm-Network address from=196.205.15.34 19/12/31@01:13:18: FAIL: Alarm-Network address from=196.205.15.34 19/12/31@01:13:19: FAIL: Alarm-Network address from=196.205.15.34 19/12/31@01:13:19: FAIL: Alarm-Network address from=196.205.15.34 19/12/31@01:13:20: FAIL: Alarm-Network address from=196.205.15.34 19/12/31@01:13:20: FAIL: Alarm-Network address from=196.205.15.34 19/12/31@01:13:20: FAIL: Alarm-Network address from=196.205.15.34 19/12/31@01:13:21: FAIL: Alarm-Network address from=196.205.15.34 19/12/31@01:13:21: FAIL: Alarm-Network address from=196.205.15.34 19/12/31@01:13:22: FAIL: Alarm-Network address from=196.205.15.34 19/12/31@01:13:22: FAIL: Alarm-Network address from=196.205.15.34 19/12/31@01:13:22: FAIL: Alarm-Network address from=196.205.15.34 19/12/31@01:13:23: FAIL: Alarm-Network address from=196.205.15.34 19/12/31@0 ... |
2019-12-31 17:50:49 |
| 154.233.216.212 | attack | 19/12/31@03:29:56: FAIL: Alarm-Network address from=154.233.216.212 19/12/31@03:29:57: FAIL: Alarm-Network address from=154.233.216.212 ... |
2019-12-31 18:00:26 |
| 81.45.56.199 | attack | Invalid user shihhsiung from 81.45.56.199 port 39438 |
2019-12-31 17:31:23 |
| 159.203.201.224 | attackspambots | Unauthorized connection attempt detected from IP address 159.203.201.224 to port 7474 |
2019-12-31 17:51:57 |