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: unknown

Region: unknown

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
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
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
Whois info:
b
Dig info:
; <<>> 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: 105
Host info
58.3.129.104.in-addr.arpa domain name pointer 104.129.3.58.static.quadranet.com.
Nslookup info:
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:
Related IP info:
Related comments:
IP Type Details Datetime
104.168.96.138 attack
2020-02-17 10:09:30
79.94.245.162 attack
Feb 17 02:59:11 localhost sshd\[2062\]: Invalid user testing from 79.94.245.162 port 38884
Feb 17 02:59:11 localhost sshd\[2062\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.94.245.162
Feb 17 02:59:13 localhost sshd\[2062\]: Failed password for invalid user testing from 79.94.245.162 port 38884 ssh2
2020-02-17 10:20:54
185.209.0.91 attackbots
02/16/2020-19:36:23.404376 185.209.0.91 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2020-02-17 09:51:47
189.208.61.170 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-17 09:54:55
222.186.173.154 attackspam
Feb 17 01:54:40 sd-84780 sshd[6288]: Failed password for root from 222.186.173.154 port 37978 ssh2
Feb 17 01:54:43 sd-84780 sshd[6288]: Failed password for root from 222.186.173.154 port 37978 ssh2
Feb 17 01:54:46 sd-84780 sshd[6288]: Failed password for root from 222.186.173.154 port 37978 ssh2
...
2020-02-17 10:08:02
189.208.61.116 attack
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-17 10:06:14
201.249.88.124 attackspam
Feb 17 03:15:11 ArkNodeAT sshd\[8937\]: Invalid user vinay from 201.249.88.124
Feb 17 03:15:11 ArkNodeAT sshd\[8937\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.249.88.124
Feb 17 03:15:13 ArkNodeAT sshd\[8937\]: Failed password for invalid user vinay from 201.249.88.124 port 46967 ssh2
2020-02-17 10:33:21
185.176.27.194 attackbots
02/17/2020-02:13:34.475435 185.176.27.194 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2020-02-17 09:58:38
129.28.166.61 attack
$f2bV_matches
2020-02-17 10:04:00
112.85.42.227 attackbotsspam
Feb 16 21:14:36 NPSTNNYC01T sshd[9179]: Failed password for root from 112.85.42.227 port 46349 ssh2
Feb 16 21:18:10 NPSTNNYC01T sshd[9256]: Failed password for root from 112.85.42.227 port 49457 ssh2
...
2020-02-17 10:28:03
181.41.8.60 attack
Automatic report - Port Scan Attack
2020-02-17 10:19:46
209.97.131.163 attackspambots
Feb 16 23:08:15 server sshd[243685]: Failed password for invalid user olimex from 209.97.131.163 port 55276 ssh2
Feb 16 23:21:39 server sshd[244246]: Failed password for invalid user kent from 209.97.131.163 port 52260 ssh2
Feb 16 23:24:18 server sshd[244369]: Failed password for invalid user content from 209.97.131.163 port 53554 ssh2
2020-02-17 09:53:36
112.85.42.237 attackbots
Feb 17 01:51:12 localhost sshd\[51025\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.237  user=root
Feb 17 01:51:14 localhost sshd\[51025\]: Failed password for root from 112.85.42.237 port 26927 ssh2
Feb 17 01:51:18 localhost sshd\[51025\]: Failed password for root from 112.85.42.237 port 26927 ssh2
Feb 17 01:54:51 localhost sshd\[51055\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.237  user=root
Feb 17 01:54:53 localhost sshd\[51055\]: Failed password for root from 112.85.42.237 port 12543 ssh2
...
2020-02-17 10:00:32
128.199.161.98 attackspambots
Automatic report - XMLRPC Attack
2020-02-17 10:25:41
186.153.138.2 attackspam
Invalid user ruzycki from 186.153.138.2 port 55310
2020-02-17 10:14:15

Recently Reported IPs

104.129.3.133 104.129.206.72 104.129.36.123 104.129.27.36
104.129.255.172 104.129.36.181 104.129.41.14 104.129.41.21
104.129.41.110 104.129.41.32 104.129.41.43 104.129.41.5
104.129.41.50 104.129.41.47 104.129.41.54 104.129.41.30
104.129.41.90 104.129.41.58 104.129.41.81 104.129.41.60