Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: Los Angeles

Region: California

Country: United States

Internet Service Provider: QuadraNet Enterprises LLC

Hostname: unknown

Organization: QuadraNet Enterprises LLC

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
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
Comments on same subnet:
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
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.129.3.144
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12378
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;104.129.3.144.			IN	A

;; AUTHORITY SECTION:
.			3600	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2019072300 1800 900 604800 86400

;; Query time: 2 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Wed Jul 24 01:40:38 CST 2019
;; MSG SIZE  rcvd: 117
Host info
144.3.129.104.in-addr.arpa domain name pointer 104.129.3.144.static.quadranet.com.
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

Non-authoritative answer:
144.3.129.104.in-addr.arpa	name = 104.129.3.144.static.quadranet.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
111.250.142.235 attackbotsspam
port scan and connect, tcp 23 (telnet)
2020-06-12 19:29:24
103.16.202.174 attackbots
Jun 12 12:57:38 mail sshd[28306]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.16.202.174
Jun 12 12:57:40 mail sshd[28306]: Failed password for invalid user matt from 103.16.202.174 port 46989 ssh2
...
2020-06-12 19:10:39
148.70.169.14 attackbots
Jun 12 16:16:54 webhost01 sshd[6178]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.169.14
Jun 12 16:16:56 webhost01 sshd[6178]: Failed password for invalid user seng from 148.70.169.14 port 45384 ssh2
...
2020-06-12 19:31:17
182.254.162.72 attack
Failed password for invalid user zhanglk from 182.254.162.72 port 40848 ssh2
2020-06-12 19:12:37
106.13.142.115 attackspam
firewall-block, port(s): 5245/tcp
2020-06-12 18:54:57
219.101.192.141 attackspam
ssh intrusion attempt
2020-06-12 19:11:34
118.69.71.106 attack
2020-06-12T05:36:47.189123shield sshd\[23819\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.69.71.106  user=root
2020-06-12T05:36:49.310633shield sshd\[23819\]: Failed password for root from 118.69.71.106 port 58773 ssh2
2020-06-12T05:38:46.876949shield sshd\[23990\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.69.71.106  user=root
2020-06-12T05:38:48.335964shield sshd\[23990\]: Failed password for root from 118.69.71.106 port 56487 ssh2
2020-06-12T05:42:51.273509shield sshd\[24569\]: Invalid user admin from 118.69.71.106 port 51907
2020-06-12 19:01:49
79.124.62.82 attackbots
 TCP (SYN) 79.124.62.82:52997 -> port 8399, len 44
2020-06-12 19:00:51
192.241.155.88 attack
Jun 12 12:48:20 OPSO sshd\[28959\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.241.155.88  user=root
Jun 12 12:48:22 OPSO sshd\[28959\]: Failed password for root from 192.241.155.88 port 39074 ssh2
Jun 12 12:52:53 OPSO sshd\[29642\]: Invalid user asik from 192.241.155.88 port 42432
Jun 12 12:52:53 OPSO sshd\[29642\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.241.155.88
Jun 12 12:52:56 OPSO sshd\[29642\]: Failed password for invalid user asik from 192.241.155.88 port 42432 ssh2
2020-06-12 19:03:58
188.254.0.112 attack
no
2020-06-12 18:58:23
83.97.20.31 attackbotsspam
Suspicious activity \(400 Bad Request\)
2020-06-12 18:56:28
91.121.104.181 attackbots
2020-06-12T09:34:38.279079shield sshd\[19972\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.121.104.181  user=root
2020-06-12T09:34:40.563917shield sshd\[19972\]: Failed password for root from 91.121.104.181 port 46908 ssh2
2020-06-12T09:37:45.317261shield sshd\[20952\]: Invalid user osb from 91.121.104.181 port 56344
2020-06-12T09:37:45.321834shield sshd\[20952\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.121.104.181
2020-06-12T09:37:48.278977shield sshd\[20952\]: Failed password for invalid user osb from 91.121.104.181 port 56344 ssh2
2020-06-12 19:07:30
69.61.84.222 attackbots
[H1.VM8] Blocked by UFW
2020-06-12 19:31:41
36.155.113.40 attack
Jun 12 13:04:59 abendstille sshd\[14023\]: Invalid user monitor from 36.155.113.40
Jun 12 13:04:59 abendstille sshd\[14023\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.155.113.40
Jun 12 13:05:01 abendstille sshd\[14023\]: Failed password for invalid user monitor from 36.155.113.40 port 42333 ssh2
Jun 12 13:08:49 abendstille sshd\[18165\]: Invalid user jinwen from 36.155.113.40
Jun 12 13:08:49 abendstille sshd\[18165\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.155.113.40
...
2020-06-12 19:11:46
60.170.166.177 attackspambots
[portscan] tcp/23 [TELNET]
*(RWIN=48640)(06120947)
2020-06-12 19:05:53

Recently Reported IPs

103.18.9.254 90.188.6.140 129.211.228.125 90.83.79.117
51.38.124.77 169.159.158.99 27.179.87.118 74.34.224.26
77.81.109.200 34.77.64.143 101.123.237.193 217.65.198.68
197.34.132.234 98.254.167.12 207.244.119.179 92.53.22.252
176.17.188.77 201.37.255.236 217.72.158.207 106.112.165.33