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
197.60.153.190 attackspam
1599929951 - 09/12/2020 23:59:11 Host: host-197.60.153.190.tedata.net/197.60.153.190 Port: 23 TCP Blocked
...
2020-09-13 21:13:57
117.50.1.138 attackbotsspam
Sep 12 04:28:49 ns sshd[12203]: Connection from 117.50.1.138 port 33884 on 134.119.39.98 port 22
Sep 12 04:28:51 ns sshd[12203]: User r.r from 117.50.1.138 not allowed because not listed in AllowUsers
Sep 12 04:28:51 ns sshd[12203]: Failed password for invalid user r.r from 117.50.1.138 port 33884 ssh2
Sep 12 04:28:52 ns sshd[12203]: Received disconnect from 117.50.1.138 port 33884:11: Bye Bye [preauth]
Sep 12 04:28:52 ns sshd[12203]: Disconnected from 117.50.1.138 port 33884 [preauth]
Sep 12 04:41:51 ns sshd[7344]: Connection from 117.50.1.138 port 53482 on 134.119.39.98 port 22
Sep 12 04:41:54 ns sshd[7344]: User r.r from 117.50.1.138 not allowed because not listed in AllowUsers
Sep 12 04:41:54 ns sshd[7344]: Failed password for invalid user r.r from 117.50.1.138 port 53482 ssh2
Sep 12 04:41:54 ns sshd[7344]: Received disconnect from 117.50.1.138 port 53482:11: Bye Bye [preauth]
Sep 12 04:41:54 ns sshd[7344]: Disconnected from 117.50.1.138 port 53482 [preauth]
Sep 12 ........
-------------------------------
2020-09-13 20:50:02
182.180.128.134 attackspambots
(sshd) Failed SSH login from 182.180.128.134 (PK/Pakistan/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep 13 07:35:12 optimus sshd[7020]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.180.128.134  user=root
Sep 13 07:35:14 optimus sshd[7020]: Failed password for root from 182.180.128.134 port 51962 ssh2
Sep 13 07:43:34 optimus sshd[9310]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.180.128.134  user=root
Sep 13 07:43:36 optimus sshd[9310]: Failed password for root from 182.180.128.134 port 43796 ssh2
Sep 13 07:48:17 optimus sshd[10820]: Invalid user server from 182.180.128.134
2020-09-13 21:02:30
104.144.170.32 attack
Registration form abuse
2020-09-13 21:04:28
222.186.175.182 attackspam
Sep 13 13:53:49 mavik sshd[13739]: Failed password for root from 222.186.175.182 port 35282 ssh2
Sep 13 13:53:52 mavik sshd[13739]: Failed password for root from 222.186.175.182 port 35282 ssh2
Sep 13 13:53:57 mavik sshd[13739]: Failed password for root from 222.186.175.182 port 35282 ssh2
Sep 13 13:54:00 mavik sshd[13739]: Failed password for root from 222.186.175.182 port 35282 ssh2
Sep 13 13:54:03 mavik sshd[13739]: Failed password for root from 222.186.175.182 port 35282 ssh2
...
2020-09-13 20:56:40
5.182.210.205 attackspambots
[N10.H2.VM2] Port Scanner Detected Blocked by UFW
2020-09-13 20:48:54
93.56.47.242 attackspam
93.56.47.242 - - [13/Sep/2020:11:56:28 +0100] "POST /wp-login.php HTTP/1.1" 200 1874 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
93.56.47.242 - - [13/Sep/2020:11:56:29 +0100] "POST /wp-login.php HTTP/1.1" 200 1877 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
93.56.47.242 - - [13/Sep/2020:11:56:30 +0100] "POST /wp-login.php HTTP/1.1" 200 1874 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-09-13 20:51:42
101.6.133.27 attackspam
Banned for a week because repeated abuses, for example SSH, but not only
2020-09-13 21:01:00
45.141.84.99 attackbotsspam
 TCP (SYN) 45.141.84.99:40464 -> port 33392, len 44
2020-09-13 20:57:11
40.117.73.218 attackspambots
BURG,WP GET /wp-includes/wlwmanifest.xml
2020-09-13 20:50:18
191.119.188.46 attackspam
1599929944 - 09/12/2020 18:59:04 Host: 191.119.188.46/191.119.188.46 Port: 445 TCP Blocked
2020-09-13 21:20:18
181.191.241.6 attack
(sshd) Failed SSH login from 181.191.241.6 (BR/Brazil/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep 13 07:00:18 server sshd[13931]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.191.241.6  user=root
Sep 13 07:00:20 server sshd[13931]: Failed password for root from 181.191.241.6 port 59285 ssh2
Sep 13 07:06:06 server sshd[15486]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.191.241.6  user=root
Sep 13 07:06:08 server sshd[15486]: Failed password for root from 181.191.241.6 port 36556 ssh2
Sep 13 07:08:08 server sshd[16368]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.191.241.6  user=root
2020-09-13 21:16:06
106.13.99.107 attackspambots
Sep 13 08:21:21 george sshd[28987]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.99.107  user=root
Sep 13 08:21:24 george sshd[28987]: Failed password for root from 106.13.99.107 port 51700 ssh2
Sep 13 08:26:08 george sshd[30645]: Invalid user aster from 106.13.99.107 port 56496
Sep 13 08:26:08 george sshd[30645]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.99.107 
Sep 13 08:26:10 george sshd[30645]: Failed password for invalid user aster from 106.13.99.107 port 56496 ssh2
...
2020-09-13 21:20:38
66.37.4.162 attackspam
SSH/22 MH Probe, BF, Hack -
2020-09-13 20:40:10
218.92.0.249 attackbots
SSH brutforce
2020-09-13 20:41: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