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
51.68.71.239 attackspambots
Sep 18 20:05:54 web9 sshd\[31550\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.68.71.239  user=root
Sep 18 20:05:56 web9 sshd\[31550\]: Failed password for root from 51.68.71.239 port 60500 ssh2
Sep 18 20:09:48 web9 sshd\[32067\]: Invalid user deployer from 51.68.71.239
Sep 18 20:09:48 web9 sshd\[32067\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.68.71.239
Sep 18 20:09:50 web9 sshd\[32067\]: Failed password for invalid user deployer from 51.68.71.239 port 38158 ssh2
2020-09-19 14:15:10
46.32.252.149 attack
Invalid user dbseller from 46.32.252.149 port 50110
2020-09-19 14:25:25
222.128.17.92 attack
2020-09-18T22:21:09.456491yoshi.linuxbox.ninja sshd[4114767]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.128.17.92
2020-09-18T22:21:09.450296yoshi.linuxbox.ninja sshd[4114767]: Invalid user admin from 222.128.17.92 port 48222
2020-09-18T22:21:11.679714yoshi.linuxbox.ninja sshd[4114767]: Failed password for invalid user admin from 222.128.17.92 port 48222 ssh2
...
2020-09-19 14:16:51
112.166.133.216 attack
Invalid user rustserver from 112.166.133.216 port 48166
2020-09-19 14:00:25
31.163.165.165 attackbotsspam
20/9/18@13:01:42: FAIL: IoT-Telnet address from=31.163.165.165
...
2020-09-19 14:21:34
152.32.229.54 attack
Sep 18 19:20:23 hpm sshd\[13166\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.32.229.54  user=root
Sep 18 19:20:24 hpm sshd\[13166\]: Failed password for root from 152.32.229.54 port 33272 ssh2
Sep 18 19:24:54 hpm sshd\[13549\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.32.229.54  user=root
Sep 18 19:24:55 hpm sshd\[13549\]: Failed password for root from 152.32.229.54 port 44966 ssh2
Sep 18 19:29:28 hpm sshd\[13995\]: Invalid user git from 152.32.229.54
2020-09-19 13:56:53
159.192.143.249 attack
2020-09-19T07:27:47.463088cyberdyne sshd[522654]: Failed password for invalid user admin from 159.192.143.249 port 32950 ssh2
2020-09-19T07:31:33.318296cyberdyne sshd[524395]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.192.143.249  user=root
2020-09-19T07:31:35.640844cyberdyne sshd[524395]: Failed password for root from 159.192.143.249 port 54392 ssh2
2020-09-19T07:33:49.822478cyberdyne sshd[524483]: Invalid user test from 159.192.143.249 port 33262
...
2020-09-19 14:15:36
168.70.55.201 attackspambots
Sep 18 19:12:22 ssh2 sshd[30431]: Invalid user support from 168.70.55.201 port 57969
Sep 18 19:12:22 ssh2 sshd[30431]: Failed password for invalid user support from 168.70.55.201 port 57969 ssh2
Sep 18 19:12:22 ssh2 sshd[30431]: Connection closed by invalid user support 168.70.55.201 port 57969 [preauth]
...
2020-09-19 13:56:22
104.244.75.157 attackspam
Sep 19 05:41:45 vpn01 sshd[11258]: Failed password for root from 104.244.75.157 port 44123 ssh2
Sep 19 05:41:47 vpn01 sshd[11258]: Failed password for root from 104.244.75.157 port 44123 ssh2
...
2020-09-19 14:10:35
96.82.91.33 attackspam
(sshd) Failed SSH login from 96.82.91.33 (US/United States/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep 19 00:23:21 server5 sshd[17834]: Invalid user admin from 96.82.91.33
Sep 19 00:23:23 server5 sshd[17834]: Failed password for invalid user admin from 96.82.91.33 port 60887 ssh2
Sep 19 00:23:24 server5 sshd[17907]: Invalid user admin from 96.82.91.33
Sep 19 00:23:27 server5 sshd[17907]: Failed password for invalid user admin from 96.82.91.33 port 60905 ssh2
Sep 19 00:23:27 server5 sshd[17915]: Invalid user admin from 96.82.91.33
2020-09-19 14:23:59
54.169.202.194 attackspambots
54.169.202.194 - - [19/Sep/2020:06:41:06 +0100] "POST /wp-login.php HTTP/1.1" 200 2208 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
54.169.202.194 - - [19/Sep/2020:06:41:09 +0100] "POST /wp-login.php HTTP/1.1" 200 2205 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
54.169.202.194 - - [19/Sep/2020:06:41:10 +0100] "POST /xmlrpc.php HTTP/1.1" 200 247 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-09-19 14:09:43
160.238.26.21 attackbotsspam
Unauthorized connection attempt from IP address 160.238.26.21 on Port 445(SMB)
2020-09-19 13:48:18
178.176.174.164 attack
(smtpauth) Failed SMTP AUTH login from 178.176.174.164 (RU/Russia/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-09-19 08:23:51 login authenticator failed for (localhost.localdomain) [178.176.174.164]: 535 Incorrect authentication data (set_id=service@goltexgroup.com)
2020-09-19 14:20:22
218.250.210.68 attack
Sep 18 17:46:26 scw-focused-cartwright sshd[29956]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.250.210.68
Sep 18 17:46:28 scw-focused-cartwright sshd[29956]: Failed password for invalid user admin from 218.250.210.68 port 60478 ssh2
2020-09-19 13:56:00
45.138.74.77 attackbotsspam
From: "Crypto Software" <AGxEiP@upc.at>
Subject: Wie man sich Cash verdienen!
Date: Thu, 17 Sep 2020 05:09:01 +0200
2020-09-19 14:12:16

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