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

;; QUESTION SECTION:
;169.101.150.214.		IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 22 19:14:11 CST 2025
;; MSG SIZE  rcvd: 108
Host info
Host 214.150.101.169.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 214.150.101.169.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
213.32.67.160 attack
Invalid user joan from 213.32.67.160 port 36298
2020-01-19 00:48:39
46.38.144.179 attack
Jan 18 17:41:34 relay postfix/smtpd\[3926\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan 18 17:42:08 relay postfix/smtpd\[6491\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan 18 17:42:22 relay postfix/smtpd\[3790\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan 18 17:42:57 relay postfix/smtpd\[9270\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan 18 17:43:14 relay postfix/smtpd\[3413\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-01-19 00:45:20
45.32.28.219 attackbots
Unauthorized connection attempt detected from IP address 45.32.28.219 to port 2220 [J]
2020-01-19 00:46:04
116.105.221.111 attackbotsspam
20/1/18@07:59:22: FAIL: Alarm-Network address from=116.105.221.111
20/1/18@07:59:22: FAIL: Alarm-Network address from=116.105.221.111
...
2020-01-19 00:33:53
178.123.107.70 attackbots
Invalid user admin from 178.123.107.70 port 58341
2020-01-19 00:55:43
94.9.63.175 attackspambots
Invalid user bata from 94.9.63.175 port 43516
2020-01-19 00:41:36
154.8.209.24 attack
Invalid user ddd from 154.8.209.24 port 53006
2020-01-19 01:00:40
68.48.240.245 attackbotsspam
Unauthorized connection attempt detected from IP address 68.48.240.245 to port 2220 [J]
2020-01-19 00:43:51
129.158.74.141 attackspam
Invalid user gb from 129.158.74.141 port 36153
2020-01-19 00:31:29
62.234.154.222 attackbotsspam
Unauthorized connection attempt detected from IP address 62.234.154.222 to port 2220 [J]
2020-01-19 00:44:22
107.172.2.203 attack
Unauthorized connection attempt detected from IP address 107.172.2.203 to port 2220 [J]
2020-01-19 00:35:58
181.48.29.35 attackspam
Unauthorized connection attempt detected from IP address 181.48.29.35 to port 2220 [J]
2020-01-19 00:55:09
132.232.113.102 attack
Unauthorized connection attempt detected from IP address 132.232.113.102 to port 2220 [J]
2020-01-19 01:03:20
148.63.53.51 attack
Invalid user guest from 148.63.53.51 port 47490
2020-01-19 00:29:47
122.116.12.110 attackspam
Unauthorized connection attempt detected from IP address 122.116.12.110 to port 2220 [J]
2020-01-19 00:32:08

Recently Reported IPs

85.48.51.67 255.191.61.24 253.162.91.21 234.28.72.240
73.144.103.71 200.209.131.86 223.25.79.121 53.170.127.10
32.142.86.79 236.103.68.9 194.190.226.191 81.67.27.105
245.215.7.45 222.111.81.156 71.158.107.68 74.121.241.182
50.225.76.57 49.168.34.244 89.18.216.60 14.202.14.138