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

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 <<>> 150.50.161.243
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21416
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;150.50.161.243.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 21 03:10:02 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 243.161.50.150.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 243.161.50.150.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
62.234.122.141 attackspam
Dec 30 15:36:46 pi sshd\[3107\]: Invalid user fulvia from 62.234.122.141 port 60712
Dec 30 15:36:46 pi sshd\[3107\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.122.141
Dec 30 15:36:48 pi sshd\[3107\]: Failed password for invalid user fulvia from 62.234.122.141 port 60712 ssh2
Dec 30 15:40:39 pi sshd\[3236\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.122.141  user=root
Dec 30 15:40:42 pi sshd\[3236\]: Failed password for root from 62.234.122.141 port 43712 ssh2
...
2019-12-30 23:52:52
87.106.157.50 attack
Unrelenting attack on my site.
2019-12-31 00:00:40
167.114.103.140 attackspambots
Dec 30 17:05:54 lnxded64 sshd[16325]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.103.140
2019-12-31 00:10:54
187.49.70.22 attack
Unauthorized connection attempt from IP address 187.49.70.22 on Port 445(SMB)
2019-12-30 23:29:08
190.37.27.83 attackspambots
Unauthorized connection attempt from IP address 190.37.27.83 on Port 445(SMB)
2019-12-30 23:24:44
183.83.145.86 attackbotsspam
Unauthorized connection attempt from IP address 183.83.145.86 on Port 445(SMB)
2019-12-30 23:50:25
116.97.46.28 attack
Unauthorized connection attempt from IP address 116.97.46.28 on Port 445(SMB)
2019-12-30 23:34:54
123.25.204.197 attackspam
Attempt to attack host OS, exploiting network vulnerabilities, on 30-12-2019 14:45:09.
2019-12-31 00:00:14
51.77.211.94 attack
--- report ---
Dec 30 12:32:35 -0300 sshd: Connection from 51.77.211.94 port 55114
2019-12-30 23:53:16
118.24.7.98 attack
--- report ---
Dec 30 11:35:04 -0300 sshd: Connection from 118.24.7.98 port 39318
Dec 30 11:35:06 -0300 sshd: Invalid user sybase from 118.24.7.98
Dec 30 11:35:09 -0300 sshd: Failed password for invalid user sybase from 118.24.7.98 port 39318 ssh2
Dec 30 11:35:10 -0300 sshd: Received disconnect from 118.24.7.98: 11: Bye Bye [preauth]
2019-12-30 23:41:14
106.51.140.146 attackspambots
Unauthorized connection attempt from IP address 106.51.140.146 on Port 445(SMB)
2019-12-30 23:32:17
163.172.204.185 attack
SSH auth scanning - multiple failed logins
2019-12-30 23:33:09
220.133.253.149 attackbots
Shenzhen TVT DVR Remote Code Execution Vulnerability
2019-12-30 23:47:43
49.231.176.19 attack
Unauthorized connection attempt from IP address 49.231.176.19 on Port 445(SMB)
2019-12-30 23:35:23
104.248.205.67 attack
"SSH brute force auth login attempt."
2019-12-31 00:11:10

Recently Reported IPs

27.204.220.95 128.122.96.247 177.5.15.210 234.155.215.224
189.123.28.84 93.195.54.48 152.136.224.146 213.11.99.242
114.247.106.116 69.143.133.193 240.63.36.250 70.146.188.127
103.42.55.238 60.184.232.65 209.43.19.172 243.67.124.255
75.50.226.223 236.64.87.102 97.213.202.115 20.99.221.146