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

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

;; QUESTION SECTION:
;169.229.54.236.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jun 14 05:15:31 CST 2022
;; MSG SIZE  rcvd: 107
Host info
236.54.229.169.in-addr.arpa domain name pointer dir-t1.calnet.berkeley.edu.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
236.54.229.169.in-addr.arpa	name = dir-t1.calnet.berkeley.edu.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
46.103.48.8 attack
Brute force attempt
2020-01-08 07:42:02
88.242.129.224 attack
Unauthorized connection attempt detected from IP address 88.242.129.224 to port 1022
2020-01-08 07:42:40
192.241.220.228 attackspambots
Unauthorized connection attempt detected from IP address 192.241.220.228 to port 2220 [J]
2020-01-08 08:05:23
80.211.63.23 attackspam
xmlrpc attack
2020-01-08 07:48:52
200.66.39.6 attackspam
Fail2Ban Ban Triggered
2020-01-08 07:51:00
41.141.250.244 attackbotsspam
Unauthorized connection attempt detected from IP address 41.141.250.244 to port 2220 [J]
2020-01-08 07:37:15
52.202.164.136 attackbotsspam
Jan  7 23:25:48 ip-172-31-62-245 sshd\[7804\]: Invalid user lfr from 52.202.164.136\
Jan  7 23:25:51 ip-172-31-62-245 sshd\[7804\]: Failed password for invalid user lfr from 52.202.164.136 port 34948 ssh2\
Jan  7 23:31:00 ip-172-31-62-245 sshd\[7911\]: Invalid user sasha from 52.202.164.136\
Jan  7 23:31:02 ip-172-31-62-245 sshd\[7911\]: Failed password for invalid user sasha from 52.202.164.136 port 50634 ssh2\
Jan  7 23:34:16 ip-172-31-62-245 sshd\[7999\]: Invalid user deployer from 52.202.164.136\
2020-01-08 07:40:57
193.31.24.113 attack
01/08/2020-00:51:40.536282 193.31.24.113 Protocol: 6 ET CHAT IRC PONG response
2020-01-08 08:07:24
68.183.72.40 attackspambots
Jan  7 16:17:10 mail sshd\[13705\]: Invalid user butter from 68.183.72.40
Jan  7 16:17:10 mail sshd\[13705\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.72.40
...
2020-01-08 08:06:05
121.162.60.159 attack
Jan  7 23:04:34 ns4 sshd[3484]: Invalid user service from 121.162.60.159
Jan  7 23:04:35 ns4 sshd[3484]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.162.60.159 
Jan  7 23:04:37 ns4 sshd[3484]: Failed password for invalid user service from 121.162.60.159 port 51692 ssh2
Jan  7 23:17:28 ns4 sshd[5545]: Invalid user rev. from 121.162.60.159
Jan  7 23:17:28 ns4 sshd[5545]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.162.60.159 
Jan  7 23:17:30 ns4 sshd[5545]: Failed password for invalid user rev. from 121.162.60.159 port 44282 ssh2
Jan  7 23:20:36 ns4 sshd[6122]: Invalid user fik from 121.162.60.159
Jan  7 23:20:36 ns4 sshd[6122]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.162.60.159 
Jan  7 23:20:38 ns4 sshd[6122]: Failed password for invalid user fik from 121.162.60.159 port 45766 ssh2


........
-----------------------------------------------
https://www.blocklist.de/
2020-01-08 08:01:04
37.19.109.246 attackbots
Jan  7 22:17:40 icecube sshd[21866]: Invalid user RPM from 37.19.109.246 port 22757
Jan  7 22:17:40 icecube sshd[21866]: Failed password for invalid user RPM from 37.19.109.246 port 22757 ssh2
2020-01-08 07:50:35
69.94.158.106 attackbotsspam
Jan  7 23:11:28 grey postfix/smtpd\[9955\]: NOQUEUE: reject: RCPT from brass.swingthelamp.com\[69.94.158.106\]: 554 5.7.1 Service unavailable\; Client host \[69.94.158.106\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[69.94.158.106\]\; from=\ to=\ proto=ESMTP helo=\Jan  7 23:11:28 grey postfix/smtpd\[9956\]: NOQUEUE: reject: RCPT from brass.swingthelamp.com\[69.94.158.106\]: 554 5.7.1 Service unavailable\; Client host \[69.94.158.106\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[69.94.158.106\]\; from=\ to=\ proto=ESMTP helo=\Jan  7 23:11:28 grey postfix/smtpd\[9959\]: NOQUEUE: reject: RCPT from brass.swingthelamp.com\[69.94.158.106\]: 554 5.7.1 Service unavailable\; Client host \[69.94.158.106\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[69.94.1
...
2020-01-08 07:58:08
51.254.204.190 attack
Unauthorized connection attempt detected from IP address 51.254.204.190 to port 2220 [J]
2020-01-08 08:11:13
128.199.199.217 attack
Unauthorized connection attempt detected from IP address 128.199.199.217 to port 2220 [J]
2020-01-08 07:40:40
195.231.5.176 attack
Unauthorized connection attempt detected from IP address 195.231.5.176 to port 81 [J]
2020-01-08 08:07:04

Recently Reported IPs

169.229.54.168 169.229.55.22 169.229.55.107 169.229.55.203
169.229.55.236 169.229.56.12 169.229.151.105 169.229.48.120
169.229.54.244 169.229.160.174 169.229.160.145 169.229.50.101
169.229.153.140 169.229.163.36 169.229.156.123 169.229.157.186
169.229.154.60 169.229.51.162 169.229.57.111 169.229.153.93