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

Region: New York

Country: United States

Internet Service Provider: Verizon

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 108.29.239.139
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8927
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;108.29.239.139.			IN	A

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

;; Query time: 66 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jun 05 14:44:35 CST 2024
;; MSG SIZE  rcvd: 107
Host info
139.239.29.108.in-addr.arpa domain name pointer pool-108-29-239-139.nycmny.east.verizon.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
139.239.29.108.in-addr.arpa	name = pool-108-29-239-139.nycmny.east.verizon.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
49.233.180.151 attackspam
SSH Brute Force
2020-04-01 19:13:57
194.204.194.11 attackbots
SSH brute force attempt
2020-04-01 19:06:23
194.5.52.17 attackspambots
Unauthorized access to hidden resource
2020-04-01 19:16:58
129.204.240.42 attack
2020-04-01T12:21:18.805234vps773228.ovh.net sshd[22832]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.240.42
2020-04-01T12:21:18.789868vps773228.ovh.net sshd[22832]: Invalid user suruiqiang from 129.204.240.42 port 53002
2020-04-01T12:21:20.653079vps773228.ovh.net sshd[22832]: Failed password for invalid user suruiqiang from 129.204.240.42 port 53002 ssh2
2020-04-01T12:27:35.443219vps773228.ovh.net sshd[25139]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.240.42  user=root
2020-04-01T12:27:37.045507vps773228.ovh.net sshd[25139]: Failed password for root from 129.204.240.42 port 35694 ssh2
...
2020-04-01 19:15:33
92.63.194.91 attack
Apr  1 13:11:46 vps647732 sshd[13013]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.63.194.91
Apr  1 13:11:48 vps647732 sshd[13013]: Failed password for invalid user admin from 92.63.194.91 port 41507 ssh2
...
2020-04-01 19:16:40
198.71.241.18 attackbots
xmlrpc attack
2020-04-01 18:53:43
107.174.148.93 attackbots
(From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across drjenniferbrandon.com a few minutes ago.

Looks great… but now what?

By that I mean, when someone like me finds your website – either through Search or just bouncing around – what happens next?  Do you get a lot of leads from your site, or at least enough to make you happy?

Honestly, most business websites fall a bit short when it comes to generating paying customers. Studies show that 70% of a site’s visitors disappear and are gone forever after just a moment.

Here’s an idea…
 
How about making it really EASY for every visitor who shows up to get a personal phone call you as soon as they hit your site…
 
You can –
  
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It signals you the moment they let you know they’re interested – so that you can talk to that lead while they’re literally looking over your site.

CLICK HERE http://www
2020-04-01 18:43:52
101.71.2.165 attackspambots
Apr  1 04:54:40 server1 sshd\[19351\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.71.2.165  user=root
Apr  1 04:54:42 server1 sshd\[19351\]: Failed password for root from 101.71.2.165 port 34802 ssh2
Apr  1 04:57:49 server1 sshd\[20741\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.71.2.165  user=root
Apr  1 04:57:51 server1 sshd\[20741\]: Failed password for root from 101.71.2.165 port 34803 ssh2
Apr  1 05:00:56 server1 sshd\[21723\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.71.2.165  user=root
...
2020-04-01 19:03:37
94.156.238.171 attack
Email address rejected
2020-04-01 18:49:15
168.1.124.238 attackbots
Mar 30 18:45:25 giraffe sshd[12047]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.1.124.238  user=r.r
Mar 30 18:45:26 giraffe sshd[12047]: Failed password for r.r from 168.1.124.238 port 47042 ssh2
Mar 30 18:45:27 giraffe sshd[12047]: Received disconnect from 168.1.124.238 port 47042:11: Bye Bye [preauth]
Mar 30 18:45:27 giraffe sshd[12047]: Disconnected from 168.1.124.238 port 47042 [preauth]
Mar 30 18:52:26 giraffe sshd[12307]: Invalid user ll from 168.1.124.238
Mar 30 18:52:26 giraffe sshd[12307]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.1.124.238
Mar 30 18:52:28 giraffe sshd[12307]: Failed password for invalid user ll from 168.1.124.238 port 53850 ssh2
Mar 30 18:52:29 giraffe sshd[12307]: Received disconnect from 168.1.124.238 port 53850:11: Bye Bye [preauth]
Mar 30 18:52:29 giraffe sshd[12307]: Disconnected from 168.1.124.238 port 53850 [preauth]


........
-----------------------------------------------
htt
2020-04-01 18:37:39
103.129.222.135 attackspambots
Repeated brute force against a port
2020-04-01 19:05:42
186.86.14.33 attack
scan z
2020-04-01 18:43:19
180.76.232.66 attackspam
Apr  1 09:59:39 marvibiene sshd[16717]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.232.66  user=root
Apr  1 09:59:42 marvibiene sshd[16717]: Failed password for root from 180.76.232.66 port 46614 ssh2
Apr  1 10:15:26 marvibiene sshd[17220]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.232.66  user=root
Apr  1 10:15:27 marvibiene sshd[17220]: Failed password for root from 180.76.232.66 port 33296 ssh2
...
2020-04-01 19:17:29
92.63.194.94 attackbots
Apr  1 12:47:53 debian64 sshd[16432]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.63.194.94 
Apr  1 12:47:55 debian64 sshd[16432]: Failed password for invalid user admin from 92.63.194.94 port 33139 ssh2
...
2020-04-01 18:48:03
148.70.68.175 attack
Apr  1 08:12:11 srv01 sshd[17791]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.68.175  user=root
Apr  1 08:12:12 srv01 sshd[17791]: Failed password for root from 148.70.68.175 port 52856 ssh2
Apr  1 08:15:42 srv01 sshd[17979]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.68.175  user=root
Apr  1 08:15:43 srv01 sshd[17979]: Failed password for root from 148.70.68.175 port 60936 ssh2
Apr  1 08:19:00 srv01 sshd[18134]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.68.175  user=root
Apr  1 08:19:02 srv01 sshd[18134]: Failed password for root from 148.70.68.175 port 40782 ssh2
...
2020-04-01 19:10:45

Recently Reported IPs

128.240.4.33 194.170.36.3 180.53.164.191 132.101.52.109
213.237.54.53 180.236.193.43 107.236.164.97 140.85.98.117
42.117.117.183 255.91.241.15 79.220.89.164 9.115.179.77
58.98.47.23 162.250.123.243 158.215.240.188 175.252.230.107
85.182.106.0 242.208.85.191 241.87.77.59 221.47.140.49