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

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.229
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 63630
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.129.3.229.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Apr 01 22:50:39 CST 2022
;; MSG SIZE  rcvd: 106
Host info
229.3.129.104.in-addr.arpa domain name pointer 104.129.3.229.static.quadranet.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
229.3.129.104.in-addr.arpa	name = 104.129.3.229.static.quadranet.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
69.28.235.203 attackbots
Failed password for root from 69.28.235.203 port 39977 ssh2
pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.28.235.203 
Failed password for invalid user fdy from 69.28.235.203 port 48564 ssh2
2020-03-10 01:11:42
175.24.107.68 attackbotsspam
2020-03-09T14:26:54.044759randservbullet-proofcloud-66.localdomain sshd[30645]: Invalid user hadoop from 175.24.107.68 port 57948
2020-03-09T14:26:54.052074randservbullet-proofcloud-66.localdomain sshd[30645]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.24.107.68
2020-03-09T14:26:54.044759randservbullet-proofcloud-66.localdomain sshd[30645]: Invalid user hadoop from 175.24.107.68 port 57948
2020-03-09T14:26:56.277443randservbullet-proofcloud-66.localdomain sshd[30645]: Failed password for invalid user hadoop from 175.24.107.68 port 57948 ssh2
...
2020-03-10 01:03:01
124.158.183.18 attackbots
$f2bV_matches
2020-03-10 00:54:27
211.252.87.37 attackspambots
(sshd) Failed SSH login from 211.252.87.37 (KR/South Korea/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Mar  9 16:49:19 amsweb01 sshd[32496]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.252.87.37  user=root
Mar  9 16:49:22 amsweb01 sshd[32496]: Failed password for root from 211.252.87.37 port 58064 ssh2
Mar  9 17:00:11 amsweb01 sshd[962]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.252.87.37  user=root
Mar  9 17:00:13 amsweb01 sshd[962]: Failed password for root from 211.252.87.37 port 42440 ssh2
Mar  9 17:03:27 amsweb01 sshd[1229]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.252.87.37  user=root
2020-03-10 00:52:08
157.230.47.241 attackspam
$f2bV_matches
2020-03-10 01:26:36
118.24.151.90 attack
Mar  9 17:48:40 vserver sshd\[13155\]: Invalid user ftpuser from 118.24.151.90Mar  9 17:48:43 vserver sshd\[13155\]: Failed password for invalid user ftpuser from 118.24.151.90 port 43884 ssh2Mar  9 17:55:36 vserver sshd\[13189\]: Invalid user postgres from 118.24.151.90Mar  9 17:55:39 vserver sshd\[13189\]: Failed password for invalid user postgres from 118.24.151.90 port 42038 ssh2
...
2020-03-10 01:12:58
61.189.43.58 attackspambots
Mar  9 17:52:10 vps691689 sshd[17175]: Failed password for root from 61.189.43.58 port 43328 ssh2
Mar  9 17:57:51 vps691689 sshd[17244]: Failed password for root from 61.189.43.58 port 43608 ssh2
...
2020-03-10 01:13:49
1.186.57.150 attackspam
Mar  9 09:55:02 ws19vmsma01 sshd[168784]: Failed password for root from 1.186.57.150 port 58034 ssh2
...
2020-03-10 00:59:26
222.186.31.83 attackspambots
Mar  9 12:44:14 plusreed sshd[32498]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.83  user=root
Mar  9 12:44:16 plusreed sshd[32498]: Failed password for root from 222.186.31.83 port 17502 ssh2
...
2020-03-10 00:44:39
192.241.222.142 attackspambots
port scan and connect, tcp 3306 (mysql)
2020-03-10 00:59:59
189.132.86.176 attackbotsspam
Mar  9 13:27:56 debian-2gb-nbg1-2 kernel: \[6016027.764928\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=189.132.86.176 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=50 ID=45255 PROTO=TCP SPT=50648 DPT=23 WINDOW=26975 RES=0x00 SYN URGP=0
2020-03-10 00:40:55
168.243.91.19 attackspam
$f2bV_matches
2020-03-10 00:43:12
91.81.95.143 attack
Scan detected and blocked 2020.03.09 13:27:26
2020-03-10 01:06:50
106.75.10.4 attackspam
Mar  9 17:52:44 v22018086721571380 sshd[21854]: Failed password for invalid user mapred from 106.75.10.4 port 45092 ssh2
2020-03-10 01:21:05
140.207.46.136 attackspam
Mar  9 14:40:57 XXX sshd[28883]: Invalid user DUP from 140.207.46.136 port 33604
2020-03-10 01:14:51

Recently Reported IPs

104.129.3.228 178.195.71.159 104.129.3.230 104.129.3.234
104.129.3.252 104.129.46.49 104.129.46.55 104.129.55.87
104.129.56.11 104.129.56.140 104.129.56.144 104.129.56.153
104.129.56.5 104.129.8.190 104.129.9.15 104.129.9.31
104.129.9.4 104.13.55.110 104.130.11.24 114.43.44.202