City: Los Angeles
Region: California
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.72
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57700
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.129.3.72. IN A
;; AUTHORITY SECTION:
. 148 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022063001 1800 900 604800 86400
;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jul 01 08:32:48 CST 2022
;; MSG SIZE rcvd: 105
72.3.129.104.in-addr.arpa domain name pointer 104.129.3.72.static.quadranet.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
72.3.129.104.in-addr.arpa name = 104.129.3.72.static.quadranet.com.
Authoritative answers can be found from:
IP | Type | Details | Datetime |
---|---|---|---|
159.203.201.142 | attackbots | 22562/tcp 22785/tcp 1400/tcp... [2019-10-16/12-15]58pkt,51pt.(tcp),1pt.(udp) |
2019-12-17 01:08:21 |
187.177.35.129 | attackbotsspam | MultiHost/MultiPort Probe, Scan, Hack - |
2019-12-17 00:37:44 |
1.172.187.62 | attackbots | Fail2Ban Ban Triggered |
2019-12-17 00:50:41 |
187.176.33.44 | attackspambots | MultiHost/MultiPort Probe, Scan, Hack - |
2019-12-17 00:57:57 |
197.210.64.156 | attack | TCP Port Scanning |
2019-12-17 01:05:01 |
51.77.201.36 | attack | 2019-12-16T15:46:48.145083shield sshd\[20050\]: Invalid user news from 51.77.201.36 port 46820 2019-12-16T15:46:48.149310shield sshd\[20050\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.ip-51-77-201.eu 2019-12-16T15:46:49.766810shield sshd\[20050\]: Failed password for invalid user news from 51.77.201.36 port 46820 ssh2 2019-12-16T15:52:38.543638shield sshd\[21503\]: Invalid user djarraya from 51.77.201.36 port 53604 2019-12-16T15:52:38.547610shield sshd\[21503\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.ip-51-77-201.eu |
2019-12-17 00:55:13 |
40.92.41.56 | attackspambots | Dec 16 20:01:24 debian-2gb-vpn-nbg1-1 kernel: [894053.899479] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=40.92.41.56 DST=78.46.192.101 LEN=52 TOS=0x02 PREC=0x00 TTL=104 ID=9530 DF PROTO=TCP SPT=6554 DPT=25 WINDOW=8192 RES=0x00 CWR ECE SYN URGP=0 |
2019-12-17 01:09:50 |
134.175.49.215 | attack | Dec 16 17:34:17 MK-Soft-VM6 sshd[28178]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.49.215 Dec 16 17:34:19 MK-Soft-VM6 sshd[28178]: Failed password for invalid user ursala from 134.175.49.215 port 55254 ssh2 ... |
2019-12-17 00:42:50 |
77.222.106.21 | attackbotsspam | 1576507477 - 12/16/2019 15:44:37 Host: 77.222.106.21/77.222.106.21 Port: 445 TCP Blocked |
2019-12-17 00:54:48 |
82.196.4.66 | attackbots | Dec 16 06:18:06 sachi sshd\[8766\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.196.4.66 user=root Dec 16 06:18:08 sachi sshd\[8766\]: Failed password for root from 82.196.4.66 port 33358 ssh2 Dec 16 06:26:02 sachi sshd\[10299\]: Invalid user strumph from 82.196.4.66 Dec 16 06:26:02 sachi sshd\[10299\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.196.4.66 Dec 16 06:26:04 sachi sshd\[10299\]: Failed password for invalid user strumph from 82.196.4.66 port 39346 ssh2 |
2019-12-17 01:09:10 |
182.139.134.107 | attackbots | Dec 16 15:44:38 [host] sshd[6416]: Invalid user timss from 182.139.134.107 Dec 16 15:44:38 [host] sshd[6416]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.139.134.107 Dec 16 15:44:40 [host] sshd[6416]: Failed password for invalid user timss from 182.139.134.107 port 21249 ssh2 |
2019-12-17 00:47:20 |
54.36.183.242 | attackspam | Dec 16 17:10:08 rotator sshd\[20507\]: Invalid user password123 from 54.36.183.242Dec 16 17:10:10 rotator sshd\[20507\]: Failed password for invalid user password123 from 54.36.183.242 port 41766 ssh2Dec 16 17:14:56 rotator sshd\[21177\]: Invalid user burste from 54.36.183.242Dec 16 17:14:58 rotator sshd\[21177\]: Failed password for invalid user burste from 54.36.183.242 port 51688 ssh2Dec 16 17:19:58 rotator sshd\[21997\]: Invalid user eliska from 54.36.183.242Dec 16 17:20:00 rotator sshd\[21997\]: Failed password for invalid user eliska from 54.36.183.242 port 38084 ssh2 ... |
2019-12-17 00:33:51 |
40.92.64.67 | attackspambots | Dec 16 17:44:45 debian-2gb-vpn-nbg1-1 kernel: [885854.391357] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=40.92.64.67 DST=78.46.192.101 LEN=52 TOS=0x02 PREC=0x00 TTL=110 ID=18458 DF PROTO=TCP SPT=10469 DPT=25 WINDOW=8192 RES=0x00 CWR ECE SYN URGP=0 |
2019-12-17 00:44:08 |
41.169.16.73 | attackspam | Unauthorized connection attempt detected from IP address 41.169.16.73 to port 445 |
2019-12-17 00:27:11 |
37.187.114.135 | attackbots | Dec 16 16:50:40 minden010 sshd[9245]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.187.114.135 Dec 16 16:50:42 minden010 sshd[9245]: Failed password for invalid user abc123$ from 37.187.114.135 port 44052 ssh2 Dec 16 16:57:16 minden010 sshd[11485]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.187.114.135 ... |
2019-12-17 00:53:08 |