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

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

;; QUESTION SECTION:
;169.229.24.164.			IN	A

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

;; Query time: 69 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jun 24 20:10:25 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 164.24.229.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 164.24.229.169.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
176.107.241.112 attack
Telnetd brute force attack detected by fail2ban
2020-02-23 01:08:58
193.31.40.36 attackspambots
firewall-block, port(s): 389/tcp
2020-02-23 01:43:41
47.92.197.187 attackbots
suspicious action Sat, 22 Feb 2020 13:51:10 -0300
2020-02-23 01:06:39
221.215.141.170 attack
suspicious action Sat, 22 Feb 2020 13:51:18 -0300
2020-02-23 00:59:49
198.12.156.154 attackbots
A Potential Directory Traversal Attempt returned code 200 (success).
2020-02-23 01:15:11
123.206.134.27 attackbotsspam
Feb 22 17:47:36 MainVPS sshd[10882]: Invalid user smbuser from 123.206.134.27 port 43024
Feb 22 17:47:36 MainVPS sshd[10882]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.206.134.27
Feb 22 17:47:36 MainVPS sshd[10882]: Invalid user smbuser from 123.206.134.27 port 43024
Feb 22 17:47:38 MainVPS sshd[10882]: Failed password for invalid user smbuser from 123.206.134.27 port 43024 ssh2
Feb 22 17:51:09 MainVPS sshd[17721]: Invalid user sonar from 123.206.134.27 port 38156
...
2020-02-23 01:06:05
182.76.31.227 attack
1582390267 - 02/22/2020 17:51:07 Host: 182.76.31.227/182.76.31.227 Port: 445 TCP Blocked
2020-02-23 01:06:55
185.92.70.87 attackbotsspam
" "
2020-02-23 01:23:15
5.253.144.66 attackbotsspam
suspicious action Sat, 22 Feb 2020 13:50:43 -0300
2020-02-23 01:28:08
80.184.232.80 attack
Port probing on unauthorized port 23
2020-02-23 01:36:50
121.185.211.78 attack
Unauthorized connection attempt detected from IP address 121.185.211.78 to port 23
2020-02-23 01:35:40
112.85.42.178 attack
Feb 22 18:34:20 dedicated sshd[8492]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.178  user=root
Feb 22 18:34:22 dedicated sshd[8492]: Failed password for root from 112.85.42.178 port 42651 ssh2
2020-02-23 01:38:23
220.116.21.225 attackbotsspam
firewall-block, port(s): 23/tcp
2020-02-23 01:41:22
51.83.77.224 attack
Feb 22 17:50:22 serwer sshd\[26458\]: User ftpuser from 51.83.77.224 not allowed because not listed in AllowUsers
Feb 22 17:50:22 serwer sshd\[26458\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.83.77.224  user=ftpuser
Feb 22 17:50:24 serwer sshd\[26458\]: Failed password for invalid user ftpuser from 51.83.77.224 port 49838 ssh2
...
2020-02-23 01:40:20
5.39.86.52 attack
Invalid user tkissftp from 5.39.86.52 port 57808
2020-02-23 01:38:45

Recently Reported IPs

169.229.24.138 169.229.24.193 169.229.24.237 169.229.24.253
169.229.25.45 169.229.25.94 169.229.25.122 169.229.25.151
169.229.26.28 47.111.130.92 137.226.6.53 137.226.10.131
169.229.91.222 137.226.144.65 137.226.95.37 169.229.25.60
137.226.237.35 169.229.24.67 169.229.24.151 169.229.24.225