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

;; QUESTION SECTION:
;104.129.3.212.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 08 04:21:02 CST 2022
;; MSG SIZE  rcvd: 106
Host info
212.3.129.104.in-addr.arpa domain name pointer 104.129.3.212.static.quadranet.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
212.3.129.104.in-addr.arpa	name = 104.129.3.212.static.quadranet.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
81.213.214.225 attackspambots
Dec 10 07:17:14 h2177944 sshd\[17808\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.213.214.225  user=news
Dec 10 07:17:15 h2177944 sshd\[17808\]: Failed password for news from 81.213.214.225 port 33090 ssh2
Dec 10 07:43:42 h2177944 sshd\[19044\]: Invalid user archer from 81.213.214.225 port 52364
Dec 10 07:43:42 h2177944 sshd\[19044\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.213.214.225
...
2019-12-10 15:16:33
111.93.246.171 attack
Dec 10 07:01:10 localhost sshd\[119449\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.93.246.171  user=root
Dec 10 07:01:12 localhost sshd\[119449\]: Failed password for root from 111.93.246.171 port 46570 ssh2
Dec 10 07:07:34 localhost sshd\[119661\]: Invalid user admin from 111.93.246.171 port 58808
Dec 10 07:07:34 localhost sshd\[119661\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.93.246.171
Dec 10 07:07:36 localhost sshd\[119661\]: Failed password for invalid user admin from 111.93.246.171 port 58808 ssh2
...
2019-12-10 15:23:53
222.186.175.140 attackbots
Dec 10 04:28:44 firewall sshd[23164]: Failed password for root from 222.186.175.140 port 29164 ssh2
Dec 10 04:28:54 firewall sshd[23164]: error: maximum authentication attempts exceeded for root from 222.186.175.140 port 29164 ssh2 [preauth]
Dec 10 04:28:54 firewall sshd[23164]: Disconnecting: Too many authentication failures [preauth]
...
2019-12-10 15:36:14
89.234.181.24 attackbotsspam
SSH Bruteforce attempt
2019-12-10 15:34:19
118.89.237.20 attackspambots
Dec 10 08:32:10 legacy sshd[23372]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.89.237.20
Dec 10 08:32:12 legacy sshd[23372]: Failed password for invalid user admin from 118.89.237.20 port 39470 ssh2
Dec 10 08:39:52 legacy sshd[23685]: Failed password for root from 118.89.237.20 port 38148 ssh2
...
2019-12-10 15:44:24
187.75.158.1 attack
Dec 10 07:58:14 sd-53420 sshd\[23523\]: Invalid user yoyo from 187.75.158.1
Dec 10 07:58:14 sd-53420 sshd\[23523\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.75.158.1
Dec 10 07:58:16 sd-53420 sshd\[23523\]: Failed password for invalid user yoyo from 187.75.158.1 port 54462 ssh2
Dec 10 08:07:22 sd-53420 sshd\[24970\]: Invalid user lanzillotta from 187.75.158.1
Dec 10 08:07:22 sd-53420 sshd\[24970\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.75.158.1
...
2019-12-10 15:21:52
159.65.13.203 attackbots
2019-12-09T23:31:02.678322-07:00 suse-nuc sshd[24886]: Invalid user sill from 159.65.13.203 port 52403
...
2019-12-10 15:10:13
83.52.139.230 attack
Dec 10 07:55:25 [host] sshd[25036]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.52.139.230  user=root
Dec 10 07:55:27 [host] sshd[25036]: Failed password for root from 83.52.139.230 port 53283 ssh2
Dec 10 08:01:21 [host] sshd[25224]: Invalid user lares from 83.52.139.230
2019-12-10 15:24:47
104.236.2.45 attack
Dec  9 21:26:38 php1 sshd\[16595\]: Invalid user sourin from 104.236.2.45
Dec  9 21:26:38 php1 sshd\[16595\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.236.2.45
Dec  9 21:26:40 php1 sshd\[16595\]: Failed password for invalid user sourin from 104.236.2.45 port 50804 ssh2
Dec  9 21:31:37 php1 sshd\[17259\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.236.2.45  user=root
Dec  9 21:31:38 php1 sshd\[17259\]: Failed password for root from 104.236.2.45 port 59012 ssh2
2019-12-10 15:45:55
146.185.181.64 attackbots
Dec 10 07:25:06 * sshd[3539]: Failed password for sshd from 146.185.181.64 port 59305 ssh2
2019-12-10 15:11:24
185.200.118.48 attackbots
1575963442 - 12/10/2019 08:37:22 Host: 185.200.118.48/185.200.118.48 Port: 1080 TCP Blocked
2019-12-10 15:39:28
54.36.189.198 attackspam
Dec 10 08:31:11 OPSO sshd\[8151\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.36.189.198  user=root
Dec 10 08:31:14 OPSO sshd\[8151\]: Failed password for root from 54.36.189.198 port 57003 ssh2
Dec 10 08:36:26 OPSO sshd\[9521\]: Invalid user server from 54.36.189.198 port 62252
Dec 10 08:36:26 OPSO sshd\[9521\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.36.189.198
Dec 10 08:36:28 OPSO sshd\[9521\]: Failed password for invalid user server from 54.36.189.198 port 62252 ssh2
2019-12-10 15:49:48
222.186.180.223 attack
Dec  9 21:28:13 web9 sshd\[13146\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.223  user=root
Dec  9 21:28:14 web9 sshd\[13146\]: Failed password for root from 222.186.180.223 port 18792 ssh2
Dec  9 21:28:31 web9 sshd\[13164\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.223  user=root
Dec  9 21:28:33 web9 sshd\[13164\]: Failed password for root from 222.186.180.223 port 47744 ssh2
Dec  9 21:28:51 web9 sshd\[13208\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.223  user=root
2019-12-10 15:35:36
185.143.223.81 attackbotsspam
Dec 10 08:09:17 h2177944 kernel: \[8836867.731052\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.143.223.81 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=33100 PROTO=TCP SPT=59834 DPT=2632 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 10 08:13:32 h2177944 kernel: \[8837123.279031\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.143.223.81 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=29626 PROTO=TCP SPT=59834 DPT=45387 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 10 08:23:34 h2177944 kernel: \[8837724.659340\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.143.223.81 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=5340 PROTO=TCP SPT=59834 DPT=42098 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 10 08:30:53 h2177944 kernel: \[8838163.503286\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.143.223.81 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=4808 PROTO=TCP SPT=59834 DPT=11219 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 10 08:33:49 h2177944 kernel: \[8838339.230582\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.143.223.81 DST=85.214
2019-12-10 15:40:45
188.166.226.209 attack
Dec 10 07:12:50 zeus sshd[6392]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.226.209 
Dec 10 07:12:52 zeus sshd[6392]: Failed password for invalid user tina from 188.166.226.209 port 38172 ssh2
Dec 10 07:18:39 zeus sshd[6618]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.226.209 
Dec 10 07:18:42 zeus sshd[6618]: Failed password for invalid user apache from 188.166.226.209 port 40466 ssh2
2019-12-10 15:30:45

Recently Reported IPs

45.180.149.59 121.206.182.22 80.39.152.195 201.156.167.228
177.249.169.221 39.128.124.9 186.46.185.248 113.177.127.167
117.28.245.29 175.8.61.150 197.49.173.185 190.80.151.24
2.154.35.156 118.175.244.111 120.242.153.12 36.95.54.114
71.238.87.206 193.142.201.208 78.84.203.220 117.198.168.10