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.210
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 36797
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.129.3.210. IN A
;; AUTHORITY SECTION:
. 293 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022040102 1800 900 604800 86400
;; Query time: 84 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Apr 01 22:50:24 CST 2022
;; MSG SIZE rcvd: 106210.3.129.104.in-addr.arpa domain name pointer 104.129.3.210.static.quadranet.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
210.3.129.104.in-addr.arpa name = 104.129.3.210.static.quadranet.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 103.56.79.2 | attackspam | Oct 30 12:27:06 hcbbdb sshd\[23407\]: Invalid user ming1234 from 103.56.79.2 Oct 30 12:27:06 hcbbdb sshd\[23407\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.56.79.2 Oct 30 12:27:08 hcbbdb sshd\[23407\]: Failed password for invalid user ming1234 from 103.56.79.2 port 48002 ssh2 Oct 30 12:33:00 hcbbdb sshd\[23997\]: Invalid user catalin from 103.56.79.2 Oct 30 12:33:00 hcbbdb sshd\[23997\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.56.79.2 |
2019-10-30 20:42:07 |
| 123.30.168.119 | attackbotsspam | Detected by ModSecurity. Request URI: /wp-login.php/ip-redirect/ |
2019-10-30 20:45:14 |
| 42.200.116.172 | attackbotsspam | 60001/tcp 60001/tcp 60001/tcp... [2019-10-26/30]8pkt,1pt.(tcp) |
2019-10-30 20:47:31 |
| 179.43.110.84 | attackbotsspam | 23/tcp 23/tcp [2019-10-25/30]2pkt |
2019-10-30 21:07:56 |
| 184.105.247.223 | attackbotsspam | 30005/tcp 50075/tcp 873/tcp... [2019-08-30/10-30]41pkt,10pt.(tcp),2pt.(udp) |
2019-10-30 20:40:17 |
| 222.186.175.148 | attack | Oct 30 02:54:17 php1 sshd\[22180\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.148 user=root Oct 30 02:54:19 php1 sshd\[22180\]: Failed password for root from 222.186.175.148 port 46412 ssh2 Oct 30 02:54:24 php1 sshd\[22180\]: Failed password for root from 222.186.175.148 port 46412 ssh2 Oct 30 02:54:29 php1 sshd\[22180\]: Failed password for root from 222.186.175.148 port 46412 ssh2 Oct 30 02:54:34 php1 sshd\[22180\]: Failed password for root from 222.186.175.148 port 46412 ssh2 |
2019-10-30 21:00:48 |
| 222.186.175.182 | attackspambots | Oct 30 14:07:07 srv206 sshd[28738]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.182 user=root Oct 30 14:07:09 srv206 sshd[28738]: Failed password for root from 222.186.175.182 port 2876 ssh2 ... |
2019-10-30 21:12:46 |
| 167.71.55.1 | attack | Oct 30 14:40:06 server sshd\[24808\]: Invalid user library from 167.71.55.1 Oct 30 14:40:06 server sshd\[24808\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.55.1 Oct 30 14:40:08 server sshd\[24808\]: Failed password for invalid user library from 167.71.55.1 port 45058 ssh2 Oct 30 14:55:12 server sshd\[28250\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.55.1 user=root Oct 30 14:55:14 server sshd\[28250\]: Failed password for root from 167.71.55.1 port 33382 ssh2 ... |
2019-10-30 20:27:55 |
| 197.96.136.91 | attack | Oct 30 13:55:33 [host] sshd[5002]: Invalid user www from 197.96.136.91 Oct 30 13:55:33 [host] sshd[5002]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=197.96.136.91 Oct 30 13:55:35 [host] sshd[5002]: Failed password for invalid user www from 197.96.136.91 port 33721 ssh2 |
2019-10-30 21:16:21 |
| 139.99.67.111 | attackbots | Oct 30 13:36:29 SilenceServices sshd[9087]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.67.111 Oct 30 13:36:31 SilenceServices sshd[9087]: Failed password for invalid user P)o9I*u7 from 139.99.67.111 port 49350 ssh2 Oct 30 13:41:13 SilenceServices sshd[10431]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.67.111 |
2019-10-30 20:44:04 |
| 46.38.144.17 | attackbots | 2019-10-30T13:31:06.259368mail01 postfix/smtpd[27075]: warning: unknown[46.38.144.17]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 2019-10-30T13:31:16.219280mail01 postfix/smtpd[549]: warning: unknown[46.38.144.17]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 2019-10-30T13:31:31.148723mail01 postfix/smtpd[9712]: warning: unknown[46.38.144.17]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 |
2019-10-30 20:39:09 |
| 87.103.201.27 | attackbots | 8081/tcp 88/tcp 81/tcp... [2019-10-04/30]9pkt,4pt.(tcp) |
2019-10-30 20:36:19 |
| 200.72.142.197 | attack | 445/tcp 445/tcp 445/tcp... [2019-10-11/30]8pkt,1pt.(tcp) |
2019-10-30 20:49:08 |
| 85.96.182.209 | attack | 23/tcp 37215/tcp [2019-10-06/30]2pkt |
2019-10-30 20:30:32 |
| 178.159.249.66 | attackbots | $f2bV_matches |
2019-10-30 20:34:40 |