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 of America (the)

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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 50.39.114.234
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 199
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;50.39.114.234.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 04 15:44:34 CST 2025
;; MSG SIZE  rcvd: 106
Host info
234.114.39.50.in-addr.arpa domain name pointer 50-39-114-234.bvtn.or.ptr.ziplyfiber.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
234.114.39.50.in-addr.arpa	name = 50-39-114-234.bvtn.or.ptr.ziplyfiber.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.13.233.83 attackspambots
Feb  3 21:04:44 v22018076622670303 sshd\[7231\]: Invalid user changeme` from 106.13.233.83 port 50122
Feb  3 21:04:44 v22018076622670303 sshd\[7231\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.233.83
Feb  3 21:04:46 v22018076622670303 sshd\[7231\]: Failed password for invalid user changeme` from 106.13.233.83 port 50122 ssh2
...
2020-02-04 04:10:53
79.244.167.16 attack
Unauthorized connection attempt detected from IP address 79.244.167.16 to port 8000 [J]
2020-02-04 03:56:57
201.143.205.206 attackspam
Unauthorized connection attempt detected from IP address 201.143.205.206 to port 80 [J]
2020-02-04 04:25:13
27.109.133.181 attackbotsspam
Unauthorized connection attempt detected from IP address 27.109.133.181 to port 5555 [J]
2020-02-04 04:20:47
27.42.109.252 attackspambots
Unauthorized connection attempt detected from IP address 27.42.109.252 to port 1433 [J]
2020-02-04 04:21:18
139.212.172.170 attackbots
Unauthorized connection attempt detected from IP address 139.212.172.170 to port 1433 [J]
2020-02-04 04:32:59
190.94.139.61 attackspam
Unauthorized connection attempt detected from IP address 190.94.139.61 to port 80 [J]
2020-02-04 04:27:37
124.156.241.4 attackbots
Unauthorized connection attempt detected from IP address 124.156.241.4 to port 2095 [J]
2020-02-04 04:35:02
52.38.219.1 attackspambots
Unauthorized connection attempt detected from IP address 52.38.219.1 to port 3389 [J]
2020-02-04 04:18:00
37.187.72.155 attackspam
Unauthorized connection attempt detected from IP address 37.187.72.155 to port 8001 [J]
2020-02-04 04:19:31
88.241.116.244 attackspambots
Unauthorized connection attempt detected from IP address 88.241.116.244 to port 23 [J]
2020-02-04 04:13:41
49.232.23.127 attackspam
Unauthorized connection attempt detected from IP address 49.232.23.127 to port 2220 [J]
2020-02-04 03:58:53
169.255.196.156 attack
Unauthorized connection attempt detected from IP address 169.255.196.156 to port 2220 [J]
2020-02-04 04:31:53
200.59.118.132 attackspam
Unauthorized connection attempt detected from IP address 200.59.118.132 to port 5358 [J]
2020-02-04 04:26:20
103.47.218.40 attackbots
Unauthorized connection attempt detected from IP address 103.47.218.40 to port 8080 [J]
2020-02-04 04:12:21

Recently Reported IPs

62.90.20.164 114.3.129.27 239.5.202.135 161.50.82.232
58.96.125.157 82.102.161.171 231.126.151.15 5.114.13.107
146.33.72.41 96.196.63.133 126.228.58.102 89.56.20.231
138.171.242.226 68.134.151.40 69.60.164.91 127.76.26.120
17.184.51.191 39.11.27.229 86.221.4.51 227.22.38.104