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: Los Angeles

Region: California

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

;; QUESTION SECTION:
;50.1.140.241.			IN	A

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

;; Query time: 83 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 11 04:21:17 CST 2023
;; MSG SIZE  rcvd: 105
Host info
241.140.1.50.in-addr.arpa domain name pointer 50-1-140-241.dsl.dynamic.fusionbroadband.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
241.140.1.50.in-addr.arpa	name = 50-1-140-241.dsl.dynamic.fusionbroadband.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
116.246.21.23 attack
Unauthorized connection attempt detected from IP address 116.246.21.23 to port 2220 [J]
2020-01-24 06:00:23
131.72.222.167 attack
unauthorized connection attempt
2020-01-24 05:44:29
165.22.144.206 attackbots
Jan 23 23:00:45 jupiter sshd[53458]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.144.206
Jan 23 23:00:46 jupiter sshd[53458]: Failed password for invalid user test from 165.22.144.206 port 43234 ssh2
...
2020-01-24 06:08:11
36.189.222.253 attackbotsspam
Jan 23 21:50:08 sip sshd[10165]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.189.222.253
Jan 23 21:50:11 sip sshd[10165]: Failed password for invalid user red5 from 36.189.222.253 port 55533 ssh2
Jan 23 21:52:49 sip sshd[10866]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.189.222.253
2020-01-24 05:29:57
81.23.112.14 attackbots
Unauthorized connection attempt from IP address 81.23.112.14 on Port 445(SMB)
2020-01-24 06:04:45
213.150.206.88 attackbotsspam
Unauthorized connection attempt detected from IP address 213.150.206.88 to port 2220 [J]
2020-01-24 06:07:08
51.91.35.67 attackspambots
Unauthorized connection attempt detected from IP address 51.91.35.67 to port 2220 [J]
2020-01-24 05:50:18
178.17.171.29 attack
Multiple suspicious activities were detected
2020-01-24 05:35:54
45.224.105.120 attackbots
Cluster member 192.168.0.31 (-) said, DENY 45.224.105.120, Reason:[(imapd) Failed IMAP login from 45.224.105.120 (AR/Argentina/-): 1 in the last 3600 secs]
2020-01-24 05:54:17
189.135.193.147 attackbots
$f2bV_matches
2020-01-24 05:59:02
51.68.210.22 attack
Port scan on 2 port(s): 139 445
2020-01-24 05:36:24
142.93.48.216 attackbots
xmlrpc attack
2020-01-24 06:00:00
61.177.172.128 attackspambots
Jan 23 18:51:17 vps46666688 sshd[4112]: Failed password for root from 61.177.172.128 port 63195 ssh2
Jan 23 18:51:29 vps46666688 sshd[4112]: error: maximum authentication attempts exceeded for root from 61.177.172.128 port 63195 ssh2 [preauth]
...
2020-01-24 06:02:40
201.234.178.151 attack
20/1/23@11:02:12: FAIL: Alarm-Network address from=201.234.178.151
20/1/23@11:02:12: FAIL: Alarm-Network address from=201.234.178.151
...
2020-01-24 05:51:39
91.187.48.138 attackspam
DATE:2020-01-23 17:01:27, IP:91.187.48.138, PORT:telnet Telnet brute force auth on honeypot server (epe-honey1-hq)
2020-01-24 06:08:56

Recently Reported IPs

75.203.244.67 77.244.50.158 31.79.128.233 53.186.72.237
198.149.155.185 7.175.113.196 94.73.124.36 227.22.109.110
115.98.229.191 132.248.250.166 212.222.215.118 36.84.60.117
247.76.145.54 175.153.72.206 0.136.173.186 11.97.104.251
41.221.147.80 87.110.91.94 72.26.181.144 231.60.139.241